Describe a team you have been part of: IELTS Cue Card Sample Answers (Band 7 and 8.5)

Describe a team you have been part of: cue card sample answers

A Band 7 and a Band 8.5 answer to the same card, what makes the second one score higher, and the Part 3 questions that follow, with short model answers.

In short: for “Describe a team you have been part of”, choose one real example in the first ten seconds and note a keyword for each bullet. Both sample answers below cover every bullet in about two minutes; the Band 8.5 one gets its extra marks from precise vocabulary, varied grammar and a fuller answer to the “explain” line rather than from extra length. Part 3 then moves to teamwork, cooperation and leadership.

The cue card

Describe a team you have been part of.

You should say:

  • what the team was
  • what it did
  • what your role was

And explain how you felt about being part of it.

You will have one minute to prepare and can make notes; then you speak for one to two minutes (IELTS on using the preparation time). This is a common practice topic, not a leaked or official exam card.

Example one-minute notes

Notes are keywords in the order you will speak, about one line per bullet. These match the sample answers below; use your own story.

Band 7 sample answer

283 words, about two minutes at a normal speaking pace. Read it as a transcript of someone talking, small slips included.

I want to talk about a team I was part of during my second year at university. It was a team for a hackathon, which is a competition where you have to build an app or a program in a very short time. Our hackathon was forty-eight hours, at IT Park in Tashkent, and there were four of us in the team.

We decided to make an app for public buses. The idea was that you can see when the next bus is coming, and also how crowded it is, because in Tashkent sometimes the buses are so full that you can't get in. Diyor was our main programmer, Sevara worked with the data, and Kamol did the technical part with the server.

My role was a little bit different. I'm not a very strong programmer, so I was responsible for the design of the app and for the presentation at the end. I made the screens, I wrote the text, and I presented our project to the judges. Honestly I was very nervous, because the judges were from big companies.

It was not always easy. On the second night, around three o'clock, we had a big argument, because the app didn't work and everybody was tired and blaming each other. But after some coffee we calmed down and fixed the problem together. In the end we got second place, which was a big surprise. I felt really proud to be part of this team. I learned that a team is not about everyone doing the same thing, but everyone doing their own part well. Also, we are still good friends, and we are planning to take part in another hackathon next year.

Band 8.5 sample answer

306 words. Same card, same two minutes.

The team that comes to mind is a group of four of us who entered a forty-eight-hour hackathon at IT Park in Tashkent during my second year at university. For anyone unfamiliar with the idea, a hackathon is essentially a race to build a working app from scratch over a weekend, with almost no sleep.

What we came up with was an app for city buses that would show you not just when the next bus was due, but how crowded it was likely to be, which, if you've ever tried to squeeze onto a number 67 at rush hour, is genuinely useful information. Diyor was our lead programmer, Sevara handled the data, and Kamol kept the server running.

My own role was a bit of an odd one. I'm a competent coder at best, so rather than slow everyone down, I took charge of the design and the final pitch. That meant mocking up every screen, writing the text, and then standing in front of a panel of judges from some fairly big tech companies, which, I'll admit, had me quite rattled.

It wasn't all smooth sailing. At around three in the morning on the second night, the app crashed completely, and the four of us had a proper falling-out, everyone exhausted and blaming everyone else. What saved us, oddly enough, was a ten-minute break and some terrible vending-machine coffee, after which we tracked the bug down together. We ended up taking second place, which none of us had expected.

Looking back, I felt more proud of that team than of almost anything I'd done alone. It taught me that a good team isn't four people doing the same job, but four people trusting each other with different ones. And the fact that we're still close, and already plotting next year's entry, says a lot.

Why the 8.5 answer scores higher

Examiners score Part 2 on four criteria. Here is where the second answer gains, criterion by criterion.

Fluency and coherenceBand 7 is logical and complete, though connections are basic ("But after some coffee", "Also"). Band 8.5 guides the listener ("For anyone unfamiliar with the idea", "What saved us, oddly enough") and ends the explain line with a neat reflection that links back to the roles described earlier.
Lexical resourceBand 7 uses "very nervous", "a big argument", "a big surprise". Band 8.5 chooses "had me quite rattled", "a proper falling-out", "tracked the bug down", "mocking up every screen", "took charge of", and the idiom "wasn't all smooth sailing", each fitting the setting.
Grammatical range and accuracyBand 7 has small issues such as "The idea was that you can see" (tense consistency) and a heavily repeated "we" + simple past pattern. Band 8.5 combines a relative clause with a conditional ("which, if you've ever tried to squeeze onto... is"), past perfect and a "not... but" contrast with ease.
PronunciationJudged from audio. The 8.5 answer requires the speaker to handle the long embedded sentence about the bus with clear pauses, stress "same job" versus "different ones" in the conclusion, and sound natural with fast phrases like "tracked the bug down".

Don't learn either answer by heart. Examiners are trained to spot memorised speech, and a recited answer usually sounds flat, which costs you on fluency and pronunciation. Take the structure and a few phrases, then tell your own story.

Useful phrases for this card

Part 3 questions and model answers

After the card, the examiner moves to broader questions on teamwork, cooperation and leadership. Part 3 answers should be longer than Part 1 answers: an opinion, a reason, and an example or a contrast.

Is it better to work alone or in a team?

It depends on the task. Creative or complex projects usually benefit from different skills and viewpoints, as long as people trust each other. But for focused work, like writing or detailed analysis, too many voices slow things down. Most jobs actually need both: independent work punctuated by team meetings to combine the results.

What makes a good team leader?

Above all, someone who makes others' jobs easier rather than just giving orders. A good leader sets a clear goal, matches people to tasks that suit them and steps in early when conflict starts. I'd also say they need to take the blame publicly when things go wrong and give the credit away when things go right.

Do schools in your country teach teamwork well?

Not especially. The system has traditionally focused on individual tests and memorising, so group work is often one strong student doing everything while the others watch. Some newer private schools and universities use proper project-based assessment, which is better. What's needed is grading that rewards how the team worked, not just the final product.

Why do conflicts happen in teams?

Usually because of unclear roles or unequal effort. If nobody knows who's responsible for what, people either duplicate work or leave gaps, and then blame each other. Tiredness and pressure make it worse, as in any deadline situation. Personality clashes matter too, but I think they're less common than simple confusion about expectations.

Common mistakes on this card

Practise it out loud

Reading a sample answer is not practice. Set a one-minute timer for notes, then answer aloud for two minutes. On BandCheck you can record your answer to this exact card and see a band for each of the four Speaking criteria, with pronunciation judged from your audio. To warm up with short questions first, use the free IELTS Speaking Part 1 practice tool or read Part 1 questions with Band 6 and Band 8 answers. For the full test (Parts 1, 2 and 3 as one spoken interview) try Live Speaking with Turna, our AI voice examiner (beta).

Frequently asked questions

Is this a real IELTS exam question for September–December 2026?

Nobody outside IELTS can promise that. IELTS does not publish its Speaking question pool. This is a common Part 2 topic from BandCheck's practice bank, chosen because cards about the same kind of people come up often. If you can talk about this one for two minutes, similar cards will feel familiar.

Should I memorise the Band 8.5 sample answer?

No. Use it to see what a higher band sounds like: the more precise words, the varied sentences, the way the “explain” part is developed. Then answer with your own story. A memorised answer usually sounds recited, and examiners can move you on or lower your fluency score.

How long should I speak on this cue card?

You get one minute to prepare and make notes, then speak for one to two minutes; the examiner stops you after two. Aim for the full two minutes, which is roughly 250–320 words at a natural pace.

Can I practise this card and get a band score?

Yes. The button below opens this card in BandCheck's Speaking practice. You record your answer in the browser and get a transcript, a band for Fluency & Coherence, Lexical Resource, Grammatical Range & Accuracy and Pronunciation (judged from your audio), and comments. Your first 2 checks are free; the band is an AI estimate, not an official result.

More cue cards about people

All cue cards about people · All IELTS Speaking cue cards · Previous card · Next card · IELTS Speaking checker

Answer “Describe a team you have been part of” out loud and get your band for each criterion.

Google sign-in · no card · works in the browser · first 2 checks free