Span of Control

You run this frontier colony from three days away by telegraph wire, so the only order that actually matters is the standing rule you wrote before you stopped watching.

Date: 2026-08-10 Genre: colony sim Platform: PC (Windows; keyboard & mouse) Status: Concept

Target player

Someone with four hundred hours in RimWorld or Dwarf Fortress who loves the systems and is tired of being the system, the one clicking every colonist into place, every tick, forever. They've read the discourse: RimWorld's Odyssey expansion doubled down on giving the player more direct presence, a mobile base you fly and fight from, and it worked, but it's also more of the same control fantasy the genre has run on since the start. This player wants the opposite bet, a colony sim where being hands-off is the skill and not the failure state. They also read the reviews calling Timberborn's late game empty once food and water are solved, and they want a colony sim that gets harder to run well the longer it survives, not easier.

Core loop

The daily loop: The Ledger flags a red entry. A colonist named Osric diverted three sacks of grain to the smithy instead of the granary, because his standing protocol says "resupply the nearest understocked building from the nearest full stockpile," and this week, technically, the grain store was the nearest full stockpile. You have two options and one week's remaining Directive budget: spend a Directive now to move the grain back by hand, or rewrite the protocol's resupply priority to exclude food stores, knowing the fix won't apply until the rule is next evaluated, so the current shortfall stands either way. You pick the rewrite. You watch to see if it holds.

The weekly loop: Monday, the supply train pulls into the depot. Charter Standing updates against last week's quota and how many Directives you burned. The Directive budget resets: three orders, this early in the tenure. You get a short window before the telegraph line's price triples for the week to make any protocol overhauls, then the game speeds up and you mostly watch. If the week runs clean, you've bought yourself a quiet one. If it doesn't, you're waiting for Monday.

Where it gets boring in hour three: a rulebook that's airtight for a twelve-person colony with two resources goes quiet fast, and a quiet Ledger risks becoming a screen you just watch. That's the exact plateau that hit Timberborn once food and water were solved and nothing else was gated behind it. Span of Control's progression is built to reopen that puzzle on its own: protocol slots don't grow with population, only with sub-foremen you hire and pay for out of quota output. A rulebook built for thirty colonists starts producing conflicts you never wrote for at sixty, because colonist traits are combining in numbers your original four rules never anticipated. Getting good enough to stop firefighting is what hands you a colony that's outgrown your rules.

Systems

• Standing Protocols: a visual if/then rule builder. About a dozen conditions at tenure start (stock thresholds, weather flags, colonist mood, day of week, incoming train) and a dozen actions (reassign a job, reorder stockpile priority, force rest, open or seal a building). More of both unlock as sub-foremen join.
• The telegraph and the Directive budget: any real-time order — the thing every other colony sim treats as free — draws from a weekly budget of three, and the price of an order roughly triples once the line "locks" partway through the week. Spending one is a real decision, not a reflex.
• Colonist temperament and interpretation drift: four traits at launch — Cautious, Reckless, Weary, Ambitious — each biasing how a colonist executes an ambiguous rule. A Cautious colonist under a resupply protocol over-pads the buffer and under-delivers; a Reckless one strips the source stockpile bare. The drift is deterministic given trait and rule, so a repeated failure is a design signal you can act on, not bad luck you have to absorb.
• The Ledger: a searchable log of every deviation, flagged by severity, that traces a bad outcome back to the exact rule-and-colonist pair that caused it — the opposite of debugging a pathing failure by staring at a colonist walk in circles.
• Silent Weeks: seasonal telegraph outages from storms or rail damage that drop the Directive budget to zero for five to seven in-game days. There is no manual fallback. It's the week your rulebook is actually tested.
• Charter Standing: the single score that governs whether you keep the job. It rises on met quotas run with low Directive spend and falls on missed quotas or heavy reliance on manual orders — the company reads a hands-on administrator as one who doesn't trust their own systems.
• Sub-foremen: hired at population and quota milestones, each holding two protocol slots of their own and one area they flatly refuse to write rules for. Delegating doesn't remove the delegation problem; it just moves it up a level.

Progression

A tenure runs four in-game years. The company raises quota roughly ten percent each year. Protocol slots start at four and grow by two per sub-foreman hired, up to three hires for ten total. Silent Weeks are absent in year one, land once in year two, and twice a year from year three on. Population grows from six colonists at the start toward sixty or more, capped only by housing you build. Charter revocation — the loss state — triggers after three consecutive quota shortfalls; the win state is completing the four-year tenure with Charter Standing above the company's renewal threshold.

New Charter+ reshuffles which trait biases which action and starts the Directive budget at two instead of three, so a veteran's rulebook from a prior tenure is a starting point, not an answer.

World & setting

The Concourse Company runs a rail line into badlands it hasn't finished naming. You're the administrator, hired out of the capital office, and you've never set foot on the land you run — everything you know about the colony arrives by wire or by whatever the weekly train brings back. The tone sits somewhere between a company ledger and the mess underneath it: quotas, telegraph forms, and a supply schedule, with colonists whose small rule violations are the only part of the world that reads as human. Palette: dust ochre, rail-iron black, oil-lamp amber, telegraph-wire grey.

Differentiators

• Direct control costs a metered resource — a real-time order draws from a weekly Directive budget that prices itself up mid-week, so the skill under test is writing rules that hold while you're not watching, not clicking fast enough to keep pace.
• Colonists distort ambiguous protocols according to a fixed personality trait, turning every bad outcome into a specific, traceable rule-and-colonist pair in a searchable Ledger, instead of an opaque pathing bug.
• The one score that matters, Charter Standing, drops the more you lean on manual Directives — the genre's usual mark of mastery, constant hands-on control, is exactly what this game penalizes.
• Failure escalates through Silent Weeks and rising quotas rather than plateauing once basic needs are met, directly answering the "nothing left to do once food and water are solved" complaint aimed at the genre's current biggest 1.0 launch.

Monetization notes

Premium purchase, roughly $24.99, with a 12–18 month Early Access period before 1.0 — the path Timberborn, RimWorld, and Going Medieval all took successfully in this genre, per the research below. Post-1.0, paid expansions add new company eras and industries rather than cosmetics, mirroring how RimWorld's Odyssey DLC sold on a genuine mechanical addition rather than skins. The genre is crowded, but Timberborn's 1.0 launch and RimWorld's Odyssey both posted major Steam numbers in the same year, which says the appetite is still there for a design with one legible hook. Span of Control's hook — you are penalized for touching the controls — is quotable in a single trailer clip and doesn't need thirty hours of play to land.

Accessibility notes

Fully remappable hotkeys for the protocol builder. Ledger severity is shape-coded as well as color-coded so it doesn't rely on red/amber/green alone. Game speed is adjustable and can be hard-paused at any time to write protocols without time pressure. UI text and the rule-builder grid both scale independently. Telegraph flavor-text audio carries captions. Silent Week frequency and length are adjustable for players who want less scarcity pressure. Full colorblind palette presets. Reduced-motion setting for storm and train VFX.

Risks

• The rule builder could end up as tedious as the micromanagement it replaces if the condition/action vocabulary is too shallow or too deep. Mitigation: cap the starting vocabulary at twelve conditions and twelve actions, and playtest for a working first protocol in under two minutes.
• The genre already has RimWorld, Timberborn, and Dwarf Fortress occupying serious mindshare. Mitigation: lead every trailer and store beat with the Directive-scarcity hook — it's the one line that doesn't also describe those games.
• Interpretation drift could balloon into a full behavior-simulation project if the scope isn't held. Mitigation: keep drift a small, tunable modifier table on existing actions rather than emergent free-form AI, and prototype with only the four launch traits.
• The Directive budget is a knife-edge to tune — too scarce reads as powerless, too generous erases the hook entirely. Mitigation: tune against real playtest data from weeks four and five of the prototype, not designer guesswork.
• Writing rules before seeing their consequences is intimidating for players new to the genre. Mitigation: open with a diegetic first in-game week under full manual control — "shadowing the outgoing administrator" — before protocols are introduced as what she used to do.

6-week prototype plan

• Week 1: Core simulation skeleton — six colonists, one resource (food), a day/night tick, manual point-and-click orders only, no protocols yet. Deliverable: colonists visibly thrive or starve based purely on manual play.
• Week 2: Build the protocol editor — condition and action dropdowns — and wire it to run colonists without manual input. Deliverable: a colonist follows a written rule unattended for at least three in-game days.
• Week 3: Add the Directive budget, the weekly telegraph tick, and a first pass on Charter Standing reacting to quota and Directive spend. Deliverable: one full week — protocols run, train arrives, budget resets, standing updates — playable start to finish.
• Week 4: Add colonist temperament traits and interpretation drift on two or three protocol actions, plus the Ledger surfacing each deviation. Deliverable: two colonists with different traits visibly execute the same protocol differently, and both are traceable in the Ledger.
• Week 5: Add the first Silent Week (a zero-Directive stress test) and a second resource (lumber) to create genuine protocol conflicts between the two. Deliverable: a full Silent Week where at least one protocol conflict is visible and traceable.
• Week 6: Vertical slice and playtest milestone — a full first in-game year (tutorial week, roughly eight regular weeks, one Silent Week) with four protocol slots, a quota target, working win/loss states, and a rough pass on the foreman's-office art. Deliverable: five external playtesters finish one full year and can say, unprompted, why they won or lost.

Genre references

• Timberborn 1.0 launch coverage — https://www.notebookcheck.net/37-000-reviews-95-positive-New-indie-city-builder-colony-sim-tops-Steam-charts-on-launch.1250971.0.html — over 37,000 reviews at 95% positive within four days confirms real commercial appetite for a well-executed colony sim even against genre giants; its logic-gate automation system is the current genre staple that Span of Control's rule-and-drift approach deliberately sidesteps.
• Ctrl.blog's Timberborn review — https://www.ctrl.blog/entry/review-timberborn-colonysim.html — direct, specific evidence of the late-game emptiness problem ("once your colony has enough food and water, then you're pretty much done"; happiness gates nothing) that Span of Control's escalating quotas and Silent Weeks are built to avoid repeating.
• dbltap's RimWorld: Odyssey review — https://www.dbltap.com/reviews/rimworld-odyssey-review — the genre's flagship title doubling down on player mobility and hands-on presence via the gravship; Span of Control counter-bets on constrained, remote administration instead of more direct control.
• "The 10 Best Colony Sims To Play In 2026" — https://strategyandwargaming.com/2026/03/09/the-10-best-strategy-colony-sims-to-play-in-2026/ — genre landscape overview confirming direct citizen and crew management as the near-universal control paradigm across current titles, which Span of Control's Directive scarcity inverts.