Fictional composite — not client work

When “Ready” no longer resolved into one clear current written basis.

A dashboard carried a clean readiness statement. The approvals, conditions, test evidence, changed date and approved minutes supported a narrower position.

Cover of the RGRA Illustrative Worked Example PDF

The situation

A fictional infrastructure programme dashboard reported “Ready for Operational Handover”. The same matter contained conditional acceptance, an approved change to the target date, a failed readiness test and minutes deferring formal acceptance. An AI-assisted summary repeated the dashboard wording without carrying forward the conditions.

The review question: At the reporting cut-off, what did the reviewed record support without asking readers to reconstruct the matter through meetings, memory or explanation?

Six records. Six different roles.

Existence was not the test. The test was what each record was authorised to establish at the operative cut-off.

Approved handover plan

Defined the mandatory readiness conditions.

Conditional acceptance

Allowed interim mobilisation while unresolved items remained.

Dashboard status

Reported “Ready” but did not create acceptance authority.

Approved change memo

Moved the operative target beyond the reporting cut-off.

Test result and minutes

Confirmed an unmet condition and deferred formal acceptance.

AI-assisted summary

Repeated the headline without the source qualifications.

What the output did

  • Separated authority-bearing, conditional, reporting and derivative records.
  • Fixed the operative time and documentary boundary.
  • Made the narrower position readable without oral reconstruction.
  • Recorded what remained open and what had to stay attached.

What it did not do

  • Provide legal, audit, safety or contractual-completion opinion.
  • Determine claims, entitlement, liability or third-party rights.
  • Treat later evidence as silently changing the released position.
  • Represent a real client engagement or outcome.