Review and evidence

Review decisions record who decided, which package revision they considered, when they decided and why. A decision can approve, reject or return the work. It belongs to a work package, identifies a Project Reviewer through a team member and carries an operation key. Existing entries help the team compare a certificate outcome with the scope that was reviewed. A changed source revision calls for a fresh review.

Record attachments support that conversation. Each attachment has a title, evidence type, upload date, visibility and uploader, and belongs to a work package. The Project Coordinator can gather site evidence for review. Internal and shared visibility values help the team mark the intended audience for an attachment. The Auditor can read authorized evidence when reviewing the project’s history.

• Decision. review decisions ties reviewer, revision, decision, reason and operation key to the package.
• Attachment. record attachments keeps a file and its descriptive details under the same package.
• Receipt. operation receipts records an action, expected revision, result state and any failure reason for a guarded operation.

Agree what evidence types the team uses and when an attachment should be shared rather than internal. Set a standard for decision reasons that explains the real issue without relying on private conversations. The reviewer should identify the package revision before deciding. The coordinator and reviewer should also agree who handles receipts marked failed or needing review and how that exception is closed after inspection.

A receipt can be pending, completed, failed or marked for review. Its operation key gives retries a stable identity. When a reviewer finds a certificate decision that seems inconsistent with the persisted effect, the receipt provides an additional record to examine. It is useful because it connects a guarded action to the package and expected revision; it is one part of the record trail the reviewer examines.

A coordinator uploads an inspection file to a package and marks its visibility shared. The certificate is submitted against the current package revision. A Project Reviewer opens the evidence, checks task completion and gives the coordinator a reasoned decision. The coordinator updates the certificate. If an operation receipt exists and needs review, the reviewer compares its expected revision and effect reference with the certificate and any decision record. The team can then identify whether the issue is in the evidence, decision or persisted action.

A second upload may clarify an earlier concern. Keep both attachments under the package with their upload dates. If the package revision changes, the earlier decision still describes its original source revision. The current version needs its own review before the coordinator records its outcome.

• Review Decisions — Named decisions with source revision, reviewer and reason.
• Operation Exceptions — Failed or review-needed receipts that need reconciliation.
• Shared Evidence — Attachments marked for sharing under their packages.

Read certificate review and evidence reconciliation.