Check-ins

Check-ins are regular progress updates on your Key Results. They keep your team aligned and help identify blockers early.

Why Check-ins Matter

Regular check-ins are the heartbeat of successful OKR adoption. They help you:

  • Track progress consistently throughout the cycle
  • Identify at-risk objectives before it's too late
  • Keep the team accountable and aligned
  • Build a history of progress for retrospectives

Recommendation

Set a weekly cadence for check-ins. Consistency is more important than frequency — pick a day and stick to it.

The Check-in Page

Navigate to the Check-ins page to update all your Key Results in one place. The page shows all Key Results assigned to you, grouped by objective.

For each Key Result, you can update:

  • Current value — The latest measurement (for metric and percentage types)
  • Completion status — Mark milestones as done
  • Confidence — Your assessment of hitting the target
  • Note — Optional context about progress or blockers

Submitting Check-ins

  1. Go to the Check-ins page
  2. Update the values for each Key Result
  3. Adjust confidence scores as needed
  4. Add notes for any Key Results that need context
  5. Click "Submit Check-in" to save all updates
You can check in on any Key Result, not just ones you own. Runsheet uses a trust-based model — anyone can update progress.

Confidence Scoring

During check-ins, update the confidence score to reflect your likelihood of hitting the target:

  • On Track — Everything is going well, expect to hit target
  • Needs Attention — Some concerns, may need adjustments
  • At Risk — Significant blockers, unlikely to hit target

Confidence scores appear on the Dashboard and help managers identify where to focus support.

Check-in History

All check-ins are recorded with timestamps and the author who made the update. You can view the history of updates for any Key Result by opening the objective detail view.

This history is valuable for:

  • Understanding how progress evolved over time
  • Running retrospectives at cycle end
  • Identifying patterns in your team's performance

Check-in Cadence

Workspace admins can configure the expected check-in frequency in Settings:

  • Weekly — Most common, good for fast-moving teams
  • Biweekly — Balanced frequency for longer cycles
  • Monthly — Less overhead, but less visibility

Best Practices

  • Check in at the same time each week for consistency
  • Be honest about confidence — early warnings help the team respond
  • Add notes for significant changes or blockers
  • Review check-ins in team meetings to discuss progress

Related Topics