Informed Consent Governance¶
Ensure agreement is informed, voluntary, specific, revocable where appropriate, and granted by someone with authority to consent.
The Diagnostic Story¶
Symptom: The system treats assent as consent even though the person had no real option to refuse, could not understand what they were agreeing to, or was not actually the one with authority to grant permission. Scope keeps expanding beyond what was originally agreed, and no workable path to withdraw exists once the agreement is on record.
Pivot: Separate the components that make permission meaningful: who has authority to consent, what material information must be disclosed and understood, whether refusal is genuinely available, what scope and duration are covered, and how the consent state can be revised or withdrawn.
Resolution: Permissions are meaningful, traceable, and specific. Disputes drop because scope and conditions were documented rather than inferred. The system can show, for any action taken, what permission covered it and how that permission was obtained.
Reach for this when you hear…¶
[clinical research] “Signing the form is not the same as consenting — if the patient could not have said no without losing care, that is not voluntary.”
[platform governance] “We have checkbox consent for everything and meaningful consent for nothing — our terms grant us the right to do things people never actually agreed to.”
[enterprise data] “The original approval covered that use case, not this one — we need to go back and get explicit permission or we are operating outside our authorization.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A system treats assent, participation, silence, continued use, a signature, or a checkbox as consent even though the person lacked adequate information, understanding, freedom to refuse, authority to grant permission, scope clarity, or a workable withdrawal path.
What this problem means
The structural failure is consent theater: a system collects evidence of assent but does not create meaningful permission. The consent record may look clean while the underlying relationship is defective. The person may not understand the action, may face hidden pressure, may be agreeing to many unrelated uses at once, may lack authority to agree, or may be unable to revoke consent later.
The root tension is that institutions and systems need permission to act, while affected people need real control over what they authorize. Without governance, consent becomes a transfer of burden from the powerful actor to the less powerful one.
Show the applicability expression
Applicability expression6 distinct conditions
groundedpartly groundedopen
6 conditions, all required.
6Required in every casenumbered 1–6
These hold no matter which pattern applies.
Prior voluntary authorization · grounded
One party must obtain voluntary authorization from the autonomous holder before acting within that holder's domain.
The source archetype describes the situation as follows: Permission-dependent action. The normalized requirement above isolates the load-bearing portion used in this condition set.
Material information asymmetry · open
The parties have materially unequal information relevant to the authorization decision.
The source archetype describes the situation as follows: Information asymmetry. The normalized requirement above isolates the load-bearing portion used in this condition set.
Compromised voluntariness · open
Power or dependency imbalance may compromise voluntariness.
The source archetype describes the situation as follows: Power or dependency imbalance. The normalized requirement above isolates the load-bearing portion used in this condition set.
Complex authorization scope · open
The proposed authorization has complex scope, purpose, reuse, risk, or downstream consequences.
The source archetype describes the situation as follows: Scope or purpose complexity. The normalized requirement above isolates the load-bearing portion used in this condition set.
Ongoing revocable consent · open
Authorization must remain valid, reviewable, and revocable as circumstances change over time.
The source archetype describes the situation as follows: Consent over time. The normalized requirement above isolates the load-bearing portion used in this condition set.
Proxy authorization · open
A representative or proxy may need authority to authorize on another person's behalf.
The source archetype describes the situation as follows: Representative or proxy permission. The normalized requirement above isolates the load-bearing portion used in this condition set.
Coverage
1 of 6 conditions grounded · 5 open.
Mechanisms / Implementations¶
- Consent Form (
consent_form):: Captures disclosure, agreement, scope, signature or acknowledgement, and often the record of authorization. - Opt-In Flow (
opt_in_flow):: Presents a permission request before a user enters a feature, data use, program, or relationship that requires affirmative agreement. - Informed Consent Conversation (
informed_consent_conversation):: Uses dialogue, question-and-answer, teach-back, and deliberation to establish understanding before agreement. - Data Consent Settings (
data_consent_settings):: Lets users grant, narrow, revoke, or inspect data permissions at different levels of granularity. - Research Consent Protocol (
research_consent_protocol):: Structures participant disclosure, voluntary enrollment, scope, withdrawal, recordkeeping, and continuing review for research participation. - Withdrawal Procedure (
withdrawal_procedure):: Operationalizes refusal, revocation, narrowing, opt-out, deletion, stopping participation, or review of existing permission. - Assent / Consent Distinction (
assent_consent_distinction):: Differentiates affirmative participation by a person from legally or institutionally authorized consent by a guardian, representative, or accountable actor. - Plain-Language Disclosure (
plain_language_disclosure):: Provides layered, accessible, and decision-relevant explanation of material information. - Granular Permission Dashboard (
granular_permission_dashboard):: Shows separate permissions, purposes, actors, and revocation controls in a single reviewable place. - Consent Renewal Prompt (
consent_renewal_prompt):: Requests renewed agreement when purpose, risk, duration, actor, or context changes materially.
- Assent / Consent Distinction: Splits one 'yes' into two: the affected person's affirmative participation and the authorized actor's binding permission — and defines what happens when they diverge.
- Consent Form: The signed artifact that fixes the disclosed terms, the bounded scope agreed to, and a durable, provable record of who authorized what and when.
- Consent Renewal Prompt: A change-triggered workflow that re-discloses what shifted and asks the person to affirmatively re-agree to the updated scope before the new use begins.
- Data Consent Settings: A standing, self-service control surface where a user can grant, narrow, revoke, or inspect specific data permissions at any time — and the toggle actually changes what the system does.
- Granular Permission Dashboard: A single review surface that lays out every permission a person has granted — split by purpose, actor, and duration — so the whole consent landscape can be inspected and spotted for staleness at a glance.
- Informed Consent Conversation: A two-way dialogue that co-produces and live-tests understanding — through questions, teach-back, and deliberation — before any agreement is sought.
- Opt-In Flow: A pre-entry interface gate that presents one permission request with its material terms at the threshold of a feature, and requires an affirmative choice against a genuine, equally-weighted decline.
- Plain-Language Disclosure: A layered, plainly-worded statement that puts the scope, limits, and boundary of what agreeing commits you to in a first-time reader's line of sight — so assent is informed rather than inferred from not-having-noticed.
- Research Consent Protocol: An oversight-governed protocol spanning the full arc of research participation — standardized disclosure, voluntary enrollment, documented consent, and a penalty-free right to withdraw.
- Withdrawal Procedure: The end-to-end workflow that executes a person's decision to take back or narrow an existing permission — receiving it, propagating the stop downstream, and stating what can and cannot be undone.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (2)
- Consent: Voluntary agreement.
- Speech Act Theory (Illocution, Perlocution): Language as action.
Also references 7 related abstractions
- Accountability: Responsibility for actions.
- Legitimacy: Accepted authority.
- Mandatory vs. Default Norms: Binding vs flexible rules.
- Normativity: What ought to be.
- Procedural Fairness (Due Process): Due process.
- Rights vs. Freedoms: Claims vs liberties.
- Transparency: Open processes.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Granular Consent Governance · implementation variant · recognized
A consent-governance variant that breaks permission into separable purposes, actors, durations, or data/action categories instead of asking for one blanket approval.
Dynamic or Ongoing Consent · temporal variant · recognized
A consent-governance variant that treats permission as a maintained relationship requiring updates, reminders, renewal, and revocation over time.
Proxy or Representative Consent · governance variant · recognized
A consent-governance variant for cases where permission is granted by an authorized representative, guardian, delegate, or collective decision process.
Assent Plus Authorized Consent · governance variant · candidate
A narrower variant in which an affected party’s affirmative participation is sought alongside formal consent from an authorized actor.
Editorial Notes¶
Problem Classification¶
Classification: Authority, Accountability, Legitimacy & Fair-Process Failure → Legitimacy, Consent & Agenda Acceptance
Problem kernel: assent is mistaken for informed and voluntary consent
Rationale: Signatures, silence, or continued use are accepted despite missing understanding, freedom to refuse, authority, or scope clarity.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A system treats assent, participation, silence, continued use, a signature, or a checkbox as consent even though the person lacked adequate information, understanding, freedom to refuse, authority to grant permission, scope clarity, or a workable withdrawal path. That is a legitimacy consent and agenda acceptance problem because Authority, embedded premises, or public agendas acquire apparent acceptance without an adequate basis in informed, voluntary, independently contestable authorization.
Review outcome: Independent reviewer agreement; high confidence.