Reporting Vulnerabilities & Defects ยท Lesson 2 of 2
Reporting a bug honestly
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Report a defect accurately, even when it will delay a release. The people accountable need the full picture to decide what happens next.
In your work
The day before a charity's fundraising appeal launches, you find Gift Aid declarations aren't saving for some donors. You tell the project lead at once, with who's affected and the options, rather than hoping nobody notices.
What the UK rules say
- The BCS Code of Conduct says IT professionals must not misrepresent or hide information about how a system performs.
- It also asks them to accept professional responsibility for their work.
What to do
- Report it as soon as you're sure it's real, with evidence.
- Say who and what is affected, and how badly.
- Offer options: fix now, delay or release with a workaround.
Watch out for
- Downplaying a defect to protect the deadline.
- Fixing it quietly after release without telling anyone.
In your organisation
How does your team record known defects at release, and who decides whether to ship?
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.
