Evidence and review

An evidence attachment belongs to a work package and identifies its uploader. It has a title, upload date, evidence type and visibility marked Internal or Shared. The file itself can be attached to the record. The visibility choice matters when the team prepares material for a project contact or another party: a shared item is deliberate, while internal working material should remain in its own scope.

A review decision also belongs to a package. It records the source revision, the reviewer, time, reason, operation key and decision of Approve, Reject or Return. These fields explain what was decided and which version of the work was considered. The reviewer must be independent of the owner for the guarded review path. A later revision calls for a new assessment rather than treating an older approval as covering changed work.

• Attachments. Package Owner adds evidence to the parent package and sets its visibility for the intended audience.
• Review request. Research Coordinator checks task progress and identifies the package revision before asking for a decision.
• Decision. Independent Reviewer examines supporting work and records the outcome and reason against that revision.

Agree which evidence types the team uses and when a file can be marked Shared. Choose a naming convention that lets a reviewer recognize a file without opening every attachment. Decide who can correct a mistaken visibility choice and how the change is communicated to people who may already have used the file. Keep the package reference and uploader intact when replacing a document.

Write down the independence rule for reviewers. The person who owned or prepared the work should not be the only person deciding whether that same revision is accepted. The coordinator should also know what to do with Return: the package owner revises or adds evidence, and the reviewer gets the revised case with its own source revision.

A package owner uploads study evidence and marks the version intended for review Shared. A private working note remains Internal. Research Coordinator checks the task completion dates and puts the package into review. Independent Reviewer opens the package, confirms that the evidence points to this package and checks the current revision. The reviewer returns the case with a reason because one supporting file refers to an earlier study result.

The owner replaces the supporting material and the package revision changes. A fresh decision should point to that revision. The earlier Return remains part of the history, explaining why the package did not proceed on the first pass. When Operations Analyst later investigates the delay, the decision record and attachment dates provide a concrete trail.

• Evidence Attachments — Files marked Shared with their parent package, type and uploader.
• Review Decision Register — Decision outcomes and reasons by package revision and reviewer.
• Packages Awaiting Review — Packages ready for an independent evidence check.

See evidence review and roles before the first decision.