Procedures your team actually follows
Opening and closing, temperature checks, waste and cash logs, equipment care, incidents and production, run the same way on every shift and reported by location. Boards, procedures and runs, on a phone.
Three pieces, one engine
Clean the ice machine and bake a batch of sourdough are the same object with different steps and statuses. Nothing is hard-coded.
Board
Owns the status flow and, if you want, the things it is about: fridges, machines, products. Opening & closing, Fridges & freezers, Equipment, Incidents are boards.
Procedure
The SOP itself: ordered steps, who does it, when it starts, what counts as a fail and what happens then. Versioned, so old runs keep the steps they were done with.
Run
One execution on a phone: step results, photos, temperatures, signatures and timestamps, moving through the board's statuses until it is complete.
Four kinds of board, every view you need
Pick a kind and the right views come with it. Start from a template or build your own statuses, colours and rules.
Starter templates. Every step, status and schedule stays editable.
Workflow
Work that moves through statuses: production, requests, approvals, incidents.
Board · timeline · list · table · calendar
Log
Each run is a record, no progression: waste, closeouts, temperature checks.
Table
Routine
Recurring scheduled checks: cleaning, equipment care, opening and closing.
Calendar · list · board
Project
One-off work where the time each stage takes matters: tasks, policy reviews.
Board · timeline · list · table
Now boards, not separate products
Waste control, maintenance logs and incident reports used to be three apps. They are three boards now, so they share steps, triggers, photos and reports with everything else you run.
Waste log board
Log the item, quantity and reason in seconds. Cost comes from the supply product, and the SOP waste report shows it by location, reason and item.
Equipment care board
Machines are items with a serial number and a photo. Daily cleans and weekly inspections run on a schedule; anything marked out of service raises an issue.
Incident tracker board
Report what happened with severity and photos, then move it through review to resolved. Every status change is on the run with who and when.
What a step can ask for
Steps can be required, conditional on an earlier answer, restricted to a job, or marked as evidence. A pre-check block can gate the rest of the run.
Checkbox
Done or not, optionally required
Number with a range
Temperature, weight, count. Out of range fails the run
Choice
Good / Needs attention / Out of service
Photo
One or several, with a minimum
Signature
Drawn on the phone, kept on the run
Timer
A target time and the elapsed time
Scan
A QR or barcode, matched to the item
Instruction
How to do it, with formatting
Critical control point
A fail schedules a recheck and blocks completion until a corrective action is recorded
Runs start themselves
You decide when a procedure is due. Fork creates the run, assigns it to a job or to whoever is on shift, and chases it when it is late.
On a schedule
Daily, weekly or monthly at a time, or every N days after the last completion.
When a shift starts or ends
Per location, optionally per job, with an offset. The opener gets the opening checklist.
When another run finishes
Morning bake done? Start "Restock pastry case".
When a date is reached
Use-by dates on items start the check before they lapse.
From a QR code
Every item prints a code. Scan the fridge, start its temp check.
By hand
From the board, the procedure or the item, when something comes up.
What was missed, where, and what it cost
Seven SOP reports by location and period, printable and exportable as PDF, next to your labor and purchasing reports.