Chapter 7 of 8 · 4 checks · 2 min
Handle a teammate who does not contribute
A teammate who stops contributing is one of the most common FYP problems. Act early, stick to facts, involve the supervisor and protect the project.
Talk to the teammate early, privately and without blameMust
Why it matters and how to check
When tasks start slipping, talk to the person within a week or two, not at the mid evaluation. There may be a reason you do not know about: illness, family responsibilities, a job, or feeling lost in the work.
Describe what you see factually, ask what is going on, and agree a concrete next step with a date. Check it is done: the conversation happened, and the agreed next step is written in the team notes.
Do
- Raise it within a week or two of tasks slipping
- Agree a specific task and date
Avoid
- Complaining in group chats instead of talking to them
- Waiting until the evaluation
Document missed tasks and agreements factuallyMust
Why it matters and how to check
Keep a factual record: the task, the owner, the due date, what happened, and any agreement made afterwards. The task board, meeting notes and contribution log already hold most of this.
Stick to facts, not opinions about the person's character. If the issue reaches the supervisor or a committee, a calm factual record is far more useful than a story. Check it is done: each missed task is visible on the board or in notes with dates.
Do
- Record tasks, due dates and outcomes
- Keep the tone factual and neutral
Avoid
- Personal attacks in notes or messages
Involve the supervisor if the problem continues after one agreed stepMust
Why it matters and how to check
If the agreed next step is missed, tell your supervisor, together with the teammate if possible. Bring the facts and what you have already tried. Supervisors handle these situations regularly and know the department's options, which may include individual marking, reassigning work or, in some departments, changes to the group.
Do this early in the semester. A supervisor who learns about the problem at the final evaluation has far fewer options. Check it is done: the supervisor has been informed in writing, with the facts and the date.
Do
- Inform the supervisor with facts and what you tried
- Follow the department's procedure for group issues
Avoid
- Covering for a non-contributing member until the end
Protect the project by reassigning critical work with the supervisor's agreementShould
Why it matters and how to check
If a must feature depends on a member who is not delivering, agree with the supervisor to reassign it or reduce the scope, rather than let the whole project slip. Record the change in meeting notes and the contribution log.
Keep the teammate informed and give them work they can realistically finish. The aim is a complete project and a fair record, not punishment. Check it is done: every must feature has an active owner and the reassignment is recorded.
Do
- Reassign critical work with the supervisor's agreement
- Record the change in notes and the log
Avoid
- Silently doing a teammate's work and saying nothing