Vision

Every offsite product carries a story the rest of the building industry needs to read. It has a cost, a set of performance ratings, a material history, and an embodied-carbon footprint. Today that story is told differently by every manufacturer, in formats that do not line up, so the information cannot be compared, summed, or trusted across a project. Uniform Product Data fixes that. It is one agreed way to describe an offsite product’s deeper data, and one agreed way to calculate it, so a pod, a module, or a panel reports its numbers in a form any designer, lender, regulator, or auditor can use without translation.

The Center for Offsite Construction is standardizing that description and the methods behind it. A product measured once, by the firm that built it, becomes a number the whole market can rely on. The hardest measurements in construction move from the job site, where they are nearly impossible, to the factory, where they are routine.

 The Problem

Whole-life carbon accounting begins with embodied carbon, and embodied carbon is where Engineer-to-Order construction fails at the starting line. A building’s embodied carbon is the sum of the materials that went into it, including everything that was cut, scrapped, glued, sealed, and replaced along the way. In an Engineer-to-Order project that sum is almost unknowable. The best BIM model describes an idealized building rather than the one that was actually built. The most diligent site diary still misses the off-cut drywall, the extra tube of adhesive, and the thousand small field decisions that each change the material total.

That gap is not a software problem. It is a structure problem. Engineer-to-Order delivery depends on an army of people making unique judgments on a unique site every day, and every one of those judgments is a measurement that no one records. The result is an army of measurement risk. Organizations that study whole-building life-cycle assessment, including the Carbon Leadership Forum and its benchmark work across hundreds of North American buildings, have shown how much labor it takes simply to harmonize carbon results from projects that were never built to be measured. The lesson is plain. As long as buildings are assembled as one-off prototypes, their carbon will be estimated rather than known.

 The Current Awkward Hybrid

The industry has answered with heroic effort rather than better structure. Sustainability consultants reconstruct material quantities after the fact. Designers pull environmental product declarations one material at a time and assemble them by hand. Each study is bespoke, expensive, and stale the moment the project changes. Manufacturers do publish data, but in incompatible formats, so a designer comparing two pods compares two documents that share almost nothing. The information exists in pieces. It cannot be added up.

This is the same hybrid that runs through the rest of offsite construction. The work has begun to industrialize, yet the data still travels as if every product were a custom artifact. Until the data is uniform, the promise of measurable, comparable, low-carbon building stays out of reach.

 The CTO Marketplace

Manufacturing changes what can be measured. A product built in a factory is built the same way every time, from a known bill of materials, with a known waste stream. Its embodied carbon can be calculated once, under controlled conditions, by the firm that knows it best. Uniform Product Data is how that calculation travels. The productizer computes the number once for a pod, a module, or a panel, publishes both the result and the method that produced it, and every downstream user reads it the same way.

That single move redistributes the hardest work in carbon accounting. The building designer no longer reconstructs the carbon of every component from scratch. They sum the component results the manufacturers already published, and they calculate only the unique conditions that remain, such as the foundation, the utility tie-ins, and the mechanical rooms. A calculation that was impossible becomes addition plus a short list of site-specific items.

A market-ready answer for three audiences

This organization is a gift to the people who have been straining against the Engineer-to-Order data problem. For government, it is an oversight dream. As states such as California raise their carbon-reporting requirements, uniform data makes compliance easier to produce for the firms that owe it and easier to verify for the agencies that receive it. For philanthropy, it is a sustainability dream. Uniform data speeds the calculations behind greener buildings, lets designers survey a far wider design space before they commit, and lets buyers read a product’s sustainability features at a glance, the way an appliance’s energy label works today, only now at the scale of a pod or a module. For the architect, it is relief from administrative burden. Product data delivered in large, standardized chunks streamlines submittals and compresses the construction-administration work that consumes so much of a project’s overhead.

The Federation Effect in the Market

A federation of firms needs to read one another’s products without translation, and uniform data is what makes that possible. A firm that publishes to the shared format becomes legible to the whole market at once, comparable on cost, performance, and carbon beside every other participant. The deeper advantage is competitive. A market increasingly rewards sustainability, through government grants to study it, through grants that require building to minimum sustainability guidelines, and through buyers who now ask for documented green credentials. Documenting that conformance is itself an administrative burden under Engineer-to-Order. A firm that has adopted the CTO tools carries market-ready sustainability reporting out of the box, because the data and the method already travel with its products. The federation turns a compliance cost into a standing advantage, and it grows stronger as every new member makes the shared dataset more complete.

Phase	What happens	Status
1	Whitepaper & format studyDraft the whitepaper that frames the ETO measurement problem and the CTO solution, recruit co-authors and a support team, and scope which product-data fields and carbon methods the standard must cover.	● In progress
2	Format & method specificationDefine the uniform product-data schema and the shared embodied-carbon calculation method, so a productizer can compute once and a designer can sum with confidence.	Next
3	Pilot data publicationWork with manufacturers to publish uniform data for sample pods, modules, and panels, and produce a worked example that sums component results against a real building.	Upcoming
4	Hold & re-integrationPause to align with the .CTO link mechanism and the registry storage option as they mature, then re-integrate so a .CTO file resolves cleanly to its uniform data.	Upcoming
5	Validation & designer toolingBuild the tooling that lets designers pull component results and add only the unique-conditions calculations, and validate the format against real projects.	Upcoming
6	Adoption & disseminationPublish the standard, convene manufacturers and sustainability programs, and align it with carbon-reporting and grant requirements.	Upcoming

 How it connects to the rest of the roadmap

Uniform Product Data is derived from the .CTO file type, and the two carry different loads on purpose. The .CTO file drives hard at delivery, with chain of custody, geometry, MSRP, and the rules that govern how a product connects and transfers. It does not try to hold every page of a product’s deeper record. It carries a link to where that wider, uniform data lives. The pattern is already familiar from manufacturing. A designer today downloads a dishwasher’s BIM file for its geometry and finds inside it links to the cut sheets, installation manuals, and specifications that sit elsewhere. Uniform Product Data is that deeper record for an offsite product, standardized so the link always resolves to something the market can read.

This project moves in parallel with the rest of the digital layer. It does not depend on the CTO Product Registry, though the registry is one reliable place the data can live among other options. It also draws a deliberate boundary around trust. The CfOC standardizes how the data is calculated and recorded, and its automations can audit whether a .CTO file is valid and functional. The CfOC does not audit a manufacturer’s carbon claim. That verification belongs to the productizer and to the third-party programs built for it, and the uniform format simply makes those claims legible and comparable.

 Sequencing and re-integration

This project can travel a long way on its own. The format and the carbon method can be drafted, piloted, and validated while the keystone matures. One sync point matters. The .CTO file’s link mechanism and the registry’s storage option both need to be ready for a .CTO product to resolve cleanly to its uniform data. The work reaches internal consistency, holds briefly for that alignment, and then resumes to stitch the link together end to end. The budget names that re-integration rather than pretending the handoff is free.

Phase	Estimated cost
1 · Whitepaper & format study	$60,000
2 · Format & method specification	$180,000
3 · Pilot data publication	$160,000
4 · Hold & re-integration (sibling sync)	$70,000
5 · Validation & designer tooling	$150,000
6 · Adoption & dissemination	$90,000
Total	$710,000

 Key Outcomes

The near-term prize is a published standard with two halves that reinforce each other. One is an agreed format for an offsite product’s deeper data. The other is an agreed method for the embodied-carbon calculation behind it. With those in place, manufacturers publish comparable data for the first time, designers sum rather than reconstruct, and a worked example can show a building’s embodied carbon assembled from component results in a fraction of the usual time. Comparability then spreads from carbon to cost, performance, and material sourcing, because the same uniform record carries all of them.

Uniform data is the precondition for AI in cost and carbon

The largest outcome reaches past any single calculation. Artificial intelligence cannot cost or carbon-account a building over data it cannot compare, and Engineer-to-Order data is exactly the kind of inconsistent, incomplete record that defeats it. Every manufacturer describes products differently, every study uses a different method, and every project’s material total is an estimate. An AI asked to optimize a design for carbon under those conditions has nothing solid to stand on.

Uniform Product Data removes that barrier. When every product reports its cost, performance, and embodied carbon in the same fields, calculated by the same method, an AI can read the whole catalog at once. It can survey an enormous design space, price and carbon-account every option, and surface directions a human would never have time to test. It can hold a design to a carbon budget the way a compiler holds code to a type. It can build the services that turn sustainability from a late-stage audit into a live constraint during design. None of that is possible over Engineer-to-Order data, and all of it becomes routine over uniform data. The same structure that lets a designer sum component results lets a machine reason across the entire market.

 Assessment

Progress is measured by comparability achieved and labor removed. The first measure is the published format and method, tested with the firms and reviewers who will use them, robust enough that two manufacturers describing similar products produce records that line up field for field. The second measure is pilot publication, the count of manufacturers who publish uniform data for real pods, modules, and panels. The third measure is the worked example, a real building whose embodied carbon is assembled from component results and a short list of unique-condition calculations, set against the time and uncertainty of the Engineer-to-Order approach it replaces.

Adoption is the longer measure. Success looks like designers pulling component results into live projects, sustainability and grant programs accepting the format as evidence of conformance, and an AI demonstration that costs and carbon-accounts across the uniform dataset reliably. Each of those signals that the data has become infrastructure rather than another document.

 Key Partners

The Center for Offsite Construction leads this work, and Jason Van Nest directs it. The project is early, and its partner set is described in prospective terms on purpose. Manufacturers are the essential first contributors, because they are the productizers who compute and publish the data the standard depends on. Designers, lenders, and insurers are the consumers whose needs shape which fields the format must carry. Life-cycle-assessment and environmental-product-declaration programs are natural collaborators on the carbon method, since the format has to interoperate with the evidence they already produce. Government sustainability and housing programs are prospective adopters, because uniform data is what makes their reporting requirements practical to meet and to verify. Academic researchers in whole-building life-cycle analysis are prospective co-authors and Senior Research Fellows, since the methodology benefits directly from current research. The page names these as the roles the project must fill, and it does not claim a partnership that does not yet exist.

 Key Idea

Every CTO tool lowers the cost of trusting another firm. Uniform product data makes that trust measurable.