Review and evidence

Record attachments stores evidence on a work package with its title, upload date, evidence type, uploader and Internal or Shared visibility. Review decisions has fields for the package source revision, decision, reviewer, date and reason. Operation receipts has fields for an action, key, expected revision, result state, timestamp and any failure reason or effect references. During setup, decide who reviews a package and which record holds that decision. Check the chosen record and permission with the coordinator before using this handoff on a live production.

• Source. Start with the production, package or person named on the record, then follow its explicit references.
• Decision. Keep the latest status and revision visible to the person responsible for the next action.
• Evidence. Open the child records before concluding that the work is ready for review or complete.

Agree which evidence types the reviewer expects before a package enters review. The coordinator should choose visibility deliberately; Shared means a different audience from Internal. Identify who reviews a package and whether review decisions will hold an Approve, Reject or Return decision for its revision. Use the source revision and operation key consistently when discussing retries or discrepancies.

A coordinator uploads a completed location confirmation and marks its visibility. The package enters review. The reviewer checks the attachment and current task completion. The team agrees how to capture its decision and reason for that revision before changing the package status. If an operation receipts row shows Failed, the team compares its expected revision and references with the package before trying again.

If the team uses review decisions, its source revision, reviewer, date and reason give an auditor a way to inspect the review. An attachment title should help identify the evidence without exposing its file to the wrong audience. When a package returns from review, the coordinator addresses the reason and presents a new revision if scope changed. An operation receipt result can guide investigation; the team still needs an agreed human review step.

• Evidence shared with partners — Inspect which package attachments are marked Shared.
• Decisions by revision — Inspect package revision, reviewer and reason fields when review records are used.

Follow production planning, shoot day review and delivery review to see how records move between people.