This tests your integrity and your ability to manage upward when a project is off track. Employers need project managers who will surface problems early instead of hiding them until the deadline.
Use a simple structure: give the headline bad news in one sentence, provide the evidence, then present options with a recommendation. Avoid burying the problem in a long update.
Start by naming the moment you knew the project would miss its target, because honesty in a status update begins before the meeting, in your own assessment. Say plainly that you scheduled a dedicated conversation rather than slipping the news into a routine report, and that you opened with the headline: the delivery date you had promised was no longer achievable. Then give the evidence, the specific cause, whether it was a dependency that failed, a resource gap, or a scope change, and show you had already quantified the impact in days or weeks. Present two or three options, each with a new date and a tradeoff, and state your recommendation with a reason. In a Philippine setting, keep the register direct but respectful, using "we" instead of "they" when describing the team's part, and avoid the Taglish hedging that softens the message. Expect the stakeholder to push back, so hold the line on the facts while staying open to their priorities. Close by confirming the decision and the next check-in, and say the result was that the sponsor thanked you for the early warning, the plan was reset, and the team avoided a last-minute scramble.
A common mistake is to soften the message too much with 'Medyo na-delay lang po tayo ng konti sir, pero kaya pa naman po siguro,' which leaves the sponsor with false confidence. Instead, say 'We are delayed by two weeks and the current date is not realistic. Here are three options with new dates and tradeoffs.'
Situation
In my previous role as a project coordinator at a logistics company, I was responsible for a system migration project that was due to go live in six weeks.
Task
I had to report to the project sponsor that our data validation had found a 12 percent error rate in migrated customer records, which meant the go-live date was no longer achievable.
Action
I scheduled a private briefing with the sponsor before the steering committee meeting and brought a one-page summary showing the error samples, the root cause, and three recovery options with revised dates. I clearly stated the risk of launching with dirty data and asked for a decision on the preferred recovery path instead of waiting for the meeting to surprise them.
Result
The sponsor approved a two-week delay and allocated one additional quality analyst. We re-ran the validation and went live with an error rate under one percent, and the sponsor later thanked me for the early warning.
Delivering bad news early with data and options preserves trust and gives decision makers room to act.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.