Back to blog Browse the expressions hub

How to Say You Don't Have Bandwidth Politely

Client & Commercial Communication · 3 min read · 2026-08-12 · Updated 2026-08-27

A professional offers a smaller fitted component beside a full workbench and points to an open future-work shelf

Bandwidth is a clear, professional way to decline work, yet it can fall flat without any added context.

Add a timeframe, trade-off, owner, or another useful option. A bare "I don't have bandwidth" can still sound abrupt, even when it is true.

Quick check: decline without a dead end

Choose the reply that respects Jae's limit and gives Morgan a usable option.

Add context, not more honesty

The refusal itself is not the problem; the missing context is. "No bandwidth" makes the other person guess about what happens next. When will you have room, and what would need to change? Who else could help with the work? One more sentence gives the requester something useful to plan around.

"I don't have the bandwidth to take this on this week, but I can review it Monday."

"I don't have bandwidth for the full rewrite, but I can do a quick pass today."

"We'd need to drop another item to make bandwidth for this — can we decide what moves?"

Each answer still says no, but the other person now has useful choices. They can wait until Monday, accept the smaller version, or help choose the trade-off. A bare "I don't have bandwidth" only closes the door. The mistake is saying "no bandwidth" without adding any context or next step. It may be true, but it gives the requester nothing to work with.

Want to actually use "Bandwidth" naturally at work?

Understanding it is one thing. Practice its nuances, see how it works in real workplace situations, and use it yourself with feedback.

Start the "Bandwidth" learning path →

Why you shouldn't say a client lacks bandwidth

This skill gets harder with a client or outside partner because you need to protect the relationship. Avoid saying that they "don't have bandwidth," and talk about your own delivery capacity instead.

Saying a client lacks bandwidth makes a claim about their team that may not be true. Discuss your own team's timeline instead; this keeps the same boundary without speaking for the client.

Risky: "Your team doesn't have the bandwidth to review this by Friday."

Safer: "Given the review turnaround we've seen, Friday may be tight — would early next week work better?"

The mistake is claiming to know another company's internal capacity. Keep bandwidth claims focused on your own team instead. Describe the client's side through the timing you have actually seen, not a judgment about capacity. The safer version still does the same job: it flags a real deadline risk without making claims about the client.

Practice scenarios

Practice turning a bare bandwidth refusal into a useful answer here.

  • declining a request without leaving the other person stuck
  • offering a smaller alternative instead of a flat no
  • setting a client-facing timeline without presuming their internal capacity

Useful phrases to practice.

  • "I don't have the bandwidth to take this on this week, but I can..."
  • "We'd need to drop another item to make bandwidth for this — can we decide what moves?"
  • "Given the review turnaround we've seen, Friday may be tight — would early next week work better?"

Offer the architect a Monday alternative

"No bandwidth" may be honest. "No bandwidth, but here's what I can do" is useful.

Say the second one.

Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.

Know "Bandwidth." What else might you be missing?

The free Workplace English Expression Gap Assessment checks your recognition of high-value expressions across common workplace situations and shows you where your vocabulary gaps may be.

Find my vocabulary gaps

Keep reading