Skip to content

Clean Rejection Notice

Document — instantiates Net-Additive Contribution Intake

Closes an unsuitable offer with a plain, final disposition and no ambiguous "maybe later," so the contributor gets a real answer and the system carries no hidden obligation.

The Clean Rejection Notice is the written artifact that formally closes an offer the system will not take. Its whole discipline is in the word clean: a direct disposition, a bounded rationale, and — the load-bearing part — no ambiguous language that leaves an implied commitment hanging. A vague "we'll keep it in mind" or "maybe down the road" is exactly what the notice exists to avoid, because a half-open offer becomes a hidden obligation that quietly consumes coordination attention forever. Where a refusal script governs how a person says no in the moment, the notice is the durable record that settles the matter: a definite answer the contributor can act on and the system never has to track again.

Example

A city's unsolicited-proposals office receives an offer from a vendor to donate and install a "smart bench" network for free, in exchange for advertising rights. It doesn't fit the city's procurement rules or its street-furniture plan, and the answer is no. The old habit was a warm, noncommittal reply — "interesting idea, let's stay in touch" — which left the vendor emailing quarterly for two years and a staffer perpetually half-managing a dead offer. Instead the office sends a Clean Rejection Notice: it states the disposition plainly (the proposal is declined), gives one bounded reason (it falls outside the current street-furniture standard and the unsolicited-proposal criteria), closes without a "reapply soon" dangle, and points to the published list of what the city is soliciting this year.

The vendor gets a real answer instead of two years of false hope, the staffer's phantom queue drops by one, and — because the notice named the actual gap — the next proposal from that vendor is likelier to be one the city can use.

How it works

What distinguishes the notice from a generic "no thanks" is what it deliberately withholds and what it feeds back:

  • State the disposition, not a debate. A single clear outcome — declined — with a rationale bounded enough that it informs without inviting negotiation.
  • No implied commitment. It scrubs the soft-decline phrases ("maybe later," "we'll keep you posted") that reopen the obligation the notice is meant to close.
  • Point the demand somewhere useful. By naming, briefly, what the system does want, the notice sends a signal back up the entry channel so the contributor's next offer self-selects toward fit.

Tuning parameters

  • Rationale detail — from a bare disposition to a specific reason. More detail feels respectful and shapes future offers; too much invites line-by-line rebuttal and turns a close into an argument.
  • Warmth vs. finality — how much relational cushioning surrounds the "no." Warmth preserves goodwill; excess warmth blurs into the ambiguous commitment the notice exists to prevent.
  • Redirect inclusion — whether to point to what is wanted or to an alternate recipient. A redirect softens the close and feeds the channel, but only when a real alternative exists.
  • Template vs. personalized — a reusable form (fast, consistent) versus a tailored note (higher-touch, slower). Match the effort to the contributor's standing and the offer's visibility.

When it helps, and when it misleads

Its strength is that it kills the zombie offer — the well-meant contribution that is never accepted and never actually closed, lingering as an unlogged obligation and a source of eventual resentment. A clean, final answer is more respectful than a warm evasion, and it is the only ending that actually frees the coordinator's attention.

It misleads when the impulse to be kind reopens what it should close: softening "no" into "maybe later" to dodge a moment's discomfort re-creates exactly the hidden commitment the notice was meant to end. Over-explaining is the mirror failure — a long rationale reads as an opening bid and invites negotiation. The discipline that keeps it clean is to decide the disposition before writing: the notice only communicates a decision already made, so it never becomes the place where the decision is relitigated.

How it implements the components

The Clean Rejection Notice realizes the safe-closure-and-signal components:

  • safe_rejection_or_deferral_path — it is the artifact that lets an offer be declined or deferred cleanly, with a real answer and no dangling obligation.
  • feedback_loop_to_entry_channel — by naming what the system does want, it sends signal back toward the entry point so future offers self-select toward fit.

It does not supply the spoken, dignity-preserving language for delivering a refusal in person, nor establish the authority to refuse — both belong to Refusal Script.