ProjectScript Logo
For the Construction CFO

How confident are you in the forecast you presented last month?
It was already old when you signed it.

Every forecast built on month-end data is a forecast built on information that was 20–30 days old at the moment of presentation. The Daily Margin Protection System applies earned value methodology at the activity level — daily — so the numbers you defend are today's numbers, not last month's.

See the 15-Day Engagement
The core problem
"When did this variance start — and how long did you have to correct it before it appeared in your report?"
With monthly reporting: 20–30 days of compounding exposure before the number appears in your report.
What changes with DMPS
1
Day to visibility
Daily
EVM calculation
6
Signed metrics
The methodology
Earned value methodology applied at the activity level — every day. The same rigour used on major capital programmes, running daily across every active project.
The Methodology

Earned value — applied daily,
not just at reporting time.

Earned value management is not new. It has been the standard for financial performance measurement on major capital programmes for decades. What the Daily Margin Protection System changes is the frequency — and the level at which it is applied.

  • Traditional EVM: calculated at project or work-package level, monthly or quarterly. Useful for portfolio reporting. Too slow and too aggregated to drive daily operational decisions.
  • DMPS EVM: calculated at the activity level, every day. Every crew, every task, every site — planned value vs earned value vs actual cost, updated before the working day ends.
  • No new methodology to learn. If your team understands earned value, they understand exactly what DMPS is measuring — and exactly how to interpret the daily output.
  • Forecast accuracy improves immediately. When cost and schedule variances are detected on Day 1, the forecast reflects corrections that have already been made — not corrections that are still pending.
How the Daily Calculation Works
Planned Value
What the activity was budgeted to cost at today's planned progress. Set at baseline.
Actual Cost
What was actually spent on the activity today. Captured from site at close of day.
Earned Value
The budgeted value of work actually completed today. The financial truth of today's performance.
The gap between Earned Value and Actual Cost is your cost variance — visible today, not at month-end. The gap between Earned Value and Planned Value is your schedule variance — in financial terms, not just days. Both calculated at the activity level. Both available before the end of the working day.
The CFO's Structural Challenge

Month-end reporting does not give you
numbers you can fully defend.

The problem is not your finance team or your accounting process. It is the structure of monthly reporting — which means your numbers are always a reconciliation of what happened, not a measurement of what is happening.

01
The Reconciliation Lag
By the time cost data moves from site through approval to your ERP, 15–25 days have passed. Your month-end report is a historical document — accurate, but not current.
02
The Forecast Credibility Gap
Every forecast adjustment happens after the variance has already compounded. You are correcting the projection of what happened — not preventing what is happening. Board presentations rely on data that was old before it was prepared.
03
The Cross-Domain Blind Spot
A safety incident, a quality rework, a crew change — each one has a financial impact. But that impact does not reach your numbers until the relevant system feeds into the monthly reconciliation. You see the financial consequence weeks after the operational event.
04
The Bid Accuracy Problem
Contingency levels and margin assumptions on new bids are built from historical performance data. If that data is systematically delayed, your bid pricing reflects what you thought was happening — not what actually happened.
The CFO-Signed Baseline

You define the measurement framework.
We operate inside it.

Most technology vendors define what success looks like. The Daily Margin Protection System does not. Before Day 1, you define and sign the six metrics that will be measured — and those metrics become the only basis on which the 15-Day Engagement is evaluated.

  • 1
    Baseline Validation Meeting
    A structured session with you and your Operations Director. Current performance across six metrics is documented and agreed.
  • 2
    You Sign the Baseline
    The documented baseline is signed by you — the CFO. This is your measurement framework, not ours. It cannot be moved during the 15 days.
  • 3
    15 Days of Daily Tracking
    DMPS runs on one active project. Earned value calculated daily at activity level. Weekly executive reviews against the signed baseline.
  • 4
    Day 15 Decision
    Results compared against your signed baseline. Every improvement converted to annualised dollar impact using your numbers — Not our projections.
"
"The ROI is measured by your numbers — signed by your CFO, calculated using earned value methodology. Not a vendor claim."
The six metrics defined and signed before Day 1:
Detection lag
Forecast accuracy
Labor variance
Material variance
Equipment variance
Reporting overhead
Numbers You Can Defend

When your financial data is current,
every conversation changes.

When you present daily-verified numbers to a board, a client, or a bid review, you are in a fundamentally different position from presenting a month-old reconciliation. Here is what that difference looks like in practice.

Board Presentations
Before"Our forecast is based on last month's cost report, reconciled against the schedule update."
After"Our margin position is verified as of yesterday. Here is the cost variance per activity across all active projects."
Client Negotiations
BeforeCost data is 20–30 days old. Variance claims rely on estimates and manual reconciliation that the other side can challenge.
AfterDaily earned value per activity. Cost position current and baseline-signed. Defensible in any negotiation.
Bid Pricing
BeforeHistorical performance data delayed and aggregated. Contingency levels reflect what you thought was happening.
After15 days of daily activity-level performance data — and ongoing programme data thereafter. Contingency built from what actually happened — at the activity level.
Cash Flow
BeforeBilling measurements based on progress data that is 20–30 days old. You bill late because your measurement is late — and your working capital suffers the compounding cost of that delay on every project.
AfterBilling measurements based on yesterday's verified progress. Earlier billing. Earlier collection. A structural improvement in working capital — on every project, every month, not as a one-time gain.
The 15-Day Engagement

A structured financial proof.
Not a software evaluation.

Fixed duration. CFO-signed baseline. Two engineers on site. Documented result at Day 15. The question the engagement answers is not whether DMPS works. It is how much margin erosion is currently invisible on your project — and what it costs you each month it stays that way.

01
Before Day 1
CFO Baseline Session
You and your Operations Director define six measurable metrics. Current performance documented. Baseline signed by you. This is the only measurement framework used for the 15 days.
02
Days 1–15
Daily EVM — Your Dashboard, Every Morning
Two DMPS engineers on site. Foremen report via WhatsApp at start and close of each working day. Earned value calculated at activity level — cost variance and schedule variance — before your working day begins. You receive the dashboard every morning. Your ERP and scheduling system continue unchanged.
03
Day 15
Your Numbers. Your Decision.
Results compared against your signed baseline. Detection lag, forecast accuracy, and all six variance metrics measured and converted to annualised dollar impact. Calculated using earned value methodology. If the improvement is demonstrated, the conversation moves to a monthly programme.
Every implementation starts with a CFO-signed baseline and ends with a documented, defensible ROI comparison.