Program Dashboard

Lighthouse Financial Services Company — Program status as at 16 October 2026, week 18 of 41 in Stage 2, 167 days before Gate 2 convenes on 01 April 2027.

1. What this dashboard does not show, and why

Most program dashboards lead with percent complete and a cost/schedule performance index. This one shows neither, and the omission is the most important thing on the page.

So this dashboard reports on a decision, not on a delivery. “Are we on track?” presumes a track running to the end of the program; there is no such track, only track as far as the next gate. The question it answers instead is: will Gate 2 be able to decide, and on what evidence? Sections 3 and 4 are that answer; Section 2 is the one variance that can legitimately be computed.

2. The one legitimate variance — inside the released tranche

Performance within a released tranche is measurable, because the tranche is a real authorization with a real amount and a real window. Stage 2 released $11,640,000 at Gate 1 for a 41-week stage.

Spend is running 5% behind elapsed time. On a conventional program that would read as favorable. Here it is reported without a verdict attached, because two very different things produce the same number: work genuinely costing less than planned, and work not yet done. The Gate 2 must-meet trajectory at §3 is what distinguishes them — and it shows contract forms and hedging readiness both behind, which points at the second explanation.

Three stories, one number

Decomposed, the under-burn admits exactly three explanations, and this dashboard's design follows from the fact that the spend figure cannot rank them. Cheaper: the work is being done for less than planned — favorable, and the only reading a conventional RAG report would offer. Later: the work is behind, and the money will arrive with it — which on a stage already compressed to 41 weeks is the unfavorable reading. Lagged: the work is on pace and the invoices are not — noise, common early in a vendor-heavy stage where the Cordelane and Brightpath billing cycles trail delivery. The milestone evidence in §3 currently supports later for two workstreams, which is why this section will not print the word “favorable.”

Why the tranche is the wall

Notice what this section does not do: extend the bar past the Stage 2 tranche to show position against total authorization. That extension is the single most common way stage-funded programs mislead themselves — it converts money the Board has explicitly withheld into a denominator, and every ratio computed on it inherits the fiction. The Stage Budget Console exists to make the four funding states visually undeniable; this dashboard borrows its discipline and reports variance only where a real authorization creates a real denominator.

3. Gate 2 must-meet trajectory

Five must-meet criteria were fixed at Gate 1. Any one unmet removes GO and GO WITH CONDITIONS from the table regardless of the weighted score, so this is the section that actually predicts the gate.

The two open conditions are not equally dangerous, and the difference is structural

GC-03 (external actuarial peer review, due 26 Feb 2027) is on-track and — more importantly — is self-contained: its critical path runs through one engagement the program itself purchased and controls, and its evidence is a report that either exists at the gate or does not. GC-05 (hedging readiness, due 12 Mar 2027) is at-risk for the opposite structural reason: its critical path runs through a counterparty's legal department. ISDA onboarding is a negotiation the program can schedule but not compel, which is why DEP-06 exists as a tracked dependency rather than a task. A condition whose closure depends on an external party's calendar deserves a different watch-level than one whose closure depends on the program's own diligence — the register scores them identically as “open,” and that is precisely the flattening this dashboard exists to undo.

What the trajectory column is actually predicting

A must-meet criterion is a knockout: any single miss removes GO and GO WITH CONDITIONS from the Board's option set before the weighted scoring even convenes. So the trajectory column is not progress reporting — it is a forecast of which decisions will be available on 01 Apr 2027. Read that way, the current picture says: on today's evidence the Board would not have a clean GO available, and the program's remaining 167 days are about restoring options, not polishing a score.

4. Gate conditions

3 of 5 closed. Full verification methods, evidence and the post-closure efficacy findings are in the Gate Conditions Register — this dashboard carries status only, so there is one place where condition detail can be wrong.

5. Top open risks

Scores are probability × impact, re-scored at the status date. The two highest are the two that rose since Gate 1, and both sit behind the conditions still open — the risk register and the condition register agreeing from opposite directions, which is the intended behavior and would be a defect if they diverged. Movement, response and the full twelve-risk register are in the RAIDD Log.

Concentration is the finding, not the scores

Three separate registers now point at the same narrow front: the two risks that rose since Gate 1 sit behind the two conditions still open, which sit in front of the must-meet criteria currently off-track. That triple agreement is worth naming because it changes what “mitigation” means — the program does not have five medium problems to work in parallel; it has one concentrated exposure (hedging readiness and the distribution commitment gap) wearing three reporting formats. It also identifies the failure mode this dashboard should be watched for: if the registers ever stop agreeing — a risk falling while its condition stays open, a condition closing while its must-meet stays off-track — the divergence is more likely a bookkeeping error than a real change, and the Register's post-closure efficacy check exists for exactly that suspicion.

6. Schedule position

7. What would make this dashboard lie

Stated deliberately, because a status report that cannot describe its own failure modes is decoration.

• Reading the Stage 2 under-burn as good news. §2 refuses to attach a verdict for exactly this reason. Under-spend against elapsed time is ambiguous until the must-meet trajectory disambiguates it.
• Treating $13,672,000 of unreleased funding as contingency. It is not available; it is money two future gates may decline to release.
• Reporting 3 of 5 conditions closed as 60% progress. Conditions are not fungible. GC-03 is named in a Gate 2 must-meet; GC-05 is not. Closing the two easiest first would show the same percentage and mean much less.
• Aggregating the risk scores into an average. The program's exposure is concentrated in two risks, and an average would dilute exactly the signal that matters.

The lie this dashboard is most likely to tell next

Every failure mode above is a misreading a careful reader can refuse. The dangerous one is different in kind: staleness wearing precision. Every figure here carries the 16 October 2026 status date, and the month between refreshes is exactly the window in which an ISDA negotiation stalls or an IMO commitment quietly softens. A reader who treats a four-week-old “on-track” as a current fact is being misled by typography — the pill looks as fresh as the day it was rendered. The mitigation is structural rather than editorial: the monthly refresh regenerates this page, the Gate Conditions Register and the Readiness Assessment from the same evidence in the same pass, so the three documents can be wrong but cannot disagree — and a reader who finds them disagreeing has found a stale copy, not a controversy.

8. Reporting cadence

Maintained by C. Tyrrell, NPD Program Manager and Chair of the Gate Review Board. Related: Gate 2 Readiness Assessment · Gate Conditions Register · RAIDD Log · Program Budget · Methodology Guide §5 (why no EVM).