Review and evidence

A review records the fixture, reviewer, source revision, decision time, reason and operation key. Attachments provide supporting files with an evidence type and visibility scope. Operation receipts record guarded action attempts with their expected revision and outcome. Together, these records help the team explain why a fixture or entry moved forward, and what happened when an operation needed further investigation.

Independent Reviewer reads the current fixture context and makes an independent decision. Fixture Coordinator sees that decision alongside the event and its attachments. Finance Reviewer checks receipts that failed or need review, comparing local effects with the referenced provider event where one exists. A receipt marked pending is an unresolved result, not a signal to repeat an external action.

• Source. Confirm the review refers to the fixture and revision the reviewer actually examined.
• Visibility. Choose internal or shared attachment scope deliberately when evidence is uploaded.
• Outcome. Use the receipt state and failure reason to route exceptions to a responsible person.

Agree which documents are shared, who may upload them and how a reviewer identifies the current source revision. Define who investigates a receipt with an external reference and where a verified result is obtained. Keep the original action key when a request has an uncertain outcome so investigation does not create a second effect.

Consider a fixture whose approval was requested just before its capacity changed. The reviewer opens the fixture, checks its current revision and records the decision against that revision. The coordinator compares the review with the fixture before opening it. Later, a reservation action leaves a receipt that needs review. Finance Reviewer checks the linked admission line and any provider reference, writes the concrete discrepancy and resolves the receipt only when the expected effect is confirmed. The earlier attachment and review remain available to explain the sequence.

A returned review is also useful evidence: it tells the coordinator what needs correction before another decision. Keep the reason visible beside the source revision and supporting file. A later approval should refer to the revised scope that was actually examined. The same discipline applies to a receipt moved from pending to review: describe the missing or conflicting effect so another person can reproduce the investigation.

• Review decisions — Read the decision, reason and source revision for a selected fixture.
• Operation exceptions — Investigate failed and unresolved actions by key and expected revision.

See the operating process for the decision and evidence sequence.