When Someone Isn't Pulling Their Weight in a Group Project

The shared document looks almost finished until you scroll to the part with somebody else's name on it. That part is still a heading and an empty paragraph.

You've sent a message. They reacted with a thumbs-up. Someone else in the group says they'll probably do it tonight. Another person privately suggests just finishing their section so the grade doesn't suffer. Nobody wants to be the person who tells the lecturer, but everyone is getting increasingly annoyed.

Group work can be genuinely good. It can also turn ordinary students into reluctant project managers, mediators and amateur detectives. When a member isn't contributing, there are two problems to solve: the work needs doing, and people need to be treated fairly. Solving one by ignoring the other usually creates a new mess.

What follows isn't a way to punish someone you don't like. It's a way to make expectations clear, protect evidence without invading anyone's privacy, and bring the teaching team in when the problem is beyond what students should have to resolve alone.

First, check whether the task was ever properly agreed

“Alex isn't doing anything” can describe several situations. Alex may have missed the meeting where the work was allocated. They may believe their role is finding sources rather than writing slides. Their access to the file may be broken. They might be struggling with a health or family problem they don't want to explain to classmates. Or, yes, they may be avoiding the work entirely.

All of those produce an empty section. The next step depends on which problem you have, so start with observable facts. What work was assigned? Who agreed to it? What was the checkpoint? Is there evidence they received the plan? Has anybody asked what support they need?

This doesn't mean you need to exhaustively investigate somebody's life. You aren't their supervisor, their doctor or their parent. It means giving the person a fair chance to correct a misunderstanding before writing a story about their intentions.

Cornell's teaching guidance describes team contracts as a way to agree roles, expectations and how conflict will be handled. That's a useful model even if your lecturer didn't require a formal contract.

Make the missing work specific enough to finish

“Please contribute more” is easy to agree with and impossible to measure. “Please add two sourced comparisons of the chosen case studies to section three by Thursday at 6 p.m., and let us know by tomorrow midday if you can't” is something everyone can understand.

Make the task small enough to show progress before the final deadline. Waiting until submission night to find out whether a section exists is not a fair test of anyone's reliability, including your own.

The first message should be firm and kind

When frustration builds, it's tempting to send a paragraph listing every irritation since the project started. The problem is that a public accusation can make someone defensive and make it harder to discuss the actual work.

Start with the task. Prefer a shared project thread where expectations are transparent, unless a private check-in would be more appropriate because someone might be having difficulty.

That message doesn't pretend the delay is fine. It asks for a clear answer and leaves space for information you don't have. If the person says they're struggling, you can discuss a smaller task, a revised split or support from the lecturer. If they don't answer, you have a documented, reasonable attempt to resolve the problem.

What if they say “I'll do it tonight” for the third time?

Don't debate their character. Move from vague promises to a concrete checkpoint: “Thanks. Could you upload the draft or outline by 4 p.m. tomorrow? We need to know what exists before we allocate editing.” If the checkpoint passes without work, stop repeating the same open-ended conversation.

At that point, tell the course team what happened. You may still be able to rearrange tasks, but the decision about grading fairness, changing membership or extensions belongs with the people responsible for the module, not a group chat conducting its own trial.

Virginia Tech's guidance on student teams recommends documenting roles, decisions and contributions, and intervening early when patterns of unequal workload or unresolved conflict emerge. That guidance is written for educators, but the student-facing lesson is clear: don't wait for a small, solvable gap to become a last-night crisis.

Keep a factual contribution log, not a dossier

If you need to approach a lecturer, screenshots of an entire chat or a spreadsheet rating everyone else's personalities probably aren't necessary. Keep a short, factual record of agreed tasks, shared files, checkpoint dates, actual work submitted and the steps taken to ask for an update.

Only record information relevant to the assignment. Don't circulate private messages, medical disclosures, account activity or speculation about where a teammate has been spending their time. If somebody tells you something personal, ask how they would like to involve the tutor rather than passing it around without their consent. Use approved university systems for sensitive matters.

And make your own contributions visible too: commits, drafts, research notes, version history or speaking roles. The aim is an accurate picture of the work, not to win an argument.

When and how to tell the lecturer

Seek academic guidance as soon as you have a meaningful risk to the deadline, fair assessment or the group's ability to complete the work. You don't need to wait for the final evening or prove deliberate bad faith.

Check the course's rules first. Some modules use anonymous peer assessments, individual contribution statements or agreed dispute procedures. Others require a tutor to authorise any change of responsibilities. Carnegie Mellon's teaching guidance shows that group marks and individual contribution can be assessed in different ways. Your institution's actual rubric takes precedence over advice from the internet.

If it's safer to email privately rather than on behalf of the group, that's fine. Don't claim unanimous agreement if the group hasn't agreed. Make clear which parts you personally observed.

What to do if submission is in 48 hours

At this point your goal isn't the ideal group process. It's to protect the submission and get the right person involved. Check the brief, alert the tutor, identify the minimum remaining deliverable and work out what can realistically be done by the people who are available.

One important limit: don't invent someone else's contribution, sign off work you haven't checked or fabricate peer-review evidence to make the group look tidy. Academic integrity still matters when the deadline is awful.

Four different situations that need different responses

They are trying, but the work isn't usable. This may be a skills or communication problem rather than an effort problem. Offer a concrete example of what the assignment needs, identify a suitable smaller task or ask the tutor whether extra support is available. Redoing their section in secret prevents them from learning and leaves resentment unspoken.

They haven't responded at all. After a clear message and reasonable checkpoint, document the lack of response and contact the course team. Don't spend days guessing whether they're ignoring you on purpose.

They're contributing in ways you can't see. Research, coding, data cleaning, proofreading and presenting can be invisible when everyone looks only at the slide deck. Ask where the work lives and agree what constitutes a completed deliverable before claiming no contribution.

They're dealing with a serious personal difficulty. Be compassionate without making yourself responsible for resolving it. Encourage them to speak to the lecturer or student support team. The course may have processes for adjustments, extensions or alternative arrangements that classmates cannot authorise.

What if the group is excluding someone?

It's possible for a student to appear absent because meetings are organised at times they cannot attend, important decisions happen in a private friendship chat, or nobody gives them access to the current files. That's not the same as refusing to work.

Share meeting notes, agree accessible ways to contribute, provide resources in advance and create clear roles. If a group repeatedly changes plans without telling one member, it's not fair to later use that person's lack of participation as evidence against them.

Different students have paid work, long commutes, disabilities, caring duties or time-zone constraints. This doesn't remove the need to contribute, but it should affect how the team organises the work. The University of Michigan's guidance emphasises clear communication and selectively involving instructors when team conflict cannot be resolved inside the group.

How to divide a project fairly from the beginning

If the next group assignment hasn't gone wrong yet, five minutes of agreements can save a lot of uncertain late-night messaging.

A charter isn't a legal contract, and it doesn't give the group permission to penalise members unilaterally. It's simply a shared memory of agreements, especially helpful when people remember last week's meeting differently.

Choosing tools without creating another project

A shared document is often enough for a small writing assignment. Version history can show drafts and changes, but it doesn't measure thinking, research quality or off-document work. A simple shared task board can help larger projects, but only if everyone has access and can update it. A group chat is useful for quick questions, but decisions worth remembering should move into the shared project space.

Use your university's approved collaboration tools where required. Some students won't have paid accounts, reliable broadband, or the same devices. Fancy dashboards and persistent video calls can add barriers to a team that already has enough of them.

Calphii, our customisable browser focus space, can be useful for your personal side of a group assignment: keeping your next task visible, working on your section with notes nearby and getting through a Deep Focus session. It isn't a group grading system, shared document editor or a way to track a teammate. Your module's official systems remain the place for submissions and disputes.

What if you're the one who hasn't contributed?

It happens. You missed a meeting, froze because the task was unclear, had personal circumstances change, or kept intending to start until it felt embarrassing to reply. Avoiding the chat makes the problem bigger because the rest of the group can't make a plan.

Send something concrete: “I've been behind on my part and I should have said earlier. I can complete [specific smaller deliverable] by [time]. If that's too late, please tell me what would help most now. I'm also contacting the tutor about my circumstances.” Then do the thing you promised, or tell them before the checkpoint if you can't.

You don't have to share intimate details with classmates. If you need formal support, speak directly with the academic team. Taking responsibility and asking for help can exist in the same message.

How to handle peer assessment honestly

Some modules allow group members to rate each other's contribution. If yours does, use the criteria you were given. Distinguish quantity of work from quality, and communication from presence in every meeting. One person may have produced a difficult analysis in two sessions while another attended every call but delivered little.

Give evidence, not labels: “Completed the methods section by the agreed checkpoint and incorporated two rounds of feedback” or “Did not submit the agreed comparison section by the final review, despite follow-ups.” Avoid coordinated retaliation, invented percentages or grading by friendship.

You may still disagree with the outcome. Use the institution's review or appeal route if available; don't promise classmates that a lecturer will automatically reduce someone's grade. Those decisions are not yours to make.

Questions that usually come up after the first awkward message

The goal isn't a perfect group chat

A good outcome might be that the missing person catches up, that the group redistributes work with the tutor's approval, or that the teaching team puts an alternative assessment process in place. Sometimes relationships remain awkward. Not every project ends with a newfound love of group work.

What you can control is keeping the expectations visible, treating people as people, telling the truth about contributions and asking for help before the deadline collapses. That's a better way to protect both the assignment and the humans making it.

If a blank document is the obstacle on your own section, start with our guide to writing when you're stuck. If it's hard to protect working time around all the group messages, see how to return after interruptions.