Evidence and review

Delivery evidence belongs to a work package, with a title, file, evidence type, upload date, visibility and uploader. Review decisions also belong to a package. Each decision records the source revision, reviewer, decision, date, reason and operation key. Together these records answer what was reviewed and who reached the conclusion.

Evidence can be Internal or Shared. Set visibility with the intended audience in mind before uploading site photos or contractor documents. A later change to package scope should not replace the files or decision tied to an earlier accepted revision. The reviewer needs the task completion and supporting attachments for the exact revision under consideration.

• Collect. Package Owner attaches the job record to the package as work is completed.
• Examine. Independent Reviewer checks the revision, task progress and evidence before recording Approve, Reject or Return with a reason.
• Decide. Public Works Manager moves complete reviewed work into accepted scope and sends unresolved issues back to the owner.

A returned review is a request for a change, with the original reason retained. An approved review should identify the reviewed revision so a subsequent correction cannot silently borrow that approval. The manager can inspect the decision history before accepting a package.

Agree which evidence types are required for common public work and who may see Shared attachments. Define an independent reviewer for each category of work. Set the rule that the reviewer cannot approve the package they prepared. Decide how a return reason reaches the owner and how a revised package receives a new decision. Keep an operation key stable when retrying a guarded action.

Rehearse a package whose task hours are entered but whose field file has not arrived. The reviewer should return it with a concrete reason rather than approve an incomplete record. Then attach the missing evidence and review the new revision.

A crew completes a drainage repair. The owner attaches a dated field file and marks the related tasks complete. The reviewer opens the package, checks the task lines and attachment visibility, and records a decision with the package revision. Ask the manager to find that decision from the review history before accepting the package. Change the package scope afterwards and confirm that the older decision remains tied to its original revision.

• All Review Decisions — Decision, reason, reviewer and source revision for each package.
• Accepted Work Packages — Packages whose delivery has passed review.
• Open Work Packages — Work awaiting completion or acceptance.

Follow review delivery and scope correction.