Check-In History and Progress Trend (Government Cloud)

Check-In History and Progress Trend

One check-in is a snapshot. A season of them is a story. The Check-In History tab on every Key Result keeps every weekly record you've ever submitted, and OKR Tracker builds a progress trend chart from that time series — so you can see not just where a KR is, but how it got there.

Key Result check-in history list with a progress trend chart Check-in history with the progress trend chart ## The history list

The history tab lists every weekly check-in for the Key Result, newest first — each with its Check-In Date, Week Number, recorded Current Metric Value, calculated Progress %, Confidence Level, and the narrative you wrote (Accomplishments, Risks/Blockers, Next Week Plan).

Because each check-in is stored as an immutable record, the list is a faithful log. Nothing is overwritten or quietly edited. If a number needs correcting, you add a new check-in — the original entry stays.

Why immutability matters

  • A defensible audit trail → when a quarterly business review asks "when did this slip?", the history answers with dates, not memories.
  • Honest signals over time → you can see exactly which week confidence dropped to Red and what the owner said was blocking it.
  • Compliance-friendly → an unalterable record of who reported what, and when, holds up under scrutiny.

How to read the trend

The progress trend chart plots Progress % across the weeks you've checked in:

  • A steady climb → the KR is compounding week over week. Keep going.
  • A flat line → progress has stalled. Two flat weeks in a row is exactly what triggers an at-risk escalation — see Reminders and At-Risk Escalation.
  • A late spike → a lot of movement crammed into the last week before a deadline. Worth a conversation about whether the KR was scoped realistically.

Pair the curve with the confidence colour on each point to separate "behind but confident" from "on pace but worried."

Beyond a single Key Result

To roll history up across Objectives and pull it out of Jira for a QBR deck or board update, see Reports and Export.