Scheduling Built Around Recurring Restaurant Accounts
A hood cleaning business lives on repeat work on a fixed cadence. HoodOps schedules, routes, and dispatches that work — and sets each account’s next service from its NFPA 96 requirement, not a sticky note.
What it does
Recurring service scheduling
Set an account once and it comes back on its own cycle — monthly, quarterly, semiannual. No rebuilding the calendar every month, no account slipping past its due date.
NFPA 96 Table 12.4 frequency cadence
Each kitchen's cooking type sets its required frequency under NFPA 96 Table 12.4 — solid fuel monthly, high-volume quarterly, and so on. HoodOps sets the next service date from that requirement, so the schedule matches the code instead of a guess.
Route optimization
Group the day's jobs by where they are, not the order they were booked. Fewer miles between roofs, more jobs in a shift.
Crew & territory dispatch
Assign work by crew and territory and push it to the field. Everyone sees their day; the office sees all of them.
Where the schedule becomes the record
A scheduled job isn’t done when the crew leaves — it’s done when the NFPA 96 report and certificate exist. Because the cadence is built from the Table 12.4 requirement, every completed service already carries the frequency it was due on.
See how NFPA 96 reporting works →More of the platform
- Mobile field app
Offline capture, auto-labeled before/after photos, and a report that builds itself.
- Invoicing & job costing
Estimates, invoicing and payments, plus what each job actually earned.
Priced by accounts, not seats
Schedule as many crews as you want — you only pay for how many customer accounts you serve.