Guidelines for estimating the workforce of significant companies, with worked anchors from canon. A calibration aid, not a lookup table: the method matters more than any single number, and every figure here is a range or an example to be adapted, never copied. Companion to PRICE_REFERENCE (wages, construction costs) and BUDGET_REFERENCE (company budgets).
Status: skeleton. Sections marked TODO are agreed in outline but not yet filled with data.
Scope
Use this when a company card needs Workforce (est.) and the company is significant enough that the number matters (strategic industry, recurring NPCs, a notable share of a colony’s economy, consistency with facility size). For minor firms [Unknown] remains the default and acceptable.
Technological context
Do not size crews by contemporary staffing intuitions. In this setting:
- Additive manufacturing is mature. Structural and mechanical parts are printed on site; the labor cost sits in integration, inspection and fit-out, not in fabrication.
- Automation is the main route to capacity. Throughput grows through automation rather than headcount (canon example: Aurelia in Descartes expands by automation, not by growing its permanent crew). Reactor and routine plant control are automated; staff supervise.
- Expert systems cover routine analysis, so back-office and diagnostic crews are small relative to physical and specialist crews.
- A modern-day shipyard, refinery or station crew is the wrong prior. Start from what must physically be done by people, not from what a comparable twenty-first-century facility employs.
Method
Estimate in this order and stop when the figure stands up to the checks.
- Physical ceiling — only if people live on the facility. Habitat volume ÷ volume per head (assume ~60–80 m³ per person including services). Not a limit when the crew commutes (see Commuting vs resident below).
- Build from functions. List what has to be done, group it, then size each group. Typical groups: management and administration, engineering, robotics/heavy equipment, manual and EVA crews, logistics, armament/specialist systems, support and services, medical. See the worked example below for proportions.
- Apply the shift rule. Size the full crew for one day shift. Add a skeleton crew only for functions that cannot be paused (reactor supervision, life support, an on-site caretaker). Do not multiply the whole crew by the number of shifts; most work stops when the day shift ends.
- Check payroll. Headcount × local average wage (Nilus ≈ 40 000 CC/year, Artalan ≈ 31 800 AC/year, Faringor ≈ 37 000 CC/year; 1 AC ≈ 1 CC). Specialists above the average are offset by lower-paid manual crews, so a plant lands near the local average unless it is unusually specialist-heavy.
- Check value. Revenue and equity value (e.g. a stake’s valuation) should be consistent with the facility’s replacement cost in PRICE_REFERENCE.
- Report a range, not a point (
~100–140), unless the figure is a canon decision.
Commuting vs resident
- Commuting crews (short shuttle run to a nearby colony) need no rotation and no large habitat; the habitat serves only the night crew and visiting ship crews. The labor pool is the nearby colony, and the facility is typically a fraction of one percent of it.
- Resident / rotational crews (remote station, refinery) need habitat capacity, rotation cover on the payroll, and food and life-support staff. Payroll headcount exceeds on-site headcount.
- Rotation cover = (days on + days off) ÷ days on. With 12-hour shifts the annual hours decide what is sustainable: 14/14 (or 7/7) ≈ 42 h/week, 2 190 h/year, cover ×2.0; 8/6 ≈ 48 h/week, ×1.75; 14/7 ≈ 56 h/week, ×1.5, the practical upper bound. 28/7 (×1.25) would be ~67 h/week and is not sustainable. Where the transfer is short (same system), short rotations are the natural choice.
What not to use
- Share of a system’s population. Companies almost never hold a noticeable share of a system, so population ratios do not discriminate. Compare against the nearest settlement only as a sanity check.
- Contemporary ratios (employees per berth, per ship, per revenue) lifted from real-world industry without the technological context above.
Functional breakdown (proportions)
Derived from one fully specified small repair yard. Treat as a starting shape, not a standard.
| Group | Share |
|---|---|
| Management and administration | ~11% |
| Engineering | ~15% |
| Robotics / heavy equipment | ~15% |
| Manual, EVA and technician crews | ~37% |
| Logistics | ~7% |
| Armament / specialist systems | ~7% |
| Support and services | ~8% |
TODO: proportions for other kinds of firm (extraction, refining, manufacturing, logistics, finance).
Anchors
| Entity | Workforce | Notes |
|---|---|---|
| Trident Shipyard | 114 | Small repair yard near Luxor (Nilus); 111 on the day shift, 3 on the evening/night skeleton; commuters; full breakdown in the card |
| Waypoint 9605 Cooperative | ~100 | Family-run fuel station and orbital refinery; ~35 rotate onto the refinery; resident |
| AgriStar (Artalan Corporation subsidiary) | 150 | Mass-scale arable farming plus limited-scale specialty crops |
| Trident Spaceworks & Shipyards (Artalan Corporation subsidiary) | 5 | Holding-level oversight only; the yard itself is Trident Shipyard |
| Faringor Spaceworks | ~1,500 (1,300–1,700) | Former civilian repair yard converted to shipbuilding; three destroyer docks with own lines (2455); resident, 14/14 rotation, two 12 h shifts; ~756 on site at once |
| Aurelia (Descartes) | ~25 000 | Population of a rigidly connected orbital industrial complex, not one company’s workforce; use only to scale a firm’s share of its host |
Calibration notes
- First-year labor share can be misleading: Trident Shipyard’s payroll was ~42% of its own-service revenue in 2455 (~11 mln CC) because the yard was under-utilised; with the extra Harrier fit-out job (~28 mln CC, mostly pass-through parts) it falls to ~12% of total billing. A steady-state yard should show a lower share.
- Wage level tracks the local economy (Nilus industrial and mining base), not the facility’s remoteness.
- Wage proxy: private consumption ÷ working population (not ÷ total population, which also counts dependants and gives a misleadingly low ~24 000 CC for Faringor). It reproduces Artalan’s canon average exactly (37.406 mld ÷ 1 176 313 ≈ 31 800 AC, 2455) and gives ≈ 36 100 CC for Faringor (2454), hence the ~37 000 CC used there. It overshoots for Nilus (≈ 54 700 vs 40 000 CC canon), so use it as a cross-check, not a source.
- A firm’s valuation can include IP (plans, supply chain, know-how), as with Faringor Spaceworks, so a stake’s value says little about headcount.
How to add an entry
| [Company](path/to/CORP_ID.md) | N or range | one-line type, location, crew model (commuting/resident, shifts) |
- Record the crew model (commuting or resident, shifts) next to the number; the same plant with a different crew model has a different headcount.
- Put the full breakdown in the company card, not here; keep this table to one line per entity.
- Order by workforce within the table when it grows.
TODO
- Wage data for polities other than Artalan and Nilus.
- Worked estimates for larger anchors (Artalan Corporation subsidiaries).
- Proportions for non-shipyard industries.
- Revenue-per-employee and labor-share ranges by industry once enough anchors exist.