One long list for everybody
The architect’s list arrives as a single document with two hundred lines. Each subcontractor has to find its own items in it, and an item without a name next to it is nobody’s.
Closeout
Construction punch list process: from the walk to the closed item, trade by trade
At the end of a job, the items found on the walk have to reach the right trade, be fixed, be rechecked and be closed, and the team has to see what is still open. This page follows that loop in Fidrel and is exact about the parts it does not cover, such as plan pins and signatures.
30 days free · No long-term contract.
Why punch lists stall at the end of a job
Items fixed but not rechecked
The trade says an item is done. Nobody walks back, so the owner finds the same scuff on final inspection and the contractor is reminded of a week it thought it had closed.
No view of what is still open
With the list in a spreadsheet and the status in text messages, the superintendent cannot say on Thursday how many items are open or which trade is behind.
Who writes the list depends on the contract
Many projects run a pre-punch, where each subcontractor walks its own work and fixes what it finds, followed by a walk with the owner and the architect. Who writes the official list, who accepts a fix and what a missed item costs are decided by the contract, not by the tool. Fidrel gives the team one place to keep the items once they exist: a record with an owner, a due date and a status that the whole project can follow.
Reviews, RFIs & issues
Grouping the list by trade
Every item can carry a company and a discipline. Type the company, such as the electrical subcontractor, into Search issues and the list shows its items; the search also looks in the title, the description, the category and the discipline. Items can point to a document in the project, to an RFI or to a view in a 3D model, so the context of a deficiency is one click away. Because the owner of each item is a project member, the Mine view gives every person their own list.
The punch list loop in Fidrel
Step 1
Raise an item for each deficiency found on the walk
Use New issue and fill in the title, a description, a category, the discipline, the company, a priority, a location typed as text such as a level and a gridline, a due date and an owner. One deficiency is one item.
Step 2
Hand each item to its trade
The Company field names the subcontractor and Discipline names the trade, and typing either into Search issues lists that trade’s items. The owner is told in Fidrel when an item is assigned to them.
Step 3
Follow the list in the Mine, Open and Overdue views
Start marks the work as begun and Resolve marks the item as fixed. The Open view lists what is not yet resolved, and Overdue lists the items past their due date, so the superintendent sees which trade is behind.
Step 4
Recheck and close the list in closeout
Walk the resolved items and keep the record in the project’s Punch list back-check folder. In Closeout, the Punch list line moves from Missing to Submitted to Approved, with who approved it and when.
The recheck and the closeout list
The project structure has an Inspections and closeout area with folders for the Pre-final inspection, the Substantial completion inspection and the Punch list back-check, which is where the records of each walk can be kept. The Closeout page in facility management has a Punch list line with a responsible party, a due date and a status. Approving it stamps who approved the line and when, so the end of the list has a date on it.
What the punch list process in Fidrel does not include
An item is not pinned to a spot on a plan sheet: its location is text, such as a level and a gridline, and it is created in the browser with a connection. Resolve is the last button on an item, so an item that fails the recheck is raised again as a new issue instead of being reopened. Fidrel has no back-charge calculation and no sign-off by signature; a closeout line records who approved it and when.
Related solutions
One project. One subscription. The entire platform included.
Your trial applies to your first own project and starts when that project is created. No card required. Afterwards, choose card or invoice to continue.
- 30 days free
- Unlimited participants
- No minimum term
Insights
View all
Project coordination just got simpler
The project system of the future connects people, documents and decisions. Discover the thinking behind Fidrel.
Read more
Your drawing, on site. Open DWG on your phone.
On site, answers need to be close at hand. Fidrel displays DWG drawings in your mobile browser, within the project’s document structure.
Read more
A clearer schedule. From the first activity to the final milestone.
When everyone can see the next step, moving the project forward becomes easier. Fidrel brings activities, dates and reported progress together in a shared Gantt view.
Read more
Fill in the Company and Discipline of each item and name an owner. Typing a company into Search issues lists its items, and the owner is told in Fidrel when an item is assigned.
Yes. The Overdue view lists every item that is not resolved and has passed its due date, and the Mine view shows the items assigned to you.
Keep the record of the walk in the Punch list back-check folder of the project, and check the Punch list line in Closeout. The line moves through Missing, Submitted and Approved.
No. An item has a location written as text, such as a level and a gridline. It can point to a document, an RFI or a view in a 3D model, but it is not placed on a sheet.
Resolve is the last button on an item, so an item that fails the recheck is raised again as a new issue. The earlier item stays in the history as it was.
Yes. Issues open in the phone’s browser and you can read and handle them there, with no app to install. Creating an item needs a connection.