On-site · tablet · offline
● site

Field playbook

Tablet flow that survives real buildings.

Pre-site prep, consistent capture, offline drafts with a clear sync story, then office QA before PDFs and client packs leave the building.

Pre-site Capture Offline QA

The playbook is the gap between “app works in demo” and “app works in a basement with no signal.”

Pre-site

Visit · Riverside Tower
ScopeFloors 2–3 · 42 doors · access window agreed
KitCharged tablet · spare labels · PPE list
RulesPhoto standard + note style in one paragraph
OwnerSite contact + escalation if access fails
RAMSOn phone offline · correct revision
KeysFob list · return time agreed

Matches the pre-site section — agree definition-of-done before you walk the route.

If access fails, log it on the job — silent skips become audit holes.

Live capture

Inspector · offline stretch
10:02Basement · 3 doors · drafts queued
10:18Signal restored · sync started
10:19Conflict check · newer server wins
10:21QA flags · 1 missing overview photo
10:25Inspector adds photo · re-sync OK
10:30Visit marked complete · office notified

Offline is normal on site — the playbook explains how to keep control when connectivity drops.

Teach crews to look for sync errors before they drive away — fixes are faster on site Wi‑Fi.

Back at base

QA before export
✓Every door on route has an outcome or explicit skip reason
✓Photos meet the agreed standard (overview + defect)
✓IDs and locations match the register and pins
✓Read full playbook for offline policy + FAQs
✓Battery + storage headroom before long routes
✓Client comms template ready if visit slips

Close the loop in the office so clients never see half-finished packs.

Playbook below Checklist →

Pair with the inspection checklist — field flow and minimum evidence are the same story.