Review and evidence

Review decisions records the subject type and reference, reviewer, decision and date. Record attachments stores a parent table name, record ID, file name, kind and link. Operation receipts records the operation type, result, actor and time. Together these records let the lead distinguish a decision, a supporting file and the result of an operation.

• Owner. Delivery Lead records a decision with the subject type, reference, reviewer and date. QA Engineer can file an attachment using its parent table and record ID. Time Approver inspects the separate decisions and receipts created by automatic time approval.
• Record. A review decision uses a subject reference rather than a direct link to every subject. Check the subject type and reference against the source record, and use the related project when one is set. An attachment needs the correct parent table choice and record ID; a file name alone cannot identify the reviewed case.
• Decision. Match the decision subject and attachment parent before the delivery lead reports an approved or returned result.

Agree how people name subject references, which files count as evidence, and who reviews a Returned or Rejected decision. Attachments use a table name and record ID, so the team must verify the intended parent record when filing a document. A decision record is valuable only when its subject and reviewer are clear.

Rehearse with one review decision, its subject record and a supporting attachment. Ask a second reviewer to find the same subject from its reference and parent record ID. Keep the original decision when a later review returns the work.

The QA Engineer records a review decision for a delivery subject and attaches a screenshot to the related record. The delivery lead checks the decision date and subject reference before reporting the package state. A time approval creates its own review decision and operation receipt through the workflow; those records can be traced to the submitted entry.

For the screenshot, choose the correct parent table and record ID, then compare them with the decision’s subject reference. A returned decision stays in the history while the QA Engineer adds new evidence for another review.

For a returned decision, keep the original subject reference and notes available. The next reviewer should see what was requested and which evidence was added before recording a new decision.

• Review decisions by outcome — Compare approved, rejected and returned decisions by subject and reviewer.
• Timesheets Awaiting Approval — Inspect submitted entries and the decisions and receipts created as they are processed.

See plan and delivery, issue triage and release window review for the steps around this work.