How to Record Tentative and Secondhand Statements in Meeting Notes

Download Hemory
On this page

“The supplier may be late” and “the supplier is late” call for different responses. If a meeting note loses that distinction, someone preparing a project update may announce a delay that has not been confirmed.

Keep the source, level of certainty, and important conditions attached to the statement. You can do this in ordinary sentences: “Priya reported a possible supplier delay; the delivery date remains unchanged.” The aim is a useful account of what is known, not a label on every line.

TL;DR

  • Preserve what the speaker knows, how they know it, and what remains uncertain.
  • Secondhand information is a source relationship, not a verdict that the information is false or unreliable.
  • A proposal, an estimate, a reported decision, and an unanswered question can require different wording. They are not mutually exclusive levels on one certainty scale.
  • Keep accepted decisions intact, including conditions. Clarify the uncertainty that affects the next step.
  • Hemory can preserve captured discussions and make their context available for later notes and supported agent drafts, reducing the need to reconstruct qualifications from memory.

Separate the source from the certainty of the claim

Two details often get combined: whether someone learned something directly, and how certain the information is.

A colleague can directly report an uncertain estimate: “I checked our progress, and I think we need another week.” Another colleague can relay a definite decision: “The review board approved the pilot this morning.” Both statements need their source preserved, but they do not have the same status.

Consider the following distinctions:

What the statement doesWhat to preserveExample of a useful note
Suggests an optionThat it is a suggestion, plus any condition“Consider a smaller pilot if training capacity is limited.”
Gives an estimateThe estimate’s range or qualification“Lee estimates roughly two weeks for setup.”
Relays informationWho reported it and the source they identified“Priya reports that the supplier expects a one-week delay.”
Reports an accepted choiceThe reported choice and its scope“Ava reports that the review board approved the five-customer pilot.”
Raises a questionWhat is still needed“The team needs to confirm whether the revised file was sent.”

A reported statement may be supported by a referenced message. Firsthand speech can still contain a prediction that does not come true. Attribution and certainty need to be assessed separately.

For work that depends on the claim, follow the relevant source or ask for the missing detail. For a routine background note, accurate attribution may be enough.

If the question is whether someone had authority to agree, use the project’s approval process. Recording assumptions and agreement covers that separate issue.

Preserve meaning, rather than copying every hedge

Words such as “might,” “roughly,” and “provided that” can materially change a statement. Keep their meaning when condensing the conversation.

But word matching alone is not enough. “Could you send the draft?” is a request, not a forecast. “I think that’s the agreed plan” may refer to an existing decision that can be checked. “We could use the smaller room” may become an accepted choice after the next speaker says, “Yes, book it.”

Read the response and relevant context before deciding how to write the note. You do not have to preserve every conversational filler, but you do need the distinction it conveys when that distinction changes the work.

Original wordingMeaning-preserving wordingChange to avoid
“We might need another week.”“An extra week may be needed.”“The deadline moved by a week.”
Priya: “The supplier told me it expects to ship Friday.”“Priya reports that the supplier expects Friday shipment.”“Delivery is confirmed for Friday.”
“The pilot is approved, but launch must wait until training is complete.”“Pilot approved; launch depends on completed training.”“Pilot approval is still pending.”
“I haven’t checked whether the file went out.”“The speaker has not checked whether the file was sent.”“The file has not been sent.”

The last example matters because uncertainty belongs to someone’s knowledge, not necessarily to the underlying event. A missing confirmation is a reason to check; it is not an answer.

Example: write a project note without changing the plan

This fictional project example illustrates the method; it is not an actual customer record or Hemory output. The current plan has a November 18 pilot date. At the November 4 review, Priya says:

“The supplier told me this morning that one component might ship a week late. I don’t know yet whether it affects the pilot kits.”

Alex, who controls the pilot schedule, replies:

“Keep November 18 for now. Let’s confirm whether the kits are affected before changing the date.”

A useful update is:

Pilot date: November 18 remains the current plan, as confirmed by
Alex at the November 4 review.

Possible issue: Priya reports that the supplier warned of a possible
one-week shipment delay for one component.

Open question: Does the component issue affect the pilot kits?
The review did not assign an owner or deadline for confirming this.

This preserves a possible problem without announcing a pilot delay. It also keeps the current date definite instead of weakening the whole update with “maybe.”

The next action is to establish the impact on the kits and arrange responsibility if needed. The note does not invent a new pilot date, a confirmed shipment delay, or a promise by Priya to investigate.

Use the recorded context when a short note is unclear

An existing project note or supplier message may already contain what you need. If it does, use it. If the working note says only “supplier late,” return to the exchange that can recover the missing qualification and scope.

If that discussion was captured in Hemory, the transcript and organized Memory preserve the spoken context. In a known conversation, you can ask what was confirmed, what was reported, and what remained unknown. For a working update drawing on several accessible discussions, a compatible AI agent connected to Hemory can draft from that context:

Draft a pilot update from the Hemory discussions you can access.
Preserve the current accepted plan. For possible changes, retain
the source, uncertainty, conditions, and affected scope.
Separate an estimated shipment delay from a confirmed change to
the pilot date. Identify the information still needed, without
inventing an owner or deadline.

Supply a newer supplier message separately if the connection cannot access it. You do not need to label every sentence or manually prepare a full timeline before requesting the draft. Hemory gives the agent recorded material to work from; your review can focus on claims that would change the plan.

Capturing the discussion also reduces the pressure to write down every qualification while participating. A detail that did not seem important at the time can still inform a later update.

Update the working conclusion when new information arrives

When the supplier confirms which components are affected, revise the current update using that new information. Keep the timing visible where it explains the change: the team had a possible issue on November 4 and a confirmed answer later.

A later answer does not change what was known at the earlier review. Nor does every new mention require reopening an accepted decision. Update the part that changed and preserve the rest.

For the next project status update, use Hemory to return to the captured discussion behind a shortened note. The uncertainty you need to explain may be a qualification you did not know to record separately at the time.

FAQ

Do I need labels such as “reported” and “proposed” on every statement?

No. Clear sentences often do the work: “Priya reports…” or “The team is considering…” Use labels when they make a dense working list easier to scan, rather than creating a separate tagging job.

Is secondhand information less useful than a direct statement?

Not automatically. A colleague may be relaying a reliable approval or message. Preserve the source and follow it when the next action needs confirmation. Direct statements can also contain estimates, assumptions, or errors.

Should an uncertain detail always stop the next step?

No. Ask whether it changes the action. You may be able to proceed with the accepted part of the plan while checking one dependency. State the relevant condition instead of treating the entire plan as unknown.

Related reading

Start building your memory palace

Download Hemory — from today on, every real conversation becomes material you can generate from tomorrow.

Get Hemory for iOS Get Hemory for Android Download APK

macOS, Windows, Linux, Web, and Self-host coming soon