Koester Expectations: Pre-punch and Completion Lists

Objective 

Clarify expectations regarding how, when and why pre-punch completion lists should be created. 

Background 

The end of a job is hectic. Lots of scopes are coming to completion and staying on top of smaller details can be difficult. A “punch list” is not the tool we want to use when tasks are still needing to be completed. Using the term “punch list” implies that an owner or architect has walked the project and any work on the list is the final work needed to complete the scope in a given area. A true punch list should be a one time use tool for a given area. After that too much confusion arises when the term punch list is used and subs will often fight back stating they have already completed the punch list, when in fact they only completed the work initially. When work needs to be completed prior to an actual punch list creation, the tool we want to use in Procore is Observations. 

Things to Consider 

Observations in Procore can be used in several ways, from creation of completion lists as described here, to QC and safety observations. It is also used differently to the punch list tool in Procore. You’ll need to have completed Procore certifications in these tools prior to using them for these tasks. 

Prerequisites 

Procore- Creating Observations 

Steps 

1. Spend some time during your weekly jobsite meeting to go over observations in Procore prior to the final stages of the job. Not all subs or their employees are familiar with Procore so a few minutes on what they are, why they get them, and what to do about it will go a long way. This is not intended to be full Procore training for sub’s employees, but a basic guide to help them help you. Be clear in your expectations and follow through. 

2. Determine if a task should be on a completion list or if it is a punch list item. 

• If an issue or area is ready to be seen and possibly considered complete finished product by an owner or architect, then issues become a punch list item. 

• If a task or issue is in no way able to be viewed as possibly complete or final product, that task should fall under an observation. Do not make a punch list item. 

3. Keep observations limited to one contractor in one area. Having multiple subs in multiple areas defeats the purpose of the observation by making it too vague and spread out. If the details of a particular task involve multiple subs, only then should they be assigned the same observation. In many cases it is still better to create individual observations for each contractor as it is easier to gauge completion for each sub and their individual task on an observation as opposed to only having half of an observation complete and having to still verify the second contractor. 

4. Use locations in Procore. Locations will be determined and created during job startup. 

5. Take good photos. A bad photo only creates confusion. Make sure the issue is clear in any pictures. 

6. Follow through on observations. Confirm the contractor has the observation and understands the task. Making and assigning observations does no good if they are not followed up on. If the Observation is complete, close it out in Procore, otherwise you lose track of what is done and not. 

See Also 

Koester Expectations: Punch Lists