# Decisions, Commitments, or Just Ideas? How to Read Past Conversations Accurately

> Distinguish decisions, commitments, and proposals in past conversations. Preserve acceptance, scope, and conditions without turning an idea into an agreement.

- URL: https://www.hemory.com/blog/searchable-memory/decisions-commitments-and-ideas/
- Language: English (en)
- Author: Hemory Team
- Published: 2026-11-02
- Last updated: 2026-11-02
- Summary: Read conversation outcomes by separating proposals, decisions, commitments, open questions, and background remarks. Assess acceptance in the actual decision process, preserve conditions and scope, and distinguish commitments from dates and completion. Hemory's organized Memory supplies a starting point and context for supported agents. A renewal example and copyable note structure show how to avoid promoting an unapproved idea or an uncertain inference into an agreed outcome.
- Tags: conversation memory, decisions, commitments, meeting outcomes

Someone suggests, “We could offer onboarding at no charge.” Later, a summary says, “Free onboarding agreed.” A sales colleague starts preparing the offer, even though the discussion never reached approval.

To use past conversations well, preserve the difference between an idea, an accepted choice, and a promise to act. This guide explains what to look for, how to record conditions and later changes, and how to carry those distinctions into AI-assisted work.

## TL;DR

- A proposal becomes a decision through a relevant act of acceptance or authorization, not through repetition or confident wording alone.
- A decision establishes a choice; a commitment concerns who will do something. Either can have conditions or missing details.
- A commitment can be real even when no deadline is stated. Record the action and owner, and clarify timing when needed.
- Hemory organizes captured discussions into summaries, decisions, action items, and unresolved questions, giving you a starting point without manually sorting every remark during the conversation.
- Keep the basis, scope, and important conditions with a recalled outcome. Check the source when a summary would materially change what someone is expected to do.

## Start With What the Statement Actually Does

Use these distinctions when reading a conversation record. They describe the meaning of a statement; they are not product-specific status controls.

| Kind of statement | What it establishes | Example | What to carry forward |
|---|---|---|---|
| Idea or proposal | An option for consideration | “We could include onboarding.” | The option, without presenting it as approved |
| Decision | A choice accepted or authorized for a defined scope | “Include onboarding for this renewal.” | The choice, scope, and basis for acceptance |
| Commitment | A person or responsible party undertakes an action | “I'll revise the renewal offer.” | The action, owner, and any stated timing or condition |
| Open question | Something remains unresolved | “Who will deliver the onboarding?” | The specific answer still needed |
| Background or aside | An explanation or remark that does not itself establish an outcome | “The last onboarding took longer than expected.” | Relevant reasoning, without turning it into a new action |

A single exchange can contain several kinds. A client may approve a direction while the delivery date remains open. A colleague may commit to investigating an option without committing to implementing it. Keep those parts separate.

## Look for Acceptance in the Actual Decision Context

Acceptance can be brief: “Yes, use that version.” It can also be a clear instruction from the person authorized to make the choice. You don't need everyone to say a formal phrase such as “we have decided.” You do need enough context to know what was accepted and whether the speaker could settle it.

Useful questions are:

- What choice was being discussed when the acceptance occurred?
- Was the speaker deciding, recommending, or reporting someone else's decision?
- Did the acceptance apply to this customer, this version, or a broader policy?
- Did a condition or later correction change its meaning?

Enthusiasm, repetition, and silence are weaker evidence. “That sounds promising” may invite more work rather than approve delivery. A repeated suggestion remains a suggestion until the decision process establishes otherwise.

An objection also needs context. It may leave a decision open, or an authorized decision-maker may acknowledge the objection and decide to proceed. Don't treat “no objections anywhere” as a universal requirement for a decision.

Hemory's organized Memory can surface decisions and the discussion around them. Start there; return to the relevant transcript passage when the difference between “suggested” and “approved” would change the next step. This keeps review focused on the consequential distinction.

## Keep a Commitment Separate From Its Schedule and Completion

“I'll send the revised draft” is a commitment even without a date. Record the owner and action, and leave the due date unspecified. If the work depends on receiving the draft by Tuesday, ask about timing instead of downgrading the whole statement to a vague idea.

“Sam should send the draft” is different. Depending on who says it and the team's process, it could be an assignment or merely a suggested owner. Don't rewrite it as “Sam promised” without a basis for that attribution.

Conditions change the action you can plan around. “I'll send it Friday if the figures arrive Wednesday” is a conditional commitment. Record the condition with the date so that a later reminder doesn't turn it into an unconditional deadline.

Finally, keep completion distinct. A commitment establishes an intended action. A later message, task update, delivered file, or report of completion supplies different information about what actually happened.

## Use a Record That Explains the Outcome

A useful decision or action note should answer the questions someone will have when acting on it. You can keep it brief:

```text
Outcome: What was decided or undertaken?
Type: Decision, commitment, proposal, or open question.
Scope: Which customer, project, version, or period does this cover?
Basis: Who accepted or authorized it, and in which discussion?
Conditions: What must happen first or remain true?
Owner and timing: Include what was stated; leave missing parts clear.
Later change: Add a reference when an explicit change is established.
```

Use the fields that matter to the item. A decision about report format may not need a separate owner; a promised draft does. This is a writing aid for your notes or generated output, not a requirement to fill every field for every remark.

For a confirmed choice, use a [decision log template](/blog/searchable-memory/decision-log-template/). For agreed follow-up work, see [how to create a meeting to-do list](/blog/workflows/create-to-do-list-from-meetings/).

Prefer describing the missing evidence to assigning a vague confidence score. “Launch delay proposed; no acceptance found in the discussion reviewed” tells the reader more than “Decision: medium confidence.” It also avoids calling an unaccepted proposal a decision.

## Example: Separate a Proposed Offer From a Commitment to Investigate

Consider a renewal discussion with these statements:

> Leah: “We could include onboarding at no charge.”
> Omar: “Before we put that in the offer, I'll check the delivery effort by Wednesday.”
> Nina, the account lead: “Agreed. Keep the current offer unchanged until we review Omar's estimate.”

The useful result is:

| Item | Reading supported by the exchange |
|---|---|
| Free onboarding | A proposal awaiting review, not an approved offer |
| Current offer | Remains unchanged until the estimate is reviewed, as directed by the account lead |
| Delivery-effort estimate | Omar committed to checking it by Wednesday |
| Approval of free onboarding | Still open |

“Agreed” refers to checking the effort and keeping the offer unchanged; it does not approve the opening suggestion. Reading the whole exchange prevents the summary from attaching acceptance to the wrong item.

Now suppose a later discussion records Nina saying, “I've reviewed the estimate. Include free onboarding for this renewal only.” That establishes a new choice for this renewal. It does not make free onboarding a general policy, and it does not prove that the revised offer has been sent.

## Preserve the Distinction When AI Uses the Conversation

Hemory captures spoken discussions and organizes their content, so you don't have to classify each remark while participating. Through a supported connection, an AI agent can use that context to help draft a brief, proposal, or plan.

Give the agent the output you need and ask it to preserve the distinctions that affect it. Ask your connected AI agent to retrieve the discussions and prepare the note:

```text
Use the renewal discussions available through Hemory to prepare
a short note for revising the client offer.

Separate approved offer changes, proposals awaiting approval,
commitments with owners, and questions still open.

Keep conditions and customer-specific scope with each item.
Check relevant later discussions for explicit changes. Include
references for approved changes and commitments. If a due date
was not stated, leave it unspecified. Do not infer completion
from a promise to do the work.
```

Review the items that would change the offer, assign responsibility, or create a deadline. If the draft promotes the onboarding proposal to an approved benefit, return to the exchange that determines approval. You don't need to manually annotate every casual remark before the agent begins.

That is the practical contribution of preserving the discussion: it supplies both the outcome and the surrounding exchange needed to use it accurately, with less manual note-taking and re-entry into AI.

## Update the Working Conclusion When the Evidence Changes

A decision can be settled at the time and later replaced. Keep the earlier record for its reasoning while updating the instruction used for current work.

Distinguish three events:

- **A new mention:** someone repeats or questions the old decision. This alone doesn't replace it.
- **An explicit change:** the relevant person or process changes the choice or commitment. Record the new scope and source.
- **A progress update:** someone reports starting or completing the work. Update execution status without rewriting what was originally agreed.

If a current written approval differs from an earlier conversation, compare their timing and authority. A transcript is a useful record of speech, not an automatic final authority over every later record.

For your next discussion in [Hemory](/features/), begin with its organized outcomes. Check whether a proposed next step retains the acceptance, conditions, and scope that make it usable. The goal is a clearer basis for action, without turning the whole conversation into a manual labeling exercise.

## FAQ

### Can a decision be valid without everyone explicitly agreeing?

Yes. An authorized person may decide after hearing others' views. Interpret the statement within the actual decision process rather than requiring unanimous wording in every transcript.

### Does a commitment need a deadline?

No. A person can undertake an action without stating when it will be done. Preserve the commitment and clarify timing if another task depends on it. Don't invent a deadline or treat missing timing as proof that there was no commitment.

### What if a summary and transcript disagree?

Read the relevant exchange to see what the summary may have omitted or misread. If the transcript itself is unclear, use another reliable record or ask the relevant person. Prefer the best-supported interpretation, not a blanket rule that one format is always correct.

### Can AI automatically distinguish every decision from an idea?

Automated organization can give you a useful first pass. Ambiguous acceptance, speaker attribution, and changing conditions can still affect the result. Focus review on items that would change an offer, deadline, responsibility, or other consequential action.