1. Construction Project Tracker
  2. Data model
Reference

The tables behind Construction Project Tracker

Construction Project Tracker ships with 10 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
10
Features
6
Change it
Add fields and tables in Proto

How the model is organised

Organization

Organizations owns Projects and team members; Users links a team member to a platform identity.

Delivery

Work packages belongs to an organization, project and owner; Tasks records the line work beneath it.

Certification

Progress certificates belongs to a package and organization and carries value, revision and status.

Evidence

Record attachments, review decisions and operation receipts connect files, decisions and operation results to the same package.

Every table, by feature

Project context

6 tablesAbout this feature
  • Organizations

    Construction delivery organizations that own projects and work packages.

  • Projects

    Client projects and sites that work packages are delivered against.

    Linked to Organizations
  • Team members

    Named staff belonging to an organization, linked to platform identities.

    Linked to Organizations, Users
  • Users

    Users

    Linked to Users
  • Work packages

    Planned delivery scope with owner, lifecycle status and due date.

    Linked to Organizations, Team members, Projects
  • Progress certificates

    Certified work progress submitted for reviewer approval.

    Linked to Work packages, Organizations

Work packages

9 tablesAbout this feature
  • Work packages

    Planned delivery scope with owner, lifecycle status and due date.

    Linked to Organizations, Team members, Projects
  • Projects

    Client projects and sites that work packages are delivered against.

    Linked to Organizations
  • Organizations

    Construction delivery organizations that own projects and work packages.

  • Team members

    Named staff belonging to an organization, linked to platform identities.

    Linked to Organizations, Users
  • Tasks

    Line items of work under a work package with planned and actual hours.

    Linked to Work packages
  • Progress certificates

    Certified work progress submitted for reviewer approval.

    Linked to Work packages, Organizations
  • Record attachments

    Evidence files attached to a work package.

    Linked to Work packages, Team members
  • Review decisions

    Independent reviewer decisions on a work package revision.

    Linked to Work packages, Team members
  • Operation receipts

    Durable receipts for guarded operations with retry-stable keys.

    Linked to Work packages

Tasks and hours

4 tablesAbout this feature
  • Tasks

    Line items of work under a work package with planned and actual hours.

    Linked to Work packages
  • Work packages

    Planned delivery scope with owner, lifecycle status and due date.

    Linked to Organizations, Team members, Projects
  • Projects

    Client projects and sites that work packages are delivered against.

    Linked to Organizations
  • Team members

    Named staff belonging to an organization, linked to platform identities.

    Linked to Organizations, Users

Progress certificates

6 tablesAbout this feature
  • Progress certificates

    Certified work progress submitted for reviewer approval.

    Linked to Work packages, Organizations
  • Work packages

    Planned delivery scope with owner, lifecycle status and due date.

    Linked to Organizations, Team members, Projects
  • Organizations

    Construction delivery organizations that own projects and work packages.

  • Tasks

    Line items of work under a work package with planned and actual hours.

    Linked to Work packages
  • Record attachments

    Evidence files attached to a work package.

    Linked to Work packages, Team members
  • Review decisions

    Independent reviewer decisions on a work package revision.

    Linked to Work packages, Team members

Review and evidence

6 tablesAbout this feature
  • Review decisions

    Independent reviewer decisions on a work package revision.

    Linked to Work packages, Team members
  • Record attachments

    Evidence files attached to a work package.

    Linked to Work packages, Team members
  • Operation receipts

    Durable receipts for guarded operations with retry-stable keys.

    Linked to Work packages
  • Work packages

    Planned delivery scope with owner, lifecycle status and due date.

    Linked to Organizations, Team members, Projects
  • Team members

    Named staff belonging to an organization, linked to platform identities.

    Linked to Organizations, Users
  • Progress certificates

    Certified work progress submitted for reviewer approval.

    Linked to Work packages, Organizations

Operations overview

7 tablesAbout this feature
  • Work packages

    Planned delivery scope with owner, lifecycle status and due date.

    Linked to Organizations, Team members, Projects
  • Tasks

    Line items of work under a work package with planned and actual hours.

    Linked to Work packages
  • Progress certificates

    Certified work progress submitted for reviewer approval.

    Linked to Work packages, Organizations
  • Review decisions

    Independent reviewer decisions on a work package revision.

    Linked to Work packages, Team members
  • Operation receipts

    Durable receipts for guarded operations with retry-stable keys.

    Linked to Work packages
  • Projects

    Client projects and sites that work packages are delivered against.

    Linked to Organizations
  • Record attachments

    Evidence files attached to a work package.

    Linked to Work packages, Team members

Keys and references

The package’s record number is the human-facing scope identifier. Task line number identifies a line beneath its parent package. Certificate number identifies a certificate when entered. Review decisions carries source revision and operation key so a decision can be compared with the relevant package revision and receipt. The project’s Code and organization Code distinguish operating contexts. Each child record should keep its parent reference intact during migration.

Migration order

  1. Create Organizations and platform Users, then team members linked to both.
  2. Create Projects under their organizations.
  3. Create work packages with organization, project and owner references.
  4. Load Tasks and record attachments under their parent packages.
  5. Load progress certificates, review decisions and operation receipts against the matching packages and revisions.
  6. Reconcile status values, dates, hours, certificate values and operation keys against source records.

Set up Construction Project Tracker your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started