# How to Prepare for a Project Stand-Up Using Past Conversations

> Prepare stand-up talking points from current tasks and past discussions. Recover relevant decisions and commitments, then focus on the blocker that remains.

- URL: https://www.hemory.com/blog/searchable-memory/prepare-project-stand-up/
- Language: English (en)
- Author: Hemory Team
- Published: 2026-11-02
- Last updated: 2026-11-02
- Summary: Start stand-up preparation with current work, retrieve missing discussion context, and compare past agreements with current delivery. A supported Hemory-connected agent can draft concise talking points. Keep meaningful carryover items, clarify remaining blockers and update the existing project record afterward.
- Tags: stand-up preparation, project coordination, conversation search

The task board says a release check is blocked. In the previous discussion, someone mentioned a configuration file, but you cannot remember whether it was missing, still being prepared, or already sent. Repeating the old blocker at the next stand-up could send the team after work that is already done.

Prepare from the current work record, then retrieve only the conversation context needed to explain a decision, commitment, or unresolved question. Turn it into a few talking points about what changed and what help is needed. The routine should support a short coordination meeting, not create another status report to maintain.

## TL;DR

- Begin with current work and the purpose of the next stand-up.
- Retrieve relevant decisions, commitments, and open questions, including older items that still affect progress.
- Compare past agreements with current delivery and later replies before carrying them forward.
- A supported agent connected to Hemory can help retrieve available context and draft talking points in one request.
- Bring the blocker, its relevant condition, and the next useful action; move detailed investigation outside the stand-up when appropriate.

## Start with what needs coordination now

Open the current task board or project record. Identify what changed, what is blocked, and where someone else's input is needed. If the record is clear, there may be nothing to retrieve.

Conversation history becomes useful when the record leaves a gap. Why was the change postponed? What input did a colleague agree to provide? Was a question answered in a later discussion?

Use the interval since the last relevant stand-up as a starting point, not a rigid boundary. An older agreement can remain active. Include known carryover items and follow references backward when they explain a current dependency.

The same approach works whether your project meets daily or at another cadence. Keep preparation focused on the coordination this meeting needs.

## Retrieve the background and draft the talking points

When project discussions are captured in Hemory, their transcripts and organized Memory give you material to return to. You can recover a dependency mentioned in passing without having selected it for detailed notes at the time.

For one known conversation, locate it and ask a follow-up question about the point you need. For several discussions, a supported connected agent can retrieve available Hemory context and prepare the talking points in the same request.

```text
Prepare concise talking points for the next Ridge project stand-up.
Use the available Hemory project discussions, the current task information
I provide, and these known carryover items: [relevant items].

Focus on decisions that affect current work, commitments and their
conditions, and questions that still need attention. Compare past discussion
with the supplied current status. Do not treat a missing later update as
proof that a task is unfinished.

For each point, state what matters now and what help or next action is needed.
Keep optional suggestions separate from agreed actions. Include a useful
source reference when a condition may need checking.
```

Replace the carryover placeholder with actual items or omit it if none are known. Provide the current task information explicitly when the agent cannot access it. The Hemory connection does not itself supply your project board or sent messages.

Without a connected agent, use the same questions to review relevant summaries and exchanges directly. Review the draft, then retrieve more detail only where a gap affects the next action.

## Ask different questions about decisions, promises, and open issues

The three information types are useful because they affect coordination differently.

For more examples of these distinctions, see [decisions, commitments, and ideas](/blog/searchable-memory/decisions-commitments-and-ideas/).

| Type | Recover from the discussion | Compare with current work |
|---|---|---|
| Decision | The agreed choice, reason, and applicable scope | Does it still apply to this task? Has an authorized change occurred? |
| Commitment | The deliverable, person who accepted it, and timing or condition | Was it delivered? Did the prerequisite arrive? |
| Open question | The unresolved issue and what was needed to answer it | Has a later reply or completed investigation resolved it? |

A summary may provide enough information. Open the relevant exchange when a condition, attribution, or interpretation changes the next action. Check current delivery using the appropriate current record.

Avoid keyword rules that silently change meaning. “I'll send it” can be a useful search clue, but a commitment may be expressed by accepting a request. “We should” may introduce a proposal. A question may have been resolved without anyone saying “closed.” Search by the subject and meaning as well as memorable phrases.

## Refine the search only where the draft has a gap

If the draft says a test depends on “the file,” look for the relevant deliverable or component name. If the date is uncertain, broaden the period. If results concern several releases, separate them before carrying a promise into the current stand-up.

Use the clues you have rather than inventing a required speaker or exact phrase. A person's name helps when you remember it, but the task may identify the relevant discussion more directly.

Stop when the point is clear enough to use or the remaining uncertainty is a specific question for the meeting. Repeated searching is unlikely to establish a status that has not been recorded anywhere you can access.

## An example: distinguish a delivered input from a remaining blocker

Suppose the previous discussion established that Lina would provide a configuration file before Omar could run the release checks. No completion date for those checks was agreed. The team also left open which sandbox account to use.

Before the next stand-up, the current task record shows that Lina uploaded the file to the shared task. Omar has acknowledged access but has not run the checks because the sandbox account is still undecided. The current project note confirms that this question remains open.

Those inputs support this short preparation note:

| Point | What matters now | What to raise |
|---|---|---|
| Configuration file | Delivered to the shared task; Omar has access | Remove it from the list of missing inputs |
| Release checks | Not run; no completion date was agreed | Confirm the plan once the sandbox is selected |
| Sandbox account | Still unresolved and blocking the checks | Ask who can confirm the account and arrange the follow-up |

A natural contribution to the stand-up could be:

> “The configuration file is available and Omar can access it. The remaining blocker is the sandbox account. Who can confirm which account we should use? Once that is settled, we can agree on the timing for the checks.”

This advances the work without reassigning Lina's completed handoff or calling Omar late against a deadline that never existed. The preparation also gives a missing-input problem a precise shape the team can act on.

## Keep the note smaller than the work it supports

Use a compact structure when you need one:

```text
Work item:
Current change or blocker:
Relevant past agreement or condition:
Question, help, or next action needed:
Supporting reference, if useful:
```

You may only need one or two points. Use the board and a short reminder when they already give you what you need.

If resolving the issue needs a technical investigation or a longer discussion, use the stand-up to identify the next coordination step. Keep the detailed source available for that follow-up rather than reading its history aloud to everyone.

The note should be understandable without access to your personal Hemory record. Include the essential condition in the talking point itself.

## Carry the outcome back into current work

After the stand-up, update the task or project record with new agreements. If someone confirms the sandbox account, record the actual account information in the appropriate place. If a colleague agrees to send it, the input is still pending until the handoff occurs.

Capture the discussion with Hemory when you start listening in a supported setup. That preserves the explanation for later use while you focus on coordination. Keep task updates in your normal project workflow; capturing the discussion does not automatically update the tracker.

Keep the reusable preparation request, but let each meeting determine the necessary searches. The stable habit is current work → missing context → useful talking points → updated work, not a fixed number of queries.

## FAQ

### How much preparation does every stand-up need?

Only enough to coordinate current work. A clear board may need little additional preparation. Retrieve background when it changes a blocker, obligation, or next step; no universal preparation time applies.

### What if the previous stand-up was not captured?

Use task comments, messages, notes, and related available discussions. Ask about a specific remaining gap. Missing one recording does not make all project context unavailable.

### Should old commitments stay in the note until I find a completion update?

Treat their current status as something to establish. Check the relevant task or delivery record before describing them as outstanding. Lack of a searchable update is not proof of non-completion.

### Can AI prepare the talking points without a manual review of every transcript first?

Yes. A supported connected agent can retrieve available Hemory context and draft against the current information you provide. Review the points that affect action and resolve consequential gaps; a complete manual extraction is not a prerequisite.

Before the next stand-up, choose one unclear blocker. Use [Hemory](/features/) to recover its spoken background, compare it with the current task, and bring the question that will actually move the work forward.