Meeting Action-Item Capture¶
Capture protocol — instantiates Speech-Act Clarification
Converts ambiguous meeting talk into explicit action items — distinguishing an idea from a decision and a casual offer from an accepted assignment — then pins each to a named owner and a deadline.
Meeting Action-Item Capture is the practice of taking the loose language of a meeting and, in real time, converting each consequential statement into an explicit action item: a decided assignment with an operational meaning, a single named owner, and a due date. Its distinguishing move among its siblings is that it serves group coordination — it turns "we should do this" into an owned, dated commitment the room agrees on, so nobody leaves with a different belief about what was decided or who is doing it. It does not classify directive force in the abstract, map who had authority, or memorialize a status-changing declaration; it captures decisions and assignments as they are made and pins them to people.
Example¶
At a weekly construction site coordination meeting, the superintendent says, "we'll get the rebar inspection sorted before the pour." Left alone, that sentence evaporates the moment the meeting ends — who is "we," by when, and was it even decided or just floated? Meeting Action-Item Capture converts it on the spot into a logged item: the intended action (schedule and pass the rebar inspection — a decided assignment, not a hope), the owner (the assistant superintendent, named, not "the team"), and the deadline (two working days before the scheduled pour). It is read back into the shared action log so the whole room sees the same commitment. The distinguishing test runs the other way too: when someone muses that "maybe we should look at a different rebar supplier," that is captured as a parked idea, not an action item, precisely because no one accepted it as a commitment. Idea and decision are sorted at the moment they are spoken, before the crew disperses to act on divergent understandings.
How it works¶
For each consequential utterance the capture makes two cuts. First, the idea/decision cut: is this a passing idea, a made decision, or an accepted assignment? Only the latter two become action items; ideas are parked separately so the list of commitments stays honest. Second, for anything that is an assignment, the single-owner rule: pin exactly one named person and a deadline, and record it in the shared log. A casual offer becomes an assignment only when someone actually accepts it as one. The distinctive discipline is that it captures what the room committed to, not what force a phrase carries in general and not what a contract would bind — it produces an owned, dated record, nothing heavier.
Tuning parameters¶
- Capture threshold — log every statement, or only decisions and accepted assignments. Capturing everything is thorough but buries the real commitments; capturing too narrowly lets a quiet agreement slip out unrecorded.
- Owner cardinality — strictly one named owner per item, or shared ownership. One owner removes the diffusion of responsibility; shared ownership reflects messy reality but blurs who actually answers for a slip.
- Capture timing — live during the meeting, or reconstructed from notes afterward. Live capture lets the room correct a misread on the spot; after-the-fact capture is tidier but re-introduces the ambiguity it was meant to remove.
- Acceptance strength — whether the named owner must explicitly accept, or is assigned in absentia. Explicit acceptance prevents owning someone who never agreed; requiring it slows the meeting and can stall when the right person is not in the room.
When it helps, and when it misleads¶
Its strength is that it kills the two everyday meeting failures at once: the room leaving with different beliefs about what was decided, and the action item that belongs to nobody. It makes a meeting produce durable, owned commitments instead of a shared vague sense that "we'll sort it."
Its failure mode is capture-theater — a crisp list of items nobody actually accepted, or that misattribute owners, giving false confidence that work is committed when it is not.[n1] The classic misuse is assigning in absentia: logging an owner who was not there and never agreed, which produces a record of a commitment that does not exist. Over-capture is the quieter failure, burying the two real decisions under thirty logged musings. The discipline that keeps it honest is to require the named owner to actually accept the item, and to hold the idea/decision cut firmly so that parked ideas are never silently promoted into commitments.
How it implements the components¶
Meeting Action-Item Capture fills the assignment-and-record side of the archetype's machinery — the components that turn meeting talk into owned commitments:
intended_performed_action— it states, operationally, what each captured statement actually commits to — a decision or an accepted assignment — rather than leaving "we should" to be read as either a musing or a mandate.audience_or_counterparty— it pins each action item to a single named owner (and, where relevant, whom it is owed to), so responsibility is specific rather than diffuse.consequence_record— it records the resulting decision or assignment with its owner and deadline in the shared log, the artifact the group relies on after the meeting ends.
It does not classify the abstract directive force of a phrase (speech_act_type, speech_act_mismatch_source) — that is Request / Order Clarification Prompt, whose label it can consume; it does not check the assigner's authority (authority_or_standing) — that is Authority Matrix; and it does not memorialize a status-changing declaration in an official channel (record_channel) — that is Formal Declaration Record. It captures owned assignments; siblings label, validate, and formally declare.
Related¶
- Instantiates: Speech-Act Clarification — the capture turns ambiguous meeting language into explicit, owned decisions so participants coordinate around one understanding.
- Consumes: Request / Order Clarification Prompt — its label for whether a statement was a decision or a mere suggestion feeds the idea/decision cut.
- Sibling mechanisms: Request / Order Clarification Prompt · Formal Declaration Record · Authority Matrix · Apology / Repair Protocol · Commitment Register · Consent Confirmation Form · Contract Speech-Act Clause · Readback Confirmation
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: The mechanism applies a repeatable idea-versus-decision cut and single-owner rule to convert meeting talk into explicit assignments, so the capture procedure is operative.
Nearest alternative: Record, Log & Register — A shared log stores the resulting commitments, but the mechanism's distinctive work is the ordered interpretation and assignment process that creates them.
Review outcome: Adjudicated after independent review; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Capturing owners and deadlines from meetings is a standard organizational coordination practice.
Related originating lineages:
- Linguistics & Semiotics — Speech-act distinctions between proposals, decisions, offers, and commitments shape the clarification rule.
Review resolution: Both independent reviews place the primary provenance in organizational_management. The queued differences (alternate_origin_disagreement, origin_mode_disagreement) concern secondary metadata, not primary lineage. The final retains linguistics_semiotics only where a reviewer supplied a formative-lineage rationale; downstream use or broad applicability by itself is not treated as origin. origin_mode=cross_disciplinary_synthesis because the supplied rationales identify formative contributions that are composed in the mechanism's present form. domain_reach=multi_domain records established application breadth separately from provenance. confidence=high preserves the more cautious evidence assessment. encyclopedia_synthesis=false records whether either reviewer identified deliberate corpus-level composition.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The capture ends at an owned, dated record; it deliberately stops short of tracking those items over their life. Where a body of commitments must be governed as a portfolio — states maintained, slips surfaced, closures evidenced — the action log should feed a Commitment Register rather than trying to become one, which keeps the fast in-meeting capture from silently taking on lifecycle duties it was never built to carry.
[n1] Diffusion of responsibility — the finding, from Darley and Latané's bystander research, that as the number of people who could act rises, each individual feels less personally responsible and action becomes less likely. It is the direct rationale for the single-named-owner rule: an action item owned by "the team" is owned by no one, which is why capture pins a specific person rather than a group. ↩