Can “OK” be a commissive?

Yes, in a context where it accepts a request to perform an action. In another context it may simply acknowledge hearing.

Is an offer already an unconditional promise?

No. It can depend on acceptance or other conditions.

Does speech act mean spoken language only?

No. Written messages can perform the same kinds of communicative actions.

AI Glossary / Natural language and speech / Intermediate

Commissive speech act

Definition

A commissive speech act is an utterance that commits its speaker to a future course of action. Promises are clear examples; offers and plans can also express commitments, with their exact treatment depending on the dialogue taxonomy and context.

What it means

Language does more than describe the world. Saying “I will send the revised quote tomorrow” can create an expectation about what the speaker will do. A listener may reasonably organize their own work around that commitment.

The relevant distinction is the function of the utterance, not just its grammatical tense. “The parcel will probably arrive tomorrow” may predict an event without committing the speaker to deliver it. “Please send the quote” asks the listener to act and is a directive rather than a promise by the speaker.

In AI applications, identifying commissives helps separate assigned tasks, possible actions and definite undertakings. A system must retain conditions and uncertainty rather than convert every future-oriented sentence into an unconditional promise.

How it works

A dialogue interpreter considers the speaker, proposed action, time, conditions and surrounding turns. An explicit promise verb is a useful clue, but commitments can also be made indirectly. After a clear request, a short acceptance may commit the respondent to the requested action.

Annotation schemes differ in detail. DAMSL, for example, distinguishes offers that depend on the listener's agreement from other speaker commitments, and recognizes that commitment strength varies. A product should document the categories it uses instead of assuming that every research taxonomy has identical labels.

For task extraction, classification is only the beginning. The system needs to connect the commitment to the correct person and action, preserve its scope and track later changes. A subsequent cancellation or revised deadline can alter what should appear in a summary. Detecting the utterance does not prove that the promised action was performed.

Three practical examples

A meeting assistant identifies “I will draft the agenda by Thursday” as a candidate action item assigned to the speaker.
A service assistant distinguishes “I can arrange collection if you agree” from a collection that has already been scheduled.
A conversation analyst separates requests made to another person from promises made by the person currently speaking.

Think of it this way

Think of putting a marker on a future task: the speaker places their own name beside an intended action. A request instead asks someone else to take responsibility, while a prediction describes what may happen.

The marker is only an analogy. Real commitments can be conditional, indirect or weak, and the linguistic classification is not a determination of legal enforceability.

Worked example

Extracting a conditional commitment

Consider this invented exchange. Customer: “Can you send the inspection notes?” Adviser: “I will send them by 4 p.m. if the inspector signs them today.”

A useful structured record contains actor=adviser; action=send inspection notes; deadline=4 p.m.; condition=inspector signs today. The response is a conditional commitment, not evidence that the notes have been signed or sent. The exact date and time zone may also need resolution from the conversation.

Compare two alternatives: “The inspector usually signs by 4 p.m.” is a general statement, and “Could you ask the inspector?” is a request directed at the customer. Keyword matching on the time or the inspector's name would blur these differences.

If the adviser later says the inspector will not sign today, the task summary should preserve that update. It should not continue presenting the original conditional undertaking as a guaranteed delivery.

Illustrative case study

A fictional design studio uses an assistant to summarize review meetings. Its first version turns “I might revise the layout” and “I will revise the layout” into identical tasks. Team members find the resulting list misleading.

The studio creates examples covering tentative plans, explicit commitments, offers and accepted requests. Reviewers check the extracted owner, deadline and conditions against the full exchange. The summary displays tentative proposals separately from confirmed undertakings and records later corrections.

The team also checks its assistant's own language. If it cannot schedule or send a file, it should not casually promise to do so. The example illustrates alignment between conversational wording and operational capability, without reporting a measured productivity result.

Common misconceptions and mistakes

Every future-tense sentence is a commissive. Some are predictions or descriptions.
A commitment must contain the word promise. Context can make other wording function as a commitment.
A detected promise is a completed action. Fulfillment requires separate evidence.
Conditional commitments can be summarized without their conditions. Removing a condition changes the meaning.
Every taxonomy uses exactly the same boundary. Annotation schemes make different practical distinctions.

Business use

Commitment-aware summaries can help teams manage handoffs and customer expectations. Preserve who undertook what, for whom, by when and under which conditions. Link the summary to the original exchange so a person can inspect an uncertain classification.

For customer-facing AI, connect promises to actual supported workflows. “I have submitted the request” should require evidence of submission; “I will submit it” describes a future undertaking. Evaluate false commitments as well as missed ones, because an invented action item can be as disruptive as an omitted task.

Check your understanding

Why is “I will check the file if you send it” different from “I checked the file”?

Answer: The first undertakes a future action under a condition. The second reports an action as completed. An assistant should not merge their timing or evidential status.

Related terms

Speech act
Dialogue act
directive
constative
intent recognition
action-item extraction
dialogue state

Learn next

Study directives and acknowledgments, then label a short fictional meeting transcript. For each potential commitment, write its actor, action and conditions, and compare your interpretation with a second reviewer before automating task creation.

Sources

Jurafsky and Martin, Conversation and Its Structure: https://web.stanford.edu/~jurafsky/slp3/26.pdf. Speech-act categories and their conversational functions.

Core and colleagues, DAMSL Revised Manual, Committing-speaker-future-action: https://www.cs.rochester.edu/research/speech/damsl/RevisedManual/node10.html. Offers, commitments and contextual examples. The inspection exchange and studio case are original illustrations.

Previous: Combs method Next: Commit (data management)