Guides / Put your SOPs into the platform — and make them fire
Put your SOPs into the platform — and make them fire
ManagementThe binder you already have is the content. Paste an SOP in, approve the Operator's distilled version, then ask Operator91 to turn the SOP's deadlines into alerts that actually fire — here, wired into the hiring process end to end.
A hiring SOP goes in as pasted text, comes back as Operator cards for review, gets approved — then Operator91 points the manager at the two automations that make its deadlines fire, and both go live.
The steps
- Open Compliance & Safety → Policies & Procedures, press + New procedure, and paste your existing SOP — title it the way your crews say it, and set the area (here: Hiring).
- Saving generates Operator cards — the platform's distilled version of your SOP: when it applies, the steps in order, the exceptions, who's responsible. Any outside system the text names is flagged as connected or not.
- Review the cards and press Approve for Operators. Until you approve, no Operator will cite the procedure — the review gate is yours.
- Now make it fire: ask Ask Operator91 to set up the SOP's alerts. It reads the deadlines your SOP names — onboarding starts the day a driver is added, renewals begin 30 days out — and points you at the matching automation templates.
- On Automations, press + New automation and start from a template — New driver → start onboarding, Medical card expiring in 30 days. The trigger, conditions, and actions fill themselves; press Create automation.
- From then on the SOP runs itself two ways: alerts land as tasks, shift-handoff notes, and emails in the screens your team already works — and anyone asking the copilot “how do we handle a new hire?” gets your procedure, cited by name and version.
Gotchas
Good to know: A step that names a system the platform isn't connected to gets an amber flag — the Operator will say a person has to check that system until the connector is added.
Good to know: Content changes always ask why — that reason becomes the change history the next manager reads before re-trying something that already failed. Cards regenerate per version and wait for approval again.
Ready to run it on your own operation?
Every guide doubles as your team's training path — the same steps, on your data.
Get early access
OPERATOR 91