Managing the Metrics
Red Flags Aren’t the Problem, Seeing Them Too Late Is
The best reporting does not give management more data. It shows them where to look.
In sales and pre-construction, most problems do not appear suddenly. Margin pressure, weak budget coverage, trade uncertainty, client-facing cost movement and stale reporting usually leave signals long before they become major issues. The challenge is that those signals are often buried inside the cost plan, scattered across reports, or only visible to the person working closest to the detail.
For everyday users, this creates a practical problem. They are expected to manage the project, protect margin, maintain budget confidence, track changes, understand market coverage and keep the cost plan aligned with the latest information. But if the key metrics are not clear, visible and easy to interpret, the user is forced to manage by memory, instinct or manual checking.
For management, the problem is different. Leadership does not need to sit inside every estimate, every trade comparison or every client-facing revision. But they do need to know which projects are healthy, which projects are exposed, and which projects need support. A headline GP position on its own is not enough. A project can appear commercially sound while carrying weak budget coverage, limited trade confidence, significant movement, unresolved assumptions or stale data.
This is where managing the metrics becomes critical. The goal is not more reporting for the sake of reporting. It is a better set of signals that help users act earlier and help management operate by exception. Green projects can keep moving. Amber projects can be watched. Red projects can be supported before the issue becomes expensive.
Good reporting creates visibility. Great reporting creates action.
When the right red flags are visible early, sales and pre-construction teams can make better decisions, protect margin sooner, maintain stronger internal confidence, and set projects up for a smoother construction phase. The earlier the signal is seen, the more options the team has to change the outcome.
Red flags rarely appear without warning
In sales and pre-construction, most project issues leave signals before they become major problems. Margin starts to drift. Budget coverage remains weak. Trade returns are thin. Client-facing changes become more severe. Reports become stale. The cost plan moves, but the warning signs are not always visible in a way that forces action.
The problem is not that the data does not exist. The problem is that the data is often buried, fragmented, or not translated into clear project health signals.
When that happens, users are left managing by instinct, and management is left governing by interrogation.
User-Level View
Managing the project without clear signals
Everyday users are closest to the detail. They are building the cost plan, managing updates, reviewing trades, tracking changes, and trying to keep the project commercially aligned as information evolves.
But if the key metrics are not clearly visible, users are forced to search for warning signs manually.
They may know the project is moving, but not how severely. They may know budget coverage is incomplete, but not where the exposure is greatest. They may know margin is under pressure, but not whether there is a realistic path to recover it.
This creates a reactive way of working.
Instead of being guided by clear metrics, users are left relying on memory, experience, and manual checking to identify what needs attention.
The important signals are buried
Metrics may exist inside the cost plan, but they are not always surfaced in a way that is easy to read, interpret, or act upon. A user can be sitting on useful information without seeing it as a red flag.
Users do not always know what the business is measuring
If management is focused on GP, budget coverage, trade readiness, client-facing movement, and reporting freshness, users need those same signals visible while they work. Otherwise, project teams and management are managing from different lenses.
Red flags become visible too late
By the time a concern is raised in a review meeting, the issue may already have moved from manageable to expensive. Early visibility gives the user time to act. Late visibility limits the available options.
Manual checking creates inconsistency
If users have to manually inspect multiple areas of the cost plan to identify risk, different people will interpret project health differently. This creates inconsistency between projects, teams, and reporting cycles.
Action is not triggered clearly
A metric should not only say “something has changed”. It should help the user understand what needs to happen next. Without clear thresholds, colour coding, or movement tracking, the red flag may be seen but not acted on.
Result: The user becomes reactive rather than proactive. Issues are identified through effort rather than surfaced through the system. The project may still be manageable, but the team loses time, clarity, and control before the right action is taken.
Management View
Too much detail, not enough signal
Management does not need to live inside every cost plan.
They do not need to inspect every line item, every trade return, every client-facing report, or every movement in the estimate. But they do need to know which projects are healthy, which projects are exposed, and which projects need intervention.
That requires more than a headline GP percentage.
A project may show a healthy margin position while still carrying weak budget coverage, limited market testing, severe cost movement, unresolved assumptions, or stale reporting. Without those signals, management can easily mistake a clean number for a controlled project.
The headline number hides the real story
Gross profit is important, but it is not enough. A strong GP position can be fragile if the cost plan is not properly covered, if trade pricing is weak, or if the latest design information has not been reflected.
Management reviews become interrogations
When the dashboard does not show the right signals, leadership has to ask more questions. What has changed? What is covered? What is assumed? Are the trade returns reliable? Is the client seeing movement? Is the report current? This pulls management into the weeds.
Projects are hard to compare
If each project reports health differently, management cannot easily compare them. One project may look strong because it is genuinely controlled. Another may look strong because its risks are not visible.
Intervention happens too late
The value of management visibility is early intervention. If the red flag only appears once margin has already moved, trust has already been damaged, or trade risk has already hardened, management has fewer ways to help.
Forecast confidence is weakened
Management needs to make business decisions based on reported project positions. If the supporting metrics are unclear, forecasts become harder to trust and decisions become more cautious, delayed, or dependent on personal confidence in the team.
Result: Management is forced to manage through questions instead of signals. Instead of operating by exception, leadership has to dive into detail to understand whether a project is healthy. This reduces speed, creates friction, and makes forecasting less reliable.
THE RED FLAGS THAT HIDE IN PLAIN SIGHT
Margin Health
Question: Is the project achieving the margin it needs to achieve?
Margin is usually the first metric management looks at, but it needs to be visible at more than one level. The total project position may look acceptable, while a section, sector, or scope area is under pressure.
What Gets Missed: Margin drift, margin pressure in specific areas, or downward movement across reporting periods.
Why it matters: A project can still look profitable while trending in the wrong direction.
Stretch Position
Question: Is there a realistic pathway to improve the position?
Current GP shows where the project is today. Stretch GP shows whether there is a pathway to improve it.
What Gets Missed: Projects that are under target with no real recovery pathway, or projects that have opportunity but no action plan.
Why it matters: A project with weak current GP but strong stretch potential may be manageable. A project with weak current GP and no stretch pathway needs attention.
Budget Coverage
Question: How reliable is the cost plan behind the headline number?
Budget Coverage combines coverage percentage, coverage quality, and assumption dependency. It helps show whether the cost plan is supported by market pricing, trade quotes, benchmarking, internal rates, allowances, or unresolved assumptions.
What Gets Missed: Unsupported scope, weak coverage, assumed items, provisional allowances, and open assumptions that make the number fragile.
Why it matters: A margin position is only as reliable as the coverage behind it.
Cost Plan Movement
Question: Is the project moving in a controlled way, or becoming volatile?
Cost movement is normal during sales and pre-construction. The issue is whether the movement is frequent, severe, unexplained, or inconsistent with the project stage.
What Gets Missed: Volatility between revisions, major movement by section or sector, repeated internal changes, or unexplained adjustments.
Why it matters: Movement is not automatically a problem. Unexplained or severe movement is the red flag.
Client-Facing Change Severity
Question: How is the client experiencing the movement?
This whitepaper is internally focused, but client-facing movement is still a key internal health signal. If the client sees large or frequent changes, trust may be at risk even if the internal commercial position is explainable.
What Gets Missed: The severity of changes from the client’s perspective, especially where changes are frequent, poorly explained, or linked to internal correction rather than client-driven decisions.
Why it matters: Management needs to know when the client journey is becoming unstable before trust is damaged.
Trade and Market Readiness
Question: Is the project ready to rely on the market position?
Trade coverage is not just about having prices. It is about whether the pricing is complete, comparable, and reliable.
What Gets Missed: Low trade return numbers, wide pricing spreads, exclusions, unresolved clarifications, incomplete scope comparisons, or weak non-price assessment.
Why it matters: A trade price is only useful if the business understands what is included, what is excluded, and how reliable it is.
Reporting Freshness
Question: Is the information current enough to trust?
A project can look healthy simply because the information is stale. If the latest design revision, client decision, trade return, or internal update has not been reflected, the dashboard may be showing false confidence.
What Gets Missed: Outdated cost plans, old dashboard positions, delayed change logs, or reports that have not caught up with the latest information.
Why it matters: A dashboard should not only show where the project is. It should show whether the information is current.
MANAGEMENT BY EXCEPTION
When red flags are not clearly categorised, every project can feel like it needs the same level of attention. That is inefficient and unnecessary.
The better model is management by exception.
Green projects can keep moving. Amber projects need watching or a focused question. Red projects need support, review, or escalation.
This changes the management conversation from:
“What is happening on every project?”
to:
“Which projects need attention, and why?”
That shift matters. It keeps everyday users focused on the metrics they can manage, and it keeps management focused on the projects where intervention can still change the outcome.