Evidence and decisions

Workers attach evidence to the parent package and choose whether each file is Internal or Shared. A review decision names the package revision, reviewer, decision, date and reason. The independent Project Reviewer reads the completed task lines, dependencies and shared evidence before deciding whether the package can be accepted.

• Evidence file. Event Worker attaches a file to the parent package and sets its evidence type and visibility.
• Review decision. Project Reviewer records Approve, Reject or Return, with reason and the package revision inspected.
• Receipt trail. operation receipts preserve the result of guarded changes and later reconciliation.

Agree which evidence types are required for common deliverables and which files may be shared with participants in the review. The reviewer must be separate from the person who prepared the work. A Return decision needs a useful reason so the coordinator knows what to correct; a Reject decision should preserve the evidence already submitted.

Agree which delivery files must be Shared for review and which remain Internal. Give the reviewer access to the task lines, dependency sequence and package revision behind each file. Require a reason for a Return or Reject decision so the coordinator knows what to correct. Keep accepted scope and executed attachments when later changes are requested.

For a supplier handoff, inspect the package in Review, confirm the attached handoff file is Shared, and compare the review source revision with the package revision. Verify that task completion and actual hours match the work. Record the decision and reason. Acceptance must keep that decision linked to the revision actually reviewed.

For a supplier handoff, the Event Worker attaches a signed delivery file to the package and marks it Shared. The Project Reviewer opens Awaiting Review, checks the completed tasks and confirms the file belongs to the current package revision. If the file is Internal, the reviewer returns the work with a reason. After correction, the reviewer records a new decision against the revision actually inspected; the earlier decision remains in the log.

• Awaiting Review — See packages awaiting an independent evidence decision.
• Work Packages — Check the parent scope, owner, due date and current status before deciding.

Follow Review delivery for the related decision path. Review the data model when mapping existing records, and use implementation to rehearse the first event cycle.