What changed
- What is different since the last conversation?
- Which decision or update should be remembered?
- What context would be painful to reconstruct later?
Template
Meeting memory is the practical thread between one conversation and the next: what changed, what still needs action, and what might matter later.
Use this manually, or let EvalSuite capture it automatically from real meetings.
Use the prompts to make the next manager action explicit. The goal is not a perfect document; it is a short record that helps the next conversation start with context.
EvalSuite is built around this loop: meeting records, carried-forward action items, manager-private context, teammate history, and review-ready evidence stay connected instead of becoming scattered notes.
Keep the recap, changed context, owner, unresolved commitment, and source. Avoid preserving raw fragments that do not help the manager follow through or prepare fairly.
A manager finishes a 1:1, records the decision and open commitment, then starts the next 1:1 from the same thread instead of reconstructing it from memory.
The visible output should be concrete enough to inspect.
This page links to related acquisition pages and canonical docs instead of duplicating support content.
EvalSuite adds the durable layer: capture, follow-through, history, and review-ready context.