1. Change Request Management
  2. Data model
Reference

The tables behind Change Request Management

Change Request Management 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, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Organization and projects

Organizations own Projects and team members; Users link people to platform accounts.

Scoped change

Work packages link to the affected Projects, owning Organizations and team members.

Delivery and impact

Impact assessments and Tasks belong to work packages, with project and person references where recorded.

Review and evidence

Review decisions, record attachments and operation receipts retain decisions, files and action outcomes under the package.

Every table, by feature

Organization and projects

4 tablesAbout this feature
  • Organizations

    Organizations that own change work, with operating time zone and currency.

  • Projects

    Projects and affected systems that change requests are raised against.

    Linked to Organizations, Team members
  • Work packages

    Scoped change work packages: the governed unit of change, baseline and revision.

    Linked to Projects, Team members, Organizations
  • Team members

    People who prepare, own and review change work, linked to their organization and platform user.

    Linked to Organizations, Users

Scoped work packages

6 tablesAbout this feature
  • Work packages

    Scoped change work packages: the governed unit of change, baseline and revision.

    Linked to Projects, Team members, Organizations
  • Projects

    Projects and affected systems that change requests are raised against.

    Linked to Organizations, Team members
  • Organizations

    Organizations that own change work, with operating time zone and currency.

  • Tasks

    Planned and actual work lines under a work package.

    Linked to Work packages, Team members, Projects
  • Impact assessments

    Impact assessments supporting approval of a scoped change request.

    Linked to Projects, Team members, Work packages, Organizations
  • Review decisions

    Independent reviewer decisions recorded against a work package revision.

    Linked to Team members, Projects, Work packages

Impact assessments

6 tablesAbout this feature
  • Impact assessments

    Impact assessments supporting approval of a scoped change request.

    Linked to Projects, Team members, Work packages, Organizations
  • Work packages

    Scoped change work packages: the governed unit of change, baseline and revision.

    Linked to Projects, Team members, Organizations
  • Projects

    Projects and affected systems that change requests are raised against.

    Linked to Organizations, Team members
  • Organizations

    Organizations that own change work, with operating time zone and currency.

  • Team members

    People who prepare, own and review change work, linked to their organization and platform user.

    Linked to Organizations, Users
  • Record attachments

    Evidence files attached to a work package record.

    Linked to Team members, Work packages

Task delivery

5 tablesAbout this feature
  • Tasks

    Planned and actual work lines under a work package.

    Linked to Work packages, Team members, Projects
  • Work packages

    Scoped change work packages: the governed unit of change, baseline and revision.

    Linked to Projects, Team members, Organizations
  • Projects

    Projects and affected systems that change requests are raised against.

    Linked to Organizations, Team members
  • Team members

    People who prepare, own and review change work, linked to their organization and platform user.

    Linked to Organizations, Users
  • Impact assessments

    Impact assessments supporting approval of a scoped change request.

    Linked to Projects, Team members, Work packages, Organizations

Review decisions

5 tablesAbout this feature
  • Review decisions

    Independent reviewer decisions recorded against a work package revision.

    Linked to Team members, Projects, Work packages
  • Work packages

    Scoped change work packages: the governed unit of change, baseline and revision.

    Linked to Projects, Team members, Organizations
  • Team members

    People who prepare, own and review change work, linked to their organization and platform user.

    Linked to Organizations, Users
  • Impact assessments

    Impact assessments supporting approval of a scoped change request.

    Linked to Projects, Team members, Work packages, Organizations
  • Record attachments

    Evidence files attached to a work package record.

    Linked to Team members, Work packages

Evidence and receipts

5 tablesAbout this feature
  • Record attachments

    Evidence files attached to a work package record.

    Linked to Team members, Work packages
  • Operation receipts

    Durable receipts for every governed action, keyed for idempotent retries.

    Linked to Team members, Work packages
  • Work packages

    Scoped change work packages: the governed unit of change, baseline and revision.

    Linked to Projects, Team members, Organizations
  • Team members

    People who prepare, own and review change work, linked to their organization and platform user.

    Linked to Organizations, Users
  • Review decisions

    Independent reviewer decisions recorded against a work package revision.

    Linked to Team members, Projects, Work packages

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

The package’s record number and Revision identify the scope under review. Review decisions.source revision identifies the revision the reviewer examined. Operation receipts.operation key and expected revision connect an attempted action with its expected package state. Use the actual references to move from a project to its packages and from a package to its assessments, tasks and review history.

Migration order

  1. Import Organizations, then Users and team members with their organization and user references.
  2. Import Projects with their organization and owner links.
  3. Import work packages with project, organization and owner references and current revisions.
  4. Import impact assessments and Tasks under their parent packages.
  5. Import record attachments, review decisions and operation receipts with the relevant parent and person references.
  6. Reconcile package revisions, decision source revisions, task effort and receipt outcomes before opening the working screens.

Set up Change Request Management your way.

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

How to get started