Punch lists go bad when there are two of them. The owner walks the job and sends a spreadsheet. The superintendent keeps a note on a phone. The architect logs items in a platform. A trade is working off last Tuesday’s email. Nobody can say what is still open, who owns it, or whether a photo actually proves the item was closed.
Procore’s punch-list tools are built to facilitate one official list: an item, a location, an assignee, a due date, often a photo, and a place to mark the work complete. That is the right process. You can run the same one with a spreadsheet and a photo folder in Google Drive or Dropbox, as long as everyone agrees that this list, not a second email chain, is the list.
What follows is a map of the process, and of a simpler setup that reaches the same goal.
What the process has to accomplish
A useful punch system, in any tool, has to make these things obvious:
- One official list, not two
- Each item has a location, a clear description, a named owner, and a date identified
- A photo of the deficiency when the item is written, and a photo of the correction when it is closed, both findable later
- A status you can filter: open, disputed, ready for re-inspection, or closed
- A record of who walked, when, and which list they walked against
Free: the Built On Record Job File Kit — logs, checklists, and a folder tree
Unsubscribe any time. Privacy
In a typical Procore project, punch items can carry an assignee, a due date, and photos, and they can be marked complete in the official project. How lists are split by area, trade, or inspection pass varies.
The simpler equivalent
Keep one punch spreadsheet in the closeout or punch folder, and a photo folder beside it, named by date and area. Each row needs:
- Item number
- Date identified, and who identified it
- Location (room, grid, elevation; specific enough that a trade can find it)
- Description of the deficiency
- Trade or person responsible
- Due date or target walk date
- Status
- Link or path to the “before” photo and the “closed” photo
- Date closed, and who accepted it if you have that
Standing rules:
- There is one official list. If a walk produces new items, they are added to that list the same day, not left in a camera roll.
- “Done” without a closed photo and a date is still open.
- If an item is disputed, say so in the status and add a short note. Never drop it quietly.
- Before a re-inspection or an owner walk, filter to open items in that area and confirm the photos are in the folder, not only on a phone.
When this is enough
A simple list will carry you through punch if it is the only list, and if photos are filed when each item is written and when it is closed. It will not hold if “the punch list” means three spreadsheets and a group text. Closeout prep can include organizing that list and the photos that go with it. The files stay yours.
If you want help, not just a checklist
Some jobs run fine on a clean file and a superintendent who gives the log fifteen minutes twice a week. Others do not: revisions are moving fast, closeout is already behind, or the field simply has no hours left for paperwork.
That is where I come in. I set up the job file, run the logs on a retainer, or prepare closeout before the scramble starts. Your files stay yours, and there is no software contract to sign.
A job-file kit you can use this week
Free logs and checklists for RFIs, submittals, dailies, changes, transmittals, pay apps, warranties, and closeout, plus a folder tree to keep them in. Sent by email, with an occasional practical note after that.
Free. Unsubscribe any time. Privacy