CxSTAT IQ · Cx Risk Engine

Predict delays before they happen.

The Risk Engine reads live readiness signals and history to forecast what actually slips: which test window holds, which issue closes late, and which dependency quietly moves your date.

app.cxstat.com/iq/risk-engine
The problem

Risk reviews look backwards, projects move forwards.

By the time a slip is visible in the schedule it has already happened. The signals were there weeks earlier, scattered across logs nobody reads together.

notifications_paused

Silent issues

The riskiest items are not the loud ones in the morning meeting. They are the ones that stopped talking 42 days ago and are still on the critical path.

event_busy

Windows booked on hope

Vendor witnesses, test prerequisites and open issues rarely line up the way the lookahead assumes. The window slips on the day.

device_unknown

Every project starts from zero

The lessons of the last five buildings live in people, not systems. The same failure modes repeat with new logos.

How it works

From signals to probabilities.

Forecasts are computed from the same evidence graph the rest of IQ runs on, so every probability can show its drivers.

sensors

01 · Watch the signals

Issue cadence, retest rates, evidence flow, vendor confirmations and dependency states, streamed from the live graph.

functions

02 · Score against history

Patterns are scored against how similar situations resolved before: silent issues, failed-retest chains, witness no-shows.

crisis_alert

03 · Rank what moves the date

A probability for each upcoming milestone, decomposed into ranked drivers with the action that most improves the odds.

What you get

Numbers your schedule can act on.

Not a red-amber-green feeling: probabilities with drivers attached.

speed

P(window holds)

A live probability for each test window and milestone, updated as evidence lands, with the trend since last week.

podium

Ranked risk drivers

The specific items moving the probability: an untested UPS, a silent issue, an unconfirmed witness, each with its days-at-risk impact.

history_edu

Root-cause recall

When a pattern matches past trouble, the engine says so, and shows what actually fixed it last time.

mark_chat_read

Early, quiet warnings

Flags raised weeks before the lookahead notices, routed to the owner of the driver, not broadcast to everyone.

Questions we get

Frequently asked.

Where do the probabilities come from?add
From the live evidence graph and resolution history: issue lifecycles, retest chains, dependency states and witness confirmations, scored against how similar situations have resolved before. Every probability lists its drivers.
Is this a schedule tool?add
No. It reads your schedule but does not replace it. It tells you which scheduled things are unlikely to happen as planned, early enough to change the outcome.
Can it be wrong?add
It deals in probabilities, not prophecies. A 0.72 will sometimes hold and sometimes not. What it will always do is show the drivers, so the judgment call is informed rather than blind.