What we do about it

The three layers

The three layers are how you scale.

Click any layer to see what it is and what it produces.

The ACRE Standard

Sets the bar

7 modules ▸

What it is

01Scope change and authorisation 02Schedule fidelity 03Cost visibility 04Decision documentation 05Commitments and coordination 06Closeout and warranty 07Communication cadence

Forty seven defined dimensions underneath (ACRE Standard, August 2026 revision)

What the client is told, by whom, on what schedule
How scope changes surface and get authorised
How decisions get recorded so the record outranks memory
What a finished job actually looks like
How schedule movement is communicated, not discovered
What evidence each of these leaves behind

Why it comes first

You cannot measure drift from a bar never set
Most standards live only in the owner's head

The operating system

Runs the day

Every morning ▸

How it works

InReceipts, field notes, emails, meetings, change orders, selections

→

Read against the barCaptured, coded, routed, checked overnight against the standard

→

OutToday's priorities, yesterday's exceptions, and the list the gap created

What it produces

A morning brief for the office and the field
A work list generated by what was missing
Client cadence that runs without anyone remembering
A decision record that becomes the reference of record
Cost visibility before the draw closes, not after
Accumulating evidence the standard was held

Why this is the part that compounds

The company remembers, so the owner does not have to
Absence becomes the to-do list, automatically

The Academy

Builds the people

8 weeks ▸

The shape of it

DBaseline

1wk

2wk

3wk

4wk

5wk

6wk

7wk

8wk

How it runs

One module per week, in your own platform
Run on live jobs by your own team
Verified before the next module begins
Graduate on installations, not sessions attended
Owner sponsorship required, because one bypass teaches optional
Your team shapes the build, which is why it sticks

The Diagnostic comes first

Separate required step, two weeks, remote
Sets the baseline so there is a measurable before

From the research

Every failure we counted was a missing process.

Click any complaint to see what was actually missing.

Communication and responsivenessStandard + System▸

A cadence guaranteeing the client hears from someone on the schedule they were promised. Cadence is installable. Charm is not.

Warranty and callback responseStandard + System▸

Cause coding at closeout, and an owned route for anything raised after move in. The most escalated category in the study.

Cost transparency and billingSystem▸

Cost decisions captured as they happen and surfaced before the invoice. Clients forgive the number they watched get built.

Schedule delay and visibilityStandard + System▸

Commitments set against a baseline, with movement communicated rather than discovered by the client.

Project management and supervisionAll three▸

Quality control that stays with the builder instead of migrating to the client. The moment a paying client becomes an unpaid employee.

Accountability and follow throughSystem▸

Open items carrying a named owner and a closure record. Nothing lost in the gap between two people.

Punch list and closeoutStandard▸

A defined finished state, and evidence it was actually reached before anyone calls the job done.

Design and expectation mismatchSystem▸

Decisions documented at the moment they are made, in one owned record rather than an email thread.

Staffing and turnoverAll three▸

A company that remembers, so a departure is an inconvenience rather than an amputation.

Price, and outright abandonmentOut of scope▸

Two of the fourteen categories we counted are honestly outside what this fixes. Saying so is worth more than claiming total coverage.

Plainly

What this is not.

+Not software

The tools are ordinary and mostly ones you already pay for. You are buying the operating knowledge that makes them work together.

+Not coaching

Coaches leave you with notes. Configurators leave you with a configured tool. This leaves an operation that runs without inspiration.

+Not a guarantee

Things will still go wrong. The system makes the same thing going wrong twice very hard, and leaves a record when it does.

Where to go from here

The Diagnostic is the only entry point, and the baseline everything else gets measured against.

The evidence

What actually goes wrong

290 customer records, 67 builders. Counted, not estimated.

Read the research → Four minutes

The Operating Gap

Ten questions about how the company runs. A ranked install list, not a grade.

Run the check → The map

The System Map

Every finished job leaves 53 pieces of proof. Six rooms by seven areas, on one grid. Free, takes an email.

Open the map → Start here

Measure your operation

Two weeks, remote. Three engagements per quarter.

Request the Diagnostic →

Working with someone who should see this?

The people who notice these patterns first are often not the ones who can act alone.

The reason things run well when the owner is on it, and slip when he is not, is not a people problem. The standard only exists in his head. This outfit writes it down, builds the system that runs the day against it, and trains the team on it. Eight weeks, on live jobs.