Copyable template
Group Project Role Split Template
Copy a group project role split template with owner, support, blocked, optional, check-in, and handoff sections.
Updated 2026-06-18
Use this group project role split template when several people share one deliverable and the next action is unclear. It names owners, support, blockers, optional polish, and a short check-in format.
Copyable Template
# Group Project Role Split Template
Project: [Project name]
Deadline: [Due date]
Final deliverable: [Presentation, report, event, packet, or handoff]
Check-in time: [Date and time]
Fill-In Notes:
- Use lead for the person who owns the next action.
- Use support for review, backup, or help that does not replace the owner.
- Use blocked when a question, file, permission, rule, or decision is missing.
- Use optional for polish that should not delay required work.
| Task | Owner | Role | Due by | Status note |
| --- | --- | --- | --- | --- |
| [Required task] | [Name] | lead | [Date] | [Next action] |
| [Review/help task] | [Name] | support | [Date] | [What help means] |
| [Blocked task] | [Name] | blocked | [Date] | [Question or missing item] |
| [Nice-to-have task] | [Name] | optional | [Date] | [Only after required work] |
Blocked questions:
- [Question] -> [Who will ask] -> [By when]
Check-in script:
- Done: [What changed]
- Next action: [What happens next]
- Blocker: [None or specific blocker]
- Help needed: [Person or resource]
Handoff check:
- [ ] One owner per required task
- [ ] Final assembly owner named
- [ ] Submission or delivery step named
- [ ] Optional work cannot block required work
- [ ] Blocked questions have an asker and deadlineUseful variants
- Class presentation with research, slides, speaking, and submission
- Volunteer event plan with supplies, map, permit, and day-of roles
- Study group packet with question writing and review owners
- Household project with shopping, setup, and cleanup owners
- Client or club deliverable where blockers need early escalation
How to adapt it
Replace bracketed text with your details, remove sections you do not need, and keep the final version short enough for the reader to act on.
FAQ
Can one person own more than one task?
Yes, but the check-in should show whether that workload is realistic before the deadline. If one person owns final assembly and several content tasks, move at least one task to support or optional.
What should be in the check-in?
Each owner should share done, next action, blocker, and help needed in one short status line. That keeps the update useful without turning it into another meeting.
How do we handle a task nobody wants?
Name a temporary owner for the next action instead of leaving it blank. The next action can be asking the teacher, reducing scope, or splitting the task into a smaller lead and support role.
What should not go in the shared template?
Do not include private contact details, grades, account logins, sensitive personal notes, or blame language. Keep the shared version focused on work, owners, blockers, and dates.