Punch items

A punch item describes a deficiency found during an inspection round. It records when the issue was reported, the work package, the responsible team member, hours, rate, billable intent and status. The item belongs to a scoped package, which in turn belongs to a project. That chain gives the site team a clear answer when someone asks where the work occurred and who owns the correction.

Site photos and other files are kept as record attachments. The attachment records its file name, URL, kind, uploader and the parent record it belongs to. A site photo can therefore be reviewed with the item during sign-off, while contracts and scope documents remain linked to the relevant records.

• Finding. The superintendent records the description and reported date before assigning the correcting trade member.
• Correction. The foreman checks hours, billable intent and package association as the trade work is completed.
• Review. Submitted items enter the sign-off flow; approved items remain visible until invoicing is handled.

Choose a naming convention for the punch item code and an expected level of detail for the description. A useful description should identify the defect and location in language the assigned crew member understands. Agree when a site photo is needed and who uploads it. Confirm that the work package is selected before anyone submits an item: the sign-off workflow checks that association, billable intent and hours.

Suppose an inspector finds a damaged door trim in a lobby package. The superintendent records the defect and assigns a foreman. The foreman adds the labor hours and a site photo after correction. The item is then submitted for review. The photo gives the reviewer context, while the package gives the billing team a place to trace the approved value.

Open a newly reported item and read the description as if you had not visited the site. Can the foreman identify the correction and the package? Open the attachment and check that it points to the intended record. Then submit the item with billable intent and positive hours. After submission, review the resulting decision and operation receipt before treating it as approved work.

Run a second case with no hours. The item should stay Submitted and have a Failed operation receipt. The team can repair the hours or package association and submit again under its review policy. A failed attempt should remain understandable to the project manager; it is evidence of a guard, not a completed sign-off.

• Approved Not Invoiced — Signed-off punch items that still need billing follow-through.
• Rejected Punch Items — Items requiring a correction or a separate review decision.

Follow site issue to sign-off and evidence review for a complete rehearsal.