The employer screens for stakeholder communication and accountability. A project manager must be able to deliver bad schedule news early and with a recovery plan, not hide the issue until it becomes worse.
Use a short STAR structure but emphasize the communication: what you told the client, when, and what options you gave. Focus on taking ownership, sharing root cause, and presenting a decision-ready recovery plan.
Start by owning the delay outright, because the first thing a client or sponsor listens for is whether you are deflecting or accountable. Say plainly that you informed them as soon as you saw the slippage, not at the last minute, and that you led with the revised date before the explanation. Explain the root cause in two or three sentences, whether it was a resource crunch, a vendor issue, or a scope change, and be honest if part of it was your team's estimation. Then move straight into the recovery plan, which should feel like a menu, not a monologue. Offer two or three concrete options, such as compressing the schedule by adding overtime, reducing non-critical scope, or shifting a deliverable, and state the impact of each on cost, quality, or the final date. Ask for a decision on the tradeoff you need, and confirm the new timeline in writing. In a Philippine workplace, keep the tone respectful but direct, and avoid the apologetic Taglish filler that sounds like you are begging for understanding. Instead, use a calm, professional register, and remember that DOLE rules around overtime and shift changes matter, so propose recovery actions that are compliant and realistic for your team, not just what sounds good to the client. End by summarizing the next check-in point so they know you are tracking the recovery, not just hoping for it.
Candidates often over-apologize with 'Sorry po, na-delay po kasi, gagawin po namin agad' and give no concrete plan. Instead state the revised date, the cause, and your recovery actions, and ask for a decision on any tradeoff you need.
Situation
In a previous role as a junior project manager at a BPO analytics company, a reporting automation project slipped six days after a data source change forced us to redo two integration modules.
Task
I needed to inform the client sponsor before the scheduled steering committee call and present a credible recovery plan without hiding the delay.
Action
I prepared a short status note with the root cause, impact to the milestone, and two recovery options. I called the sponsor first, explained the slip directly, and then proposed moving a non-critical dashboard enhancement out of phase one to recover four days. I followed up with a written RAID log update and a revised milestone plan.
Result
The sponsor approved the plan and later said the early transparent update preserved trust. The project delivered four days late but with full scope for phase two intact.
Early, direct communication about schedule slippage is what preserves client confidence.
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.