Re: Deliverable Due Last Month - Status Check
79/100“I'm reaching out about the deliverable due on April 15. Since we're now comfortably into June, I wanted to check if there's been a calendar system malfunction I should be aware of.”
For when 'end of day' is treated as a suggestion, 'ASAP' means 'whenever you get around to it,' and project timelines are viewed as aspirational fiction. Hold people accountable with style.
“I'm reaching out about the deliverable due on April 15. Since we're now comfortably into June, I wanted to check if there's been a calendar system malfunction I should be aware of.”
“I've attached a spreadsheet tracking our last 12 project deadlines alongside actual delivery dates. I thought the data visualization might be... illuminating.”
“Absolutely, take all the time you need. I've preemptively pushed back the client delivery, my vacation, and possibly my retirement date to accommodate.”
“When we agreed to 'EOD Friday,' I wanted to confirm we're operating under the same definition. Specifically: this Friday. In the current calendar year. On planet Earth.”
Reference the original date agreed upon, note the impact of the delay, and request a new realistic timeline - all while maintaining level 4-5 diplomatic hostility.
Use level 3 'Concerned' to set expectations early. Reference past patterns without direct accusation: 'Given the timeline sensitivity, I wanted to confirm our alignment on the delivery date.'
Level 5-6 with documentation of all missed deadlines, original agreements, and business impact. CC relevant stakeholders 'for visibility.'