What to Do If a Team Member Doesn’t Do Their Part

If your teammate isn’t doing their work and the deadline is getting closer, you have more options than giving up or doing everything yourself. In this tutorial you’ll learn how to make sense of the situation, talk to the person, redistribute tasks and, if necessary, ask for help from the right people, without damaging the relationship or your own performance. We’ll start with what’s worth having at hand before you make a move.

Gather what you need before acting

Before bringing anything up with the group, you need information, not impressions. When you’re frustrated, it’s easy to say «they never do anything», and that phrase invites defensiveness. What helps is being able to point to concrete facts: what was agreed, who had each part and what has happened with it.

Gather these materials:

  • The assignment brief or the grading criteria, so you know what is expected of each person.
  • The agreed division of tasks, whether in a shared document, a chat or your notes from the last meeting.
  • A simple record of dates: when each part was due and what was actually received.
  • The message history where something was requested or promised, in case there are doubts about what was agreed.

If the group never put anything in writing, start by reconstructing it honestly: write down what you remember and check it with the others. Having this foundation keeps the conversation from turning into a clash of versions and lets you speak calmly and with facts.

Check whether there really is a workload problem

Not every delay is a lack of commitment. Before labeling someone as an irresponsible teammate, check whether the uneven split comes from a misunderstanding: maybe the task was ambiguous, maybe it depended on someone else finishing first, or maybe someone didn’t understand what they were supposed to deliver. A conflict over responsibilities usually starts with unclear instructions rather than bad intentions.

Ask yourself a few honest questions. Was the task defined with a concrete result and a date? Did that person have the information they needed? Did they flag a problem that nobody answered? Was their part really comparable in effort to everyone else’s? Sometimes you’ll discover the workload was poorly estimated from the start.

If, after reviewing everything, it’s still clear that someone hasn’t done what was agreed, you can move to action with a clear head. And if you find that part of the failure was organizational, you’ll have a fairer and far more productive conversation, because you’ll arrive acknowledging your share instead of accusing.

Talk to the person before going to anyone else

The first conversation should be direct and private. Posting a reproach in the group chat in front of everyone almost always causes embarrassment, and embarrassment pushes people to go quiet or argue, not to work. Suggest talking one-on-one, whether in person, on a call or in a well-written individual message.

A structure that works is to describe the fact, explain its effect and ask. For example: «The analysis section hasn’t arrived and the rest depends on it to move forward. What happened and how can we sort it out?». Notice that you’re not judging the person, you’re talking about the task. That final question opens the door for them to explain if they have a real difficulty, such as lack of time, doubts about the content or personal problems.

Really listen to the answer. If there is a reasonable cause, you can renegotiate. If there are only vague excuses, don’t get angry: move on to asking for a concrete commitment with a clear date. That commitment, spoken aloud or in writing, already changes the dynamic. To practice this kind of conversation, it helps to develop social skills for teamwork, especially listening and assertive communication.

Redefine tasks with small, verifiable goals

When someone has fallen behind, handing them a huge, vague task again tends to repeat the problem. It’s more effective to split it into parts that can be easily checked: an outline, a draft of one section, a list of sources. That way everyone sees the progress, and it’s easier for the person who is behind to get back into rhythm.

Each redefined task should include three elements: what is delivered, who delivers it and by when. Ideally, write it down somewhere the whole group can access. If the person has doubts about the content, offer a short support session or assign them a part they know better, because sometimes the block comes from not knowing where to start.

Also set intermediate review points, before the final date. A check halfway through lets you spot a new delay while there’s still room to react. This applies to every team member, not just the one who fell short: it makes follow-up a habit of the group rather than surveillance of one person.

Protect your own study time in the meantime

A common mistake when you end up with someone else’s work is leaving everything until the end and burning out, with your other subjects neglected. It’s wise to plan realistically what you can take on and what you can’t. Someone not delivering doesn’t oblige you to rescue them at the cost of your health or your overall performance.

Set aside defined work blocks for the part of the project that does depend on you. A simple way is to alternate focus and rest with the free pomodoro timer, which works directly in the browser and has buttons to start, reset and skip phases. Keep in mind that it doesn’t save your progress if you close the tab, so jot down what you complete on your own.

If you decide to cover a pending part so the deadline isn’t put at risk, do it consciously and say so: make it clear what you’re taking on, why, and that it’s a one-off measure. That way you avoid the rest of the group getting used to someone always making up for the missing work, and you keep an honest record of who contributed what.

Bring the issue to the group with a proposal, not a complaint

If the individual conversation changes nothing, it’s time to raise it with the whole team. Here the goal isn’t to point fingers, but to agree on rules that make the work fairer. Start by recalling the original split and mention which parts are pending, relying on the record you prepared at the beginning.

Bring concrete proposals instead of reproaches. You can suggest reviewing the pending tasks, setting checkpoints, agreeing on how an unexpected problem will be reported or deciding what happens if a part doesn’t arrive on time. When the group defines the rules, they’re easier to accept and easier to remember later.

Mind your tone and timing. Choose a meeting with plenty of time, without rushing, and let everyone speak, including the person concerned. If the team coordinates its contributions well, the final phase of the project will also be easier, especially when it comes to presenting group work in a coordinated way, where each part has to fit with the others.

Escalate the situation to the teacher with evidence and calm

If you’ve talked, redefined tasks and set rules, and the situation stays the same, informing whoever runs the course is a legitimate decision, not a betrayal. It’s best to do it as early as possible, while there’s still room to find a solution, and not on the day of the deadline, when all that’s left is to lament.

Prepare the message with the materials you gathered: the agreed split, the dates, the attempts to resolve it and the current state of the work. Explain the facts neutrally, without adjectives about your teammate, and state what you need: guidance, an adjustment to individual assessment or a guideline for moving forward. Ask how this is usually handled at your school, because the criteria vary.

If possible, it’s best for the whole group to sign the notice or, at least, for the person involved to know it is going to happen. Blindsiding them damages trust and can complicate the rest of the work. Transparency also protects you: it shows you acted with judgment and in good faith.

Close the project and learn for the next one

Once the work is handed in, take a while to review what happened. A brief group reflection on what worked and what didn’t turns a bad time into learning. Ask yourselves when the problem was detected, what signs appeared earlier and what would have helped you react sooner.

Draw out rules for future groups: define tasks with clear results from day one, put the split in writing, schedule intermediate reviews and agree on how unexpected problems are communicated. These habits greatly reduce the risk of a conflict over responsibilities coming back, even with new teammates.

If the experience left a bad taste, don’t turn it into a permanent label on anyone. People change from one project to the next, and you can also improve the way you coordinate. What you take away is a more mature way of dividing work, communicating and holding people accountable without losing respect.

When a group project goes off track, act early, with facts in writing, talking to the person first and leaving the more drastic measures for last: the sooner it’s clear who does what, the less energy it will cost you to keep the project going.

Frequently asked questions

What material should I keep as evidence if the problem reaches the teacher?

Keep the agreed division of tasks, the messages where dates or commitments were set, the versions of the shared document with its history and a short note on the attempts to resolve it. They should be verifiable facts, not opinions.

What if my teammate says they will work but never delivers?

Replace promises with measurable commitments: a small deliverable, a date and a review point. If that first commitment isn’t met, you already have an objective fact to bring to the group and, if necessary, to the teacher.

Is it fair for me to cover their part so the quality of the work doesn’t drop?

It can be a one-off solution if it works for you, but it shouldn’t become the norm. Say that you’re doing it as an exception, keep a record of who contributed what and avoid letting it repeat without the group knowing.

How do I avoid coming across as bossy or as a snitch?

Rely on group agreements rather than your personal judgment. If the team decides the rules and checkpoints, you’re only reminding them of what was agreed. And when you inform the teacher, do it with facts, transparently and without adjectives.

Similar Posts