1. Risk Management
  2. Data model
Reference

The tables behind Risk Management

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

How the model is organised

Risk and issue work

Risk register holds assessments and mitigation; Escalations holds current defects and change items. Both point to Projects.

Delivery

Organizations connect to Projects; work packages and Tasks organize work under those projects. Team members appear as owners and assignees.

Review

Review checkpoints carry dated project outcomes. Time entries carry submitted hours; review decisions and operation receipts preserve decisions and operation results.

Files and access

Record attachments stores file references by parent record. Users stores user identity and access state.

Every table, by feature

Risk register

4 tablesAbout this feature
  • Risk register

    Project risks with likelihood, impact, owner and mitigation.

    Linked to Projects, Team members
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Review checkpoints

    Dated checkpoints a project must meet.

    Linked to Projects, Team members
  • Tasks

    Individual pieces of work assigned to a delivery team member.

    Linked to Work packages, Team members, Projects

Mitigation work

5 tablesAbout this feature
  • Risk register

    Project risks with likelihood, impact, owner and mitigation.

    Linked to Projects, Team members
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Work packages

    Groupings of work inside a project.

    Linked to Projects, Team members
  • Tasks

    Individual pieces of work assigned to a delivery team member.

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

    Delivery staff with role, practice and weekly capacity.

Review checkpoints

5 tablesAbout this feature
  • Review checkpoints

    Dated checkpoints a project must meet.

    Linked to Projects, Team members
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Risk register

    Project risks with likelihood, impact, owner and mitigation.

    Linked to Projects, Team members
  • Tasks

    Individual pieces of work assigned to a delivery team member.

    Linked to Work packages, Team members, Projects
  • Escalations

    Defects and change items raised against project work.

    Linked to Projects, Team members

Escalation triage

5 tablesAbout this feature
  • Escalations

    Defects and change items raised against project work.

    Linked to Projects, Team members
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Team members

    Delivery staff with role, practice and weekly capacity.

  • Operation receipts

    Evidence that a delivery operation was executed.

    Linked to Team members
  • Risk register

    Project risks with likelihood, impact, owner and mitigation.

    Linked to Projects, Team members

Project context

7 tablesAbout this feature
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Organizations

    Client and internal business organizations that projects are delivered for.

  • Work packages

    Groupings of work inside a project.

    Linked to Projects, Team members
  • Tasks

    Individual pieces of work assigned to a delivery team member.

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

    Delivery staff with role, practice and weekly capacity.

  • Risk register

    Project risks with likelihood, impact, owner and mitigation.

    Linked to Projects, Team members
  • Review checkpoints

    Dated checkpoints a project must meet.

    Linked to Projects, Team members

Time approval

6 tablesAbout this feature
  • Time entries

    Hours booked by a team member against a task and project.

    Linked to Team members, Projects, Tasks
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Tasks

    Individual pieces of work assigned to a delivery team member.

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

    Delivery staff with role, practice and weekly capacity.

  • Review decisions

    Recorded approval decisions on delivery subjects.

    Linked to Team members, Projects
  • Operation receipts

    Evidence that a delivery operation was executed.

    Linked to Team members

Evidence and decisions

6 tablesAbout this feature
  • Review decisions

    Recorded approval decisions on delivery subjects.

    Linked to Team members, Projects
  • Operation receipts

    Evidence that a delivery operation was executed.

    Linked to Team members
  • Record attachments

    Files attached to delivery records.

    Linked to Team members
  • Time entries

    Hours booked by a team member against a task and project.

    Linked to Team members, Projects, Tasks
  • Escalations

    Defects and change items raised against project work.

    Linked to Projects, Team members
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

A risk or escalation references its project and may reference a team members owner. Tasks reference work packages and can also reference Projects directly. Time entries reference team members and Projects, with an optional Tasks reference. Review decisions can reference a related project, while attachment parent identifiers and operation references are text values that need careful matching during migration.

Migration order

  1. Load Organizations and team members, then review Users access.
  2. Load Projects with their organization and owner references.
  3. Load work packages and Tasks under their projects.
  4. Load risk register, Escalations and review checkpoints with project and owner links.
  5. Load time entries, review decisions, operation receipts and record attachments after the subjects they describe.
  6. Check a representative project from risk through mitigation, approval and evidence before inviting the wider team.

Set up Risk Management your way.

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

How to get started