Hemory TeamOn this page
Five voice notes can contain more than five useful items. One may hold a decision and a promise; another may be a duplicate you no longer need in your active list. Assigning one label to each recording can hide work as easily as it organizes it.
This example sorts five notes into decisions, ideas, follow-ups, and material to leave out of the active review. It shows how to preserve multiple items from one note, avoid inventing owners or approvals, and finish with something you can use.
TL;DR
- Classify the useful items inside a note, rather than forcing each recording into one category.
- Keep a decision and any associated follow-up: recording the decision does not complete the promised work.
- An idea can stay an idea. An unanswered question can need follow-up even before anyone accepts ownership.
- Hemory’s transcripts and organized Memory can provide the starting material; a supported connected agent can help prepare a first pass.
- Remove duplicates from the active review only when they add nothing you need. That does not automatically mean deleting the source.
Define what each category is for
Use these categories to decide what needs attention. They are not an exhaustive filing system for everything you might record.
| Category | Question to ask | What to keep |
|---|---|---|
| Decision | What choice was actually made, and by whom? | Choice, scope, relevant conditions, and basis for treating it as agreed |
| Idea | What possibility is worth returning to? | The thought, its reason, and important unknowns |
| Follow-up | What needs doing or answering? | The action or question, accepted owner if known, and real timing or dependencies |
| Discard from this review | Does this item add anything to the current work? | Nothing further in the active list when it is a true duplicate or irrelevant here |
Some material belongs as reference rather than in any of these four groups. A useful observation or explanation does not become disposable because it contains no decision or action.
Source type matters too. The five notes below are personal spoken notes. A recap reports what its narrator understood; it is not the other participants’ original wording. When a consequential agreement is uncertain, consult the original exchange or clarify it.
The five notes and the current information available
This fictional review is prepared on November 4. The five notes and supporting updates are teaching material, not actual client records or Hemory output.
Note 1 — November 2, launch call recap
“Harbor launch: the client agreed to move from November 14 to November 21. I said I would send the revised timeline by November 6.”
Note 2 — November 3, onboarding idea
“Could we combine account setup and the first-project wizard? Two customers told me they couldn’t tell what to do after creating an account. I don’t know yet whether the cause is the separate screens or the wording.”
Note 3 — November 3, pricing reminder
“I need to send Maya the approved partner pricing sheet before our November 5 review.”
Note 4 — November 3, repeated dictation
“I recorded the Maya reminder again because I couldn’t see the first note. Same task: send the approved partner pricing sheet before November 5. Nothing new to add.”
Note 5 — November 4, export question
“Could scheduled exports help Cedar’s weekly reporting? I haven’t asked them. I want to discuss the question with the account team; nobody has taken it on yet.”
For this example, the original launch-call record supports Note 1’s date change and promise. The revised timeline is not yet finished. The approved pricing sheet is available, and the sender’s task list shows it has not been sent. No one has yet accepted the export follow-up. These current facts are supplied for the review; the old notes alone would not establish completion or ownership.
Sort the items without losing their status
| Note | Classification | Reason | Result to carry forward |
|---|---|---|---|
| 1 | Decision and follow-up | The launch date was changed, and the narrator promised a revised timeline | Record November 21 as the agreed launch date; retain the separate promise to send the timeline by November 6 |
| 2 | Idea | There is a proposed change and two reported observations, but the cause is unresolved | Keep the combined-flow idea with the question about screens versus wording |
| 3 | Follow-up | A specific task remains unsent according to current information | Send the approved pricing sheet to Maya before the November 5 review |
| 4 | Duplicate; leave out of the active review | It explicitly repeats Note 3 without a new condition or state change | Keep one active task, not two |
| 5 | Idea and follow-up question | Scheduled exports are a possibility; the narrator wants a discussion, but ownership is unassigned | Preserve the possibility and raise who should explore it; do not claim Cedar requested the feature |
Note 1 is the easiest place to lose work. A decision log entry saying “launch moved to November 21” does not preserve the separate obligation to send the revised timeline. The follow-up belongs in the work list even though the note has already been classified as a decision.
Note 4 is safe to exclude from this active list because the example establishes that it is a duplicate. A note that instead said “Maya confirmed she received it” would be a meaningful status change, not repetition to throw away.
Note 5 needs attention without an invented assignee. “Unassigned” describes the current gap. It does not make the question disappear, and it does not give permission to name the account lead as the owner.
Turn the classification into a usable review
A concise result from these inputs could look like this:
Decision
- Harbor launch moved from November 14 to November 21, agreed on November 2.
Follow-ups
- Me: finish and send Harbor's revised timeline by November 6.
Current state: not yet finished.
- Me: send Maya the approved pricing sheet before the November 5 review.
Current state: approved sheet available; not sent.
- Proposed question: whether to explore scheduled exports for Cedar.
No investigation owner has accepted the work; no customer request established.
Ideas to retain
- Combine account setup and the first-project wizard.
Reason: two customers reported uncertainty after account creation.
Open question: separate screens, wording, or another cause?
- Scheduled exports as a possible aid to Cedar's reporting.
Customer need and approach still to explore.
Excluded from the active list
- The repeated Maya dictation; its task is already retained above.This is a proposed review output, not evidence that tasks have been saved or messages sent. Put the actionable items into the system you use for work. Keep the ideas available without assigning development dates just to fill a planning table.
The Cedar question is a point to raise, not a commitment someone has already accepted. For speaking an action and its reasoning clearly, see voice note templates for reminders and ideas.
If you share the review, include the deadlines, pending ownership, and uncertainty in the text. A personal source reference cannot substitute for information colleagues need to act.
Use the available records to reduce the sorting work
Start with transcripts or summaries your existing tool provides. If these notes were captured with Hemory, its transcripts and organized Memory give you a readable starting point without manually transcribing each recording. For a known note, you can ask about the decision, idea, or qualification it contains.
For a set of available notes, a compatible AI agent connected to Hemory can help prepare the first pass. Provide the current completion information alongside the task:
Review the five available voice notes described above.
Use accessible Hemory context and the current updates I supplied.
Separate decisions, ideas, follow-ups, and duplicates to omit from this review.
A note may produce more than one item.
Keep promised work even when the same note records a decision.
Do not assign owners, invent due dates, or treat my ideas as customer requests.
Combine repeated mentions of one task, while preserving real status changes.You do not need to create the full table yourself before asking. Read the draft for the judgments demonstrated above: whether a promise survived, whether an idea became an approval, and whether “available” was confused with “sent.”
FAQ
Must each note have one category?
No. One note can contain several decisions, questions, or actions. Separate the useful items when their next uses differ, while keeping enough context to understand their relationship.
Should I delete notes marked as discard?
Not automatically. Here, discard means leaving a duplicate out of the active review. Whether to retain the original record is a separate choice based on its remaining reference value and your record-keeping needs.
Does every follow-up need an owner and deadline before I keep it?
No. Keep the unresolved question or action and identify what is missing. A commitment can have no stated deadline; an unassigned question can still deserve attention.
Do I need to review all voice notes every week?
No. Review the material relevant to your work and handle urgent items when needed. A scheduled review can help some routines, but it is not a prerequisite for searchable notes or useful ideas.
Use this example on the notes relevant to your next task. With material already captured in Hemory, you can spend less time turning recordings into reviewable text and more time deciding what needs attention.
