How to split group project work fairly.
Start with what the assignment requires, compare the workload, and give each task a clear owner. Equal task counts alone do not tell you whether the split is fair.
By Cadence
First, agree on what “done” means
Read the assignment brief together. Write down the required outputs, the rubric criteria, and the final deadline. A report may need an argument, supporting evidence, citations, and a specific format. A presentation may also need slides, speaker roles, and rehearsal.
Keep a checklist of these requirements. Every task should help satisfy something on it. If a requirement has no task or owner, the work can fall through the cracks even when everyone is busy.
- Read the briefWhat must the team deliver?
- Map requirementsWhat will be assessed?
- Define the tasksWhat does finished look like?
- Agree on ownersWho moves each part forward?
Start with the requirements. Assign people after the work is clear.
Turn broad responsibilities into concrete outputs
“Do research” leaves room for different expectations. “Compare three competitors in a table, cite the sources, and explain the strongest difference” creates an output that another teammate can review.
For each task, write a deliverable, a definition of done, an owner, a due date, and any dependencies. Include the less visible work: combining drafts, checking references, fixing inconsistent formatting, and preparing the submission.
You can use the free group project plan template to record those decisions.
Compare workload, then choose owners
Ask the group to label tasks light, medium, or heavy. Consider how much research is needed, how difficult the judgement is, how familiar the owner is with the work, and how much coordination it involves. These labels start a conversation; they are not a precise measure of effort.
- Alex83 tasksillustrative workload points
- Sam33 tasksillustrative workload points
- Jordan63 tasksillustrative workload points
- Taylor43 tasksillustrative workload points
Everyone has three tasks. Alex still has more than twice Sam’s illustrative workload.
A teaching example using 12 invented tasks. Weights of 1, 2, and 3 are illustrative, not hours, research findings, or Cadence’s scoring system. Your team should discuss complexity and circumstances.
| Task | Illustrative workload | Why discuss it? |
|---|---|---|
| Build the financial model | Heavy | Requires assumptions, calculations, and checking. |
| Write the recommendation | Medium | Depends on the research and the model. |
| Check the final file format | Light | A bounded check, but it still needs an owner. |
One heavy task can be more work than several light checks. Review each person’s complete set of responsibilities, including editing and coordination. Discuss availability and access needs privately where appropriate, and agree on changes instead of assuming that everyone has identical circumstances.
Plan the handoffs before the final deadline
A slide designer cannot finish a deck while the findings keep changing. Identify which drafts need to exist before another task can move forward. Set a research handoff, a combined first draft, and a review point before the final submission.
Give each handoff an expected output. A folder of unlabelled links is different from evidence notes with a conclusion. Clear handoffs reduce the amount of work another person has to reconstruct.
- Research ready
Evidence notes and checked sources
The argument has a foundation. - First draft
One complete report or slide deck
The team can review the whole story. - Peer review
Rubric, source, and consistency checks
There is room to make changes. - Final hand-in
The agreed, checked submission
An owner confirms it was received.
An illustrative sequence. Choose actual dates from your assignment and team availability.
Make the split visible and review it
Keep the task list somewhere the whole group can see. At each check-in, review what is complete, what is blocked, and whether the workload has changed. A task can turn out to be larger than expected. Reassigning part of it is often more useful than waiting until the deadline to discuss fairness.
For example, in the four-person presentation example, research unlocks the financial model and recommendation, then feeds the slides. If the slide work grows, another teammate can take on citation checks or draft a section of the deck. Record the agreed change so ownership stays clear.
If someone is not contributing
Start with a specific conversation about the missing output, the blocker, and a realistic next step. Keep a factual record of agreed tasks and contributions. If the problem continues, follow your course’s group-work or escalation process and speak with your instructor. A task tracker can show the work; it cannot decide academic consequences.
A short check-in that leads to a decision
Go around the group with the same questions. Focus on outputs and blockers rather than treating time online as proof of contribution.
| Ask | Record the next step |
|---|---|
| What is ready to review? | Link the output and name its reviewer. |
| What is blocked? | Name the missing input and who can provide it. |
| Has the task grown? | Adjust its scope, support, or ownership together. |
| Which handoff comes next? | Confirm the output, owner, and agreed date. |
Finish by repeating any changes to owners or dates. A check-in is useful when the group leaves with a shared decision and a clear next action.
Use Cadence to keep requirements and owners connected
Cadence suggests a plan from the assignment brief and lets your group review tasks, workload, and ownership. Members can claim work within the leader’s limits, or the leader can choose a workload-balanced random draw. Comments and submissions stay attached to the task.
AI suggestions need your review against the original brief. Your group remains responsible for the research, sources, final submission, and your institution’s academic integrity rules.
You can explore and prepare a brief before signup. Generating and saving a project requires an account.