Declining on Behalf: Writing Regrets and Saying No Well

An executive supported well declines more often than they accept. Speaking invitations, conference panels, charity boards, networking coffees, demo requests, vendor pitches, podcast interviews, mentor calls, and the constant stream of meeting requests that do not have a clear business case — most of these need a polite no, sent within a few days, in language that does not damage the relationship for whatever the next ask might be.

This is one of the few admin skills that compounds visibly into reputation. An executive whose declines are consistently gracious — never curt, never overpromising a "next time," never accidentally insulting — accumulates good will across the industry. An executive whose declines are written badly, even occasionally, accumulates the opposite. The admin writing the declines is the one shaping that reputation.

This page covers the operating craft. The broader rules around what information to include and not include in any external correspondence sit in the confidentiality and discretion guide, and the discipline for saying no inside the company is closer to the managing up content in the guides hub.

The Three-Part Structure

Almost every effective decline has the same three parts in the same order. The order matters; reordering them produces the version that lands badly.

1. Acknowledge the ask specifically

"Thanks for the invitation to speak at [event]" is acknowledgement. "Thanks for reaching out" is not — it could be the opening of any decline ever written, and the reader registers it as such. The specificity in the first line tells the reader you actually read what they sent.

2. Decline cleanly

One sentence. "Unfortunately, [executive] is not able to take this on right now." Clean, complete, no qualification. The temptation is to soften by stacking modifiers ("quite unable," "really regretfully"); resist it. Stacking modifiers signals discomfort and invites pushback.

3. Leave the door open or close it cleanly

If a "next time" is genuine, say so concretely: "If you run a similar event next year, please reach back out — the timing is the binding issue here." If a "next time" is not genuine, do not promise one. The repeated mistake admins make is offering a vague "perhaps in future" when the answer is actually no. The recipient diaries it as a soft yes and re-asks six months later, at which point the admin has to decline again.

The Reasons You Can Give and the Ones You Cannot

The hardest judgement call in declining is what reason — if any — to give. The general rule:

Reasons that travel well

• Capacity. "Their commitments through the end of the quarter are full." Generic, true in almost every case, hard to argue with.
• Timing. "The window for that overlaps with travel they cannot move." True often enough; specific without being identifying.
• Topical fit. "This isn't an area [executive] focuses on; you'd get a better answer from someone closer to it." Genuinely helpful when applicable.
• Policy. "[Executive] doesn't accept paid speaking engagements" or "[Company] doesn't have a media program around this kind of request." Policy reasons are unimpeachable when they are real.

Reasons that travel badly

• Specific competing meetings. "She's at a board meeting that day" tells the recipient where she is and when. Stay vague.
• The actual content of their day. "He has back-to-back interviews that week" leaks personnel information.
• Personal reasons. "Her son has a school thing." Never. Even when true, even with permission, stay general.
• Anything that names a competitor or another priority. "She's prioritizing the [other company] partnership conversations" is the kind of detail that comes back in unexpected ways.
• The actual no-this-is-not-worth-his-time judgement. Even when true. The judgement stays internal; the decline stays gracious.

The honest version of "we don't think this meeting is valuable" is not "we don't think this meeting is valuable." It is "she is not able to take this on right now." Both can be true at once. The recipient does not need the first version; the relationship is healthier without it.

Patterns by Request Type

Speaking and conference invitations

The default pattern: thank them for thinking of the executive, decline citing schedule capacity, and — if genuinely applicable — suggest a follow-up window or an alternate person. If the invitation is from a recurring event, reference it: "We hope to find a window in a future year." Do not promise a specific year unless the executive has agreed.

Networking coffees and introductory meetings

These pile up faster than any executive can absorb. The clean decline acknowledges the asker, declines, and offers a substitute path: "[Executive] is not able to take introductory meetings right now. If there's a specific question I can route to someone on the team, happy to do so." This converts about half of these requests into something more efficient and politely closes the rest.

Podcast and interview requests

If your company has a communications team, route every media request through them — even the declines. "Media requests for [executive] go through [comms contact] — copying them here so they can respond." This is faster, safer, and saves you from writing media policy on the fly.

Charity, board, and pro-bono requests

The hardest category, because the requester is often emotionally invested and the cause is often legitimate. The pattern: acknowledge the cause specifically, decline citing capacity, and — if you have permission — offer a small gesture (a donation referral, a one-time introduction, a one-line social post). The gesture is the thing that distinguishes a gracious decline from a perfunctory one.

Vendor and sales pitches

The shortest category. "Thanks for reaching out — [executive] handles this kind of decision through [team or person], who will be in touch if it is a fit on our side." Polite, specific, redirects without committing. Unsolicited follow-ups after this can be ignored without further response.

Internal declines

Declining internal meetings is its own discipline. "She's not going to be able to make this; can you proceed without her and brief in the readout?" is usually the right shape. Internal declines should never be sent as a calendar decline alone — always pair with a one-line message explaining why and what to do instead. A bare decline lands as dismissive even when it is not.

The Voice Question

Declines you write under your own name and declines you write under your executive's name are different documents. The same words land differently depending on who appears to have sent them.

Under your name

Most external declines should go under your name, not the executive's. "Hi, I'm [name], working with [executive]. They've asked me to come back to you on this." This signals two things: the executive saw the request, and the response is considered. The recipient does not receive a literal "no" from the executive themselves, which is easier on the relationship for any future ask. The executive's review can be light — sometimes just a thumbs-up on a draft — but their fingerprint matters.

Under their name

Reserve the executive-as-author version for the cases where it truly matters: a personal connection, a senior peer, a board member, someone the executive specifically wants to address themselves. In those cases, write the draft, save it for them to send (do not send under their name yourself unless they have explicit standing authority for this), and let them edit. The discipline around draft-vs-send in shared inbox work applies directly here.

Common Mistakes

• Apologizing too much. One acknowledgement is enough. Three apologies in a four-line decline reads as discomfort and sometimes as guilt — neither is the impression you want to leave.
• Promising a "next time" you cannot deliver. The recipient diaries it. They will follow up. The follow-up will be more awkward than the original decline would have been.
• Over-explaining. A decline with five reasons sounds defensive. A decline with one clean reason sounds final.
• Going passive. "It might not be possible for [executive] to attend at this time" is a longer way to say "[executive] cannot attend." The longer version is harder to read and easier to push back on.
• Speaking for the executive without their input. Even routine declines benefit from a quick scan by the executive on the first instance with a new sender or a notable institution. Once the pattern is established, you can act on standing instructions.
• Sending the decline three weeks late. A fast decline is part of the courtesy. Sitting on a meeting request for a month and then declining is worse than a same-day no, even though the language is identical.

Building a Personal Phrasebook

Most admins running a busy executive's correspondence end up declining variations of the same five or six requests dozens of times a year. The leverage is to write each one well once, save the language as a snippet, and re-customize the opening sentence for each new sender. The result is decline letters that read as personal — because the opening is — while the body lands cleanly because it has been refined over time.

Two practices keep the phrasebook from going stale:

• Edit twice a year. Re-read each saved snippet and ask whether it still fits the executive's current voice and the company's current positioning. Snippets that worked two years ago can sound dated.
• Notice when you have a new pattern. The third time you write a similar decline from scratch, save the version you just wrote. The fourth time will be easier.

Your phrasebook belongs in the same place your other reusable documents live — referenced from the desk manual, organized by request category, accessible to whoever covers your role on your vacation. The communication templates section in the templates library is a starting point if you have not built one yet.