Run a playbook end-to-end
Tips for actually getting through one.
Most playbooks run in 5–20 minutes. A few (winterization, hurricane prep) take hours and span days. Both flows work the same way.
Steps
-
Start once, run anywhere
After you tap Start Check, every check is saved live. Lock the phone, switch apps, come back hours later — your progress is still there.
-
Tap an item for actions
Each item is more than a checkbox. The action chips below the title let you take a photo (evidence the task was done), add a note (free text), or log an observation (creates an Observations record linked to this item).
-
Skip an item if it doesn't apply
Tap the Skip chip on the item — it sits with the other action chips, no long-press needed — and say why. The reason is optional; if you give one, the item reads "Skipped — your reason" in the run and in the run's history.
A skipped item counts as resolved: the run can still be completed. There is no 'Mark not applicable' wording anywhere in the app.
-
A run a schedule starts
When an item has a schedule — an underway check every few hours, say — theONE starts a run for it when it comes due. That run holds only the items that came due; another that comes due while it is open joins it. Check or skip each one and Complete Run is ready.
-
When stuck, log it
If an item can't be completed because something's wrong (engine won't start, valve is seized), tap the observation chip and log it. The observation is filed with your note plus a line saying which playbook run it came from, and it stays linked to that item so you can come back. There is no 'Blocker observation logged on item N' line — the app has never written one.
-
What completion records
Completing a run stamps it finished, syncs it, and keeps it in the run history — where the checks, the notes, the photos and every skip reason stay readable.
It does NOT write to the trip log or the Maintenance Log, and a run carries no trip association to key one off. If you want a completed playbook on the deck log, write the line yourself.