1. PM with AI Scheduling
  2. Data model
Reference

The tables behind PM with AI Scheduling

PM with AI Scheduling 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 context

Organizations contain Projects and team members; Users provide platform identity.

Delivery work

Work packages belong to Organizations and Projects and have an Owner from team members. Tasks and scheduling proposals belong to a package.

Review and evidence

Review decisions, record attachments and operation receipts keep decisions, files and guarded action results with the package.

Every table, by feature

Organizations and projects

5 tablesAbout this feature
  • Organizations

    Client and delivery organizations that own projects and work packages.

  • Projects

    Client projects that work packages are delivered against.

    Linked to Organizations
  • Team members

    Named delivery staff with their organization membership and platform identity.

    Linked to Organizations, Users
  • Users

    Users

    Linked to Users
  • Work packages

    Contracted units of delivery with lifecycle, budget hours and accepted baseline.

    Linked to Organizations, Team members, Projects

Work packages

5 tablesAbout this feature
  • Work packages

    Contracted units of delivery with lifecycle, budget hours and accepted baseline.

    Linked to Organizations, Team members, Projects
  • Projects

    Client projects that work packages are delivered against.

    Linked to Organizations
  • Organizations

    Client and delivery organizations that own projects and work packages.

  • Team members

    Named delivery staff with their organization membership and platform identity.

    Linked to Organizations, Users
  • Tasks

    Scheduled task lines inside a work package with planned and actual hours.

    Linked to Work packages

Tasks and dependencies

3 tablesAbout this feature
  • Tasks

    Scheduled task lines inside a work package with planned and actual hours.

    Linked to Work packages
  • Work packages

    Contracted units of delivery with lifecycle, budget hours and accepted baseline.

    Linked to Organizations, Team members, Projects
  • Scheduling proposals

    AI-generated schedule proposals awaiting review and approval for a work package.

    Linked to Work packages, Organizations

Scheduling proposals

5 tablesAbout this feature
  • Scheduling proposals

    AI-generated schedule proposals awaiting review and approval for a work package.

    Linked to Work packages, Organizations
  • Work packages

    Contracted units of delivery with lifecycle, budget hours and accepted baseline.

    Linked to Organizations, Team members, Projects
  • Tasks

    Scheduled task lines inside a work package with planned and actual hours.

    Linked to Work packages
  • Review decisions

    Independent reviewer decisions recorded against a work package revision.

    Linked to Work packages, Team members
  • Operation receipts

    Durable receipts for every guarded operation, keyed for idempotent retries.

    Linked to Work packages

Review and evidence

5 tablesAbout this feature
  • Record attachments

    Evidence files attached to a work package with visibility scope.

    Linked to Work packages, Team members
  • Review decisions

    Independent reviewer decisions recorded against a work package revision.

    Linked to Work packages, Team members
  • Work packages

    Contracted units of delivery with lifecycle, budget hours and accepted baseline.

    Linked to Organizations, Team members, Projects
  • Tasks

    Scheduled task lines inside a work package with planned and actual hours.

    Linked to Work packages
  • Team members

    Named delivery staff with their organization membership and platform identity.

    Linked to Organizations, Users

Operations oversight

5 tablesAbout this feature
  • Operation receipts

    Durable receipts for every guarded operation, keyed for idempotent retries.

    Linked to Work packages
  • Work packages

    Contracted units of delivery with lifecycle, budget hours and accepted baseline.

    Linked to Organizations, Team members, Projects
  • Tasks

    Scheduled task lines inside a work package with planned and actual hours.

    Linked to Work packages
  • Scheduling proposals

    AI-generated schedule proposals awaiting review and approval for a work package.

    Linked to Work packages, Organizations
  • Review decisions

    Independent reviewer decisions recorded against a work package revision.

    Linked to Work packages, Team members

Keys and references

Keep organization and project codes stable when importing data. Match package record numbers to their project and owner. Preserve the parent reference on every task, proposal, attachment, decision and receipt. Proposal and decision revisions identify the version considered during review; they should not be inferred from the latest display alone.

Migration order

  1. Create Organizations and Users, then team members with their linked identities.
  2. Create Projects under their Organizations.
  3. Create work packages with project, organization and owner references.
  4. Load Tasks and scheduling proposals against package parents.
  5. Bring in record attachments, review decisions and operation receipts with source identities and revisions.

Set up PM with AI Scheduling your way.

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

How to get started