How to Give an Update When There's No Progress

The Update You're Dreading

It's Monday. Time for your status update.

The problem: You have nothing to report.

You've been blocked all week. Or waiting on someone else. Or the project is on hold.

What you want to say: "No update. Nothing changed."

What you're afraid of: "They'll think I'm not working. They'll think I'm useless."

So you either:

Make something up
Stay silent and hope they don't ask
Give a vague non-answer

None of these work.

Here's how to give a meaningful update even when nothing has progressed.

Why "No Update" Makes You Look Bad

It Suggests You're Not Engaged

When you say "no update":

People think:

"Are they even working on this?"
"Do they care?"
"Are they waiting around doing nothing?"

Even if you're blocked, "no update" sounds like disengagement.

It Doesn't Explain What's Happening

"No update" tells them:

Nothing

They still don't know:

Why there's no progress
What's blocking you
When you expect progress
What you're doing about it

Silence creates assumptions (usually bad ones).

You Miss the Chance to Get Help

If you're blocked and don't say so:

Nobody knows to help you
The block continues
You stay stuck

A good update about blockers gets them removed.

What to Report When There's No Progress

Template #1: The Blocked Update

Structure: "No progress this week due to [blocker]. [What you're doing about it]. Expected to resume [when]."

Example:

✅ "Status: No progress this week on the API integration.

Blocker: Waiting on security review approval, which is taking longer than expected.

Action: I followed up with security team yesterday. They're finishing another high-priority review first and expect to get to ours by Wednesday.

Next: Will resume integration work as soon as approval comes through. In the meantime, I'm working on documentation so we're ready to move fast once unblocked."

Why this works:

Explains WHY no progress
Shows you're actively managing the blocker
Gives timeline expectation
Shows you're still productive (working on docs)

Template #2: The Waiting Update

Structure: "Waiting on [dependency from X]. Followed up [when]. Using this time to [productive activity]."

Example:

✅ "Status: Waiting on design mockups from the design team before I can start implementation.

Follow-up: Checked in with Sarah on Friday—designs will be ready by Tuesday.

Meanwhile: I've set up the project structure, written the data models, and created test cases so I can hit the ground running when designs arrive."

Why this works:

Clear about dependency
Shows you're tracking it
Demonstrates you're using time productively
Ready to move fast when unblocked

Template #3: The On-Hold Update

Structure: "Project on hold pending [decision/event]. [What's needed to resume]. [How you're preparing]."

Example:

✅ "Status: Project remains on hold pending leadership decision on Q1 budget priorities.

What's needed: Leadership team meeting scheduled for next Thursday to finalize priorities.

Prep work: I've completed the technical spec and resource plan so we can start immediately if approved. Also identifying which parts could be done with reduced budget if needed."

Why this works:

Explains the hold
Timeline for decision
Shows you're prepared to move quickly
Thinking ahead about alternatives

Real Examples: Wrong vs Right

Scenario: Blocked by Another Team

❌ WRONG

Manager: "What's the status on the customer dashboard?"

You: "No update. Still waiting on data team."

What's wrong:

No detail about the blocker
No indication you're managing it
Sounds passive
Manager doesn't know what to do with this info

✅ RIGHT

Manager: "What's the status on the customer dashboard?"

You: "I'm blocked waiting on the data schema from the data team. They originally said last Monday but got pulled into a production fire. I spoke with their manager yesterday—new ETA is this Wednesday. Once I have the schema, it's 2-3 days of work to complete the dashboard.

In the meantime, I've built the frontend components with mock data so integration will be quick when the schema arrives."

What's right:

Specific about blocker
Explains why it's delayed
Shows you're actively tracking it
Timeline for when work resumes
Demonstrates productive use of time
Manager knows exactly what's happening

Scenario: Waiting on Client Input

❌ WRONG

You (in Slack): "No progress—still waiting on client."

What's wrong:

Passive voice
No follow-up indicated
Looks like you're just sitting around

✅ RIGHT

You (in Slack): "Status: Waiting on client feedback on designs.

Follow-up: I sent reminder on Monday. If no response by Thursday, I'll schedule a call to walk through the designs directly and get live feedback.

Alternative plan: If we can't get feedback by next week, I recommend we proceed with Version A based on prior discussions and iterate after launch."

What's right:

Specific about what you're waiting for
Shows proactive follow-up
Has a backup plan if client doesn't respond
Taking ownership, not just waiting

How to Frame Different Types of "No Progress"

Blocked by External Dependency

✅ "Blocked waiting on [X from Y]. I've followed up [when] and expect it by [date]. Using this time to [productive activity]."

Shows: You're managing it, not just waiting.

Blocked by Decision/Approval

✅ "Paused pending [decision] from [who]. That decision is expected [when]. I've prepared [deliverables] so we can move immediately once approved."

Shows: You're ready to execute when cleared.

Blocked by Technical Issue

✅ "Stuck on [technical problem]. I've tried [approaches]. Reaching out to [expert/team] for input. If no solution by [date], will implement [alternative approach]."

Shows: You're troubleshooting actively and have a backup plan.

Project Deprioritized

✅ "Project is on hold per [decision/meeting]. It's been moved to [timeframe]. In the meantime, I've documented everything so we can pick up quickly when it's reprioritized."

Shows: You're organized and ready when it resumes.

What to Do While You're Blocked

Use the Time Productively

Instead of sitting idle, work on:

✅ Documentation ✅ Testing infrastructure ✅ Refactoring/cleanup ✅ Learning/research ✅ Other projects ✅ Prep work for when unblocked

Then report this in your update: "While blocked on X, I completed Y and Z."

Actively Manage the Blocker

Don't just wait. Take action:

✅ Follow up with blocking party ✅ Escalate if needed ✅ Identify alternative approaches ✅ Find workarounds ✅ Document the impact of delay

Show you're pushing to get unblocked.

How to Ask for Help in Your Update

Make the Ask Clear

Vague: ❌ "I'm blocked on X. Let me know if you have any ideas."

Clear: ✅ "I'm blocked on X. Could you help by [specific action]? This would unblock me by [date]."

Examples:

✅ "Could you escalate with the data team to prioritize the schema?" ✅ "Can you approve the vendor selection so I can proceed?" ✅ "Would you make the decision on approach A vs B so I can start implementation?"

Specific asks get action.

How Often to Update When Nothing's Changing

Regular Cadence Still Matters

Even when blocked, maintain regular updates:

✅ Weekly: "Still blocked on X. Here's the latest..." ✅ Bi-weekly: "No change—still waiting on Y. I'll update again when..."

Why:

Shows you're still engaged
Keeps blocker visible
Prevents "whatever happened to that project?"

Update When Status Changes

Even if no progress:

✅ "Still blocked, but now we have a timeline..." ✅ "Still waiting, but I've found a potential workaround..." ✅ "Still on hold, but I've completed the prep work..."

Any status change = worth updating.

Special Situations

When You're Blocked for Weeks

Long blocks need more detailed updates:

✅ "Week 3 blocked on legal review.

What's happening: Legal is working through contract terms with vendor. Complex negotiation around data privacy clauses.

Timeline: Legal expects resolution in next 2 weeks.

Plan: I've prepared two implementation approaches—one for each possible legal outcome—so we can move immediately when contract is signed.

Alternative: If this extends beyond 2 more weeks, I recommend we consider Vendor B as backup option."

Shows:

You're tracking it closely
You're prepared for either outcome
You have a backup plan
You're thinking strategically

When You're Waiting on Your Manager

Delicate situation:

✅ "Waiting on decision about [X] so I can proceed. We discussed this on [date] and you mentioned you'd decide by [date]. Let me know when you'd like me to move forward."

Why this works:

Reminds them without sounding pushy
References previous conversation
Gives them graceful out
Professional nudge

When the Entire Project Is Cancelled

✅ "Project cancelled per [meeting/decision]. I've documented all work completed and learnings for potential future reference. Moving to [next project] as of today."

Shows:

You're aware of the decision
You've closed it out professionally
You're already moving forward

The "No Update" Template Library

Copy-Paste Templates for Common Situations

Waiting on another team:

"Waiting on [deliverable] from [team], ETA [date]. I've followed up [when]. Using this time to [prep work]."

Technical blocker:

"Stuck on [technical issue]. I've tried [approaches]. Reaching out to [resource] for input. Backup plan is [alternative]."

Decision blocker:

"Paused pending decision on [topic]. Decision expected [when]. I've prepared [deliverables] for immediate execution once approved."

External dependency:

"Blocked on [vendor/client]. Followed up [when]. If no response by [date], will [alternative action]."

The 4 Tests for "No Progress" Updates

Before sending an update when nothing has progressed:

1. SIGNAL: Am I explaining WHY there's no progress?

Specific blocker? Or just "no update"?

2. OPPORTUNITY: Am I showing what I'm doing about it?

Active management? Or passive waiting?

3. RISK: Am I asking for help if needed?

Clear ask? Or suffering in silence?

4. AFFECT: Do I sound engaged or checked out?

Actively managing? Or just going through motions?

Check Your Status Update

Not sure if your "no progress" update is effective?

Analyze it free with 4Angles →

Write out your update. See how it scores on:

SIGNAL (Are you explaining the situation clearly?)
OPPORTUNITY (Are you showing active management?)
RISK (Are you asking for help if needed?)
AFFECT (Do you sound engaged?)

Get specific guidance on status updates.

No signup required. Just instant analysis.

The Update You're Dreading

It's Monday. Time for your status update.

The problem: You have nothing to report.

You've been blocked all week. Or waiting on someone else. Or the project is on hold.

What you want to say: "No update. Nothing changed."

What you're afraid of: "They'll think I'm not working. They'll think I'm useless."

So you either:

Make something up
Stay silent and hope they don't ask
Give a vague non-answer

None of these work.

Here's how to give a meaningful update even when nothing has progressed.

Why "No Update" Makes You Look Bad

It Suggests You're Not Engaged

When you say "no update":

People think:

"Are they even working on this?"
"Do they care?"
"Are they waiting around doing nothing?"

Even if you're blocked, "no update" sounds like disengagement.

It Doesn't Explain What's Happening

"No update" tells them:

Nothing

They still don't know:

Why there's no progress
What's blocking you
When you expect progress
What you're doing about it

Silence creates assumptions (usually bad ones).

You Miss the Chance to Get Help

If you're blocked and don't say so:

Nobody knows to help you
The block continues
You stay stuck

A good update about blockers gets them removed.

What to Report When There's No Progress

Template #1: The Blocked Update

Structure: "No progress this week due to [blocker]. [What you're doing about it]. Expected to resume [when]."

Example:

✅ "Status: No progress this week on the API integration.

Blocker: Waiting on security review approval, which is taking longer than expected.

Action: I followed up with security team yesterday. They're finishing another high-priority review first and expect to get to ours by Wednesday.

Next: Will resume integration work as soon as approval comes through. In the meantime, I'm working on documentation so we're ready to move fast once unblocked."

Why this works:

Explains WHY no progress
Shows you're actively managing the blocker
Gives timeline expectation
Shows you're still productive (working on docs)

Template #2: The Waiting Update

Structure: "Waiting on [dependency from X]. Followed up [when]. Using this time to [productive activity]."

Example:

✅ "Status: Waiting on design mockups from the design team before I can start implementation.

Follow-up: Checked in with Sarah on Friday—designs will be ready by Tuesday.

Meanwhile: I've set up the project structure, written the data models, and created test cases so I can hit the ground running when designs arrive."

Why this works:

Clear about dependency
Shows you're tracking it
Demonstrates you're using time productively
Ready to move fast when unblocked

Template #3: The On-Hold Update

Structure: "Project on hold pending [decision/event]. [What's needed to resume]. [How you're preparing]."

Example:

✅ "Status: Project remains on hold pending leadership decision on Q1 budget priorities.

What's needed: Leadership team meeting scheduled for next Thursday to finalize priorities.

Prep work: I've completed the technical spec and resource plan so we can start immediately if approved. Also identifying which parts could be done with reduced budget if needed."

Why this works:

Explains the hold
Timeline for decision
Shows you're prepared to move quickly
Thinking ahead about alternatives

Real Examples: Wrong vs Right

Scenario: Blocked by Another Team

❌ WRONG

Manager: "What's the status on the customer dashboard?"

You: "No update. Still waiting on data team."

What's wrong:

No detail about the blocker
No indication you're managing it
Sounds passive
Manager doesn't know what to do with this info

✅ RIGHT

Manager: "What's the status on the customer dashboard?"

In the meantime, I've built the frontend components with mock data so integration will be quick when the schema arrives."

What's right:

Specific about blocker
Explains why it's delayed
Shows you're actively tracking it
Timeline for when work resumes
Demonstrates productive use of time
Manager knows exactly what's happening

Scenario: Waiting on Client Input

❌ WRONG

You (in Slack): "No progress—still waiting on client."

What's wrong:

Passive voice
No follow-up indicated
Looks like you're just sitting around

✅ RIGHT

You (in Slack): "Status: Waiting on client feedback on designs.

Follow-up: I sent reminder on Monday. If no response by Thursday, I'll schedule a call to walk through the designs directly and get live feedback.

Alternative plan: If we can't get feedback by next week, I recommend we proceed with Version A based on prior discussions and iterate after launch."

What's right:

Specific about what you're waiting for
Shows proactive follow-up
Has a backup plan if client doesn't respond
Taking ownership, not just waiting

How to Frame Different Types of "No Progress"

Blocked by External Dependency

✅ "Blocked waiting on [X from Y]. I've followed up [when] and expect it by [date]. Using this time to [productive activity]."

Shows: You're managing it, not just waiting.

Blocked by Decision/Approval

✅ "Paused pending [decision] from [who]. That decision is expected [when]. I've prepared [deliverables] so we can move immediately once approved."

Shows: You're ready to execute when cleared.

Blocked by Technical Issue

✅ "Stuck on [technical problem]. I've tried [approaches]. Reaching out to [expert/team] for input. If no solution by [date], will implement [alternative approach]."

Shows: You're troubleshooting actively and have a backup plan.

Project Deprioritized

✅ "Project is on hold per [decision/meeting]. It's been moved to [timeframe]. In the meantime, I've documented everything so we can pick up quickly when it's reprioritized."

Shows: You're organized and ready when it resumes.

What to Do While You're Blocked

Use the Time Productively

Instead of sitting idle, work on:

✅ Documentation ✅ Testing infrastructure ✅ Refactoring/cleanup ✅ Learning/research ✅ Other projects ✅ Prep work for when unblocked

Then report this in your update: "While blocked on X, I completed Y and Z."

Actively Manage the Blocker

Don't just wait. Take action:

✅ Follow up with blocking party ✅ Escalate if needed ✅ Identify alternative approaches ✅ Find workarounds ✅ Document the impact of delay

Show you're pushing to get unblocked.

How to Ask for Help in Your Update

Make the Ask Clear

Vague: ❌ "I'm blocked on X. Let me know if you have any ideas."

Clear: ✅ "I'm blocked on X. Could you help by [specific action]? This would unblock me by [date]."

Examples:

Specific asks get action.

How Often to Update When Nothing's Changing

Regular Cadence Still Matters

Even when blocked, maintain regular updates:

✅ Weekly: "Still blocked on X. Here's the latest..." ✅ Bi-weekly: "No change—still waiting on Y. I'll update again when..."

Why:

Shows you're still engaged
Keeps blocker visible
Prevents "whatever happened to that project?"

Update When Status Changes

Even if no progress:

✅ "Still blocked, but now we have a timeline..." ✅ "Still waiting, but I've found a potential workaround..." ✅ "Still on hold, but I've completed the prep work..."

Any status change = worth updating.

Special Situations

When You're Blocked for Weeks

Long blocks need more detailed updates:

✅ "Week 3 blocked on legal review.

What's happening: Legal is working through contract terms with vendor. Complex negotiation around data privacy clauses.

Timeline: Legal expects resolution in next 2 weeks.

Plan: I've prepared two implementation approaches—one for each possible legal outcome—so we can move immediately when contract is signed.

Alternative: If this extends beyond 2 more weeks, I recommend we consider Vendor B as backup option."

Shows:

You're tracking it closely
You're prepared for either outcome
You have a backup plan
You're thinking strategically

When You're Waiting on Your Manager

Delicate situation:

✅ "Waiting on decision about [X] so I can proceed. We discussed this on [date] and you mentioned you'd decide by [date]. Let me know when you'd like me to move forward."

Why this works:

Reminds them without sounding pushy
References previous conversation
Gives them graceful out
Professional nudge

When the Entire Project Is Cancelled

✅ "Project cancelled per [meeting/decision]. I've documented all work completed and learnings for potential future reference. Moving to [next project] as of today."

Shows:

You're aware of the decision
You've closed it out professionally
You're already moving forward

The "No Update" Template Library

Copy-Paste Templates for Common Situations

Waiting on another team:

"Waiting on [deliverable] from [team], ETA [date]. I've followed up [when]. Using this time to [prep work]."

Technical blocker:

"Stuck on [technical issue]. I've tried [approaches]. Reaching out to [resource] for input. Backup plan is [alternative]."

Decision blocker:

"Paused pending decision on [topic]. Decision expected [when]. I've prepared [deliverables] for immediate execution once approved."

External dependency:

"Blocked on [vendor/client]. Followed up [when]. If no response by [date], will [alternative action]."

The 4 Tests for "No Progress" Updates

Before sending an update when nothing has progressed:

1. SIGNAL: Am I explaining WHY there's no progress?

Specific blocker? Or just "no update"?

2. OPPORTUNITY: Am I showing what I'm doing about it?

Active management? Or passive waiting?

3. RISK: Am I asking for help if needed?

Clear ask? Or suffering in silence?

4. AFFECT: Do I sound engaged or checked out?

Actively managing? Or just going through motions?

Check Your Status Update

Not sure if your "no progress" update is effective?

Analyze it free with 4Angles →

Write out your update. See how it scores on:

SIGNAL (Are you explaining the situation clearly?)
OPPORTUNITY (Are you showing active management?)
RISK (Are you asking for help if needed?)
AFFECT (Do you sound engaged?)

Get specific guidance on status updates.

No signup required. Just instant analysis.

How to Give an Update When There's No Progress

The Update You're Dreading

Why "No Update" Makes You Look Bad

It Suggests You're Not Engaged

It Doesn't Explain What's Happening

You Miss the Chance to Get Help

What to Report When There's No Progress

Template #1: The Blocked Update

Template #2: The Waiting Update

Template #3: The On-Hold Update

Real Examples: Wrong vs Right

Scenario: Blocked by Another Team

❌ WRONG

✅ RIGHT

Scenario: Waiting on Client Input

❌ WRONG

✅ RIGHT

How to Frame Different Types of "No Progress"

Blocked by External Dependency

Blocked by Decision/Approval

Blocked by Technical Issue

Project Deprioritized

What to Do While You're Blocked

Use the Time Productively

Actively Manage the Blocker

How to Ask for Help in Your Update

Make the Ask Clear

How Often to Update When Nothing's Changing

Regular Cadence Still Matters

Update When Status Changes

Special Situations

When You're Blocked for Weeks

When You're Waiting on Your Manager

When the Entire Project Is Cancelled

The "No Update" Template Library

Copy-Paste Templates for Common Situations

The 4 Tests for "No Progress" Updates

1. SIGNAL: Am I explaining WHY there's no progress?

2. OPPORTUNITY: Am I showing what I'm doing about it?

3. RISK: Am I asking for help if needed?

4. AFFECT: Do I sound engaged or checked out?

Check Your Status Update

Related Reading

Ready to Analyze Your Message?

How to Give an Update When There's No Progress

The Update You're Dreading

Why "No Update" Makes You Look Bad

It Suggests You're Not Engaged

It Doesn't Explain What's Happening

You Miss the Chance to Get Help

What to Report When There's No Progress

Template #1: The Blocked Update

Template #2: The Waiting Update

Template #3: The On-Hold Update

Real Examples: Wrong vs Right

Scenario: Blocked by Another Team

❌ WRONG

✅ RIGHT

Scenario: Waiting on Client Input

❌ WRONG

✅ RIGHT

How to Frame Different Types of "No Progress"

Blocked by External Dependency

Blocked by Decision/Approval

Blocked by Technical Issue

Project Deprioritized

What to Do While You're Blocked

Use the Time Productively

Actively Manage the Blocker

How to Ask for Help in Your Update

Make the Ask Clear

How Often to Update When Nothing's Changing

Regular Cadence Still Matters

Update When Status Changes

Special Situations

When You're Blocked for Weeks

When You're Waiting on Your Manager

When the Entire Project Is Cancelled

The "No Update" Template Library

Copy-Paste Templates for Common Situations