Hemory TeamOn this page
You have three useful meeting notes about a registration pilot. One records the agreed scope, another raises an exception, and a third confirms that the pilot can proceed. Sending all three links to a colleague still leaves them to work out whether the exception was accepted.
Keep the original notes, then add a short explanation of how they relate. Link the records around the same work item, describe whether each discussion proposes, confirms, clarifies, or revises something, and give readers a dated summary of the position the sources establish.
Choose the work item that connects the notes
Start with the question someone needs to answer: “Which visitors can use QR check-in in this pilot?” That is more useful than grouping every meeting containing the word “registration.”
Identify the relevant project, audience, phase, or deliverable. Two discussions can use similar language while covering different scopes. Link them as background where useful, but do not present one as revising the other unless the content supports that relationship.
If you cannot yet locate the relevant discussions, use the guide to finding past conversations by topic. This method begins once you have candidate records to connect.
Explain the relationship beside each source reference
A date tells the reader when a discussion happened. Add what it contributes to the question:
| Relationship | What to explain |
|---|---|
| Establishes | The accepted decision, condition, or undertaking recorded here |
| Proposes | An option or exception raised without established acceptance |
| Confirms | An earlier position reaffirmed for the stated scope |
| Clarifies | Meaning or scope made clearer; specify whether this is later clarification |
| Revises | The accepted change and the part of the earlier arrangement it replaces |
| Supplies current status | Delivery, review, or another later event, separate from the original promise |
These are writing aids for your own document, not required Hemory fields. Use a plain sentence when that is clearer. “Confirmed standard registration; exception still awaiting review” is more useful than a bare “related meeting.”
Where the relationship is uncertain, say what needs clarification. The latest date alone does not establish that an earlier decision was superseded.
Example: three notes connected without extending the pilot
The following fictional example illustrates the document structure. It is not actual Hemory output.
| Source | What the record establishes | Relationship to the pilot |
|---|---|---|
| September 3 planning discussion | The event owner approves QR check-in for preregistered visitors; walk-ins keep staffed registration | Establishes pilot scope |
| September 12 operations discussion | Operations requests QR check-in for walk-ins too; the event owner says this exception needs review | Proposes an extension; no acceptance established |
| September 20 readiness discussion | The event owner confirms that the preregistered-visitor pilot can proceed; the walk-in exception is still awaiting review | Confirms original scope and the unresolved exception |
Beside these source references, a current summary could read:
Position established through September 20: QR check-in can proceed for preregistered visitors. Walk-ins continue to use staffed registration. The proposed walk-in extension remains under review; it has not changed the pilot scope in these records.
This summary explains the relationship instead of making the reader infer it from three dates. It also avoids treating “pilot can proceed” as approval for every proposed extension.
In your real document, replace the source labels with links or references people can use. Add the relevant passage or enough explanation when recipients cannot open the underlying source.
Recover missing context with Hemory
A short meeting note may not preserve the response that established whether an exception was accepted. Hemory retains captured discussions as transcripts and organized Memory, giving you the surrounding exchange to consult.
For a known conversation, ask a follow-up question about the disputed relationship: “Was the walk-in extension accepted here, or left for review?” Check the relevant passage when it changes the summary you will share.
When several discussions are involved, a compatible AI agent connected to Hemory can help prepare the relationships from available context:
Use the available registration-pilot discussions to draft a short index
of related records for the question: who can use QR check-in?
For each relevant record, identify its date, source reference, and what
it establishes. Explain whether it proposes, confirms, clarifies, or
revises an earlier position. Keep different audiences separate.
End with a dated summary and any unresolved question. Do not treat a
later proposal as an accepted change. Flag relationships the available
sources do not establish.Provide current plans or task updates separately if they are needed and outside the connection’s access. The draft helps you prepare the linked explanation; it does not automatically insert backlinks into your notes or update the project system.
Keep the index where the work happens
Use your existing project page, note, or decision document. A small structure is enough:
Work item and question:
Position established as of:
Current summary:
Related records:
- Source reference and discussion date
- What it establishes
- Relationship to another record, where supported
Open question or later update needed:Keep the source notes identifiable. If you add a retrospective explanation to an old note, date it as an addition so it is distinguishable from what was known at the meeting.
For an accepted change, identify exactly which term or scope it replaces. If only timing changed, do not imply that the owner or deliverable changed too. The guide to tracking requirement changes covers a fuller timeline when that is the output you need.
Update the explanation when a relevant decision changes
When a later discussion accepts or rejects an exception, add its reference and revise the dated current summary. Keep the earlier proposal and decision distinguishable so readers can still follow the history.
Include action-critical scope in the working task or plan. A personal source link alone may not give a colleague access, and a collection of links should not be the only explanation of what they should do.
FAQ
Do I need to combine the transcripts into one document?
No. A short index can connect the relevant records while each source remains intact. Include enough explanation for the reader’s task and link to fuller detail where accessible.
Should every related note link to every other note?
Use links that help answer the work question. A project page with the relevant sources may be enough; add a reference in an individual note when it helps someone find an important clarification or update.
What if the records concern different scopes?
Explain the distinction. They may provide related background without changing each other’s decisions. If the relationship remains unclear and affects action, ask for clarification before presenting a single current position.
Use Hemory to preserve the conversations behind your notes while you participate. Later, the linked explanation can draw on the exchange itself, rather than depend on everyone remembering how the meetings fit together.
