Period 8, issued May 3, 2024 — eighteen days after the profiling run returned. A change request has been drafted and has not been decided. This report is written with the recommendation on the table and the outcome unknown, and it is deliberately not written as though the answer were already obvious.
Contents
1. Period summary
| Area | Status | Movement this period |
|---|---|---|
| Overall | Red | Moved from amber. Identity resolution cannot complete inside the TSA term at current capacity. |
| Schedule | Red | Clerical review is now the critical path and exceeds the remaining window. |
| Cost | Amber | Contingency substantially committed. A reserve draw is in prospect but not yet requested. |
| Scope | Amber | Two candidate deferrals identified; no decision taken. |
| Quality | Green | Steward false-positive audits within tolerance. No member impact recorded. |
| Day 1 integrity | Green | Held throughout. No member-facing failure attributable to integration. |
Why overall is red while quality and Day 1 are green. Nothing has gone wrong operationally — members are being served, claims are paying, the platform is stable. The program is red because a measurement taken this period showed that a workstream cannot finish inside the time available, and no amount of current operational health changes that. Status reflects the ability to complete, not the absence of incidents, and the two are routinely confused in the direction that flatters the program.
2. The finding and what it forces
The first full profiling run against the consolidated member estate completed on April 15, 2024. It measured the population that the deal model had estimated but could not examine before close.
| Band | Deal model | Measured |
|---|---|---|
| Deterministic match | 65% | 41% |
| Probabilistic auto-match | 27% | 33% |
| Clerical review band | 8% | 26% |
The review band is the band that requires a human decision per record. At the modeled rate the queue was sized to fit the TSA term with margin. At the measured rate it does not fit, and the gap is not marginal.
This is not an estimating failure and the report should not be read as one. Antitrust rules bar an acquirer from examining member-level records before close, so the deal model's identity assumptions were a Class 5 estimate made under a legal constraint rather than a lazy one. The measurement could not have been taken earlier by anyone. What the program is accountable for is not the assumption but the response — whether the profiling was scheduled as the first substantive post-close data activity rather than deferred behind operational work, and whether the exposure was carried on the risk register in the meantime. Both were done; R-01 has been scored Critical since February.
3. Schedule position
Steward throughput is bounded and the boundary is not a resourcing choice. Three responses were examined and none is available.
- Offshore capacity — barred. Member-level data cannot be worked offshore under the state contract. A change request proposing it was raised and rejected this period.
- Higher throughput per steward — refused on quality grounds. A steward working faster produces more false merges, and a false merge is the error that nothing in normal operations surfaces.
- More onshore stewards — approved and already in progress, and insufficient on its own. Recruitment, clearance and training run weeks, and the second cohort reaches full productivity partway through the remaining window.
What remains is time. The drafted change request seeks a three-month extension of the transitional services agreement, which consumes negotiated margin without breaching the eighteen-month contractual maximum.
4. Cost position
Approved changes to date have committed the bulk of the contingency held against the post-close baseline. The drafted extension would exceed what remains and require a draw on management reserve, which is a Steering Committee decision rather than a program one.
Contingency and reserve are not interchangeable and the distinction is about authority, not accounting. Contingency covers identified risks inside the baseline and the program may commit it. Management reserve sits outside the cost baseline for unknowns and is released by the sponsor. Reaching for reserve is therefore a signal in itself — it says the program has exhausted what it was authorized to spend against known risk and is now asking for something it cannot grant itself. A program that quietly reclassifies a reserve draw as contingency use has removed the sponsor from a decision the sponsor is supposed to make.
5. What happens if the change request is refused
This section exists because a recommendation presented without its alternative is not a decision paper. Three courses are available to the Committee and the program's view of each is recorded here before the outcome is known.
| Course | Consequence | Program view |
|---|---|---|
| Approve the extension | Spends negotiated margin and reserve; identity resolution completes inside the revised term | Recommended |
| Refuse and exit on the original date | Exit occurs with the review queue open; unresolved records remain split, and continuity screening, claims history and reporting all inherit that state | Not recommended — it converts a schedule problem into a permanent data problem |
| Refuse and raise throughput | Queue clears on paper inside the term | Not recommended — it manufactures false merges, which is the one error class normal operations never reveals |
The second and third courses are both available and both survivable in the short term. The program's objection to each is that the cost is paid later, by someone else, in a form that is difficult to attribute back to this decision.
6. Everything else
Reported briefly, because a period in which one item dominates still has to account for the rest.
- Claims and core administration — parallel adjudication reconciles within tolerance; host claims processing retired on schedule.
- Cloud and infrastructure — migration waves on plan; managed-service step-down proceeding.
- Application integration — transaction interfaces stable; two batch defects closed this period.
- Vendor and contract — consolidation savings continue to land ahead of the technical tracks.
- Provider network — renegotiations proceeding as contract anniversaries open; no adequacy exceptions.
- Retention — no departures among retention-covered roles this period.
Related artifacts: 31 — Data Profiling Results · 43 — Steering Committee Deck · 28 — Risk Register · 44 — Change Control Log