The 60-Second Status Update Script
The Formula That Executives Actually Want to Hear
Why Most Status Updates Fail
Here's what executives hear when you give a typical status update: 'blah blah blah technical detail blah blah blah we're working on it blah blah blah.' They're not listening because you're not speaking their language. They want three things: Where are we? What's the risk? What do you need? Everything else is noise. This 4-part formula gives them exactly that—in 60 seconds or less.
The STAR Formula
S = Status (10 seconds)
Lead with the headline. Are you on track, at risk, or blocked? Don't bury the lead in details—executives want the bottom line first.
Wrong:
"So we've been working on the integration and there have been some challenges with the API documentation and we're trying to work through them..."
Right:
"Project X is on track for the March 15 delivery."
Why it matters:
The executive now knows the most important thing. Everything else is context.
Action Item:
Start every status update with ONE sentence that answers: 'Are we on track?'
T = Timeline (15 seconds)
Give the key milestones—what's done, what's next, and when. Use dates, not vague timeframes.
Wrong:
"We finished the first phase recently and we're working on the next part now. It should be done soon."
Right:
"Phase 1 completed last Friday. Phase 2 starts Monday and delivers March 1. Final delivery March 15."
Why it matters:
Specific dates show you have control. Vague timelines signal uncertainty.
Action Item:
Always have three dates ready: last milestone, next milestone, final delivery.
A = At Risk (20 seconds)
Proactively flag anything that could derail the project. If nothing's at risk, say so clearly. If something is, name it and your mitigation plan.
Wrong:
"Well, there are a few things we're keeping an eye on... the vendor might be late and there's a resource question..."
Right:
"One risk: the vendor API documentation is incomplete. Mitigation: I've scheduled a call with their team Thursday to resolve."
Why it matters:
Executives respect people who see problems coming. They lose trust in people who get surprised.
Action Item:
Before every status meeting, ask yourself: 'What could go wrong this week?'
R = Request (15 seconds)
End with what you need—a decision, resource, or just acknowledgment. If you need nothing, say that too.
Wrong:
"So yeah, that's where we are... any questions? I guess we'll just keep going..."
Right:
"I need one thing from you: approval to bring in a contractor for two weeks. That keeps us on schedule."
Why it matters:
Clear requests get clear answers. Vague endings get forgotten.
Action Item:
End every status update with 'I need...' or 'No blockers—we're good to continue.'
The Complete 60-Second Script
Here's how it sounds when you put it all together: 'Project X is on track for the March 15 delivery. [STATUS] Phase 1 completed last Friday. Phase 2 starts Monday and delivers March 1. Final delivery March 15. [TIMELINE] One risk: the vendor API documentation is incomplete. Mitigation: I've scheduled a call with their team Thursday to resolve. [AT RISK] I need one thing from you: approval to bring in a contractor for two weeks. That keeps us on schedule. [REQUEST]' Total time: 45 seconds. Total confidence: 100%.
Robert Cushman
I help Latin American tech professionals communicate with executive-level confidence so they can close bigger contracts, command premium rates, and advance their international careers.
After coaching 200+ professionals from Smarttie, Grupo Kopar, Terramar Brands, and Sourceability, I know that what separates good from great in high-pressure meetings isn't vocabulary—it's leadership communication.