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.
- Agencies PM
- Data model
The tables behind Agencies PM
Agencies PM 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
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Client context
Organizations anchor Projects and their owner in team members.
Delivery plan
Work packages belong to Projects; Tasks belong to work packages and can point to Projects.
Studio follow-up
Creative milestones, revision requests and Risks point to Projects and name team members as owners.
Time and evidence
Time entries link a team members row to Projects and optionally Tasks. Review decisions, operation receipts and record attachments preserve decisions and evidence.
Access records
Users holds account identity and a basic role value.
Every table, by feature
- Client Projects2
- Work Planning4
- Creative Milestones3
- Revision Requests4
- Team and Time6
- Delivery Evidence5
- Shared and settings1
- 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 - 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.
- Creative milestones
Creative deliverable checkpoints on a client project, each with a due date, an owner and a Pending / Met / Missed state.
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.
- Revision requests
Client and studio revision requests raised against project work, with severity, status, reporter note and owner.
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
- Team members
Delivery staff with role, practice and weekly capacity.
- 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 - 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
- Risks
Project risks with probability, impact, owner and mitigation.
Linked to Projects, Team members - Record attachments
Files attached to delivery records.
Linked to Team members - 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 - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members
Keys and references
The project reference is the thread across the engagement. A task’s required work package keeps execution with the planned scope. A time entry requires a team member and project; its task reference is optional. Revision requests and creative milestones require their project. Review decisions use a subject type and text reference, so agree how that reference matches a real delivery record before use.
Migration order
- Organizations and people. Bring in Organizations, team members and Users first.
- Engagements. Add Projects with owners, dates and budget.
- Delivery structure. Add work packages, Tasks and creative milestones.
- Follow-up. Add revision requests, Risks and time entries after the referenced projects exist.
- Evidence. Add review decisions, operation receipts and record attachments with their intended subject references.
Set up Agencies PM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.