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
- Data model and import order
The tables behind Construction Punch List
Construction Punch List ships with 13 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 13
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Site and scope:
Organizations, Projects and work packages identify the business unit, project owner, package manager, dates and contract context.
Trade delivery:
Team members, punch items, labor entries and job expenses keep assigned people, defects, hours and costs connected to the package.
Closeout billing:
Tasks and payment records carry task sign-off, invoice reference, due date and collection status.
Review evidence:
Record attachments, review decisions and operation receipts retain files, human decisions and execution results.
Access:
Users holds application identity and its available user status and role values.
Every table, by feature
- Projects
Construction projects and sites the punch list covers, with the owning organization, code and contact.
Linked to Team members, Organizations - Organizations
Firm business units, practice groups and regional offices.
- Team members
Consultants and delivery staff with rates and capacity.
Linked to Organizations - Work packages
Scoped packages of work on a project that punch items and closeout tasks are raised against.
Linked to Projects, Team members, Organizations
- Work packages
Scoped packages of work on a project that punch items and closeout tasks are raised against.
Linked to Projects, Team members, Organizations - Projects
Construction projects and sites the punch list covers, with the owning organization, code and contact.
Linked to Team members, Organizations - Organizations
Firm business units, practice groups and regional offices.
- Punch items
Deficiencies raised on site during an inspection round, corrected by the responsible trade and closed on sign-off.
Linked to Work packages, Team members - Labor entries
Hours logged by a trade crew member on a project and work package.
Linked to Team members, Projects, Work packages - Job expenses
Job costs charged to a work package, with category, amount and approval status.
Linked to Work packages, Team members - Tasks
Scheduled closeout tasks under a work package that carry a due date, owner and sign-off status.
Linked to Work packages, Team members
- Punch items
Deficiencies raised on site during an inspection round, corrected by the responsible trade and closed on sign-off.
Linked to Work packages, Team members - Work packages
Scoped packages of work on a project that punch items and closeout tasks are raised against.
Linked to Projects, Team members, Organizations - Team members
Consultants and delivery staff with rates and capacity.
Linked to Organizations - Record attachments
Files linked to records across the app.
Linked to Team members - Review decisions
Approval decisions recorded against service, time and expense subjects.
Linked to Team members - Operation receipts
Evidence of executed billing, approval and document operations.
Linked to Team members
- Team members
Consultants and delivery staff with rates and capacity.
Linked to Organizations - Labor entries
Hours logged by a trade crew member on a project and work package.
Linked to Team members, Projects, Work packages - Job expenses
Job costs charged to a work package, with category, amount and approval status.
Linked to Work packages, Team members - Work packages
Scoped packages of work on a project that punch items and closeout tasks are raised against.
Linked to Projects, Team members, Organizations - Projects
Construction projects and sites the punch list covers, with the owning organization, code and contact.
Linked to Team members, Organizations - Organizations
Firm business units, practice groups and regional offices.
- Punch items
Deficiencies raised on site during an inspection round, corrected by the responsible trade and closed on sign-off.
Linked to Work packages, Team members - Review decisions
Approval decisions recorded against service, time and expense subjects.
Linked to Team members - Operation receipts
Evidence of executed billing, approval and document operations.
Linked to Team members - Record attachments
Files linked to records across the app.
Linked to Team members - Work packages
Scoped packages of work on a project that punch items and closeout tasks are raised against.
Linked to Projects, Team members, Organizations - Team members
Consultants and delivery staff with rates and capacity.
Linked to Organizations
- Tasks
Scheduled closeout tasks under a work package that carry a due date, owner and sign-off status.
Linked to Work packages, Team members - Work packages
Scoped packages of work on a project that punch items and closeout tasks are raised against.
Linked to Projects, Team members, Organizations - Payment records
Payments raised against a closed-out task, with invoice reference, due date and settlement status.
Linked to Tasks - Operation receipts
Evidence of executed billing, approval and document operations.
Linked to Team members - Team members
Consultants and delivery staff with rates and capacity.
Linked to Organizations
Keys and references
Keep project and package identifiers stable during import. A punch item points to a work package and team member. A closeout task points to a package and owner; its payment records point back to the task. Labor entries should reference both the project and the package. Match those references before relying on package delivery totals.
Attachments use a parent table name and parent record ID. Verify both values against the intended record, especially when several findings share a similar description. Review decisions and operation receipts use subject or operation references; reconcile them to the item or task that triggered the action. Preserve original receipt and file UR ls during migration.
Migration order
- Load Organizations, Users and team members with stable identifiers and active status.
- Load Projects and work packages, reconciling owners, managers, organizations and dates.
- Load punch items, labor entries, job expenses and Tasks against the correct package.
- Load record attachments, review decisions, operation receipts and payment records with their source references.
- Reconcile package delivery totals, sample attachment links and rehearse sign-off, task invoice and payment receipt cases.
Set up Construction Punch List your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.