Blog · Group work

Group Projects When Nobody Else Is Doing the Work

September 18, 2026 · 5 minute read

You set up the group chat eleven days ago. Two people replied. One of them replied with a thumbs up and nothing since. The deadline is in six days and you are quietly doing the whole thing yourself while telling yourself it is easier this way.

It is not easier. It is just quieter. And it comes with a real cost: you are carrying four people's grades with one person's time, and you are doing it invisibly.

Here is how to fix it without turning into the group's manager.

First, find out what you are actually being marked on

Before you do anything else, open the syllabus and answer three questions:

Is the group mark split per person, or is it one shared mark? Courses that use individual peer evaluation usually say so plainly. If there is one shared mark and no peer evaluation, your group's problem is now directly your grade, and that changes everything below.
Does the rubric grade the process or the product? If you are marked on a submitted report, the group can be dysfunctional and still score well. If you are marked on evidence of collaboration, a silent chat log is your problem, not just theirs.
What is the escalation route? Most modules have one. It is usually a line about contacting the module leader early if a group is not functioning. Find it now, while you still have six days, because that line becomes useless on the day the thing is due.

Ten minutes with the syllabus tells you whether you are protecting a shared mark, your own mark, or nothing at all. Almost nobody does this, and it is the difference between a plan and a mood.

Decide whether you are the organiser, once

Someone has to be. If nobody is, that is genuinely everyone's fault and it will stay that way.

So decide: are you the organiser, or are you a passenger who will deliver their own section and nothing more? Both are legitimate. What is not legitimate is being an unwilling organiser who complains the whole way, because that is the version that burns you out.

If you take the organiser role, take it for a fixed scope: you set the structure, you set the dates, you send the messages. You do not do the work that belongs to someone else. Those are two different jobs and merging them is how the whole thing lands on your desk.

The message that actually moves a dead group

"Hey everyone, just checking in, where are we at?" gets nothing. It asks for a status update, which is a thinking task, and thinking tasks get deferred.

Plan, so we can all stop thinking about it:

Section 1 (intro plus problem statement) · Priya · draft by Saturday 6 PM
Section 2 (data and method) · Dan · draft by Sunday 6 PM
Section 3 (findings) · Me · draft by Sunday 6 PM
Section 4 (recommendations) · Ama · draft by Monday 6 PM
Formatting and merge · Me · Monday night

Reply with a yes if that works. If a date does not work for you, reply with the date that does and I will move the merge.

We submit Thursday, so Monday is the hard stop for text.

Four things make that message work where "where are we at" fails:

Names are already on it. Nobody has to volunteer, which is the step where groups die.
No meeting. A meeting needs six schedules to line up. A named date needs nothing.
The default is yes. Silence becomes agreement, so two replies are enough to move. Say that out loud if you have to.
There is a hard stop date. Monday for text, so the merge is not a midnight scramble.

Do not chase privately

The temptation is to message the one person who is behind, one to one, so nobody is embarrassed. Resist it for anything that affects everyone's deadline.

One to one chasing puts you in the position of being someone's supervisor, creates no written record, and asks the same question again next week. Keep deadlines in the group thread and keep the private messages for the actual work.

If someone's date passes with nothing, put a single line in the group thread naming the deliverable, not the person: "Section 2 is not in, so the merge is paused until tomorrow 6 PM." Then keep going with what you have. That is not you being difficult. That is the group's plan doing its job.

Document your own contribution as you go

You will need this whether or not anything goes wrong, and it takes no extra time if you do it while working.

Do your writing in a shared document with edit history switched on, rather than in a private file you paste at the end.
Keep your drafts. Version history is the only evidence of who wrote what, and it does not exist if you work offline.
Send short written updates in the group thread when you finish something. "Section 3 first draft is up" is one line and it timestamps your work.
If you did the merge or the formatting, say so once, plainly, in the thread. Coordination effort is real work and it is the first thing to become invisible.

When to take it to the module leader

Go early, go factual, and go once.

Early means at least four or five days before the deadline, when something can still be arranged. Factual means dates and deliverables, not character. Once means you send one message and let it be handled, rather than emailing every day as the situation develops.

Something like this is enough:

Hello Dr Okafor,

I am writing about the group report for MKT 340, due Thursday. Our group agreed a section split on the 12th. Three of four sections were due Sunday; two have come in. The group chat is on the shared drive if you want to see the timeline.

I can merge the three sections we have by Wednesday. I would like to know whether it is better to submit with the missing section marked as incomplete, or to request the short extension as a group.

Thank you,
Jordan

Notice it does not accuse anyone. It gives the module leader the two things they need: the timeline, and a decision to make. That is a request for guidance, not a complaint, and it gets a very different response.

Do not carry it silently

The worst outcome of a broken group project is not a lower mark. It is doing four people's work for six days, telling nobody, and then being too tired to do your own sections well.

Set the plan, name the dates, document what you do, and escalate once if the dates pass. Then submit what you have with a clear head, because the thing being graded is a report, not your willingness to absorb other people's silence.

If you are already the person quietly holding three group projects together, that is a load problem worth fixing now rather than in week ten. Send us your modules for a free class audit and we will show you where the term is about to collide.