Communicating Delays & Blockers ยท Lesson 1 of 3
Raising a delay early
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Say a task will be late as soon as you know, with the reason and your options. Early bad news is something people can plan around.
In your work
On Tuesday you realise a client's data import, due Wednesday, needs two more days because their spreadsheet is messier than expected. That morning you message the project lead with the reason, a new estimate and an option to deliver part of it on time.
What the UK rules say
- The BCS Code of Conduct asks IT professionals to work with due care and diligence, in their client's or company's best interests.
What to do
- Flag the risk when you first see it, not on the due date.
- Give the reason, a new estimate and what you need.
- Offer options, such as delivering part of it first.
Watch out for
- Waiting until you're certain, when it's too late to adjust.
- Vague updates like 'nearly there'.
In your organisation
How does your team flag delays: at stand-up, in a channel or on the ticket?
Your employer's own policies come first.
Sources
- BCS, BCS Code of Conduct (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
