Clarification Script¶
Communication script — instantiates Cooperative Communication Repair
A pre-worded, reusable bank of clarifying questions that lets anyone ask what a message is missing without sounding hostile — turning "I'm confused" into a specific, answerable, cooperative request.
A Clarification Script is a curated, reusable library of clarifying questions — each already worded and each wrapped in a cooperative frame — that people can draw from when a message is too vague, too thin, or too loaded to act on. Its whole reason to exist is that the hard part of clarifying is rarely knowing that something is missing; it is asking for it out loud without the question landing as an accusation, an interrogation, or an admission of stupidity. The script solves that by doing the phrasing work in advance: "just so we get this right the first time, can you point to one example that feels right?" is safer to fire than an improvised "what do you actually mean?" The mechanism standardizes and de-risks the ask itself — its tone, its specificity, its cooperative framing — rather than diagnosing what broke, grounding a claim, or checking that the answer landed.
Example¶
An account manager at an advertising agency receives a client brief: "make it pop, modern but timeless, like the last campaign but different." Improvising here is dangerous — a blunt "that's contradictory, what do you want?" reads as combative, and guessing wastes a design cycle. So the manager reaches for the shop's standard intake script, a laminated card of pre-approved clarifying questions grouped by the kind of gap. For a missing reference she pulls: "To make sure we're aiming at the same target — can you show me one thing out there you love and one you'd hate to be compared to?" For a missing constraint: "So we don't over-invest in the wrong direction, what's the one thing this absolutely has to do?" Each question is already softened with a stated cooperative reason.
The vague brief becomes a specific, answerable spec within one call — a reference image, a hard constraint (must work as a 15-second cutdown), and a definition of "timeless" the client can actually name. The client never feels cross-examined, because every question arrived pre-framed as asked in service of the shared goal. The manager did not have to invent tactful phrasing under pressure; the script had already done it.
How it works¶
- Pre-write question stems keyed to gap types. Missing scope, missing example, missing constraint, missing success criterion — each has one or two ready-made stems, so the asker matches a stem to the gap instead of composing from scratch.
- Wrap every stem in a cooperative frame and an intent marker. The stem ships with its softening preamble ("so we get this right…") and an explicit statement of benign purpose, so the question reads as help, not challenge.
- Pick and fire, don't author. Under time pressure or social risk, the asker selects rather than writes — the design work lives in the script, not the moment.
- Curate the library over time. Questions that reliably land are kept; ones that read as passive-aggressive or draw defensiveness are rewritten or retired.
The distinguishing discipline is that a script optimizes wording and stance, not diagnosis: it assumes you already know roughly what is missing and need a safe, repeatable way to ask for it.
Tuning parameters¶
- Inventory breadth — how many gap types the script covers. Broad libraries handle more situations but get unwieldy and tempt people to fire a near-miss question; narrow ones are fast but leave gaps uncovered.
- Framing warmth — how much softening each stem carries. Warmer phrasing protects rapport and suits fragile or high-status relationships; leaner phrasing is quicker but edges toward blunt.
- Rigidity vs. adaptation — whether stems are used verbatim or as adjustable templates. Verbatim guarantees the tested tone; adaptation fits the moment but reintroduces the phrasing risk the script existed to remove.
- Intent-marker explicitness — how loudly each question announces its cooperative purpose. Louder disarms suspicion but can feel performative if overused.
When it helps, and when it misleads¶
A script shines on recurring, predictable gaps and wherever the cost of asking is what actually suppresses clarification — junior staff afraid to look slow, client-facing roles afraid to seem difficult, cross-cultural exchanges where improvised phrasing misfires. By pre-solving tone, it lowers the social tax on a good question and makes clarifying a normal, low-friction move rather than a confrontation. A clarification question is, structurally, a mild face-threatening act;[n1] the script's framing is what keeps it from being received as one.
Its failure mode is that a script has no eyes. Fired without a read of what is actually missing, it can ask a well-worded question about the wrong thing — soliciting more detail when the real trouble was relevance, or politely re-asking something already answered. Used mechanically it turns robotic, and the very framing that should disarm can read as insincere ritual; at its worst it is weaponized into feigned confusion, a stall dressed as diligence. The guarding discipline is to pick the question that fits the gap you have already spotted — the script supplies phrasing, not the diagnosis of what broke — and to keep a light, informal read of whether the answer actually cleared things up, leaving the formal loop-closing check to a different mechanism.
How it implements the components¶
clarification_request— the script is a library of these: pre-worded, specific, answerable requests for the missing distinction, example, or constraint.repair_frame— each stem carries its cooperative framing, so the request is received as help toward a shared goal rather than as pushback.intent_marker— the built-in preamble ("so we get this right…") signals benign, cooperative intent, keeping the ask from reading as challenge.
It does not diagnose which cooperative expectation actually failed (violated_expectation_diagnosis — Meeting Repair Move), route the request to whoever owns the fix (repair_owner), or confirm the answer was understood (shared_understanding_check — Readback / Teach-Back). Its nearest twin is Support Triage Question Set, which owns repair_owner: a triage set extracts and routes the specific facts a resolver needs, whereas this script standardizes the cooperative tone of any ask.
Related¶
- Instantiates: Cooperative Communication Repair — the script gives people a safe, repeatable way to issue the clarification request the repair depends on.
- Sibling mechanisms: Support Triage Question Set · Documentation Review for Cooperative Expectations · Evidence Linking · Meeting Repair Move · Readback / Teach-Back · Relevance Reframing · Sufficiency Calibration Checklist · Clarification Protocol
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: A pre-worded, reusable bank of clarifying questions that lets anyone ask what a message is missing without sounding hostile — turning 'I'm confused' into a specific, answerable, cooperative request, making its operative form a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding.
Independent corroboration: The frozen evidence defines Clarification Script as 'A pre-worded, reusable bank of clarifying questions that lets anyone ask what a message is missing without sounding hostile — turning 'I'm confused' into a specific, answerable, cooperative request', so its operative form is Communication, Facilitation & Learning.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Linguistics & Semiotics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Pragmatics, conversation analysis, and politeness theory supplied clarification requests that retrieve missing content while protecting face.
Related originating lineages:
- Communication & Media Studies — Interpersonal communication contributes reusable cooperative frames and organizational script deployment.
- Psychology — Social psychology contributes threat, defensiveness, and relational-safety mechanisms.
Review resolution: Schegloff, Jefferson, and Sacks established conversational repair as a systematic method lineage, and Brown and Levinson established linguistic strategies for softening face-threatening requests. Those directly support linguistics as primary; interpersonal communication and social psychology shape the reusable cooperative script, which is an Encyclopedia synthesis.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- Schegloff, Jefferson, and Sacks (1977): The Preference for Self-Correction in the Organization of Repair in Conversation
- Cambridge University Press: Politeness—Some Universals in Language Usage
Notes¶
Do not confuse this with the similarly named Clarification Protocol, a sibling from a different family: that mechanism is a receiver's response move for engaging a message whose buried premise it won't concede (premise–action decoupling). A Clarification Script is the opposite posture — a sender-directed asking tool for pulling missing content into a cooperative message. Same word, different job: one refuses to accept a premise, the other simply asks for what's absent.
[n1] In Brown and Levinson's politeness theory, a face-threatening act is any move that risks the hearer's self-image — and asking someone to explain themselves is a textbook case. Their account of positive- and negative-politeness strategies is exactly the pre-worded softening a clarification script bakes into each question. ↩