Recognition conditions

How to recognise a Decision-Basis condition.

The trigger is not “many documents”. It is a defined reliance point where the agreed records no longer state one sufficiently bounded written position for the intended use — and no existing accountable process already closes that gap.

01

Approval / authority / execution

The file establishes approval or authority, while evidence of the later act sits elsewhere or at a later date.

02

Current / superseded positions

Multiple versions remain in circulation and it is not clear which position governs the intended use.

03

Historical cut-off

A past decision must be read using what existed then, not what became known later.

04

Qualification loss

A condition, caveat or exclusion disappears as the position moves into a summary, dashboard or executive pack.

05

Carry-forward

A position is moving into the next handover, payment, closure, governance or operating reliance point and must travel with its limits intact.

06

During an expert or advisory engagement

An instructed specialist team may identify a specific unresolved record-position question during its work and need an inspectable, appropriately bounded documentary starting point.

What the trigger is not

Volume, complexity and urgency are not sufficient on their own.

Not “the repository is large”

Large record volume can exist without a decision-basis gap.

Not “the project is difficult”

Technical or commercial complexity does not automatically create a separate RGRA mandate.

Not “we need another opinion”

RGRA does not add a parallel judgement where the authorised position already exists.

Check one matter

Describe the uncertain record position; you do not need to frame the final question.

A short non-confidential problem outline is enough for an initial fit check. RGRA can propose specific documentary questions for your written approval before any substantive review.

Describe the problem