FREE · 23 COMPONENTS · ABOUT 5 MINUTES
Most of what's going wrong on your project is a symptom.
Something upstream is causing it. Score your project across all 23 components of the IPCS and you get a graded report that names the root causes, separates them from the symptoms, and tells you which one to fix first.
This is the full assessment, not a sample. All 23 components, including the five that sit outside your control, because knowing which problems are not yours is half the value.
Why grade it at all
How construction projects actually finish
58%
Finish on budget
8%
On budget and on time
0.5%
On budget, on time,
as the owner wanted
as the owner wanted
Source: Bent Flyvbjerg and Dan Gardner, How Big Things Get Done.
Those numbers don’t move because teams aren’t working hard enough. Most teams on a failing job are working harder than the teams on a good one.
They move when a team stops firefighting the loudest problem and starts owning the operating system underneath the work. That starts with one thing — knowing which component is the cause, and which ones are just downstream of it.
Those numbers don’t move because teams aren’t working hard enough. Most teams on a failing job are working harder than the teams on a good one.
They move when a team stops firefighting the loudest problem and starts owning the operating system underneath the work. That starts with one thing — knowing which component is the cause, and which ones are just downstream of it.
Who this is for
Superintendents & PMs
Running a live job.
Executives
Who own more than one of them.
Trade partners
Who want to know what a good general contractor should be doing before they sign.
If you’re on a project right now, grade that one. The report is worth more when the scores are real.
How it works
Three steps. About five minutes. Nothing to install, no call to book, and your progress is saved if you stop
01
1 Score 23 components
Each one gives you five specific descriptions of what it looks like on a real site. You pick the one that matches your job. No vague one-to-five ratings for the team to argue about.
02
2 See your grade
One score out of four, a verdict, and how many components need work — with the ones causing the rest named separately from the ones just suffering from them.
03
3 Get the full report
Emailed as a PDF: every weak component, what it’s already doing to your site, and the order to fix them in. Root causes first, not worst score first.
Start here. This is question one.
Twenty-three of these, about five minutes. The answers describe behavior, not opinion, which is why the result is worth acting on.
- Every answer describes a real site condition, not a rating
- Your progress is saved if you lose signal
- Built for a phone in a trailer
The questions you're
actually asking
What does this cost?
Nothing. The assessment and the report are free. If you want help with what it finds, that’s a boot camp, a guidebook or a field-walk engagement, and those are priced on this site.
What if my score is bad?
Most are. Worldwide, projects run 60% over budget and in the US they finish an average of 58 days behind. A low score isn’t a verdict on you. Some of it is set by things you don’t control — the owner’s paradigm, the contract, the rules you’re handed — and the report says which ones those are, so you stop carrying them.
Is someone going to call me?
No. We email the report, then follow up on the components you scored lowest. Unsubscribe any time.
How long does it take?
About five minutes. Twenty-three components, each with five specific descriptions to pick from. It is longer than a quiz because it is not a quiz. It is the full diagnostic. Your progress is saved, so you can stop and come back.
We already run lean. Is this for us?
Then it takes five minutes and either confirms it or finds the gap. Teams already running lean usually score well on production planning and badly on individual balance — whether every person on the team has a personal organization system underneath it all.
Can I grade more than one project?
Yes, and you should. Grade each one separately. The comparison is where it gets interesting.
What lands in
your inbox
A PDF you can put in front of the team on Monday morning.
The fix order, by dependency
Components are ranked by what’s causing what, so you start where fixing one
thing lifts the others.
What each one is doing to your site
Written as what’s happening on your job right now, not as an abstract risk, so the team recognizes it.
The symptoms, kept separate
Listed apart from the causes on purpose. Working on those first is how teams spend a year fixing the same problem.
Optional 60–90 sec video: "Why I built this"
Why I built this
I’ve spent years walking onto projects that were already in trouble. Every single one was missing one of the same few things.
That’s the whole reason this exists. I would rather you find it in three minutes on your phone than nine months in, when the only thing left to try is overtime.
You’re going to score badly on something. That’s fine — almost everyone does. What matters is whether you’re fixing the thing that’s causing the rest, or the thing that’s shouting the loudest.
— Jason Schroeder
Elevate Construction
Grade the project
you're on right now
Twenty-three questions, about five minutes, and a report that names the one thing to fix first.
Free. No call. Unsubscribe any time.
One score is a snapshot.
The trend is the diagnosis.
Grade it again in 30 days and compare. What you’re looking for isn’t a higher average. It’s whether the components downstream of your root cause came up on their own. That’s the system working.
Today→30 days→60 days