These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Construction Punch List
- Features
- Projects
Projects
Keep site identity, owning organization and project responsibility together.
OverviewActive Projects×
Construction Punch List · Projects
New
Active Projects
Projects
| Project code | Project name | Status | Project owner | Owning organization | |
|---|---|---|---|---|---|
| PC-127 | Project 472 | Active | ORG-2300 | ||
| PC-867 | Project 405 | Active | ORG-8849 | ||
| PC-727 | Project 957 | Active | ORG-7865 | ||
| PC-798 | Project 680 | Active | ORG-6468 | ||
| PC-959 | Project 805 | Active | ORG-4120 |
6 of 6 records
PC-127Projects · PRJ-30752
ActiveProject nameProject 472
Owning organizationORG-2300
What you can do
Begin with the site
The project record gives every deficiency a place to belong. A Project Manager identifies the site, the owning organization, the project contact and the person responsible for the project. Work packages then carry the actual scope. This distinction matters when one site has several trades or closeout areas: the project remains the common reference while each package has its own manager, dates and contract value.
A project can start as Prospect and become Active when work begins. The Project Manager should agree what a project code identifies before importing or creating records. A name alone is a weak matching key when several sites share a customer or location label.
How the work is organized
- Project ownership. The project owner is a named team member; the owning organization groups the work under the business unit.
- Scoped packages. Each work package belongs to a project, so the site team can keep trade scope and delivery measures separate.
- Operating status. The active project list keeps current work visible, while prospects can be reviewed before site work starts.
What to agree during setup
Decide whether one project means one physical site, one contract, or one phase at a site. Pick a convention for the project code and record the primary contact in the same way across the portfolio. Agree who can move a project from Prospect to Active and who can close it after all package and payment follow-up is complete. The project owner should be a current team member, and the owning organization should be selected before packages are created.
For a renovation with two trade packages, create one project and give each package its own subject and manager. This keeps the reported deficiencies under the right site while allowing the project manager to see the work for each trade separately. A third package can be added later without recoding the original project.
Check the handoff on an actual case
Open an active site and follow one work package to a punch item. Check that the site contact, project owner and organization are clear to the superintendent. Then open the package and confirm that the manager can tell which crew member owns the item and which task carries the closeout date. If that route is confusing, correct the project or package assignment before asking the inspector to review sign-off.
A prospect is a useful second check. It should appear in the prospect list with its intended owner, but the team should not mistake it for current site work. When it becomes Active, the relevant packages should be reviewed for dates and scope.
What your team sees
- Active Projects — Current sites with the responsible owner and organization beside the project name.
- Project Prospects — Sites being assessed before work packages are opened for delivery.
Follow the work through
Start with site issue to sign-off, then review package delivery and the data model.
What it keeps track of
Data model- Projects
- Construction projects and sites the punch list covers, with the owning organization, code and contact.
- Organizations
- Firm business units, practice groups and regional offices.
- Team members
- Consultants and delivery staff with rates and capacity.
- Work packages
- Scoped packages of work on a project that punch items and closeout tasks are raised against.
Who uses it
Permissions- Project Manager
- Owns project setup; Site Superintendent uses the site context; Owner reviews the portfolio.
Set up Construction Punch List your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.