Summary
Check-ins are the heartbeat of your OKR system — the regular moments where progress is recorded and context is captured. This article explains how check-ins work in Brev, what happens when you submit one, and what makes a great check-in.
What Is a Check-In?
A check-in is an update submitted to a goal that records:
The current value (for Metrics) or status (for Projects/Milestones)
A confidence level (on track, at risk, off track)
Optional commentary — context, blockers, next steps
Every check-in is timestamped and attributed to the submitter. Together, they form the complete history of a goal — the story of what happened, not just where it ended up.
How Check-Ins Are Triggered
Check-ins happen in three ways:
1. Proactive — Owner-Initiated
The goal owner opens the goal anytime and submits an update. No prompt needed. This is the most flexible approach and works for teams that have strong self-discipline around goal updates.
2. Reminder-Triggered
Brev sends a check-in reminder to the goal owner based on the configured frequency (weekly, bi-weekly, or monthly). The reminder includes:
The goal title
Current progress
A link to update directly
Clicking the link opens a lightweight check-in form — no need to navigate the full app.
3. Cadence-Triggered
During Cadence meetings (WBRs, QBRs), Brev surfaces goals that need updating as part of the meeting agenda. The team reviews them together, and updates can be submitted live during the meeting.
Submitting a Check-In From the Goal Detail View:
1. Open any goal.
2. Click Update or Add check-in.
3. Fill in:
Current value (for Metrics) — the number right now
Status — On track, At risk, Off track
Commentary — what happened, what's next (optional but valuable)
4. Click Submit.
Quick Check Ins - Drag and Release
From a Reminder Link:
1. Click the link in your reminder email or Slack notification.
2. A check-in form loads with the goal pre-filled.
3. Enter your update and submit.
4. Done — no login friction if you're already authenticated.
From Slack:
If your Brev-Slack integration is active, you can update goals via a Slack command or by responding to a Brev bot prompt. See the Updating Goals in Slack article.
What a Good Check-In Looks Like
A check-in with just a number is better than nothing. A check-in with a number and context is infinitely more useful.
Weak check-in: > Current value: $480,000
Strong check-in: > Current value: $480,000 — On track. > Closed 3 enterprise deals this week. Pipeline still strong; concerned about renewals in late March. Targeting $510K by EOM if nothing slips.
The strong version gives anyone reading it — today or six months from now — a clear picture of what was happening.
Pro tip: Treat your check-in commentary like a one-paragraph memo to your future self. When you're writing the end-of-quarter retrospective, you'll thank yourself for the context.
Check-In History
Every check-in is stored permanently in the goal's Detail View under Check-in History. You can see:
The date and time
Who submitted it
The value recorded
The status at the time
Any commentary
This history is searchable and exportable. It's also what Brev's AI uses to surface trend insights and risk signals.
Skipping a Check-In
If nothing has changed, you don't need to submit a full update — but you should acknowledge it. Brev lets you submit a "no change" check-in with one click: "Same as last week." This resets the staleness timer without requiring you to re-enter data.
⚠️ Note: Goals with no check-in for 14+ days are automatically flagged as "potentially stale" in the Goals view and in AI Insights. Even a "no change" check-in prevents this flag.
Who Can Submit a Check-In
By default, only the goal owner submits check-ins. Workspace admins can also submit on behalf of an owner. Teammates can leave comments on any goal they have access to, but comments are not the same as check-ins — they don't update progress or reset the staleness timer.
More Questions?
As always, feel free to reach out to us at [email protected] with any questions or directly chat with us in the Brev app.