Hemory TeamOn this page
Your task list shows that a deliverable is complete, but your manager also wants to know why the scope changed and whether a new dependency affects the launch. Those answers may be in project discussions rather than the task record.
Combine current progress with the decisions and explanations from those conversations. Hemory helps retrieve the relevant discussion, and a connected AI agent can use it to draft an update. The result should make the project’s position clear: what is done, what changed, and what needs attention next.
TL;DR
- Search for what changed since the last update: scope decisions, dependencies, commitments, and unresolved questions.
- Begin with organized conversation outcomes and a focused question. Add names, dates, or distinctive phrases if you need to narrow the search.
- Keep past promises separate from confirmed progress. “We will finish it” is not evidence that the work is done.
- Hemory preserves and organizes spoken context; a connected AI agent can use it alongside current information you provide to draft the update.
- Report the change, its impact, and the next action or decision. Keep source context available where a reader may need to revisit an important point.
1. Start with the audience, period, and known progress
Begin with the last update and the next milestone. This gives your search a useful boundary: what has changed, and what now affects the plan?
Use the latest task or delivery record as your starting point for progress. You can give it to the agent alongside the reporting objective; there is no need to rewrite the whole record. Identify:
- The project and period covered.
- The milestone or outcome being tracked.
- The audience and any decision you need from them.
A delivery team may need detailed dependencies and owners. A sponsor usually needs the overall position, material changes, risks, and decisions requiring attention. Use that difference to decide which conversation details belong in the update.
For example:
Prepare this week’s update on the customer reporting pilot. Focus on readiness for Monday’s internal trial and whether the current access restrictions affect it.
Do not limit every search to the reporting period. If a new question depends on an older decision, retrieve that earlier context too. The update window defines what is new, not how far back you are allowed to look.
The two inputs answer different questions. Current work records show whether an export check passed or an account was configured. Saved discussions explain why the pilot excludes a format, who agreed to a dependency, or which condition must be met before customer access begins.
2. Search for decisions and changes that affect the plan
Start with the captured project discussions and their organized outcomes. Hemory brings together topics, decisions, action items, and open questions so you can begin with the relevant material instead of rereading each transcript.
Ask a question tied to the update:
What changed in the reporting pilot discussions since our last update? Focus on export scope, access permissions, the trial date, and unresolved dependencies. Distinguish agreed changes from suggestions.
Use the actual project name and date of the previous update in your request. If the response is too broad or misses a known discussion, narrow the question with the clues you have.
| What you need | A focused follow-up |
|---|---|
| Reason for a scope change | Why did we keep exports limited to CSV for the pilot? |
| A dependency | What must happen before customer accounts can join the trial? |
| An unclear owner | Did anyone agree to own the access review? |
| A possible date change | Was Monday confirmed, or was it still a proposed trial date? |
| A missing discussion | What was said about role permissions in the working session with Maya last Thursday? |
When using transcript or keyword search, try a distinctive project term, deliverable name, or phrase from the discussion. Add alternative wording if colleagues used different names for the same thing. You do not need a separate search log unless the work itself calls for one.
3. Draft the update using both sources
If your AI agent is connected to Hemory through Model Context Protocol (MCP), ask it to use the relevant project discussions and the current progress information you have. The retrieval request and drafting request can be combined; you do not need to finish a separate manual search report first.
Draft a project status update for the reporting pilot sponsor.
Cover changes since the previous update on [date]. Use the relevant
conversations available through Hemory to explain scope decisions,
dependencies, and unresolved questions.
Current progress:
- The CSV export check passed on Thursday.
- Internal test accounts are configured for Monday's trial.
- The permissions review for customer accounts is still open.
- Maya owns the review; the revised completion date is not yet confirmed.
Use these sections: overall position, completed work, decisions and changes,
risks or blockers, next steps, and decisions needed.
Keep commitments distinct from completed work. Include the source
conversation for important decisions I may need to revisit. If information
is missing, flag the specific question instead of inferring an answer.The agent helps assemble a draft from the context it can access. You add current information from sources outside that access and decide whether the overall status accurately reflects the milestone. The workflow does not require an automatic connection to every project tool.
Without an external agent, use Hemory’s Q&A to recover the relevant discussion context, then add current progress in your normal update document.
4. Resolve differences that change the reported status
Read the draft for claims that affect the milestone, rather than checking every sentence in the same way. A conversation may establish a commitment or explain a risk. To establish whether work is complete, use delivered work, test results, the task record, or an owner’s update. Resolve differences that could change the reported status.
| Conversation finding | Current information to check | How to report it |
|---|---|---|
| “We’ll finish the export check by Thursday” | The check’s actual result | Complete, still in progress, or delayed, with the relevant impact |
| The team agreed to limit the pilot to CSV | Whether a later decision changed that scope | Current scope and the reason it matters |
| Customer access depends on a permissions review | Whether the review has finished | Dependency status and any effect on the trial |
| Someone suggested moving the trial | Whether the date was subsequently changed | A proposal or a confirmed date change, as appropriate |
If sources appear to conflict, compare what each statement actually addresses. “The export is ready” may refer to the file format, while “access is not ready” may refer to who can use it. Those can both be true.
Check the surrounding exchange when a distinction affects the update. A later mention is not automatically a replacement decision, and an unsuccessful search is not proof that no agreement exists. If the gap matters, ask the owner a focused question and keep the unresolved point visible in the draft.
Then choose an overall position that matches the milestone. If internal accounts are ready but customer permissions are still under review, “ready for the internal trial; customer access pending” is more useful than calling the whole pilot blocked.
A project status update template
Use this structure as a starting point. Keep routine detail short and give more space to changes that require attention.
PROJECT:
REPORTING PERIOD:
NEXT MILESTONE:
OVERALL POSITION:
State where the project stands against the milestone and why.
COMPLETED WORK:
List outcomes confirmed during this period.
DECISIONS AND CHANGES:
State the change, its reason, and its effect on the plan.
RISKS OR BLOCKERS:
Describe the issue, impact, owner, and next checkpoint.
NEXT STEPS:
State the action, owner, and agreed timing, where available.
DECISIONS NEEDED:
Name the question, decision owner, and timing needed.
SOURCE CONTEXT:
Keep references for material decisions or details worth revisiting.Worked example: reporting pilot update
Suppose the captured planning discussion confirms two choices: keep the pilot export to CSV so the trial can focus on reporting accuracy, and run an internal trial before enabling customer access. The latest work records provide the progress described in the drafting prompt above.
The resulting update could read:
Overall position: Ready for Monday’s internal trial. Customer access remains dependent on the permissions review, whose completion date is still unconfirmed.
Completed: The CSV export check passed on Thursday. Internal test accounts are configured.
Decisions and changes: The pilot remains CSV-only so the trial can focus on reporting accuracy. The internal trial will proceed before customer accounts are enabled, as agreed in the planning discussion.
Risk: An extended permissions review could delay customer participation. It does not currently block the internal trial.
Next steps: Run the internal trial on Monday. Ask Maya to confirm the revised review date before setting a customer-access date.
Decision needed: After the internal trial, decide when to invite customer users based on the trial findings and permissions review.
Source context: Pilot planning discussion; Thursday’s export check; latest access-review update.
The conversation supplies the reason for the scope and sequence. Current work records supply completion and readiness. Combining them makes it clear why the project can proceed with one milestone while another remains uncertain.
The sponsor can now distinguish work that can proceed from the decision that still needs more information.
5. Keep the next update easy to prepare
Save the issued update as the starting point for the next reporting period. In the next cycle, look for changes to its open questions, commitments, and milestone assumptions.
During new discussions, focus on resolving the work rather than manually preserving every remark. Where capture is appropriate, Hemory keeps the conversation available and organizes the outcomes for later use. You can return to a relevant detail even if it did not seem important enough to note at the time.
For agreed follow-up work, use the organized meeting action items to clarify owners and next steps. Keep current completion information in the work records you already rely on. The next update can then combine the new discussion context with actual progress.
FAQ
How far back should I search?
Start with discussions since the previous update. Go further back when a current change depends on an older decision, condition, or commitment. Search depth should follow the question, rather than a fixed number of meetings.
What if I cannot find a decision?
Try a different project term, participant, or approximate date. Check the likely written record as well. If the point still affects the update, ask the decision owner. Say that the decision needs confirmation rather than claiming that no decision was made.
How should I report a changed decision?
State the current agreement, what changed, and its effect on scope, timing, or dependencies. Include the reason when it helps the audience understand the plan. A proposal to revisit a decision should remain a proposal until agreement is established.
Can an AI agent write the whole update?
A supported agent connected to Hemory can help draft it using captured context and current information available to it. Review the overall position, completion claims, and commitments before sharing. The most useful input is a clear reporting objective and accurate current progress, not a manual rewrite of every meeting.
Use Hemory to keep the spoken decisions behind your next project update available, so preparation can focus on what changed and what needs to happen next.
