What to Do When a Group Member Is Not Doing Their Work

Start with a private check-in, not an accusation

Most stalls have boring causes: an overloaded week, unclear scope, a broken dependency nobody flagged, or a member who does not actually understand the task and hopes silence hides it. The first move is a short private message - what is the blocker, can I help, here is what the section needs - because it costs one minute and resolves a large share of cases. Ask what is happening rather than asserting that nothing is; the difference in reply rate is real.

Keep the first contact off the group channel. A public callout hardens positions, invites an audience-performance defense instead of an honest answer, and spends goodwill the group will need if the problem turns out to be structural. If the check-in fixes it, log the new date anyway in the shared document - the fix that is not written down has a way of not happening, and the log is what makes the next step proportionate if it comes to that. Most first messages get a reply within a day, and the reply usually names a fixable problem nobody had said out loud.

The numbers at a glance

Escalation ladder for a group member who is not delivering — the range, and where each row actually shows up in coursework. Skim it first; the sections below explain why the range exists and which row applies to you.

Re-split the work in public, with dates

If the private nudge fails, re-split the stuck member's task into smaller, named, dated chunks and announce the new split in the group channel: the section they owed becomes three half-day tasks with explicit dates and one already assigned to whoever can absorb it. Shrink the unit of work until it fits inside a single evening - a stalled member facing a 1,500-word section often can start a 300-word draft. Make dependencies explicit, because work that blocks someone else is the work that needs the earliest date.

The re-split is the step most groups skip and the step that fixes most cases, because it converts a vague grievance into a schedule. The group-workload-splitter tool re-divides a lopsided split quickly if the arithmetic is contested. If the second deadline also slips, the pattern is now visible to everyone, which changes the conversation from one member's complaint into the group's shared problem - and that shift is exactly what makes the remaining steps legitimate. It also protects the member: a re-split with dates is a chance to succeed again, where silence never is.

Document without turning hostile

From the first slip onward, keep dated artifacts: the original charter with names and deadlines, the status updates, the re-split message, and a contribution log showing who delivered what by when. Tone stays boring - what was due, what arrived, what happens next. Shared-document version history counts as documentation, which is a reason to keep the project in one platform rather than scattered across personal drafts. One platform, one file, one history - the documentation writes itself when the group has been working in the same place all along.

The paper trail matters because most courses grade group work with an individual component, and peer evaluations plus a documented log are what instructors act on. Documentation also protects you from the counter-story that the work was always meant to be shared, which surfaces surprisingly late and works surprisingly often on undocumented groups. Screenshots of a heated argument, by contrast, usually damage the reporter more than the subject - instructors act on timelines, not tone.

Involve the instructor with facts and enough lead time

Bring the instructor in when a documented re-split has failed and there is still runway: a week or more before the deadline is a request the professor can act on, two days out is a complaint they can mostly only note. Read the syllabus first, because it defines the toolkit - some courses specify individual scoring from peer evaluations, some apply a group multiplier, and some leave it to judgment - and knowing the policy signals that the request is procedural rather than emotional.

The message itself stays neutral: what was assigned, what was delivered, what the group tried, and what outcome you are asking about. The professor-email-builder tool structures exactly this kind of message. Hedge expectations, because instructors cannot always reassign grades mid-project; they can sometimes split the deliverable, note the contribution record, or apply the syllabus clause. What they reliably cannot do is fix what they learn about after the deadline. Copy the syllabus language into the message when it applies, because instructors move faster on clauses than on summaries, and the clause does the arguing for you.

Protect your own grade with a triage plan

While the process runs, triage the rescue: rubric-critical sections first - thesis, evidence, citations - your own assigned sections second, polish last. If the arithmetic says the project cannot reach standard without absorbing the missing work, cut scope explicitly with the instructor rather than silently surrendering nights to a teammate's section. The how-to-plan-a-term-paper guide covers the same triage logic for solo deadlines, and it transfers whole. Triage beats heroism: deciding in advance which sections carry the grade is faster and calmer than discovering the ranking at two in the morning.

The hedge that matters: silently absorbing a free-rider's section usually teaches the pattern to repeat, to you and to them. The fair move is the documented one - do the work if the deadline demands it, but say so in the group channel with the date and note it in the log. The how-to-divide-work-in-a-group-project page covers the prevention side of this problem; most groups that run its charter never need the ladder above step two. The ladder is the repair manual; the charter is the reason the repair rarely gets opened, and both live better in the group than in memory.

Back-planning from the due date

Take the due date and subtract the phases, not one block: research and outlining get the first 40 percent of your budget, drafting the next 35, revision and formatting the final 25. A paper due Friday that needs eight hours means sources and outline locked by Wednesday morning, a complete draft by Thursday noon, and Thursday evening reserved for the revision pass that actually moves grades.

Protect the revision block as fiercely as the deadline itself. The most common failure pattern in writing-center data isn't slow drafting — it's schedules that leave revision for the final hour, where it can't work. The deadline planner below splits any due date into phase checkpoints automatically; set the paper length and it does this arithmetic for you.