Agreement & confirmation — Unit 29, Pre-intermediate to Intermediate English

Last month, a simple communication error caused our team to miss the start of an important presentation. A colleague had sent a message saying the meeting was in Room 4. Without stopping to think, everyone **assumed** this was correct — nobody bothered to **check** the booking system. I did wonder whether the room was **right**, but I did not want to seem unhelpful by questioning it aloud.

When we arrived at Room 4 at nine o'clock, the room was already occupied by another department. Our colleague Marcus immediately **pointed out** that he had written Room 4B, not Room 4. This was a small but significant difference. "The meeting is in Room 4B, **isn't it**?" he said. Several people **agreed**, but others were **not sure** what they had understood from the original message.

We quickly moved to Room 4B and arrived seven minutes late. Our manager was calm but made an important observation afterwards. "**As far as I know**," she said quietly, "this is the third time a room booking has been **assumed** rather than properly **confirmed**. We need to **check** all venue details in advance from now on."

"**That's true**," several of us **agreed**. It is easy to **assume** that written instructions are always clear, but small ambiguities can cause real disruption. One colleague **disagreed** slightly, suggesting the original message had been unclear rather than incorrect. "**Exactly**," said Marcus — "the message was ambiguous, which is precisely why we all needed to **confirm** it before we left."

The lesson we learned was straightforward: never **assume** when you can quickly **check**. A simple confirmation reply — "Room 4B, **right**?" — takes only seconds but prevents significant confusion. **Confirming** even obvious details is always worth the effort, as any professional team will eventually discover.

There was a small change after that meeting, and it worked better than anything the manager said.

Marcus started ending every message that contained a detail with a question tag. "Room 4B, **isn't it**?" "Deadline is the 14th, **right**?" At first it looked slightly odd in writing. Within a month, three other people had copied it.

The reason it works is not politeness. A statement invites no reply, so silence is ambiguous — it might mean agreement and it might mean nobody read it. A tag question requires an answer, so silence becomes information: if nobody confirms, something is wrong.

We have not been late to a meeting since.

One of the team **disagreed**, incidentally. He said the habit makes people sound unsure of themselves. **That's true** in some settings, and I would not write to a client that way.

Inside a team, though, I would rather sound slightly unsure than be confidently in the wrong room.