Evidence and decisions

Retain delivery files and independent decisions against the exact work package revision. The team uses evidence type, visibility, source revision, decision, reason, and reviewer to keep that context together. Use a pilot package to check the record links and each role’s handoff.

• Evidence. Contributor attaches a titled file to the package with an evidence type, uploader, date, and visibility setting.
• Decision. Independent Reviewer records a decision, reason, source revision, and reviewer against the same package.
• Handoff. Project Coordinator checks returned work and asks for review against the current revision before acceptance.

An attachment’s Internal or Shared setting is an access decision, not proof that the file supports delivery. The reviewer reads the task completion and attachment in context. A prior decision remains useful history even when a changed package needs a fresh one.

Agree which evidence types support each delivery step and who may mark an attachment Shared. Define how the reviewer checks completed tasks and related files. Require the reviewer to be independent of package ownership, and keep the decision reason specific enough for the coordinator to act on a Return or Reject. A decision on an older source revision does not authorize acceptance of the current package.

Independent Reviewer records the decision and reason against the inspected source revision. Project Coordinator addresses a returned decision before requesting another review.

Consider a delivery candidate with completed tasks but a missing build file. Contributor uploads the file to the correct package and sets its visibility under the studio’s rule. Independent Reviewer checks the source revision, task completion, and attached file, then records Return with a reason if the evidence remains incomplete. Project Coordinator corrects the handoff and requests another decision against the current revision.

Repeat after the package revision changes. The earlier decision stays in the register, but the new revision must have its own independent review. Check that the reviewer cannot approve a package they own and that a file linked to another package is not accepted as this delivery’s evidence.

• Review Decision Register — Read decisions, source revisions, reviewers, and reasons.
• Work Package Review Queue — Find packages in review and inspect their current evidence.

Follow planning, execution, and delivery review for the handoffs that connect these records. The data model shows the exact references to migrate and verify. Set up a pilot through implementation before broadening the team.