Review and evidence

A review decision records a subject, a reviewer, a decision, its date and notes. It can relate to a project. Attachments keep a file name, kind, URL and parent record reference, allowing the team to preserve material used during review. Operation receipts record whether specific delivery actions succeeded, failed or remain pending. Together these records make the handoff between execution and review easier to inspect.

• Decision. Approved, Rejected and Returned are recorded against a project, work package, task, milestone or deliverable subject.
• Evidence. An attachment identifies its parent record and kind, such as Requirement, Design, Evidence or Report.
• Receipt. An operation result records its type, reference, occurrence time, result, notes and actor.

Decide which delivery subjects require a Reviewer decision and what that person must inspect. Use the subject reference consistently so a later reader can find the record. A decision should include the date and notes that explain why the work was Approved, Rejected or Returned. If the reviewer asks for changes, the Project Manager should identify the task or package that needs updating before another review.

Set an attachment naming convention and decide which record should hold each file. The parent table name and parent record ID provide the connection, so a wrong ID can make evidence hard to find. Check who may upload, and confirm that the file URL is accessible to the people who need it. Operation receipts serve a different purpose: they show an attempted action and its result. A Failed receipt does not indicate that the requested status transition happened.

A delivery team finishes a release checkpoint. Attach a report to the milestone or project, then ask the Reviewer to inspect the underlying tasks and the dated checkpoint. The Reviewer records a decision for that subject with a reference, date and note. If Returned, the Project Manager creates or updates the necessary task and brings the subject back for another decision. If Approved, the record states who made that decision and when.

Now inspect an issue triage and a submitted time entry. Each configured workflow writes an operation receipt; the time approval also writes a review decision. Compare the receipt result with the source record’s status. For an invalid time entry, the receipt should show Failed and the entry should remain unapproved. For a valid one, the approved status, decision and successful receipt should align. This rehearsal lets the team distinguish evidence of an attempted action from evidence of a completed one.

• Review Decisions by Project — Reviewers trace delivery outcomes to subjects and projects.
• Time Entries Awaiting Approval — Managers find entries that still need a valid workflow result.

Use delivery review for decision handling and time approval for workflow receipts.