Troubleshoot: A review has fewer Moments than expected

A review writer sees fewer Moments than they expected, or work they know happened is not represented. Moments are a curated set of meaningful evidence rather than a complete log of activity, so a shorter list is not automatically a defect.

Access and Availability

  • Review writers can see the Moments available for the review they are writing.
  • Checking or changing the performance period requires permission to manage that review cycle, including review admins and collaborators where applicable.
  • Available in the Total Platform and Perform & Goals pricing packages.
  • Applies to manual review cycles. Lifecycle Reviews are excluded from AI-Assisted Reviews and are unaffected by these settings.

Diagnose

Check: The performance period does not cover the work

  • How to check: Open the cycle's settings and look at the performance period. It is separate from the cycle's own open and close dates.
  • If true: The performance period defines the date range of work eligible to become a Moment. Work outside that range will not become a Moment for the cycle. Use the fix below.
  • If not: Continue to the next check.

Check: The activity falls outside the period even though it feels inside it

  • How to check: Compare the dates of the specific work to the start and end of the performance period.
  • If true: Take particular care with activity near the beginning or end of the period. Different sources determine dates differently, so work a writer mentally associates with the review period may not fall inside the configured window.
  • If not: Continue to the next check.

Check: The source is not supported or not connected

  • How to check: Confirm the tool the work happened in is a supported Moment source and is connected for your account. See Understand Moments in AI-Assisted Reviews.
  • If true: A tool being used by your team does not by itself mean it is currently a supported Moment source. Connected work tools are optional, and Moments are still drawn from 15Five activity without them.
  • If not: Continue to the next check.

Check: Not enough source history was available

  • How to check: Confirm when the work tool was connected, and compare that to the length of the performance period.
  • If true: Connecting a work tool does not guarantee that the whole performance period is immediately available. Historical data availability varies by integration, so a twelve-month performance period does not guarantee twelve months of source history. A recently connected tool commonly has less history than expected.
  • If not: Continue to the next check.

Check: The writer does not have access to the information

  • How to check: Consider whether the writer already has access to the work in the source system.
  • If true: AI-Assisted Reviews works within existing permissions. Two writers at the same company can have different evidence available even when the same tools are connected.
  • If not: Continue to the next check.

Check: The expectation is that all activity becomes a Moment

  • How to check: Ask what the writer expected to see.
  • If true: This is expected behavior. Falling inside the performance period makes activity eligible to become a Moment. It does not mean every message, ticket, meeting, or objective update becomes one.
  • If not: See If It Still Fails below.

Fix

Fix for: the performance period does not cover the work

  1. Open the review cycle's settings.
  2. Set the performance period to the date range the review should reflect.
  3. Save your changes. For an active cycle, see Edit settings in an active performance review cycle.

Fix for: the evidence is not available as a Moment

  1. Add a Note describing the work that should inform the answer.
  2. Add a File to the Context library.
  3. Review the available 15Five Data for a relevant record.
  4. Include another applicable Moment.
  5. Ask 15Five AI to draft the answer again, or write the answer yourself.

Validate

After the performance period is corrected, the writer reopens the review and Moments reflect work inside the new date range. Where evidence was added as a Note, File, or 15Five Data, it appears in the Context library and can inform a new draft.

If It Still Fails

Contact the 15Five Support Team with the review cycle name, the performance period, the participant, the review writer, the specific work that is missing, and where that work happened. Supported evidence that is still missing after the performance period, source history, and permissions have been checked is worth reporting.

Not Covered Here

This article does not cover reviews with no drafts at all, or drafts that appear but are inaccurate. See Troubleshoot: A review writer has no AI drafts. For what a Moment is and where Moments come from, see Understand Moments in AI-Assisted Reviews.

Related Articles

Was this article helpful?

Sorry to hear that. Tell us what was missing β†’