A Moment is a piece of evidence about work that actually happened, gathered so a review writer can decide what is worth including. Moments are drawn from the performance period set for the cycle, and each one shows what it came from so the writer can check it before relying on it.
This article applies when AI-Assisted Reviews is the review experience selected for the cycle.
What a Moment is
Moments are evidence, not conclusions. 15Five AI gathers them first and then works out which review questions they help answer, rather than generating evidence against the wording of a question. That order matters, because generating evidence to fit a question can bias the result toward whatever the question appears to be looking for.
The writer decides what happens to each Moment. Evidence the writer excludes is not used when 15Five AI drafts, and 15Five AI does not introduce evidence the writer has not been shown.
Where Moments come from
Moment evidence can be produced from supported connected work tools, including Slack, Microsoft Teams, Jira, Asana, Zendesk, Linear, GitHub, Google Drive, OneDrive, Notion, Kona, and Google Calendar. Connected work tools are optional. A customer with none connected still uses AI-Assisted Reviews, with Moments drawn from 15Five activity.
Certain 15Five activity can contribute as well, including check-ins, objectives, and 1-on-1 activity.
What does not become a Moment
Not every piece of context becomes a Moment, and this is the distinction that causes the most confusion:
- High Fives do not currently produce Moments. A writer can still include them for a specific question through 15Five Data in the Context library, where they can inform a draft.
- 1-on-1 notes can inform a draft directly through 15Five Data. Separately, certain 1-on-1 activity and feedback observations can contribute to Moments.
- Company Context does not become a Moment. Its role is to provide organizational framing rather than evidence.
So a writer who does not see a High Five represented as a Moment is seeing expected behavior, not a gap.
How the performance period applies
The performance period set for the cycle is separate from the cycle's own open and close dates. It sets the boundary for what can become a Moment. Not everything inside that period becomes one.
Working with Moments while writing
Moments live in the Context library alongside 15Five Data, Notes, Files, My Context, and Company Context. Existing permissions apply inside the Context library, so a writer only sees what they already have access to.
While writing, a writer can include another applicable Moment, add a Note, add a File as context, review 15Five Data for a relevant record, or write an answer themselves. They can also add context and ask 15Five AI to draft again.
For the writing walkthroughs, see Write a manager review with AI-Assisted Reviews and Write a self review with AI-Assisted Reviews.
If Moments appear empty or sparse
A sparse or empty result is not automatically a defect. Moments are a curated set of meaningful evidence rather than a complete log of activity, so falling inside the performance period makes activity eligible to become a Moment without guaranteeing that it becomes one. To work through the specific causes, see Troubleshoot: A review has fewer Moments than expected.