The first 48 hours decide everything
Group projects are lost in the first two days far more often than in the final week. What happens in that window is nothing: everybody waits for somebody else to start, politeness prevents anybody from assigning work, and by the time the silence becomes uncomfortable a third of the time has gone.
So be the person who posts first, and post something concrete rather than a greeting. A skeleton of the deliverable with the sections listed and nobody's name attached does more work than any amount of introducing yourself, because it turns a vague obligation into a visible list of tasks.
Then claim one, in writing, in the group space. Claiming a section rather than assigning one to somebody else is socially easy and it creates the norm you want. Most groups follow within a day, and the ones that do not have told you something useful very early.
Documentation is not paranoia
Everything important happens in the shared group space rather than in private messages, and that is a deliberate choice rather than distrust. If a section is agreed in a text thread and never delivered, you have nothing. If it is agreed in the course's own group area, the record exists and is timestamped by the platform.
The same applies to the document itself. Work in a shared file with version history intact rather than emailing drafts around, so who wrote what is visible without anybody having to make a claim about it.
None of this needs to feel adversarial. Frame it as organisation, which is what it genuinely is for the eighty percent of groups that work fine. For the other twenty percent it is the only evidence you will have.
- Post a skeleton of the deliverable in the first 48 hours
- Claim your own section in writing, publicly, before assigning anything to anyone
- Keep all agreements in the course group space, never in private messages
- Work in one shared file with version history rather than emailing drafts
- Set an internal deadline two or three days before the real one
- Write the summary of who is doing what after every meeting, however brief
When somebody goes quiet
There is a sequence, and following it matters more than any individual message. First, a direct and friendly check in the group space, naming the section and asking whether they still have capacity. People go quiet for real reasons and a surprising number reappear when asked kindly and specifically.
If nothing comes back within a couple of days, say publicly and without hostility that you will draft that section as a placeholder so the group is not blocked. That protects the deliverable and it makes the situation visible without anybody being accused of anything.
Only then does your instructor come into it, and by that point you are not complaining. You are reporting, with a record, before the deadline. That distinction is enormous, and it is the reason to move early rather than waiting to see whether it resolves itself.
Talking to faculty about it, properly
The difference between a message that helps and one that reads as tattling is almost entirely about timing and framing. Before the deadline you are seeking guidance. After it you are asking to be excused, and the instructor has considerably fewer options.
Keep it factual and unemotional: here is what was agreed and when, here is what has been delivered, here is what I have done to cover the gap, and I wanted you to know before the submission. No adjectives about anybody's character.
Most faculty respond well to that, and many have discretion they will not advertise. What they cannot do is unwind a grade afterwards on the strength of an account nobody could verify.
The version where you do the whole thing
Sometimes the group genuinely folds and you finish it alone. That is unfair and it happens, and it is worth knowing that the marks usually survive it: a complete, coherent deliverable submitted on time scores well regardless of how many people produced it.
What you should not do is submit something visibly incomplete to make a point. Graders mark what is in front of them, and a half-finished project punishes you far more than it punishes the people who vanished.
So finish it, keep the record, and raise it before submission rather than after. If the whole thing has landed on you in a week you did not have spare, a group deliverable is a perfectly ordinary thing to hand over, and it is a great deal cheaper than repeating the course.
Questions people actually ask
My group hasn't posted anything and we're three days in. What do I do?
Post a skeleton of the deliverable yourself and claim one section publicly. Don't assign work to anyone else at this stage, just make the shape visible and take a piece of it. Most groups activate within a day of somebody doing that, and the ones that don't have given you very early warning at almost no cost.
Should I message my instructor about a teammate?
Yes, but before the deadline rather than after, and framed as information rather than complaint. State what was agreed, what arrived, and what you've done to cover the gap. Faculty have discretion they rarely advertise, and they can use it while the project is live. Afterwards there's usually nothing left to do.
Is it worth submitting incomplete work to prove a point?
No, and it costs you far more than the people you're proving it to. Graders assess what's in front of them, so an unfinished project mostly damages your own mark. Finish it, keep the record of who did what, and raise the participation problem separately and in advance.
How do I document without seeming hostile?
Frame everything as organisation, because for most groups that's exactly what it is. Summarise who's doing what after each discussion, keep it in the course group space rather than private messages, and work in one shared file. Nobody objects to being organised, and the record simply exists if it's ever needed.
