Reading paths by role

The book has more pages than any one reader needs. Reading depends on the seat: a new member needs the competition and the four missions, a subsystem lead needs one study plus its interfaces, and a systems lead needs the budgets and the registers. Each path below is ordered, states what each page is for, and names the decision it supports.

New member

A new member starts with the executive summary and the competition, then reads the missions in scoring order. The aim is to hold the whole shape of the problem before joining a subteam, which takes about six hours of reading.

1. Executive summary: the ten findings, the ten decisions and the eight risks. About twenty minutes, and it names every other page worth reading.
2. The 2027 competition: the four missions, the 500-point structure and what changed from 2026.
3. Missions and scoring: each mission, task by task, with the clauses that define it.
4. Rules, limits and the field: the 50 kg limit, the 1.2 m cube, the $26,000 fielded-equipment cap, the E-stop and the spectrum rules.
5. The URC landscape and the 68-team census: who else competes, how the field is tiered, and what the score distribution looks like.
6. How the missions evolved: why the 2027 shape is not the shape a 2023 video shows, which is the most common source of stale advice.

The decision this path supports is whether to join the team at all, and which subteam to ask for.

Subsystem lead

A subsystem lead reads one subsystem page closely, then reads around it before choosing. The subsystem page carries the requirement, the design space, the comparison table, the failure modes and a shortlist for a first build; the four pages that follow it are what turn a shortlist into an integrated choice.

1. The subsystem page for the area, linked in the table below.
2. Interfaces and couplings: the 66 interfaces, 37 of them high criticality, and the four chains that decide architecture.
3. How rovers fail: 54 sourced failures, grouped by cause, so the option is judged against what actually broke.
4. Mass and power: the budget the subsystem has to live inside, and the peak that sizes its wiring.
5. Two or three team dossiers from the teams that built each option. A dossier says what a team built, in which year, and what it scored.
6. The mission page for the mission the subsystem is scored in, so the task force, the clock and the tolerance are known before the component is chosen.

The decision this path supports is the architecture choice for one subsystem, and the interface list it must not contradict.

Systems lead

A systems lead holds the budgets that no single subsystem owns. The reading order is chosen so that the numbers come before the registers, because the registers are only useful once the units and the samples are understood.

1. Mass and power: the 249 W average, the 3.7 kW peak, the 400 to 500 Wh pack and the closed mass loop.
2. Interfaces and couplings: the 66 interfaces and the chains that turn one decision into five.
3. What separates the top from the rest: which missions explain the variance, and what consistent teams do differently.
4. The 110 engineering problems: ordered by dependency wave, each with the experiment that closes it.
5. The 70 risks and the 77 open questions: what can go wrong, and which answers are not yet available.
6. System Acceptance Review and review, judging and awards: the gate, its rubric and the evidence it needs.
7. The first 90 days and the 13-week plan: the sequence, with the four gates that close it.

The decision this path supports is the configuration and the mass allocation, which is the first decision on the executive summary’s list.

Reviewer

A reviewer, a judge, a faculty advisor or another team arrives without the context the book assumes. The path is short and sceptical.

1. Key numbers: every headline value with its sample, period, owner and chart.
2. Statistics: the distributions behind those values, one page per subject.
3. Bibliography: 1,251 registered sources, each with a title, a publisher, a date and an original link where one exists.
4. Primary documents: the archived rulebooks from 2007 to 2027, the official score sheets from 2022 to 2026 and the 2027 Q&A snapshot.
5. About the evidence: the four evidence grades, the citation form and the known limits.
6. Asset index and gallery: every figure, its author, its year and its licence.

The decision this path supports is whether to trust a number, which is the only question a reviewer ultimately asks.

Project manager or faculty advisor

The management path is separate from the technical one, because the review rewards a plan more than it rewards a component.

1. Deadlines and milestones: the fixed dates, what each submission requires, and the penalty for missing one.
2. From analysis to build: how the problems, risks and questions fit together.
3. The first 90 days: the window from registration to the design review, with the gates inside it.
4. The 13-week plan: the plan to the first design review, week by week.
5. Review, judging and awards: what the review scores, and what it will not read.
6. Credits and reuse: the terms for reusing the book’s charts and tables in a report.

The decision this path supports is scope: which capabilities are attempted in the first season and which are deferred in writing.

Cross-subsystem reading paths

Three couplings cut across the twelve studies, and a team that reads by subsystem alone will miss them. Each path below follows one coupling to its end.

Short readings by question

Most reading starts from a question rather than a role. This table maps the common ones to the page that answers them.

How much reading

The executive summary takes about twenty minutes. A role path takes an evening. The registers are lookup pages rather than reading: the problem register is worked 45 minutes a week, and the risk register is re-scored at each milestone.

Two habits make the book easier to use. A number is clearer with its sample beside it, because a figure that covers 162 finals team-years and one that covers 17 rovers answer different questions. A citation is worth following before a value is quoted, since the bibliography row carries the date, the publisher and the archived copy that the claim depends on.