Common Ground Checklist¶
Verification checklist — instantiates Pragmatic Context Alignment
Enumerates the background facts a message silently counts on, then checks each is actually shared with the audience before it goes out.
A message is only as clear as the background it can safely assume. Common Ground Checklist is a pre-send audit that turns those assumptions into an explicit list: every fact, term, referent, and prior event the draft is counting on the reader already knowing — who "we" is, which system "the platform" means, why the date matters — with each item marked shared, partly shared, or not shared for this audience. Its one defining move is to work outward from the writer's own presuppositions and grade them against a model of the reader; it does not test whether the reader understood after the fact, and it does not trace the reader's reasoning step by step. It answers a single question — what am I assuming they already know, and is that true? — and hands back a gap list to close before sending.
Example¶
A foundation program officer is emailing a cohort of forty first-time grant applicants for the first time. Her draft is technically complete, but she runs a Common Ground Checklist over it before it ships. Item by item: it assumes readers know what a "letter of inquiry" is (not shared — most have never applied before), that the submission portal autosaves drafts (not shared), that "rolling review" means decisions come continuously rather than on a single date (partly shared), and that "we" refers to the program team, not the whole foundation (ambiguous). Each unshared item is a place the technically-correct email will be read wrong.
She closes the gaps cheaply: a one-line gloss defining the letter of inquiry, a sentence on autosave, a reframe of "rolling review," and a masthead line naming who "we" are. She also logs these resolutions so next month's cohort email inherits the same established common ground instead of re-deriving it. The outcome is not a longer email but a better-anchored one — and a noticeable drop in the "wait, what does this mean?" replies that the first draft would have generated.
How it works¶
- Surface the presuppositions. Read the draft as an outsider and list every referent, term of art, and prior-event assumption it leans on.
- Grade each against an audience model. Mark shared / partial / unshared for the specific readers, not for the writer's own peers.
- Close the gaps in place. State, define, or link the unshared items — the minimum that makes the intended reading recoverable.
- Post to the register. Record what is now established so later messages to the same audience neither re-explain nor wrongly re-assume it.
Tuning parameters¶
- Audience resolution — one persona versus segmented sub-audiences. Finer segmentation catches more real gaps but multiplies the checklist and can fracture a single message into caveats.
- Presupposition depth — stop at surface jargon, or go down to relationship and institutional assumptions. Deeper audits catch subtler misreads but cost time and risk over-explaining.
- Statement threshold — state every assumption versus only the load-bearing ones. Over-stating patronizes an expert audience; under-stating leaves newcomers stranded.
- Register carry-over — how much previously-established common ground to assume from earlier exchanges. Aggressive carry-over keeps messages short but goes stale when the audience turns over.
When it helps, and when it misleads¶
Its strength is on heterogeneous or unfamiliar audiences, where the writer's fluent shorthand is exactly the part that fails to land. By making assumed-shared knowledge explicit, it converts "obvious to me" into a checkable claim about the reader — an operational take on Herbert Clark's account of common ground as knowledge two parties mutually believe they share.[n1]
Its central failure mode is that the checklist is only as good as the guessed audience model behind it: a confident writer lists few gaps because they cannot see their own assumptions, and the register can drift out of date as the audience changes while the writer keeps assuming old common ground still holds. The classic misuse is over-explaining to experts — which itself signals a misread of the relationship and can read as condescension. The guarding discipline is to validate the audience model against a real proxy reader periodically, and to date the register so stale common ground gets re-checked rather than trusted forever.
How it implements the components¶
shared_background_model— its core output: a graded model of what background this audience does and does not share.common_ground_register— it maintains the running record of what has already been established, so it need not be re-audited each time.context_anchor_set— the checklist items include the deictic anchors ("we," "the platform," "the deadline") that must be shared for the message to resolve.
It does not run an uptake_validation_probe or open a repair_and_clarification_path — confirming the reader actually understood is Readback for Situated Meaning; and it does not build the inference_path_map, which is Recipient Inference Walkthrough.
Related¶
- Instantiates: Pragmatic Context Alignment — supplies the shared-background audit the rest of the alignment work depends on.
- Sibling mechanisms: Context Frame Header · Context Shift Test · Example and Boundary Case Pair · Implicature Audit · Politeness/Directness Adjustment · Pragmatic Breakdown Log · Readback for Situated Meaning · Recipient Inference Walkthrough · Scope and Audience Note
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Enumerates the background facts a message silently counts on, then checks each is actually shared with the audience before it goes out, making its operative form a bounded evaluation of existing evidence or work that produces a finding or disposition.
Independent corroboration: The frozen evidence defines Common Ground Checklist as 'Enumerates the background facts a message silently counts on, then checks each is actually shared with the audience before it goes out', so its operative form is Assessment, Review & Assurance.
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 and grounding theory made mutually recognized background knowledge a formal condition of successful communication.
Related originating lineages:
- Communication & Media Studies — Audience analysis contributes applied methods for testing presuppositions against a real recipient population.
Review resolution: Both reviewers agree on linguistics_semiotics as primary. Reading the source mechanism confirms that its defining operation belongs to that lineage; the final record retains communication_media_studies only where it materially formed the mechanism and keeps present-day application breadth separate from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Common ground — the sum of knowledge, beliefs, and assumptions two parties mutually believe they share, and which they draw on to interpret each other (Herbert Clark's work on grounding in communication). The checklist is a deliberate audit of that ground rather than a bet that it exists. ↩