The Method
Decision-Centered Construction Project Control
A practical way to run project controls: name the decision first, then the evidence, the threshold, and the action.
Decision architecture
Twelve links, in this order.
The Decision-Centered Construction Project Control Methodology is built around Decision Control Points, or DCPs. A DCP is not a report. It is a decision the project has already agreed must be made when a defined threshold is crossed.
The aim is straightforward. Fewer surprises, and a recorded path from a signal to an action someone owns.
Read it as a chain. Each link exists so the next one can be used. Skip a link and the project is back to a number without an owner.
- 01
Decision
The choice the project actually has to make.
- 02
Responsible Actor
The person accountable for making that choice.
- 03
Information needed
The facts that person must have in hand.
- 04
Source
Where those facts come from, and who produces them.
- 05
Baseline
The approved plan the facts are judged against.
- 06
Indicator
The measure that shows movement toward or away from the baseline.
- 07
Threshold
The value that turns a measure into a required decision.
- 08
Root Cause
Why the threshold was crossed, not only that it was.
- 09
Forecast
What happens to cost, time, or scope if nothing changes.
- 10
Corrective Action
The specific response the responsible actor commits to.
- 11
Verification
Whether that action brought the indicator back inside the threshold.
- 12
Lesson Learned
What the project will do differently on the next cycle.
Operational cycle
How the work moves each period.
The architecture says what a decision contains. The cycle is how the team runs it. Learn feeds the next Capture. The loop does not stop at a report.
Follow the steps in order. After Learn, the next step is Capture. The diagram reads clockwise.
- 01
Capture
Collect the current field, cost, and schedule data.
- 02
Validate
Check that the data is complete, current, and consistent.
- 03
Integrate
Put the validated data on one picture of the project.
- 04
Analyze
Read performance against the baseline.
- 05
Compare
Set actuals next to the plan and the thresholds.
- 06
Detect
Flag every indicator that has crossed a threshold.
- 07
Diagnose
Find the root cause, not only the symptom.
- 08
Forecast
Project the effect on cost, time, and the remaining work.
- 09
Decide
The responsible actor chooses, inside the Decision Control Point.
- 10
Communicate
Tell the people who must act, in writing.
- 11
Act
Carry out the corrective action.
- 12
Verify
Check whether the indicator moved back inside the threshold.
- 13
Learn
Record what held, and feed it into the next cycle.
Instruments
Tools, tied to a decision.
The method does not replace the instruments a project already trusts. It connects them to a decision, an owner, and a threshold. Pharus works with:
LPS
Last Planner System
Short-term commitments, and a clear record of why a commitment was missed.
EVM
Earned Value Management
Cost and schedule performance measured against the approved baseline.
CCBM
Critical Chain Buffer Management
Buffer consumption as an early signal, before the finish date slips in the open.
BIM
Building information modeling
Quantities, coordination, and scope context from the model, on projects that have one.
Monte Carlo
Monte Carlo schedule-risk analysis
A range of finish outcomes, instead of a single date treated as certain.
Resources
Resource optimization
Crews and constraints lined up with the work the decisions depend on.
KPIs
KPIs and early-warning alerts
A short set of indicators whose thresholds call a decision, not a dashboard kept for its own sake.
The difference
A metric without a decision is not a control.
Pharus does not sell an isolated schedule or a periodic report. Every metric is tied to a specific decision, the person who owns that decision, and a threshold that triggers action. If a measure is not attached to those three things, it is not yet part of the control set.