Review and evidence

Record attachments store a title, file, upload date, evidence type, uploader and visibility. The visibility choice distinguishes Internal from Shared material. Review decisions carry the source revision, decision, date, reason and reviewer. Together, these records let a delivery lead see what was supplied for a decision and what the reviewer actually accepted, rejected or returned.

• Evidence audience. Choose Internal or Shared visibility deliberately.
• Reviewer identity. Keep the decision separate from the person who prepared the work.
• Revision. Compare the decision with the package under review.

Agree which evidence types support schedule approval and final acceptance. Decide who can upload files and who can share them. Reviewers need a consistent way to record reasons for Approve, Reject and Return. The coordinator should revisit a returned decision rather than treating it as approval.

A team member attaches delivery evidence to a package. The evidence manager checks its audience. The reviewer opens the package at the submitted revision, compares completed task lines with the files and records a reasoned decision. If one task remains incomplete, the reviewer returns the work. After the team finishes that task, the lead asks for another review of the current revision. A prior decision stays attached to its original source.

Files and decisions serve different purposes. An attachment shows what was offered for consideration, while the decision states what the reviewer concluded. Keep the upload date and uploader visible so the team can tell whether a file was present when the decision was made. Choose visibility according to the audience that should see the file. At final delivery, the reviewer compares the current task completion dates and actual hours with the package scope, then records a decision and reason. If a correction follows, preserve the earlier decision under its source revision and request a new review. The delivery lead can then explain the accepted outcome without rewriting the review trail. During rehearsal, ask the reviewer to open the earlier returned decision beside the new one and confirm that each names the revision actually considered.

• Shared package evidence — Find files intended for the shared review audience.
• Review decisions — See decisions with reviewer, reason and source revision.
• Packages due for review — Locate packages at the acceptance gate.

Follow review and evidence in the operating process. Review the data model when mapping project, package and evidence records.