# Status Note for a Delayed Project: Say It Early, Say It Plainly

> A practical guide for founders and owners on writing status notes for delayed projects — surface the gap between plan and fact early, without spin, and ask for the decision you need.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-10-28
- Updated: 2026-10-28
- Source: https://aiadvisoryboard.me/blog/status-note-delayed-project-say-it-early-plainly

I have read too many status notes that describe a delay without actually saying the project is late. Founders of 30-500 person companies tell me they find out about slippage only when a deadline has already passed, and by then the gap between plan and fact is too wide to close cheaply.

## TL;DR
- A delayed project status note belongs to the owner, not the team.
- Say it early: surface the delay before the owner asks.
- Say it plainly: state the new date, the cause, and the recovery step.

### Definition: Status note
A short, written update that tells a leader where a project stands relative to its last committed date, without narrative padding.

### Definition: Plan → Fact → Gap
The operating taxonomy owners use to see reality: what was promised (Plan), what actually happened (Fact), and the difference between them (Gap).

## What a Status Note for a Delayed Project Actually Is
A status note for a delayed project is not a progress report. It is an exception report. Its only job is to tell the owner that the committed date will not be met, why, and what happens next.

Owners of 30-500 person companies do not need color. They need signal. A status note that buries the delay in paragraph three is worse than no note at all, because it creates false confidence while the gap widens.

> **Tool tip (AiAdvisoryBoard.me):** When you surface a delay, write it as Plan → Fact → Gap. Plan: ship the vendor integration by June 10. Fact: the API documentation arrived three days late, and the build is still in QA. Gap: four working days. That structure tells the owner exactly where control was lost, without asking them to read between the lines. See how the 7-day diagnostic surfaces these gaps automatically: https://aiadvisoryboard.me/?lang=en

## When to Send It
Send the note the moment you know the date will slip — not when the date arrives and passes.

Early means before the owner’s Monday review, before the client asks, and before downstream teams start re-planning around a date that no longer exists. If you wait until Friday to say something was due Thursday, you have already cost the company recovery time.

Plainly: if a milestone is at risk, the status note goes out the same day the risk becomes a certainty.

## What to Include (Copy/Paste Template)

```markdown
# Project Status — [Project Name]

**Owner:** [Name]
**Committed date:** [Original date]
**Status:** Delayed
**New expected date:** [Revised date]

## Gap
[One sentence: what was supposed to happen vs. what actually happened]

## Cause
[One sentence: the root constraint — people, process, tooling, or dependency]

## Impact
[Who is blocked, and what slips next if this date holds]

## Recovery step
[The one action being taken this week to close the gap]

## Decision needed from owner
[Yes/no, resource, or scope trade-off — or “none”]
```

If you cannot fill the “Decision needed” line, you are writing a status update, not a status note. A status note asks for something specific, even if that something is just acknowledgment.

## Good vs Bad Examples

**Bad:** “We’re making good progress on the integration. Some minor blockers with the vendor’s API have appeared, but the team is working through them and we should be close to done soon.”

**Good:** “The vendor integration committed for June 10 will slip to June 17. Their API documentation arrived late, pushing QA by four days. The frontend team is blocked on the endpoint. I need a decision today: accept the June 17 date, or reduce scope to read-only access for now.”

The bad version sounds like work is happening. The good version tells the owner the project is late, why, what is blocked, and what decision is required.

## Manager Scan (2-Minute Digest Example)

- Project: Customer portal migration — committed May 22, now June 5 (Gap: 10 business days)
- Cause: dependency on third-party SSO provider; no internal workaround
- Impact: sales onboarding for three pilot clients moves to July
- Recovery: internal team builds fallback auth; decision needed from owner by EOD today
- Next check-in: June 2

This is the layer an owner can scan across five projects and immediately see where their attention is required. It is not micromanagement; it is visibility without meetings.

## Micro-Case (What Changes After 7–14 Days)

A founder of a 120-person logistics company used to learn about project delays during Friday standups, when a team lead would say “we’re almost there” and the date would quietly move again. After switching to plain status notes with a required “decision needed” line, the founder began receiving delay notices on Tuesdays instead of Fridays. Within two weeks, the average time from slip-to-decision dropped from nine days to two. The team stopped treating dates as suggestions, and the founder stopped discovering crises in weekend email.

> **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

## FAQ

**Should I send a status note if I already told the owner in a meeting?**
Yes. Verbal updates disappear from memory and inboxes. A written note creates a record the owner can forward, file, or act on without scheduling another call.

**What if I don’t know the new date yet?**
Say that. “We do not have a reliable new date yet; we will have one by Thursday after the vendor call.” An honest unknown is better than a fabricated date.

**Does this apply to internal projects, or only client work?**
Both. Internal delays compound just as quietly, and they often cost more because nobody is paying for the slippage.

**How is this different from a daily standup?**
A standup is for the team to coordinate. A status note is for the owner to see reality. They serve different audiences and should not be confused.

## Conclusion

A delayed project does not get better with silence. It gets more expensive. The moment you know a date will slip, write the note: say it early, say it plainly, and end with the decision you need.

Start today: pick the one project that is already late, and send the owner a status note using the template above before the end of the day.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works: https://aiadvisoryboard.me/?lang=en

---

When citing, link to https://aiadvisoryboard.me/blog/status-note-delayed-project-say-it-early-plainly. More articles: https://aiadvisoryboard.me/blog