Extracted text blocks

This appendix preserves the main static text blocks from the original HTML presentation in plain markdown.

Hero

Title

The operating system of a new U.S. single-family home build

Lede

This map treats a home build as an information network, not just a physical jobsite. The same project is seen differently by the Census, by the architect, by the builder, by trade contractors, and by the authority having jurisdiction (AHJ). The goal here is to make those viewpoints legible and connected.

Hero stats

  • 73.1% — of 2024 single-family starts were built for sale, so the default map uses the production / built-for-sale lane. (Evidence: S2, S1)
  • 17.5% — were custom homes in 2024, so the custom / owner’s-land lane is shown as a second operating model. (Evidence: S2, S1)
  • 2 clocks — run at once: the statistical clock (authorized → started → completed) and the delivery clock (programming → design → procurement → construction → closeout). (Evidence: S1, S3, S4)
  • Many AHJs — adopt model codes by law and may amend them; planning, building, fire, utilities, and public works may all touch one project. (Evidence: S11, S12, S13)

Hero notes

  • Analyst’s note: U.S. “new home sales” statistics are mostly a production-builder lens. Census counts new houses sold when a contract or deposit is taken, and excludes owner-built houses and houses built by a general contractor on the owner’s land. (Evidence: S1)
  • How to read this map: dark-blue source tags point to the evidence library below. “National” sources are stronger for generalization; “Local example” sources are used to show how the fragmented permitting and inspection system looks in practice. (Evidence: S11, S12, S13, S30, S31)

Structural ideas

1. The “owner” changes meaning by delivery model

In a custom home, the human homeowner is usually the active owner from day one. In a built-for-sale project, the builder-developer often plays that role through land, design, permits, and early construction; the end buyer may join later through a sales contract and option selections.

Evidence: S1, S2, S3

2. Documents are the real handoff points

Needs become sketches; sketches become design development; that becomes construction documents; then permit sets, bid packages, subcontracts, RFIs, change orders, inspections, pay applications, waivers, and closeout records. Most delay and rework comes from document handoffs going fuzzy, late, or out of sync.

Evidence: S3, S4, S5, S7, S8, S9, S10

3. Residential is local by law, fragmented by workflow

Model codes are national, but adoption and amendment happen by jurisdiction. That means one homebuilding process exists in principle, but many local versions exist in practice. Permit portals, checklists, plan review comments, and inspection scheduling are typically local.

Evidence: S11, S12, S13, S30, S31

Section intros

Three structural ideas to keep in mind

These are the mental shortcuts that make the rest of the map easier to navigate.

Ecosystem map

Click any actor to jump to a deeper actor card. The center is the project itself: one house moving from idea to legal approval to physical completion to owner use.

Actors and the people inside them

Emphasis is on people who process information and make decisions, while still naming hands-on field roles.

Process flow

The swimlane below is the delivery clock. It is intentionally different from the Census statistical clock, which tracks authorized / started / under construction / completed. Use the model toggle above to see where the “owner” and buyer differ.

Information flows

What travels is usually some mix of scope, risk, money, design intent, compliance evidence, schedule commitments, and proof of completion.

Where the system loses time, money, and trust

These are the most recurrent friction points found across the sources. Some are structural to construction; some are especially acute in single-family housing.

Glossary

The quickest way to learn the industry vocabulary used in the rest of the map.

Source library

Grouped by evidentiary role so you can tell what is a national definition, what is professional-practice guidance, what is a local example, and what is an industry or policy analysis.

Ecosystem core and nodes

One new single-family home

What matters most is not just who does work, but who approves, prices, interprets, coordinates, and records it.

  • Owner / sponsor — (dynamic text depends on operating model) — scope • budget • approvals
  • Architecture + consultants — Translate goals into drawings, specs, and permit/bid packages; interpret them during construction. — design intent • permit set
  • Builder / general contractor — (dynamic text depends on operating model) — precon • schedule • field coordination
  • City / county / state authorities — Adopt and enforce local rules, review plans, issue permits, inspect work, and sign off occupancy/use. — zoning • permits • inspections
  • Vendors / suppliers — Turn scopes and selections into quotes, lead times, product data, deliveries, and warranty records. — materials • deliveries • product data
  • Subcontractors / trades — Execute specialized scopes such as framing, MEP, roofing, drywall, finishes, and site utilities. — estimate • crew • install

Model summaries

Built for sale - production

Built-for-sale / production: the dominant U.S. path. The builder typically controls land, standard plan choices, permit strategy, purchasing, trade relationships, and early schedule. The end buyer may appear later and can legally count as a sale before the house is finished. (Sources: S1, S2)

Custom - owner’s land

Custom / owner’s land: the owner is active from the beginning, often hiring the architect early and choosing a builder later through bid, negotiation, or preconstruction services. Census separates contractor-built and owner-built houses inside this lane. (Sources: S1, S2, S3, S33, S34)

This map is scoped to U.S. new single-family residential construction . Local permitting, planning, and inspection details vary widely by jurisdiction; local examples here are meant to show workflow shape, not to stand in for every city or county. Model codes and contract forms also do not mean every project uses the same exact paperwork.