Skip to content

Assent-Scope Confirmation

A confirmation protocol — instantiates Premise–Action Decoupling

A read-back step that reflects exactly what the responder is and isn't agreeing to, requires an active restatement, and checks the yes was freely given — so the assent on record matches the assent actually made.

Where a disclosure states the scope going out, Assent-Scope Confirmation verifies it coming back. It is the read-back step that reflects the responder's own commitment to them — "here is exactly what you are agreeing to, and here is what you are not" — and requires an active, un-led restatement before that scope is treated as settled. Its defining move is confirming the receiver's understanding rather than the sender's claim: it checks that the assent about to be recorded matches the assent actually given, that its scope is neither broader nor narrower than the responder intended, and that it was given freely rather than by pressure or default. It is the antidote to "you agreed by proceeding" — assent counts only once it has been restated and owned.

Example

A homeowner with no heat calls an HVAC company; the technician arrives and quotes $89 for the diagnostic visit. Before touching anything, an Assent-Scope Confirmation happens at the door: "To confirm — you're authorizing the $89 diagnostic only. That's not authorization to repair. If I find something, I'll quote it and you decide separately. Can you tell me what you're okay with me doing today?" The homeowner restates it in their own words — "diagnose today; any repair is a separate yes" — and that restatement, not the act of letting the technician in, is what fixes the scope of consent. If a $600 part is later swapped without a second yes, "but you let me in" carries no weight; the confirmed scope was diagnosis only. The step also surfaces voluntariness: a family with no heat in January is under real pressure, so pausing to separate the cheap, reversible yes from the expensive one matters most exactly when it is least convenient.

How it works

  • Reflect the scope both ways. State what the assent covers and name what it explicitly excludes; the exclusion is half the confirmation.
  • Require an active restatement. The responder confirms in their own words, or by a distinct, deliberate act — not by silence, a pre-checked box, or simply continuing.
  • Check voluntariness. Note whether the yes is given under time pressure, dependency, or a penalty for refusing, and slow the high-stakes ones down.
  • Record the confirmed scope, not the participation. What goes on the record is the read-back that was owned, so later reconstruction matches what was actually agreed.

The distinguishing point is that it verifies the receiver's uptake — which is why a leading read-back ("so you're fine with everything, right?") defeats the mechanism even while performing it.

Tuning parameters

  • Read-back neutrality — how open versus leading the restatement prompt is. A neutral "tell me what you're agreeing to" confirms understanding; a leading "you're OK with all this?" manufactures it.
  • Scope granularity — how finely the confirmed scope is itemized. Finer catches over-broad consent but can turn a simple yes into an ordeal.
  • Voluntariness sensitivity — how hard it probes for pressure or dependency. Higher protects the coerced but can feel patronizing where consent is genuinely free.
  • Confirmation weight — a verbal check, an initialed line, or a witnessed signature; match the ceremony to how consequential and irreversible the assent is.

When it helps, and when it misleads

Its strength is that it makes the recorded assent match the real one, and it is the point where a too-broad or not-actually-voluntary "yes" gets caught before it hardens into a settled fact. It protects both sides — the responder from over-reading, the sponsor from a consent that later evaporates.

Its failure mode is that the read-back can be run backwards — used to lead the witness into confirming a scope broader than they understood ("so you agree we can proceed however we see fit — yes?"), turning a verification step into a manufacturing one.[1] It can also degrade into ritual, an "I confirm" checkbox that confirms nothing. The discipline is to keep the restatement in the responder's own words, to confirm the exclusions as explicitly as the inclusions, and to treat a confirmation obtained under undisclosed pressure as no confirmation at all.

How it implements the components

Assent-Scope Confirmation realizes the assent-verification components — the ones a read-back protocol fills at the moment of agreement:

  • consent_scope — it fixes the exact extent of what is agreed, inclusions and exclusions both.
  • uptake_confirmation — it verifies the responder actually received and understood that scope, via active restatement rather than inferred participation.
  • voluntariness_check — it tests whether the assent was freely given rather than extracted by pressure, dependency, or default.

It confirms an assent that already exists but does not state the terms in plain language up front (that's Plain-Language Disclosure) or supply the non-ratifying answer a responder gives when they will not assent at all (that's Non-Ratifying Response Option).

Notes

Assent-Scope Confirmation is a protocol — the read-back-and-own step — while the sibling Consent Confirmation Form is the artifact that records the result. The protocol can run verbally with no form, and a form can be signed with no real confirmation; keeping them distinct is what stops "a signed form" from being mistaken for "an understood, voluntary yes."

References

[1] Teach-back (or "show-me") is a health-literacy technique in which the professional asks the person to restate the plan in their own words, so comprehension is checked rather than assumed. Its integrity depends on a neutral prompt; a leading version ("you understand, right?") confirms nothing. ↩