Everyday Echoes · Role Play · B2/C1 · 50 min

Giving a Statement

A delivery van, a cyclist, a screech, a crunch — over in four seconds, right in front of you. Nobody's badly hurt, but somebody's insurance will hang on what witnesses say. An officer opens her notebook: 'Talk me through what you saw.' Now the hard part: being accurate in a second language, about four seconds of chaos.

The Scene 🎬

The rarest kind of speaking: where the goal isn't to be interesting, persuasive or fluent — just precisely, boringly true.

You were waiting to cross by the bakery when it happened: a white delivery van turning right, a cyclist coming through, brakes, a shout, and a bike on the tarmac. The cyclist is up and swearing — shaken, scraped, alive. The van driver is pale. Traffic is stopped, and a police officer, PC Webb, is working through the bystanders.

Here's what nobody teaches you about being a witness: your brain has already written a story. It has decided who was at fault, filled the gaps with guesses, and stamped the whole thing "what I saw". The officer doesn't want the story — she wants the fragments you can actually stand behind: where you stood, what you saw first, what you heard, what you'd swear to and what you wouldn't. A witness who says "I can't swear to that part" is worth ten who are confident about everything.

And in a second language there's a quiet extra pressure: the temptation to simplify your account into something easier to say. Resist it. The phrases in this lesson exist so that precision never has to be sacrificed to grammar.

  1. Two honest people watch the same accident and report different things. How is that possible — and does it make them liars?
  2. When did you last say "I saw" about something you'd actually only concluded?
YouStood four metres away, saw most of it, heard all of it — and has already caught their own brain filling in gaps.
PC WebbPatient, practical, notebook out. Has taken a thousand statements and can smell a guess dressed as a fact from across the street.
First: read the conversation and underline every place You separates seeing from assuming. That separation — not the vocabulary — is what makes this a good statement.

Useful Phrases 🧰

Here's your toolkit. You don't need to memorise it. Read each phrase, say it out loud once, and pick the ones that sound like you. You'll have it open while you practise.

The shape of this conversation
1 · Offer to help2 · Say where you were3 · Separate fact from guess4 · Estimate carefully5 · Correct the record6 · Close
It's a map, not a script. Real conversations skip steps, repeat them and go off in new directions.
Cover it later, when you want to test yourself.

When you're the witness

🙋 Offer to help
"I saw it happen. Do you need a statement?"
"Let me start from the beginning."
📍 Say where you were
"I was standing about four metres away, so I had a clear view of the junction."
"I was waiting to cross by the bakery."
🤷 Separate fact from guess
"That's the bit I can't swear to."
"I assumed he had right of way because he was going straight on, but I didn't see it."
📏 Estimate carefully
"Roughly twenty. I couldn't give you an exact speed."
"It might have been a bit more, but I wouldn't like to say."
✏ Correct the record
"Sorry, that's not quite what I said. Can we change 'at speed'?"
"Could you read the whole thing back to me before I sign?"
🌟 Close
"If anything else comes back to me, who do I call?"
"He kept saying something like 'I didn't see you'. I'm sure about 'see'. The exact words, less so."

When you're the officer

"Can you tell me what you saw?"
"How far away were you?"
"Did you see who had right of way?"
"Let me read that back to you."
"I'll need you to sign here."

When something changes

"Could you repeat the question?"
"I'm not sure I saw that part."
"Could I see what you have written?"
"Do I need to come back?"

Whenever you need a moment, or you missed something

"Sorry, I didn't quite catch that. Could you say it again?"
"Do you mean…?"
"Just so I've got this right, you're saying…"
"Could you go a bit slower, please?"
"Give me a second to think."
"How do you say that in English? I mean…"

Speed round 🎯

Draw a card and say what you'd say, out loud, in one or two sentences. Use your own words or the toolkit. Then peek at one possible answer.

Press the button to start.

Done a few rounds? Try again with the toolkit covered. When it flows, you're ready to hear them in a real conversation.

The Conversation 💬

The pavement outside the bakery. The cyclist is being checked over; PC Webb turns to you.

PC WebbWere you here when it happened?
YouYes — I saw it happen. Do you need a statement?
PC WebbPlease. Take your time. Talk me through what you saw.
YouLet me start from the beginning. I was standing about four metres away, there — by the bakery door, waiting to cross. So I had a clear view of the junction.
PC WebbGood. Go on.
YouThe van was coming from my left, indicating right — I saw the indicator, that part I'm sure of. The cyclist was coming straight through the junction towards it. The van started its turn, and the cyclist braked hard and went down. The van stopped — I'd say half a second later.
PC WebbDid the van hit the bike, or did the cyclist come off braking?
YouHonestly — that's the bit I can't swear to. There was a bang, but I was watching the cyclist's face by then, not the wheels. It might have been the bike hitting the ground.
PC WebbThat's fine — better you say so. What about the cyclist's speed?
YouRoughly twenty, twenty-five maybe — I couldn't give you an exact speed. Quick, but not crazy. And I should be careful here: I assumed he had the right of way because he was going straight on — but I didn't see the light for his lane. I saw my crossing light, not his.
PC WebbNoted — that's an important distinction, thank you. Anything before the collision? Sound, shout, horn?
YouA shout — the cyclist, I think, though I couldn't say what he shouted. No horn. And brakes — I heard the van's brakes and the bike's at almost the same time. It all happened in a few seconds, honestly. Four, five at most.
PC WebbAnd after?
YouThe driver was out of the van very fast — first to reach the cyclist. He kept saying something like "I didn't see you". I'm sure about "see" — the exact words, less so.
PC WebbRight. *writing* So: witness positioned four metres east of the junction, clear view. Van indicating right, cyclist proceeding straight at speed—
YouSorry — that's not quite what I said. Can we change "at speed"? I said twenty-ish and not crazy. "At speed" sounds like I'm blaming him.
PC WebbFair. "At normal cycling speed, estimated twenty." Better?
YouMuch. Could you read the whole thing back to me before I sign? I want to be sure it says what I actually saw — not what I think I saw.
PC Webb*reads it back* …and that's everything. Sign here. You'd be surprised how few people listen to the read-back.
YouOne last thing — if anything else comes back to me tonight, who do I call? Things surface later sometimes.
PC WebbThey do. This number, that reference. And — genuinely — that was a useful statement. The "can't swear to it" parts most of all.

From memory — don't scroll back up.

  1. Which three things does You explicitly refuse to claim — and what makes each refusal valuable?
  2. You corrects the officer's notes once. What was the phrase, and why did it matter?
  3. What does You do before signing, and what does You arrange for afterwards?
1. Whether the van actually hit the bike ("that's the bit I can't swear to"); the cyclist's exact speed (an estimate, given as one); and the right of way — You saw their own crossing light, not the cyclist's lane, and says so. Each refusal marks the boundary between evidence and assumption, which is exactly what the statement is for.

2. "At speed" — the officer's summary had quietly hardened "twenty-ish, not crazy" into words that blamed the cyclist. Statements get written in someone else's words; correcting them is your right and your job.

3. Asks for the whole statement read back before signing — and gets a number and reference to call if anything else surfaces later, because memories do.

Your Turn 🎭

No script this time. You'll have a real conversation with a real person. They have their own mind, and you have a goal.

1 · Warm up your voice 🎤

Say each step once, out loud, in your own words. No writing, no peeking at the phrases.

  1. Offer to help. Say what you saw.
  2. Say where you were. Give your position and view.
  3. Separate fact from guess. Say clearly what you did and did not see.
  4. Estimate carefully. Be honest about uncertainty.
  5. Correct the record. Fix something that was written wrongly.
  6. Close. Offer to help later.

2 · The scene 🎬

Pick your situation. Your partner plays the other person.

Your card
Where
The situation
You have
You want
Your ruleStay precise and honest. A statement is not a story.
Who you're talking to

🏆 You win when the statement is accurate and you are comfortable signing it.

⏱ 4:00
Twist deck

🎲 Something changes

Start the scene first. Partway through, draw a card. Whatever it says, it just happened.

Nothing has changed yet.

3 · Swap seats 🔁

Now you're on the other side. Your partner takes your old part.

Your card
Who you areA police officer taking a statement. Invent your name.
Your methodOpen question first, then closed ones. Repeat back to check.
Your powerYou write down the statement and ask the witness to sign.
Your goalGet a statement that is precise and true.

Draw another twist whenever you like.

4 · Afterwards ✅

Tick what you actually did, in either seat.

Phrases I want to use next time

Go again

⚡ Same situation, harder

Run it one more time. Draw a twist before you start, and try to reach a good result faster than before.

The Echo 🕰️

In Salem, Massachusetts, in 1692, testimony killed people. Nineteen were hanged on the strength of what witnesses said they had seen — girls pointing across a courtroom, neighbours recalling spectres in doorways, assumption piled on assumption until it weighed as much as fact. Almost none of it was lying, which is the terrifying part. The witnesses believed themselves. Their stories had simply eaten their observations.

The turning point came when a few people began doing the modest thing this lesson teaches: separating what they knew from what they had concluded. Ministers who asked how, exactly, a spectre could be identified. Jurors who later signed a public confession that they had convicted "on evidence we now know we could not understand." The trials collapsed not through drama, but through the arrival of the question "what did you actually see?"

Your traffic statement will hang nobody. But it lives on the same blade: the space between witnessed and assumed is where other people's futures get decided — a licence, a claim, a job. "I can't swear to that part" is a small sentence. Salem is what the world looks like when nobody says it.

🕯️ Want the full story? The girls, the trials, and the jurors who took it back…Open →

Two bigger questions

  1. The Salem witnesses weren't lying — they were certain. Which is more dangerous in a witness: dishonesty, or sincere certainty?
  2. Where in modern life do we still convict on confident stories — and what would the "what did you actually see?" question change?