Assign package planning, independent review and delivery oversight to named people.
The person who submits a proposal should not approve that same work.
Team members need assigned work and supporting evidence; reviewers need the current package revision.
Link each team members record to the intended Users record before assigning work.
| Role | Organizations and projects | Work packages | Tasks and dependencies | Scheduling proposals | Review and evidence | Operations oversight |
|---|---|---|---|---|---|---|
| Project Coordinator | View | Edit | Edit | Edit | View | View |
| Project Reviewer | — | Approve | View | Approve | Edit | Edit |
| Delivery Lead | Edit | Edit | View | View | View | View |
| Team Member | View | View | Edit | View | Edit | — |
| Evidence Manager | — | View | View | View | Edit | View |
| Admin | Edit | Edit | View | View | Edit | View |
Prepares work packages and task plans, submits scheduling proposals and applies authorized changes.
Starts on: Schedule review inbox
Independently decides on schedule proposals and delivery evidence for a current revision.
Starts on: Schedule review inbox
Owns delivery oversight, reviews exceptions and confirms package acceptance after independent review.
Starts on: Active work packages
Updates task progress and provides evidence for assigned delivery work.
Starts on: Due task lines
Maintains supporting files and checks their audience before review.
Starts on: Shared package evidence
Maintains organization and identity records and assigns access for the operating team.
Start free, then use Proto to change fields, steps and approvals before your team goes live.