Back online
S5 Feature Standard — Trend Detection

Spreadsheets Show Numbers. POD Shows Where They're Heading.

Productivity was up 12% in week 3. Nobody noticed that inspection pass rates had dropped 8% simultaneously. By week 6, the rework was undoing every productivity gain. The number was fine. The trend was not. POD watches the trends.

0–0d
Avg Advance Warning
0%
Alert Accuracy Rate
0+
Metric Pairs Monitored
24/7
Continuous Tracking

The Signal Was There. Nobody Was Looking for It.

Divergence between correlated metrics is the most valuable early warning in construction. It is also structurally invisible to any tool that shows numbers without watching relationships.

Numbers look fine. The trend is not.

Productivity was up 12% in week 3. Everyone celebrated. Nobody noticed that inspection pass rates had dropped 8% in the same period. By week 6, the rework was undoing all of the productivity gain. The number was fine. The trend was not.

Spreadsheets show snapshots, not direction

A snapshot tells you where you are. A trend tells you where you are going. A divergence tells you two things that should be correlated are pulling apart — and that something has broken. Spreadsheets cannot produce this. They were never designed to.

The signal existed. Nobody was watching for it.

The divergence between quality and productivity started on day 19. The rework crisis arrived on day 43. Twenty-four days of warning, all present in the data — but no system was watching for the divergence pattern and no alert fired.

How Trend Detection Works

01

POD tracks correlations between all metrics

Every KPI pair that should move together is monitored continuously. Productivity and quality should correlate. Schedule pressure and safety should inversely correlate. Budget burn and progress should correlate. POD watches all of these relationships.

02

TrendDivergenceAlert fires when correlations break

When two metrics that normally move together start pulling apart, an alert fires. Not when the divergence has caused a problem — but when it first appears. The signal precedes the consequence by days or weeks.

03

MomentumVector shows direction and velocity

Knowing that metrics are diverging is half the picture. MomentumVector shows the net direction — is the project composite health accelerating, stable, or degrading, and at what rate? The vector quantifies the drift.

What Trend Detection Changes About How You Manage

Catch divergences while they are still correctable

A 5% quality drop paired with a 12% productivity rise is easy to correct in week 3. It is expensive to correct in week 6, after the rework has cascaded. Trend detection fires in week 3.

Early intervention window

Turn directional data into decisions

MomentumVector does not just show that something is wrong — it quantifies the rate and direction of drift. A momentum vector pointing down at 30 degrees is different from one pointing down at 70 degrees. The angle drives urgency.

Quantified urgency

See the relationship between metrics, not just the metrics

TrendDivergenceAlert forces a question other tools cannot even ask: why are productivity and quality pulling apart? The relationship is the insight. The individual numbers were both within acceptable range — the relationship was not.

Relational intelligence

The Direction Your Data Is Heading — Before You Have to Ask

Two lines animate across 20 data points. They run parallel — then diverge. Watch the alert fire and the momentum vector point down.

HighMidProductivity (rising)Quality (diverging)Day 1Day 9Day 13Day 20The signal existed. POD fired the alert 7 days before the rework cascade.

The Direction Your Data Is Heading — Before You Have to Ask

TrendDivergenceAlert identifies when correlated metrics pull apart. MomentumVector shows the net direction and rate.

Trend Divergence

POD
Pairs0
Divergent
AlignedNaN
divergent pair/ gap is largest

Momentum Vector

POD
Steady
0.0Accel: 0.0
Velocity0.0
Accel0.0
Pillars0
Momentum steady — velocity holding at 0.0

Trend Detection That Watches Everything

Cross-domain divergence detection

POD monitors divergence not just within categories but across them — safety vs schedule pressure, budget vs productivity, quality vs crew fatigue. Cross-domain patterns are where the most important signals live.

Configurable alert thresholds

Set the divergence threshold that triggers an alert. Conservative projects may want an alert at 5% divergence. Fast-moving projects may set it at 10%. The sensitivity is yours to configure.

Trend history with event markers

TrendDivergenceAlert history shows when previous alerts fired and what happened after. Did the divergence correct or continue? The historical pattern trains better responses.

Push notifications on divergence

When TrendDivergenceAlert fires, a push notification goes to the assigned project manager immediately. Not in the next report. Not at the end of the week. Now.

Divergence cone visualization

The shaded cone between diverging metrics shows how fast the gap is widening. A narrow cone means early signal. A wide cone means the divergence has been building. Width communicates urgency.

Momentum vector components

MomentumVector breaks down into its components: schedule momentum, safety momentum, budget momentum, quality momentum. You can see which domain is dragging the composite vector down.

“TrendDivergenceAlert fired on a Wednesday. We had two weeks of productivity gains paired with quietly declining quality scores. Without POD we would have hit the rework wall in two more weeks. We caught it, slowed down, and saved $180K in rework.”

Project Controls Manager, Industrial GC, Ohio

Common Questions

Stop Watching Numbers. Start Watching Directions.

POD doesn't conform to tools that display static numbers. POD defines the standard — directional intelligence that watches where your metrics are heading before you have to ask.

Last updated: March 2026