The flaw is usually in the split.
Watch how a group divides work and you can predict the outcome before anybody goes quiet. The default division is by section, in the order the sections appear: one person takes the introduction, the next takes the analysis, the next takes the recommendations. That arrangement chains everybody to everybody, and a single member who stops replying blocks every task downstream of theirs while the calendar keeps moving.
The alternative costs one conversation and changes the risk entirely. Divide into units that can be produced in parallel and combined later: each member owns a complete piece of work with its own inputs, and one named person owns integration. If somebody disappears, what is lost is that unit rather than the project, and a unit can be absorbed by whoever has capacity. What cannot be absorbed on short notice is the middle link of a chain that four people were waiting on.
Make the first meeting a scoping meeting.
Half an hour at the start decides most of what happens later, and it is half an hour spent on administration rather than on the topic. Produce the following, in writing, in the space the whole group can see, and the project acquires a spine that does not depend on goodwill.
- The deliverable list, taken from the rubric rather than from the prompt, since the rubric is what will be scored; the method is set out in the note on rubrics
- An owner and an internal due date for each item, set several days ahead of the real deadline so that a miss is recoverable rather than terminal
- One shared document as the only place work exists, so that nothing important lives in an attachment somebody forgot to send
- A named integrator who assembles, edits for one voice and submits, credited for that work in the split
- One agreed channel and a response window, stated plainly: a message unanswered after two days is treated as an absence, not an insult
Keep a record, and keep it dull.
Work in the group's own space rather than in private messages, and the record creates itself. Requests, drafts, dates and answers accumulate where an instructor can read them without anybody having to assemble evidence in a crisis. This is not preparation for conflict; it is the ordinary bookkeeping of any project with more than one person on it, and it is the reason well-run groups never need to argue about who did what.
Tone matters more than volume. A log that reads as a schedule carries weight; one that reads as a grievance invites the reader to weigh personalities instead of facts. Record what was asked and when, what arrived and when, and nothing about how any of it felt. If the project is going well, the record is a curiosity. If it is not, it is the only thing standing between you and somebody else's version of events.
Escalate early, and ask a question rather than make a case.
The commonest mistake is escalating on the final day, at which point an instructor has no remaining moves and can only apportion blame. Raise it as soon as an internal deadline is missed and the person is unreachable, which is usually two weeks out, when regrouping, reallocation or an extension are all still available.
Keep the message short and make it answerable. State what was agreed, what has arrived, what has not, and ask a specific question: whether to proceed on the assumption that a section is not coming, and how the instructor would like the shortfall handled in the submission. A question invites a decision. A complaint invites a reply expressing sympathy, which changes nothing about the deliverable.
Salvage, when it is already the last week.
At that point the project stops being a collaboration and becomes a triage exercise. Establish what the deliverable minimally needs in order to be gradeable at all, then work the heaviest rubric criteria first and let the lightest ones be merely adequate; the general order is set out in the triage order. Submit on time and incomplete rather than late and complete, unless the course's own policy makes the opposite arithmetic true.
Two things not to do. Do not invent content and attribute it to an absent member, which converts an attendance problem into an integrity problem that belongs to you. And do not submit silently: include a brief factual note of what was contributed by whom, and send the instructor the same note separately. Where a term has produced several of these at once, carrying the individual share of a collapsed group is routine work for the business pages.
Questions to the desk.
Should I just do the missing work myself?
Sometimes, and only as a decision rather than a reflex. Absorbing one small unit late in a project is usually cheaper than a dispute. Absorbing half the deliverable teaches the group that silence works and leaves you with a workload nobody agreed to. Decide by asking what the remaining time actually permits, then tell the instructor what you have taken on, in writing, before you do it.
When is the right moment to tell the instructor?
When an internal deadline passes and the member is unreachable, which should be well before the submission date. Early notice lets an instructor regroup members, reallocate scope or extend a deadline. Notice on the final day lets them do none of those, so the conversation becomes about fault rather than about the deliverable. Early escalation is also read as project management rather than as complaint.
How do I document contributions without seeming petty?
Keep it factual and keep it in the shared space from day one, so it exists as a matter of routine rather than as evidence gathered against someone. Dates, requests, drafts and what arrived are enough. Avoid characterizing anybody. A neutral record is more persuasive than an aggrieved one, and it costs nothing to maintain when the project goes well.
Do peer evaluations actually affect grades?
In many courses they do, either by adjusting individual marks or by informing the instructor's judgment, though the weight varies and is often unpublished. Treat them as one input rather than as a remedy. They arrive after submission, which is too late to change the deliverable, so they are no substitute for raising a problem while the project can still be repaired.
