Making the Request

  • I want to flag early that [deliverable] is at risk — here's what's causing the delay.
    Early warning with cause
    "I want to flag early that the API integration is at risk — the third-party documentation was incomplete and we've had to reverse-engineer several endpoints."
  • To deliver to the quality we'd agreed, I need [X] additional days.
    Framing the extension as a quality decision
    "To deliver the level of reliability we'd agreed, I need 3 additional days to complete the load testing."
  • I can hit the original deadline if we descope [feature] — is that acceptable?
    Offering a scope trade-off as an alternative
    "I can hit the original deadline if we descope the CSV export feature — is that acceptable for the first release?"
  • I should have flagged this sooner — I apologise for the late notice.
    Taking responsibility for late communication
    "I should have flagged this risk sooner — I apologise for the late notice and will aim to raise blockers earlier in future."

Proposing Solutions

  • Here's my revised plan: [deliverable] by [date], [deliverable] by [date].
    Presenting a concrete revised schedule
    "Here's my revised plan: the backend API by Thursday, integration tests by Monday."
  • I can prioritise [most critical part] and ship a partial solution by the original date.
    Offering a phased delivery
    "I can prioritise the core authentication flow and ship that by Friday — the advanced permissions module would follow the week after."
  • Would it help if I brought in [colleague] to parallelize the remaining work?
    Offering to add resource
    "Would it help if I brought in Lena to parallelise the testing — that could recover 2 days."

Phrases to Avoid

These common phrasings undermine your professionalism. Here are better alternatives.

Avoid "I can't do it by then."
Better "The current timeline is at risk — here's why and here are my proposed options."

"I can't" without context or alternatives sounds like a refusal. Always pair a problem with options.

Avoid "It's taking longer than expected."
Better "The integration complexity was higher than estimated because [specific reason] — I should have flagged this earlier."

"Taking longer than expected" is vague. Naming the specific cause demonstrates self-awareness and helps prevent recurrence.

Avoid "There were a lot of blockers."
Better "I was blocked by [specific issue] for [duration] — here's what I've done to unblock it."

"A lot of blockers" is a catch-all that lacks credibility. Specific blockers with resolution steps show you were active, not passive.

Practice Exercises

Choose the most professional or correct phrase for each scenario.

Frequently Asked Questions

What does "descope" mean?

"Descope" means to remove a feature or requirement from the current scope of work — often to protect the timeline or reduce complexity.

What is a "phased delivery"?

Phased delivery (or incremental delivery) splits work into stages. A minimum viable version ships first, with additional features delivered in follow-up phases.

What does "at risk" mean in project communication?

"At risk" means a deliverable or timeline may not be met — a formal early warning that something needs attention. Preferable to a last-minute miss.