Rotation system (the “wheel” renamed)
The wheel is just a metaphor. Operationally we call it Rotation: a simple way to share load, keep standards, and stay resilient.
Hub
The hub is direction + coordination: it sets the plan and keeps the day stable.
- Decide today’s priorities and service windows
- Assign roles (who owns what)
- Track issues and decide escalation
Spokes
Spokes are the workstreams that create output. Diversity adds strength.
- Feeds & forage handling
- Farm routines (water, soil, animals)
- Receiving / packing / dispatch
Rim (people)
The rim is the community: people + mutual support. Without the rim, the system fails.
- Buddy checks, handovers, covering breaks
- Local knowledge (weather, roads, seasons)
- Respect + fairness keeps teams together
If a spoke fails, we don’t panic. We rotate: protect safety, keep the hub stable, and reassign work. The rim (people) is the resilience.
Shift handover (minimum standard)
Handover must be short, consistent, and written down. No “memory-only” operations.
| Item | What to write | Owner |
|---|---|---|
| Today’s priorities | Top 3 outcomes for next shift | Hub lead |
| Open issues | What’s broken / delayed / risky | Hub lead |
| Inventory notes | Feeds, forage, produce, consumables | Store / yard |
| Safety notes | Hazards, near-misses, fatigue/heat | All |
| Next actions | Who does what, by when | Hub lead |
How to share this with staff (without publishing it)
Option A: Local-only
Keep it on the work computer. Use Live Server locally when needed.
- No internet exposure
- Best for early drafts
Option B: Password gate (later)
If you host later, put /ops/ behind authentication.
- Stops customers finding it
- Requires proper hosting
Option C: Share as a ZIP
Send staff a zip of /ops/. They open ops/index.html locally.
- Simple
- Works offline
Don’t link to /ops/ from the public site. Keep it separate.