Agree who owns capacity assumptions, assignments and the human delivery decisions.
Delivery Lead maintains the planning baseline and authorizes the project scope the team accepts under the review policy agreed during setup.
Project Manager organizes work packages and tasks, follows time-validation outcomes and coordinates milestones and resource concerns.
Developer and QA Engineer maintain assigned work and time. QA Engineer examines fixes before recording the verification outcome.
Admin maintains users, organizations and team-member records. Configure access with the actual people in the pilot and test what each person can read and change.
Human scope and delivery review decisions are separate from the automatic validation of submitted time. Explain both paths before the first operating cycle.
| Role | Portfolio and scope | Team capacity | Work packages | Task workload | Time and effort | Delivery exceptions |
|---|---|---|---|---|---|---|
| Admin | Edit | Edit | View | View | View | View |
| Delivery Lead | Approve | Approve | Approve | Approve | Approve | Approve |
| Project Manager | Edit | Edit | Edit | Approve | Edit | Approve |
| Developer | Edit | View | View | Edit | Edit | Edit |
| QA Engineer | Edit | View | View | Edit | Edit | Edit |
Maintains user access and the organization and personnel records used to identify delivery work.
Owns capacity assumptions and authorizes the project scope the team is prepared to deliver.
Starts on: Timesheets Awaiting Approval
Plans assignments and coordinates time, milestones and exception follow-through for delivery work.
Starts on: Timesheets Awaiting Approval
Maintains assigned task progress, records work time and raises issues with supporting evidence.
Starts on: Timesheets Awaiting Approval
Examines fixes and delivery evidence, records verification outcomes and books time against assigned work.
Starts on: Timesheets Awaiting Approval
Start free, then use Proto to change fields, steps and approvals before your team goes live.