The Golden Rule: Slack First
Slack (or your team's equivalent) is the primary operating system for the operation — not a nice-to-have alongside texting. All shift handovers, maintenance issues, and operational updates live here, full stop.
- Centralization: all data must be visible to the entire 24/7 cycle, not just whoever was on shift when it happened.
- The goal: move communication out of private text threads and into searchable, triaged channels.
Communication Tier System
To protect focus and make sure urgent issues actually get seen, every message gets sorted into one of three tiers before it goes anywhere.
| Priority | Channel | Definition | Action required |
|---|---|---|---|
| Urgent | Text / call | Threats to life, property, or immediate operational shutdown. | Call or text immediately; document in the primary channel once stabilized. |
| Transitionary | Text / email | New hires, re-hires, or ops partners without active platform access yet. | Use for onboarding coordination only; move to the primary channel within 24 hours. |
| Standard | Slack | Shift reports, "what's up with this?" flags, equipment issues, scheduling. | Use the designated forms/threads for that issue type. |
The Onboarding Exception Protocol
New hires, re-hires, and certain ops partners often don't have platform access on day one — that's fine, but it's an exception with a strict expiration, not a standing workaround.
- The 24-hour rule: texting is permitted for coordination during the first 24 hours of an employee's start or return date, and only that window.
- Immediate integration: the shift lead or ops manager is responsible for getting the individual into the workspace and the app installed by the end of their first shift.
- Reporting via proxy: if someone without access yet flags a non-emergency issue, a team member with access "proxies" that report into the primary channel so it still gets triaged.
Standardized Workflows
Once access is granted, every report follows one of a small set of standard forms — consistency here is what makes the archive searchable later.
- Beginning / End of Shift (BOS/EOS): the backbone of 24/7 continuity — nobody starts a shift blind.
- "What's up with this?": the catch-all for anomalies, broken equipment, or process confusion.
- Triage: leads react to posts to confirm receipt and route the issue to the right department — visible acknowledgment, not a silent inbox.
The Text-Messaging Sunset Strategy
The end goal is to make texting for operational reasons unnecessary — not by banning it, but by fixing whatever keeps forcing people back to it.
- Post-emergency audit: every time a text goes out for an emergency, ask what process failed that made a text necessary.
- Onboarding audit: if someone is still texting after 48 hours, that's a signal to run a "tech check" and fix their setup immediately.
- Notification hardening: tune notification settings (high-priority tags, escalation pings) so the primary channel carries the same urgency as a text — so there's no reason to default back to it.
Summary for the Team
"We respect your time. By moving away from text and into a shared system, the person on shift has the info they need, and the person off shift isn't being bothered. Texting is for fires, property threats, and the first 24 hours of onboarding. Everything else goes through the channel." — How this gets pitched to the team
This is a sample of the kind of operational SOP I build as part of a Mobility Operations Roadmap or Compliance & Safety Audit engagement — the unglamorous documentation that turns "we have the technology and the funding" into an operation that actually runs clean under a city audit or an investor's diligence review.
It's written to be dropped into any 24/7 field operation — fleet, transit, campus mobility — and adapted to whatever tools that team already runs on.