Part 01 made the case that you do not price a campus by pricing the campus. You measure one module completely, prove that measurement, and let the repetition work for you instead of against you. That is the argument. Takeoff is where it stops being an argument and becomes arithmetic on a real set of sheets.
Measure one module off the real set
A data hall is a module before it is a campus, and the shipped work starts there. Ruh works from your real drawing set, PDF or CAD. It classifies the foundation plans, sections, and structural sheets, calibrates scale, measures the concrete elements, and reads the reinforcing schedule the way an estimator does. Nothing is traced by hand off a screenshot. The quantities come off the set that will be built.
For an office park you could eyeball your way to a number and land close enough. A campus does not forgive that. The module is small relative to the program, so the measurement has to be right at the module before anything scales. Reading the drawing set correctly is the whole game, not a preliminary to it.
Shipped today: measured takeoffs off your real drawing set, PDF or CAD, for the shell, site, and fit-out scopes.
Reconcile the whole set, not one sheet
Real drawings scatter a single element across many sheets. Footing schedules, wall sections, and embed plans that live apart are reconciled against the whole set instead of read in isolation. That is the difference between a number and a guess. A module measured this way is one you can defend line by line, which is the only kind worth repeating.
Then the repetition is multiplication, not compounding
This is where campus scale pays back. In Part 01 the danger was that a small error tiles: price the module a little wrong once and the mistake repeats with the pads. Invert it. Measure the module honestly once and the honesty repeats too. A campus is a small number of module types stamped across many pads, so an accurate measure of each type is what you carry across the program. Repetition stops being a risk multiplier. It becomes leverage.
Pads are not identical, and honest repetition means saying so. Grades differ, the site scope under each slab is not the same, and the fit-out varies by hall. So the module is the unit you measure, not the unit you assume. The shell logic and the structural takeoff repeat. The earthwork and the site do not, and they get measured per pad. Knowing which is which is the difference between leverage and wishful thinking.
Measure one module you can defend, and every pad that repeats it inherits the proof instead of the error.
Every number carries provenance
Owners of this asset class audit everything, and the estimate has to survive that. On the priced side, Ruh runs on your own history: your coverage rates, your labor multipliers, applied consistently across a nine-stage estimate, with sub bids leveled and gaps priced as labeled allowances. About ten strong historical projects grounds the pricing, and up to fifty sharpens it. Every assumption is written down where your estimator can challenge it, and your estimator signs every line.
That is what makes the estimate falsifiable in the sense Part 01 asked for. Whether a number was measured off the set or rests on an assumption, every one links back to its source, and every assumption is written down where your estimator can challenge it. A campus estimate that can show its work is the opposite of a round number defended by reputation.
Shipped today: priced estimates on your own history, exported to Excel and your own workbook beside the Procore and Bluebeam workflows your team already runs.
From one honest module to the bid
The takeoff hands you a module you can stand behind and a number that shows its work. The next part follows that number into the bid: how a measured set becomes a priced position an owner can interrogate line by line, and how one project record is built to carry it from bid toward build without re-keying between phases.
