Refusal Script¶

Template — instantiates Net-Additive Contribution Intake

Reusable, respectful language for saying no or not-yet — grounded in a legitimate right to refuse — so front-line people can decline without negotiating, over-apologizing, or damaging the relationship.

The Refusal Script is reusable, pre-written language for delivering a refusal in a live interaction — face to face, on a call, in a thread — respectfully and without folding. Its defining property is that it makes the "no" both sayable and legitimate: it hands a front-line person words that decline clearly, hold the line without negotiating, and preserve the contributor's dignity, all resting on an explicit, stated basis for the system's right to refuse. Where a rejection notice is the written record that closes an offer, the script governs the human moment — the awkward instant when someone offering genuine help must be told no, and the person saying it needs language that neither caves nor wounds.

Example¶

A community library is regularly offered book donations at the front desk — often boxes of mildewed paperbacks and outdated textbooks that cost more to sort and dispose of than they're worth. New desk volunteers, caught off guard and eager to be kind, keep accepting boxes they shouldn't, or stammer through an apologetic refusal that invites the donor to argue. The library gives them a Refusal Script: a warm opening that thanks the donor, a clear decline grounded in a stated reason the volunteer can stand on ("we can only take books we have the shelf space and staff to process, and we're at capacity"), a calm non-negotiating hold if pressed, and a redirect to a nearby charity shop that does want them.

A volunteer using it can now decline a box of moldy encyclopedias without accepting it out of guilt and without the donor leaving offended — the refusal is kind, firm, and clearly not personal, because the words and the legitimacy behind them were prepared in advance.

How it works¶

What distinguishes the script from improvised politeness is that it packages legitimacy into sayable language:

Acknowledge, then decline. It opens by honoring the offer and the contributor before stating the "no," so the refusal reads as respect, not dismissal.
Ground the "no" in a stated right. The decline rests on an explicit basis — capacity, scope, fit — so it lands as a legitimate policy rather than an arbitrary personal rejection.
Hold without negotiating. It gives calm, repeatable language for staying with the answer if pressed, so a front-line person doesn't get argued into a yes.^[1]

Tuning parameters¶

Warmth vs. firmness — how much cushioning surrounds the decline. Warmth protects the relationship; too much reads as an opening to negotiate, too little as cold dismissal.
Reason depth — how much of the legitimating basis to voice. A brief stated reason confers legitimacy without inviting debate; a long justification invites rebuttal.
Alternative offered — whether the script redirects the contributor somewhere useful. A redirect softens the "no" and honors the goodwill, but only where a real alternative exists.
Scripting degree — verbatim wording versus talking points. Verbatim ensures consistency and protects nervous staff; talking points sound more natural but demand more judgment in the moment.

When it helps, and when it misleads¶

Its strength is that it makes refusal possible for the people who most often can't do it — front-line staff and volunteers who, without prepared language, accept things they shouldn't or refuse them so badly the relationship breaks. It protects the contributor's dignity and the refuser's, and it keeps refusals consistent across everyone who fields offers.

It misleads when it becomes robotic — a script delivered as a recitation feels dismissive and can wound more than an honest fumble. Its real danger is using the script to refuse things that should be accepted: smooth refusal language makes it easy to stonewall legitimate, additive contributions simply because saying no is now frictionless. The discipline that keeps it honest is to script the tone, not the verdict — the decision about what to refuse comes from triage; the script only delivers that decision kindly, and must never become the reason good offers are turned away.

How it implements the components¶

The Refusal Script realizes the legitimacy-and-dignity components — the human side of saying no:

refusal_legitimacy_rule — it embeds the system's stated right to refuse into speakable language, so a decline lands as legitimate policy rather than personal rejection.
contributor_dignity_and_non_exploitation_guardrail — its whole construction preserves the contributor's dignity and the relationship while still declining.

It does not produce the durable written disposition that formally closes an offer — that is Clean Rejection Notice — and it does not decide *what to refuse, which comes from triage (Automated Classification and Routing and net-value review).*

Instantiates: Net-Additive Contribution Intake — the script is how a refusal is delivered in person.
Consumes: the decision about what to decline (from triage / net-value review); the script delivers that verdict, it does not form it.
Sibling mechanisms: Clean Rejection Notice · Automated Classification and Routing · Side-Channel Redirect Notice · Overflow Redirection

References¶

[1] The broken-record technique from assertiveness training — calmly restating one's position without escalating or being drawn into negotiation. It is what lets a front-line person hold a legitimate "no" against pressure without either caving or turning combative. ↩