Standing Orders Template for Small Ops Teams: The One-Page Order Sheet That Runs the Shift Without You

Every small team runs on invisible orders — the things the owner would say if you could ask. Standing orders make them visible: one page that says what "normal" looks like, what you're authorized to do alone, when to wake somebody up, and what never gets touched. This template turns tribal knowledge into a standing order sheet you can hand to whoever is on duty — and it's the difference between a team that runs the shift and a team that waits for the boss.

TL;DR: What Standing Orders Give You

• The gap they close: when the owner is asleep, in a meeting, or on a plane, the shift still needs decisions — standing orders are the decisions, written down in advance.
• The one page: seven sections — watch conditions, escalation triggers, delegated authority, comms plan, battle rhythm, never-do list, day-close checklist.
• The rule of thumb: if a question comes up twice, it becomes a standing order; if it happens three times, it gets a checklist of its own.
• The payoff: fewer 2 a.m. pings, faster first response, and a team that acts instead of waits.

Why Most Small Teams Run Without Standing Orders

In the military, standing orders are the set of instructions that remain in force until changed — the sentry doesn't ask what to do if the patrol is late; the answer is already on the card. In small ops teams the equivalent rarely exists. Everything lives in the owner's head: which alerts matter, who can approve a $200 spend, when it's acceptable to reboot the staging box. So when the owner is unreachable, the shift does one of two things — nothing, or something regrettable.

The symptoms are easy to recognize:

• Affordable decisions wait hours because "I wasn't sure if I was allowed."
• The same escalation question gets asked in three different chats and answered three different ways.
• The first incident of the night starts with "I didn't want to wake you, but…"
• Everyone's judgment is fine — nobody wrote it down.

Standing orders fix this with one document and one habit: write down what you'd decide anyway, while you're calm, so the shift doesn't have to guess while you're gone.

The Standing Orders Sheet: Seven Sections

One page. If it runs past two pages, you're writing a policy manual — cut it back until everything fits on the page someone actually prints.

1. Watch Conditions (what "normal" looks like)

Define the shift's default state so deviations are obvious:

• Expected traffic range, batch jobs, and their finish times
• Which dashboards are checked, at what cadence
• Green/yellow/red definitions for the three systems that matter most

2. Escalation Triggers (when to wake somebody)

Name the exact conditions — not "use judgment," but lines that are crossed or not:

• Revenue-affecting outage > 10 minutes → call, then escalation policy
• Security signal with admin credentials → call immediately, page on-call
• Staging down, single worker down, cosmetic bugs → log it, fix it, mention at handoff

3. Delegated Authority (what you can do alone)

The money-and-risk section. Borrow from your delegation of authority and keep the numbers explicit:

• Spend: up to $___ per incident, $___ per day, no approval needed
• Reboot/restart: allowed for listed services, forbidden for the two named critical ones
• Customer comms: template answers allowed; promises of refunds, credits, or dates forbidden

4. Comms Plan (who hears what, where)

• Status channel where the shift posts a one-line update every 2 hours
• Who the incident commander is when the owner is away (incident commander checklist)
• Handoff: written, at a fixed time, using the handoff checklist

5. Battle Rhythm (the shift's fixed beats)

Recurring events that happen regardless of chaos: dashboard sweep at shift start, mid-shift patch window check (maintenance window policy), end-of-shift audit sweep (daily ops audit).

6. Never-Do List (the guardrails)

Every team has three to five actions that are always wrong, always tempting: raw SQL against prod during an incident, disabling alerts "just for tonight," sharing credentials over chat. Name yours on the sheet.

7. Day-Close Checklist

Five items, two minutes: open items logged with owners, handoff written, dashboards green-or-explained, tomorrow's known events listed, sheet date updated.

The Copy-Paste Standing Orders Template

STANDING ORDERS — [TEAM/SHIFT]                      Sheet date: ____
Valid until changed. When this sheet and a human disagree, the sheet wins
until the owner says otherwise.

1. WATCH CONDITIONS
   Normal traffic: ____ req/min ± ____   Batch 0230-0310   Dashboards: ____
   GREEN = ____   YELLOW = ____   RED = ____

2. ESCALATION TRIGGERS (call = phone, not chat)
   [ ] Revenue-affecting outage > 10 min .......... CALL OWNER, then IC checklist
   [ ] Admin-credential security signal ........... CALL NOW, page on-call
   [ ] Payment/checkout errors > 5 in 15 min ...... CALL, payment outage playbook
   [ ] Staging down / cosmetic / single worker .... LOG + FIX + note at handoff

3. DELEGATED AUTHORITY (no approval needed)
   Spend: $__ per incident, $__ per day
   Restart allowed: [list]     Restart FORBIDDEN: [two named systems]
   Allowed comms: templates.  Forbidden: refund/credit promises, dates.

4. COMMS PLAN
   Update channel ____ every 2h.  IC when owner away: ____.
   Handoff at ____: written, handoff checklist.

5. BATTLE RHYTHM
   Shift start: dashboard sweep.  Mid-shift: patch-window check.
   Day close: audit sweep + handoff.

6. NEVER-DO LIST
   [ ] Raw SQL on prod during an incident
   [ ] Silence an alert instead of fixing it
   [ ] Credentials over chat

7. DAY-CLOSE
   [ ] Open items logged w/ owners  [ ] Handoff written  [ ] Dashboards green-or-explained
   [ ] Tomorrow's known events listed  [ ] Sheet date updated

Worked Example: The Night the Checkout Went Dark

02:14, the owner's phone is on do-not-disturb. Checkout errors start climbing. With standing orders on the fridge (metaphorically), the on-duty tech: (1) hits trigger 2 at 02:23 — five payment errors in fifteen minutes — and calls; (2) meanwhile opens the payment outage playbook and flips the banner to "payments temporarily unavailable — orders held, not lost"; (3) spends $0, promises nothing, logs everything; (4) at 06:00 hands off in writing. The owner wakes to a resolved incident instead of a missed-call list. Without standing orders, the same night starts at 09:30 with a support inbox on fire.

How to Keep Standing Orders Alive

1. Write v1 in 30 minutes — done beats perfect; a sheet with three blanks teaches you what to decide next.
2. Rule of two: every question asked twice in one week becomes a line on the sheet.
3. Review at handoff, weekly: crossed-out triggers and new dollar limits keep the sheet honest.
4. Version it: sheet date at the top, one page, printed copy next to the runbook binder.
5. Test it: one tabletop drill per quarter — "owner unreachable, checkout down, go."

Instant-Download Ops Kits

This template is part of the Hive80 Lab ops kit line — field-tested, instantly downloadable:

• The First 30 Minutes — free incident quick-start
• Ops Field Cards — 12 printable incident checklists — $4
• Ops Starter Kit — full incident-response kit for small teams — $14
• Ops Mega Bundle — all 5 kits in one download — $29

⚡ Launch pricing is live at the store — check the banner for today's code.

Related Ops-Notes Pages

• Delegation of Authority Template — the who-can-do-what document behind section 3
• Escalation Policy Template — the full ladder behind trigger section 2
• On-Call Handoff Checklist — the written handoff standing orders require
• Maintenance Window Policy — the battle-rhythm patch beat
• Daily Ops Audit Checklist — the day-close sweep in one habit
• Incident Commander Checklist — who runs the incident when the sheet says call

A shift without standing orders isn't autonomous — it's just waiting. Write the sheet once, review it weekly, and let the team run.