Mark an event
A hard call, a tough stretch, a big change. Mark it, and the weeks of check-ins that follow will tell you how the team is really coming back. Team trends only, never one person's answers.
If you're reading this the morning after something hard, start with step one. The setup is short. The rest of this page is about what comes after.
When to mark an event
A critical incident. A loss in the unit. A major call, a big training, a policy change, a change in leadership. If your team went through it together, it's worth marking. Marking ordinary events also makes the tool familiar, to you and to them, before the day it really matters.
How it works
Open Mark an Event
From your My Crew dashboard, choose Mark an Event in the quick actions row.
Describe what happened
Pick an event type and the date. The short name is optional; it's how the event appears on your dashboard. In "What happened?", write a sentence or two so check-ins can acknowledge the event with the right touch. Sanora draws on your words when it acknowledges the event, so assume your team will meet them. Write plainly; the tone you set here is the tone they'll get. For a loss, that might be: "We lost one of our own this week. Services are Saturday. People will be carrying this differently."
Choose the window and the teams
Track impact for 30, 60, or 90 days. Recovery isn't linear, so for heavier events choose 60 or 90: teams often rally in week one and dip weeks later. Then pick the teams that were affected. Careful with the default: leaving it empty applies the event to everyone in your organization. Starting small is fine.
Decide how actively to follow up
Two optional toggles, both off by default, and most events need neither. Required on next check-in means each affected member's next check-in opens by acknowledging the event. They choose whether to engage with it, and their answers stay private either way. Use it rarely; the check-in belongs to your people. If you do use it, tell your team what it means in your own words: nothing is required of them, their next check-in just knows what week it is. Send notification sends one text and email inviting the affected teams to check in. On a hard week, a message from a platform lands worse than a word from you. Say your own piece first and let Okaya follow.
Follow the recovery, and act on it
Your dashboard now shows the event next to your baseline: quick metrics, trends, and conversation topics for the event window alongside the same numbers from all check-ins. Early on, that tells you whether the support you brought in is landing. Around week three, when attention fades, it shows you the quiet dip you'd otherwise miss. And weeks later, if the hallway says fine but the trend disagrees, that's a reason for one more conversation with the team, one you wouldn't have known to have. The event stays available under Filters for the whole tracking window.
That's it
Talk to your team, mark the event, and let the next few weeks tell you where to look.
Frequently asked
What will my team members see?
Their next check-in acknowledges the event and gives them room to talk about it, or not. It's the same private conversation as always, with one difference: it knows the week it's landing in. If you made the event required, it opens the check-in; members still choose how much to engage.
Can I see how a specific person is coping?
No. Individual answers aren't shown to any leader or admin, on any screen. If you're worried about one person, that's a conversation, not a dashboard question.
What happens if someone is really struggling?
Okaya offers that person crisis resources and a path to human support, directly and privately. You won't be told who. They won't be left without a door.
What should I write in "What happened?"
One or two plain sentences: what happened, anything time-bound (services, an investigation, a return date), and how people might be affected. Skip names and graphic detail. Write it as if your team could read it.
Can I mark something that happened last week?
Yes. Set the date to when it happened. The tracking window starts from that date.
What if two events overlap?
Each is tracked separately, and you can switch between them under Filters. If more than one is marked required, members see one at a time, earliest first. Better: keep required prompts rare enough that this never comes up.