Oral Consent as Workflow Step

Pattern IDD-002
Pattern Typedesign
AuthorMat Bettinson
Last updated2026-03-31
Keywords oral-consentBOLDIndigenous-languagesmobile-toolsfieldworkconsentcolonial-traumaaccessibility
HASS Domains linguisticsIndigenous-studiesanthropology
Source typeinterview-transcript
Source refMat Bettinson, RSE-CEP practitioner interview (2026-03-23)

Oral Consent as Workflow Step

Integrating oral consent as a first-class task type within fieldwork and remote consultation tools, replacing written consent forms in research contexts where written documentation carries cultural harm or where participant literacy cannot be assumed.


Pattern Metadata

FieldValue
Pattern IDD-002
Pattern TypeDesign
Keywordsoral-consent, BOLD, Indigenous-languages, mobile-tools, fieldwork, consent, colonial-trauma, accessibility
Author(s)Mat Bettinson
Last Updated2026-03-31

Intent

Design fieldwork and remote consultation tools so that consent collection is an integrated, oral, and dispatchable workflow step — not a separate written form — enabling ethical consent practice in Indigenous and minority language research contexts where written documentation carries historical harm or where literacy cannot be assumed.


Context

When This Pattern Applies

When This Pattern Does NOT Apply

Prerequisites


Issues

Issue 1: Written Documentation as Colonial Harm

In many Indigenous communities, written documentation has a specific colonial history — used by colonial administrations as a bureaucratic mechanism of control, extraction, and forced labour. Requiring written consent in such contexts is not merely inconvenient; it reproduces a form of power that the community has legitimate reasons to resist. Researchers who press for written consent in these settings face either refusal to participate or consent given under cultural duress.

Issue 2: Literacy Cannot Be Assumed

Oral language communities — particularly elders who are primary repositories of cultural and linguistic knowledge — frequently cannot read or write in the language of research, or in any written form. A written consent form addressed to a participant who cannot read it is not informed consent. Ethical consent requires that participants understand what they are consenting to, which means all consent interactions must have an oral pathway when literacy cannot be guaranteed.

Informal verbal consent — a researcher simply asking without recording — provides no audit trail and cannot be linked to the specific data it covers. Research ethics frameworks, even those that accept oral consent, require that consent be documented in some form. The tool must produce a verifiable, time-stamped consent record that can be associated with specific recordings or datasets.

Issue 4: Mediated Device Use

In communities with communal or family-based device ownership, participants often do not hold the device themselves — a younger family member opens links, navigates interfaces, and mediates the interaction for an elder. Consent workflows designed around individual device ownership (requiring the participant to type a name, sign with a finger) fail in this context. The design must function through mediation.

Key Constraints


Motivating Example

The Situation: A linguist working in rural Taiwan collects a multi-participant recording session with speakers of an Indigenous language. The community had been under Japanese colonial rule for fifty years, during which written documentation was used as a bureaucratic tool for forced labour. On returning from the field, the researcher realises that formal consent was not obtained from one participant.

The Issues That Emerged: Written consent cannot be sought without causing cultural harm; informal verbal consent in the field was not recorded; the participant is geographically remote; the recording cannot ethically be used or retained without consent.

Why Balance Is Needed: Ethical research requires provable, informed consent. Cultural safety requires that the consent process not reproduce colonial dynamics. A written form satisfies the first requirement while violating the second. The design challenge is to satisfy both simultaneously.


Solution

Core Idea

Make oral consent a first-class, typed task within the research tool’s workflow. The researcher creates a consent-seeking task — specifying what is being consented to — and dispatches it to the participant via whatever communication channel is available: SMS, email, or social media. The participant (or a family mediator) opens the URL on a mobile device, which presents a focused single-task interface. The researcher’s consent request is presented orally, and the participant’s affirmation is captured as audio. This audio record is the consent artefact — linked to the specific recording or dataset it covers.

Key Principles

  1. Oral-first: All key research interactions — including ethical ones — must have an oral pathway when literacy cannot be assumed
  2. Integrated, not incidental: Consent is a typed workflow step with its own task interface; it is not an informal practice that happens to precede tool use
  3. Channel-agnostic dispatch: The consent task is delivered via a URL that can travel by any route that reaches the participant
  4. Post-hoc capable: The design must explicitly support retrospective consent-seeking as a first-class scenario, not a workaround

Solution Structure

Researcher creates consent task (job specification)
      |
      v
Task URL dispatched via available channel
(SMS / email / social media -- whatever reaches the participant)
      |
      v
Participant or family mediator opens URL on mobile device
      |
      v
Focused single-task interface presents consent request
      |
      v
Participant gives oral affirmation -- audio captured
      |
      v
Consent record linked to original recording(s) or dataset

How the Issues Are Balanced

Values and Considerations

When designing the consent interface:

When deciding whether oral consent is appropriate:


Implementation Examples

Example 1: Aikuma-Link (Oral Consent as Post-Hoc Task)

Context: Language documentation fieldwork with speakers of Indigenous languages in rural Taiwan, conducted using Aikuma-Link, a mobile web application built on a URL-dispatched job specification architecture.

How They Balanced the Issues: The researcher had a multi-participant recording and realised one participant had not provided formal consent. A consent-seeking task was created in Aikuma-Link’s job specification system and dispatched to the participant as a URL — sent via whatever communication channel was available, making it channel-agnostic and reachable in a remote community without dependence on any particular communication infrastructure. The participant opened the focused mobile interface for the single task of giving oral consent: the researcher’s request was recorded, the participant’s affirmation was captured as audio.

What Worked Well: Consent was obtained without requiring the participant to write, sign, or travel; the audio record satisfied the researcher’s ethical obligations; the design functioned through the mediated device context of the community.

Link to Details: Aikuma-Link is not publicly deployed; this use case is documented in the RSE-CEP practitioner interview series.


Context-Specific Guidance

For HASS Research

For Indigenous Research

CARE Principles Application (Carroll et al., 2020):

Cultural Considerations:

For Different Scales

Small Projects / Solo Researchers: A full job specification system is not required to apply the core principle. A simple recorded audio note — the researcher asking for consent, the participant affirming, filed with the relevant recording — captures the essential design intent: oral, provable, linked.

Large Collaborative Projects: A formal task dispatch system provides provenance, timestamps, and explicit linkage between consent records and specific data items — essential when managing consent across many participants and multiple collectors. The URL-dispatch architecture ensures any collector can trigger a consent request without requiring the participant to interact with complex infrastructure.


Consequences

What You Gain

What You Accept

Risks to Manage


Known Uses

BOLD Framework (Foundational Reference)



Common Variations

Variation 1: Simple Audio Record (No Dispatch System)


Pitfalls to Avoid


Resources

Further Reading


Citation

APA:

Bettinson, M. (2026). Oral Consent as Workflow Step. CDL Recommended Patterns in RSE
for HASS & Indigenous Research, D-002.

Acknowledgments


Key References

Alexander, C. (1977). A Pattern Language: Towns, Buildings, Construction. Oxford University Press.

Alexander, C. (1979). The Timeless Way of Building. Oxford University Press.

Carroll, S. R., Garba, I., Figueroa-Rodríguez, O. L., Holbrook, J., Lovett, R., Materechera, S., Parsons, M., Raseroka, K., Rodriguez-Lonebear, D., Rowe, R., Sara, R., Walker, J. D., Anderson, J., & Hudson, M. (2020). The CARE Principles for Indigenous Data Governance. Data Science Journal, 19(1), 43. https://doi.org/10.5334/dsj-2020-043

Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994). Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley Professional.

Reiman, D. (2010). Basic oral language documentation. Language Documentation and Conservation, 4, 254–268. http://hdl.handle.net/10125/4479