Recurring operational checklists your team actually finishes.
Checklists spawn on a schedule, escalate as the deadline approaches, and lock when the window closes — leaving proof of what got done, when, and by whom.
Cloud beta · 14-day trial · Self-hosting available today
- Food service
- Facilities
- Labs
- Field ops
How it works
Schedule it. Run it. Prove it.
One template defines the work and its recurrence. Everything after that happens on its own.
01 · Schedule
Templates spawn occurrences
Set the recurrence once. Each occurrence arrives with its own due window and grace period — no one has to remember to create it.
02 · Run
The runner holds the line
Items can require a photo, a number, or a note. Skipping isn't silent — it takes a written reason.
03 · Prove
History and the exception ledger
Every action is recorded with a name and a time. Misses land in a ledger that has to be acknowledged.
Deadline tiers & locking
Colour means one thing: how long you have left.
An occurrence moves from on-track to due soon to overdue to critical, then locks. The countdown is always visible, so triage takes a glance rather than a meeting.
After the lock, the record is closed. Nothing gets back-filled at the end of the month.
Reasons & approvals
A skipped item still has to be explained.
Marking something N/A takes a written reason, and that reason counts as complete — so the checklist stays honest instead of quietly half-done.
Where sign-off matters, finishing can require manager approval. The approver's name and time are part of the record.
Audit-grade history
Every miss is on the ledger until someone owns it.
When a window closes unfinished, the occurrence becomes an exception. It stays on the ledger — with what was missed and who it belonged to — until a manager acknowledges it.
That record is the deliverable: proof work happened, when, and by whom. Export it whole.
Works on phones
Built for the walk-in, the roof, and the plant floor.
The runner is the same on a phone as on a desk: big targets, one item at a time, the countdown always in view. That's where the work actually gets done.
Two editions
We run it, or you do.
Same product either way. The difference is whose infrastructure it sits on.
Cloud
We host it at yourteam.task-raven.com. Every tenant gets a fully isolated dedicated instance with its own database — not a shared table with a tenant column.
- Dedicated instance and database per tenant
- Backups, upgrades and monitoring handled
- 14-day trial
Self-hosted
The same product on your infrastructure, licence-based. For teams whose data policy — or auditor — says it stays in the building.
- Your servers, your database, your backups
- Docker Compose, one host to start
- Annual licence, no per-seat metering
Stop asking whether it got done.
The cloud beta is opening in batches. Tell us about your operation and we'll get you a dedicated instance.
Request beta accessbeta@task-raven.com