001The invisible workload.
Splitting a deliverable creates a second job nobody is assigned: keeping the parts consistent with each other, chasing what has not arrived, reconciling formats, and deciding things that cut across sections. That job grows with the number of participants rather than with the length of the document, and in a four or five person group it can exceed the writing itself.
None of it is visible to a grader. The hours spent in messaging threads produce nothing that appears in the submission, which is why students finish a group project feeling they worked hard and cannot point at what they produced. They did work hard. Most of it was coordination.
This is not an argument against group work, which teaches something genuinely useful about how organizations actually function. It is an argument for treating coordination as a named task with an owner, rather than as something that will happen by itself. Unowned, it does not happen, and then it happens all at once on the final evening.
002Split by section, not by task type.
The most common division is by activity: one person researches, one writes, one edits, one builds slides. It sounds efficient and it is the worst available structure, because it makes everyone a blocker for everyone else. The writer cannot start until the researcher finishes; the editor cannot start until the writer does; and any delay anywhere stops the whole chain.
Split by section instead, so each person owns a complete piece from research through to a submission-ready draft. Everyone can work simultaneously, a delay affects one section rather than all of them, and each person is accountable for something a grader will actually read.
Then name a compiler as a separate role with real time allocated, because merging five sections into one coherent document is a genuine job rather than a formality. The compiler needs the sections at least three days before the deadline, and that internal deadline is the one that matters.
003Balance by hours, not by page count.
Equal page counts are not equal work, and treating them as equal is how resentment enters a group that was functioning fine. Estimate each section in hours before assigning anything.
- Sections requiring original data collection or analysis cost several times what a comparable length of prose costs.
- The introduction and conclusion are shorter and harder, because they have to be written last and must be consistent with everything else.
- Compilation and formatting is a real allocation, usually several hours, and is systematically underestimated because it is invisible until it is late.
- Any section depending on another person's output carries waiting time that belongs in the estimate rather than being absorbed silently.
- Presentation material, where required, is its own job and should not be added to whoever finished their section first.
004Decide the cross-cutting questions before writing starts.
Some decisions affect every section and cannot be made independently by each owner. Who the audience is. What the central argument or recommendation is. Which framework the analysis uses. What the citation style and formatting conventions are. Whether the tone is a report or an essay.
Make these together, in the first meeting, and write them down. Left undecided, each section owner resolves them differently and reasonably, and the compiler discovers on the final evening that they have five documents built on four different premises. Reconciling that late is either a bad night or a submission that visibly does not cohere.
This is the same discipline a charter enforces on ownership, and it is worth the same twenty minutes. The detailed version, including the clause about what happens when somebody misses an internal deadline, is at the charter issue.
005When one person is not delivering.
Raise it about the schedule rather than about the person, in the shared channel rather than privately, and early. A message noting that a section is not in and asking whether the deadline still works is answerable, impersonal, and doubles as documentation. The framing that goes badly is one requiring the recipient to defend themselves before they can reply.
Tell the instructor while the problem is developing rather than after the submission. Documentation filed early protects you; the same account filed afterwards reads as an excuse however accurate it is. Most instructors have seen this repeatedly and would far rather hear about it in week six than in a grade appeal.
If you end up writing the missing section, do it and make sure the record shows you did. Quietly absorbing someone's work protects the grade and erases the evidence, which matters when the same thing happens on the next project. Where compilation or a section genuinely needs handing off, it is scoped like ordinary weekly coverage rather than as a whole assignment.
Questions.
What if nobody wants to be the compiler?
Rotate it if the course has several group deliverables, or trade it against a smaller writing section, since it is a real allocation and should be treated as one. What does not work is leaving it unassigned in the hope that someone steps up, because the person who eventually does is whoever panics first, on the last evening.
Should I do more than my share to protect my grade?
Sometimes it is the pragmatic call, and if you make it, make it visibly. Tell the instructor what happened while it is happening. Doing extra work silently protects this grade and guarantees the same position next time, because nothing in the record shows the imbalance ever occurred.
How do peer evaluations factor in?
Where a course uses them, they are your formal channel and worth completing carefully and specifically rather than diplomatically. Vague positive evaluations for a member who did not contribute remove the only mechanism the instructor has. Say what happened factually, without characterizing the person, and reference the dates in your own record.
Can a group project ever be genuinely efficient?
Yes, when the deliverable is large enough that parallel work outweighs the coordination overhead, and when sections are genuinely independent. Short group assignments are almost always slower than working alone, which is worth knowing so you plan for the overhead rather than being surprised by it every term.
