Held over? OffYet traces your relief chain and tells you when you can go home.
Requires an active OSS-Riverside login.
You can leave
about 10:40 AM
3 stations deep
about 2 hr 40 min after shift change
via ST17 → ST31 → ST64
Example reading for a made-up crew, Tue 10/27.
The problem
Your phone buzzes. “When are you home?”
You open OSS. Then another screen. Then eight more.
You still don’t know.
With OffYet, you can tell them in about 30 seconds.
It follows the chain for you.
Signs in as you
With your own OSS-Riverside login. It reads the schedules you can already open, and nothing else.
Gives you a time
Drive time from each station plus a 20-minute passdown at every handoff. Marked as an estimate, because it is one.
Shows how deep it goes
Your relief, the station holding them, and theirs, until it reaches the crew that moves first.
Texts it home
One tap, from your own phone.
The answer, sent home in one tap.
Held over. My relief should get here around 10:20 AM, so I’m off around 10:40 AM. Chain is 3 stations deep. (estimate via OffYet)
Written for youThe night before, it opens with “Looks like I’ll be held over tomorrow.”
Sent from your phoneIt opens your share sheet with the text filled in. OffYet never sees who you send it to.
No namesThe message carries times and depth, never anyone on the chain.
Free during early access.
$0
during early access
$5
day pass, later
$60
a year, later
It pays for itself with one holdover. You’ll get 15 days’ notice before paid plans start, then a 30-day free trial from that day. No card until you choose to pay.
How your login is protected
OffYet signs in to OSS-Riverside as you, so it needs your login. This is exactly how that login is handled.
You
Enter your OSS login once, over HTTPS.
OffYet
Stored encrypted at rest with AES-256-GCM.
The key is kept outside the database.
OSS-Riverside
Read only. One request at a time, for your own lookups.
- How it’s stored
- Encrypted at rest with AES-256-GCM. Your OSS username, password and device trust are encrypted before they’re saved. None of it is kept in plain text.
- The encryption key
- Kept outside the database, versioned and rotatable. A copy of the database can’t be read on its own.
- What it reads
- Your own schedule and profile, and the schedules of the stations your chain passes through. Only for your own lookups.
- What it changes in OSS
- Nothing. It never writes to OSS, and it sends one request at a time.
- Logs
- Never logged. Your login never appears in logs, error messages, or anything sent to a browser, including yours.
- Deleting your account
- Your login is deleted with it. Cached schedules expire after 7 days.
- Admin access
- Two-factor sign-in required, and every admin action is written to an audit log.
- Sharing
- Nothing is sold or shared. The only outside companies that hold your data are the ones that run OffYet, such as hosting and the database, and they can’t use it for anything else.
Built by a fellow firefighter.
OffYet is independent. It isn’t affiliated with, endorsed by, or run by CAL FIRE, Riverside County, or OSS.
Before you sign up
Is this official?
No. It’s built by a fellow firefighter and isn’t affiliated with CAL FIRE, Riverside County, or OSS.
How accurate is it?
It’s an estimate. It counts how deep the chain runs and adds drive times and passdown. It can’t see late calls or decisions made that morning.
Who can use it?
Anyone with an active OSS-Riverside login. That login is how it checks.
Does it work outside Riverside?
Not yet. It reads OSS-Riverside.
When can I go home?
Requires an active OSS-Riverside login.