A punch list — a snag list, in much of the world — is the record of everything that is incomplete, wrong, or damaged when a project reaches substantial completion. The building is nearly done, the owner walks it with the design team, and every scuffed door, missing gasket, and out-of-plumb frame gets written down. Then the real work of closeout begins: assigning each item to the trade that owns it, correcting it, re-inspecting it, and signing it off. This template models that full cycle — from the Substantial completion walk to Project closeout — as a living graph that assigns deficiencies to trades and tracks them to closed.
It is built for the people who drive closeout: the architect, owner, or construction manager who leads the walkthrough and logs items, and the general contractor and superintendents who assign them to the trades and push them to done. Anyone who has watched a project sit at ninety-eight percent complete for two months because a handful of punch items never got re-inspected knows the pain this process is meant to prevent.
The flow has seven steps and one loop. The main path carries a deficiency from discovery through correction to sign-off; a single branch sends an item that fails re-inspection back to be reassigned. That loop is what keeps the list honest — an item is not closed because a trade says it is done, but because it was checked and verified.
How this punch list workflow template works
Substantial completion walk. The process starts with the walkthrough. The owner, architect, or construction manager tours the completed work and identifies everything that is deficient, incomplete, or damaged. This is the moment the list is born, and a thorough walk is what makes the rest of closeout predictable.
Log deficiencies. Each item found is written down with its location, a clear description of the problem, and ideally a photo. Precision matters here — "door hardware" is not actionable, but "Room 214, closer leaking, replace" is. A well-logged item is one a trade can fix without a second site visit to figure out what was meant.
Assign to trades. Every logged item is assigned to the responsible trade — the painter, the glazer, the mechanical contractor. This is the accountability step: each deficiency now has an owner who is on the hook to correct it. It is also the target of the reassign loop later in the flow.
Trade corrects. The assigned trade returns to the work and fixes the item — repaints the wall, replaces the cracked pane, adjusts the door. The correction is where the physical work happens, but on its own it does not close anything.
Re-inspect. Someone from the owner's or contractor's side goes back and checks the correction against the original deficiency. This step is the guard against a trade marking its own homework. The flow branches from here.
The reassign branch. If the re-inspection shows the item is still open — the fix was incomplete, wrong, or created a new problem — the edge labeled still open — reassign loops from Re-inspect back to Assign to trades. The item goes back into the queue with fresh direction. Tracking how many times an item loops is a direct signal of a trade that is not taking the punch list seriously.
Verify & sign off. An item that passes re-inspection is verified and signed off. This is the only way an item legitimately closes — inspected and confirmed, not merely reported done. Sign-off is the documented moment the deficiency ceases to exist.
Project closeout. Once the punch list is fully signed off, the project moves to closeout — final payment, warranties, as-builts, and the handover of the finished building. A clean, verified punch list is the gate that stands between substantial completion and final completion.
How to use it in FlowGraph
- Open the template. Click Open in FlowGraph to load the punch list workflow as a live graph. Viewing and editing are free with no account, so you can adapt the flow to your project before saving anything.
- Log each deficiency. Add a card per item with its location and the responsible trade. Duplicate the flow across every open item so the graph becomes your live punch register — dozens of small cards, each tracked to closed — rather than a single static diagram.
- Assign and track. Move each item through Trade corrects, Re-inspect, and Verify & sign off until it closes. Because every edit is governed and carries a receipt, you always know who moved an item, when, and why — and the reassign loop makes stubborn items visible instead of letting them hide.
- Pin to the model. Link a punch item to the element in your 3D model so the trade knows exactly where. Import an IFC model into FlowGraph and connect a deficiency to the specific door, window, or wall it concerns — no more hunting for "the leaking closer somewhere on the second floor."
- Extend it with AI. With your own AI key you can ask FlowGraph to group open items by trade, or to flag which deficiencies block closeout. The AI proposes; you verify and decide. Nothing changes on the list until you accept it.
Why a living graph beats a static punch list
A punch list on a clipboard or a PDF tells you what is wrong, but not where it lives in the building, who owns it right now, or how long it has been open. Because every card in FlowGraph is a real object linked by typed relationships, you can connect a deficiency to the model element it concerns, to the trade responsible, and to the closeout milestone it blocks. In construction the relationships are the work, and a flat list throws them away.
Every change flows through a single governed write path and carries a receipt: who logged this item, who reassigned it, when it was verified. That reversible, honest history is exactly what you want at closeout, when final payment and retention hinge on which items are genuinely done. The record is already there, timestamped — not reconstructed from memory and photos on a phone.
And the graph keeps up with the project. Ask AI to sort the open list by trade the night before a walk, replicate the correction-and-verify pattern across a whole floor, or wire the punch list to a live model so every item points at exactly where it belongs — all without leaving the traceable write path underneath. It stays local-first and yours: the template opens with no account, and signing up only comes in when you want to save it to a vault or plan with AI.
Frequently asked questions
What is a punch list?
A punch list, or snag list, is the record of incomplete or deficient work found during the substantial-completion walkthrough of a construction project. Each item is assigned to the responsible trade, corrected, re-inspected, and signed off before the project can be closed out.
It is the last quality gate on a job — the shared, documented agreement of exactly what remains between "nearly done" and "finished." Getting it clean and verified is what allows final payment to be released and the building to be handed over.
Who creates the punch list?
The architect, owner, or construction manager typically leads the substantial-completion walkthrough and logs the items. The general contractor then assigns each item to the trade that owns it and drives the corrections to completion.
Assigning that ownership explicitly in FlowGraph — a named party on Log deficiencies and each item pointed at its trade on Assign to trades — is what keeps a punch list from becoming a document everyone has seen and no one is closing.
When is a punch item closed?
An item is closed only after the correction has been re-inspected and verified — not when the trade reports it done. The re-inspection is the check that prevents a list from closing on trust alone.
This template models that discipline directly: the Re-inspect step branches to Verify & sign off for items that pass, and loops back to Assign to trades with a still open — reassign label for items that fail. An item earns its closure by passing inspection, and the graph records exactly when it did.