Reminders and At-Risk Escalation
The reason check-ins lapse isn't that people don't care — it's that nobody remembers to ask. OKR Tracker takes that job off your plate. Set the reminder once; the app does the chasing. It nudges the people who haven't checked in, and it raises a flag when a Key Result has quietly stalled — so you find out before the quarter does.
At-risk escalation banner on an objective
## The Monday reminder
A weekly scheduled trigger runs on a cron each Monday and looks at who hasn't checked in:
- It finds the gaps → any Key Result owner who has not submitted a check-in this week.
- It notifies them directly → via Jira's native notify API, so the nudge lands where they already work — no separate inbox, no chasing on your part.
This is a nudge, not a nag. Owners who've already checked in hear nothing.
At-risk escalation when progress stalls
A KR that stops moving is the early warning that an Objective is about to miss. OKR Tracker watches for it against the check-in history:
- Two weeks, no movement → if a Key Result's progress hasn't changed across two weeks of check-ins, the KR is marked At Risk.
- The Objective owner is notified → so the person accountable for the outcome hears about the stall while there's still time to act.
Red confidence escalates too
A stall isn't the only signal. If an owner reports Red confidence on a check-in, that escalates as well — surfaced through the update trigger so a deliberate "this is off track" call doesn't sit unseen until the next review.
Reminders and escalation are set up by your admin and left to run:
- Reminder day and time → when the weekly nudge goes out.
- Escalation recipient → who gets told when a KR goes At Risk.
You set these in OKR Settings — see Quarters and Reminder Schedule. After that, the app keeps the ritual alive on its own.