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.
- Research Projects PM
- Data model
The tables behind Research Projects PM
Research Projects PM 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 own Projects and team members; team members link to Users.
Research work
Work packages connect to Organizations, Projects and an owning team members record. Tasks and research milestones sit beneath the package.
Review and evidence
Record attachments, review decisions and operation receipts point back to work packages. Attachments and decisions also identify their team member.
Every table, by feature
- Projects and organizations5
- Work packages7
- Tasks and hours4
- Milestones and grants6
- Evidence and review5
- Operations overview6
- Organizations
Research organizations that own projects, work packages and research milestones.
- Projects
Funded research projects acting as the counterparty for work packages.
Linked to Organizations - Team members
Staff membership linking a platform user to an organization and role name.
Linked to Organizations, Users - Users
Users
Linked to Users - Work packages
Baseline and accepted units of research work with budgeted hours and revisions.
Linked to Organizations, Team members, Projects
- Work packages
Baseline and accepted units of research work with budgeted hours and revisions.
Linked to Organizations, Team members, Projects - Projects
Funded research projects acting as the counterparty for work packages.
Linked to Organizations - Organizations
Research organizations that own projects, work packages and research milestones.
- Team members
Staff membership linking a platform user to an organization and role name.
Linked to Organizations, Users - Tasks
Dependent task lines under a work package with planned and actual hours.
Linked to Work packages - Review decisions
Immutable reviewer decisions recorded against a work package revision.
Linked to Work packages, Team members - Operation receipts
Stable idempotency receipts for every guarded workflow operation.
Linked to Work packages
- Tasks
Dependent task lines under a work package with planned and actual hours.
Linked to Work packages - Work packages
Baseline and accepted units of research work with budgeted hours and revisions.
Linked to Organizations, Team members, Projects - Research milestones
Grant milestone and extension evidence requiring independent review before completion.
Linked to Organizations, Work packages - Record attachments
Uploaded evidence files with visibility scope attached to a work package.
Linked to Work packages, Team members
- Research milestones
Grant milestone and extension evidence requiring independent review before completion.
Linked to Organizations, Work packages - Work packages
Baseline and accepted units of research work with budgeted hours and revisions.
Linked to Organizations, Team members, Projects - Tasks
Dependent task lines under a work package with planned and actual hours.
Linked to Work packages - Record attachments
Uploaded evidence files with visibility scope attached to a work package.
Linked to Work packages, Team members - Review decisions
Immutable reviewer decisions recorded against a work package revision.
Linked to Work packages, Team members - Organizations
Research organizations that own projects, work packages and research milestones.
- Record attachments
Uploaded evidence files with visibility scope attached to a work package.
Linked to Work packages, Team members - Review decisions
Immutable reviewer decisions recorded against a work package revision.
Linked to Work packages, Team members - Work packages
Baseline and accepted units of research work with budgeted hours and revisions.
Linked to Organizations, Team members, Projects - Team members
Staff membership linking a platform user to an organization and role name.
Linked to Organizations, Users - Tasks
Dependent task lines under a work package with planned and actual hours.
Linked to Work packages
- Operation receipts
Stable idempotency receipts for every guarded workflow operation.
Linked to Work packages - Work packages
Baseline and accepted units of research work with budgeted hours and revisions.
Linked to Organizations, Team members, Projects - Tasks
Dependent task lines under a work package with planned and actual hours.
Linked to Work packages - Review decisions
Immutable reviewer decisions recorded against a work package revision.
Linked to Work packages, Team members - Research milestones
Grant milestone and extension evidence requiring independent review before completion.
Linked to Organizations, Work packages - Record attachments
Uploaded evidence files with visibility scope attached to a work package.
Linked to Work packages, Team members
Keys and references
Work packages use record number for a human reference and Revision for a changing scope. Tasks have line number and Revision under their parent package. Research milestones have their own Revision and point to a parent package. Review decisions keep source revision and an operation key; operation receipts keep operation key and expected revision. Keep these values with their relationships when moving data, so a decision can still be traced to the scope it reviewed.
Migration order
- Import Organizations and Users, then link team members to both.
- Import Projects and confirm each project’s Organization.
- Import work packages with Organization, Owner and Counterparty references.
- Import Tasks, research milestones and record attachments under each work packages parent.
- Import review decisions and operation receipts only after their parent and reviewer references can be checked.
Set up Research Projects PM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.