Delivery confidence

The Delivery Truth Engine

One delivery confidence number, checked against the work.

Lighthouse flags where the numbers contradict each other and tells you what to fix before you share a steering pack.

One number, checked

Each initiative is scored from the angles below. Lighthouse combines them and shows you which one disagreed.

Delivery confidence

Are milestones and progress hitting their dates?

Capacity confidence

Do the squads have the hours?

Data confidence

How fresh and complete the numbers are.

Financial confidence

Is spend tracking to plan?

Governance confidence

Gates passed, approvals recorded, dependencies acknowledged.

Scenario confidence

The best alternative plan from your scenarios.

Pre-mortem confidence

Lighty imagines the initiative failing and names the top 3 reasons.

Simulated finish

Thousands of simulated plans to find a realistic finish date.

Reported confidence

What the PM said in their last update.

Example. “Apollo” reports 78% delivery confidence. Lighthouse checks it against the work and drops it to 52%: the squad is at 145% utilisation and a vendor risk was never recorded.

Catches contradictions

Every steering pack is checked for contradictions like these.

  • Reported healthy, but capacity is at 145%.

  • A 28-week initiative with 4 weeks of plan.

  • An overdue milestone with green confidence.

  • Reporting on people who aren’t allocated.

  • A dependency that is silently broken.

  • A steering pack built on a baseline older than the last reset.

  • Scenario confidence far better than the live plan.

  • Two measures more than 30 points apart.

  • A stage-gate decision that was never recorded.

Before

Apollo: 78% confidence, on track

Capacity is at 145% and nobody flagged it. The PM’s update stands.

After

Apollo: Lighthouse sees 52%, capacity contradicts what was reported

The pack shows the contradiction next to the number.

Decision audit trail

Every Lighty recommendation, every call you make and every outcome is logged per initiative.

When
Lighty recommended
You decided
What happened
2026-04-08
Pause Apollo, free 2 engineers for Checkout
Hold scope on Apollo, defer Checkout one sprint
Checkout slipped one sprint; Apollo capacity stayed at 145%
2026-04-22
Promote scenario S-7 (rebalanced) to live
Promoted with caveat: Range tribe vacancy still open
pending — outcome captured at the next gate

Why this matters. When someone asks why you chose a path, you have a row, not a screenshot of a Slack thread.

Blocks bad packs

A steering pack is only marked “ready to share” when the numbers add up.

Ready to share

The numbers agree. Take it to your board.

With caveats

Mostly aligned. The caveats are printed so you can answer the question first.

Not ready to share

The numbers contradict each other. Fix them, then re-run.

Why this matters. A bad board meeting costs weeks of recovery. Exports are blocked for packs that aren’t ready.

See it on your own data.

It runs on every steering pack.