How to Survive a Group Assignment
Group assignments fail in a small number of predictable ways, and almost none of them are about the work being hard.
Someone disappears. Someone hands in a section at 11pm the night before that is unusable. Nobody wrote down who was doing what, so three people did the introduction. The person who did most of it resents the others for a decade.
The fix is administrative. Not a better attitude, not a group-bonding session — a written record of who agreed to do what by when, created in the first meeting, and one message sent early enough that a marker can act on it.
The 10-minute version
- Write roles and deadlines down in the first meeting, in the group chat, in writing. That single message resolves most future disputes because it makes the original agreement visible.
- Set internal deadlines a week before the real one. The buffer is the difference between a missing section and a disaster.
- Escalate early, not at the end. Markers can act on a problem raised two weeks out. A complaint the night before the due date arrives too late to do anything but sympathise.
Meeting one: the fifteen minutes that decides everything
Do all of this in the first meeting and post it in the group chat afterwards.
Split the work into named chunks with one owner each. Not “we’ll all do research” — “Priya: sections 1 and 2, first draft”. Shared ownership means nobody owns it.
Set internal deadlines a week before submission. Every chunk due to the group, not to the marker. This is the single most effective mechanism available to a student group, because it converts a cliff into a checkpoint.
Agree the format now — referencing style, file format, who compiles, who proofreads. Merging four documents in four styles at midnight is where marks die.
Agree how you communicate, and that messages get answered within 48 hours.
Post the summary in writing. One message: who, what, when. Nobody has to be the enforcer later; the message simply exists.
The paper trail
This sounds cynical. It is actually protective, and it protects the group as much as you.
- Keep it in one place. One group chat, one shared drive folder. Not four DMs.
- Written asks, not verbal ones. “Are you still able to do section 3 by Friday?” in the chat, not in the corridor.
- Save the version history. Shared documents record who wrote what and when, automatically. That is the most persuasive evidence there is.
- Do not delete anything, even when it gets tense.
If you end up needing to explain that you carried the assignment, this record does it without you having to characterise anyone. Dates and messages speak for themselves.
The free-rider protocol
In order. Escalate a step only if the previous one fails.
Step 1 — Ask directly and privately. “Hey, are you still good for section 3? Anything I can do?” People vanish for reasons: illness, work, family, being overwhelmed. A private, non-accusatory message resolves a surprising share of cases.
Step 2 — Ask in writing in the group chat, with the date and the deliverable. “Just confirming — section 3 due to the group Friday, still on track?” This creates the record without escalating socially.
Step 3 — Offer a smaller scope. “If section 3 is too much right now, can you do the reference list instead?” Often the barrier is that the task has become insurmountable in their head. A smaller ask gets partial contribution rather than none.
Step 4 — Tell the marker, at least two weeks out. Email the tutor or coordinator with the facts: who agreed to what, what has been delivered, what has not, what you have tried. No adjectives.
That timing is the whole point. Two weeks out, a marker can reallocate work, adjust expectations, or contact the student. The night before, they can do nothing except note it.
Step 5 — Deliver the assignment anyway. Do not sabotage the submission to make a point. Submit the best work you can, with the record intact. Many institutions can weight individual marks where there is evidence, and evidence is what you have been building.
What actually goes wrong
Nothing is written down, so the original agreement becomes a matter of memory and everyone remembers favourably.
The deadline is the deadline. With no internal buffer, one late section sinks the submission.
Nobody says anything until it is too late. The most common and most fixable failure.
One person quietly does everything. It feels easier at week three and produces both a worse mark and real resentment. Ask for help in writing, early.
Formats are merged at the end. Four referencing styles and three fonts, at 1am.
The group chat becomes the argument. Keep it factual. Anything you would not want a coordinator to read, do not send.
Nobody proofreads the whole thing. Sections written separately contradict each other. One person reads it end to end.
Thresholds
| Situation | The rule |
|---|---|
| First meeting | Roles, chunks and internal deadlines posted in writing |
| Internal deadlines | One week before submission, without exception |
| No reply to a message | Follow up in the group chat within 48 hours, in writing |
| Someone misses an internal deadline | Private ask, then written ask, then reduced scope |
| A member is genuinely absent | Email the marker at least two weeks before the due date |
| Anything heated | Move it to writing, keep it factual, do not delete |
| Final week | One person compiles, one different person reads it end to end |
| Submission | Submit regardless. Never sabotage to make a point |
What it costs
| Tier | Spend | What it buys |
|---|---|---|
| Free | $0 | A shared document with version history, one group chat, a written summary after meeting one, internal deadlines in your calendar |
| Free but rarely used | $0 | Your institution’s academic skills service, which will help with structure and referencing. Also the tutor’s consultation hours |
| Worth knowing | $0 | Most institutions have a documented process for unequal contribution. Find it in week one, not week eleven |
The drill: the first-meeting template
Copy this into the group chat after meeting one. Fill in the blanks. That is the entire technique.
“` Assignment: ____________ Due: ____________ Internal deadline (all sections to group): ____________
Sections and owners
- ____________ — owner: ________ — to group by: ________
- ____________ — owner: ________ — to group by: ________
- ____________ — owner: ________ — to group by: ________
- ____________ — owner: ________ — to group by: ________
Compiler: ________ Final proofreader: ________ Referencing style: ________ File format: ________ Shared folder: ________ We answer messages within 48 hours. “`
Ten minutes of typing. It prevents most of what goes wrong, and if something does go wrong it is the document that shows you did your part.
Frequently asked questions
What do I do if a group member is not contributing?
Ask privately, then ask in the group chat in writing, then offer a smaller task. If none of that works, email the marker at least two weeks before the due date with dates and facts. Then submit the best work you can regardless.
When should I tell the tutor about a problem?
At least two weeks before the due date. Early enough and they can reallocate work or contact the student; the night before, there is nothing left to do.
Should I just do the work myself?
No. It produces a worse mark, no record, and real resentment. Ask in writing and early, so that if you do end up carrying it, the evidence exists.
How do I protect my own mark?
Keep everything in one group chat and one shared document with version history, make asks in writing, and never delete anything. Version history showing who wrote what and when is the most persuasive evidence available.
What if the group argues?
Move the conversation into writing and keep it factual, without adjectives. Anything you would not want a coordinator to read should not be sent.
Who should compile and proofread?
One person compiles and a different person reads the whole thing end to end. Sections written independently contradict each other, and nobody notices from inside their own section.