Sign-off

A submitted punch item enters the sign-off approval workflow. It checks billable intent, hours and the work package. For an approvable item, the workflow moves the item to Approved and records a review decision and an operation receipt. The decision identifies the subject, reviewer, outcome and date. The receipt identifies the operation, reference, result and time.

This gives the project team a way to distinguish a signed-off correction from an attempted sign-off that failed a guard. A failed attempt leaves the punch item Submitted and writes a Failed receipt. The reviewer can inspect the source item, repair the missing detail through the responsible owner and run the review again.

• Submitted queue. The superintendent prepares the item and checks the site evidence before review.
• Site review. The inspector checks the correction and evidence before the item is submitted.
• Recorded outcome. The item status, review decision and operation receipt should tell the same story.

Name the inspector or other authorized reviewer for each site. Agree which site evidence is required and what billable work means for the contract. Decide who corrects an item when the hours or package link is wrong. The guard is specific: a nonbillable item, an item with no hours, or an item with no work package does not advance to Approved. Teams should test those cases before treating the saved approved list as a billing instruction.

For a lobby trim defect, the foreman supplies hours, marks the item billable and links it to the finish package. The inspector checks the work and site photo. Approval moves the item to Approved and produces a decision row and successful operation receipt. The project manager can later find it in the approved, not invoiced list.

Open the submitted item and verify that its package, hours and billable flag are correct. Have the inspector check the site correction before submission. Submit the item, then check its new status, the review decision and the operation receipt together. The record should make it clear which item was reviewed, who reviewed it and when.

Repeat with a missing package. The item should remain Submitted and a Failed receipt should explain the blocked operation. It should not appear in the approved, not invoiced list. Correct the package, repeat the review and keep both attempts visible. This is especially important when a site team works quickly through many small corrections.

• Rejected Punch Items — Items that need correction or renewed review.
• Approved Not Invoiced — Signed-off items that need the billing team to act.

Use site issue to sign-off and evidence review to test both success and failure.