Independent assurance vs an SI readiness review

Your system integrator knows the configuration, the test cycles and the cutover plan better than anyone. Its readiness review is the best source of what has been done, and it should be the first input to any go-live decision.

But it is part of delivery. The integrator is reporting on its own work, and its final milestone depends on the date holding. That is a structural position, not a question of honesty, and it is why a steering committee needs a second view before it signs.

An integrator’s commercial plan, staffing and next phase usually assume the date holds. Teams under that pressure can report faithfully and still read every ambiguity in the direction of the plan: a test cycle “substantially complete”, a reconciliation “with minor differences”, a cutover plan “approved in principle”.

Each of those is defensible on its own. Together they can add up to a Green status that the evidence does not support. The same applies to any team whose fee, bonus or next phase depends on the date, including internal ones. Independent assurance does not replace the integrator’s judgement. It checks it.

Comparisons describe typical market practice, not specific firms.

• Every critical claim tested for status, owner, evidence, date and action.
• Claims checked against each other across workstreams, where the most expensive risks sit.
• A recommendation the steering committee can defend: Go, Conditional Go or No-Go.
• Decision conditions with named owners and evidence-by dates, so a Conditional Go can be tracked.

• No implementation fees, no software resale and no system integrator partnerships or referral fees.
• A fixed scope and a published price, so you can judge the cost before you talk to them.
• A sample of the output you can see before you buy.
• Tests claims against evidence, rather than reviewing documents for completeness.
• Reports to the sponsor, and the person who signs the findings is the person who did the review.
• Says plainly that a review does not guarantee go-live success.
• Can start within days, because the review works from the documents you already have.

• Six to sixteen weeks before the go-live decision. Earlier is fine.
• When the date is fixed by something outside the programme, such as a regulatory deadline or the end of mainstream maintenance for the current system.
• When workstreams report Green but the steering committee cannot see the evidence behind it.
• When the integrator’s milestone payment is tied to the go-live date.
• Before rolling out to further entities or countries.

Mostly, documents the programme already has: test logs and defect lists, reconciliation outputs, the cutover plan and rehearsal results, the RAID log and the latest status reports. Then short interviews with workstream leads, held only where the documents disagree.

It also needs a sponsor who receives the findings directly. If the findings reach the steering committee only through the delivery team, the review loses the independence it was bought for.

A decision brief the steering committee can read in minutes, an evidence register showing each claim and the evidence behind it, a contradiction map, dated decision conditions with owners, the leadership actions for the next 30 days, and a readout for the sponsor. If a provider cannot show you a sample of these before you sign, ask why.

Independent assurance is not an audit of the integrator. The review asks for the documents the programme already has on day one, and holds interviews only where the evidence conflicts, which keeps everyone’s time to a minimum. Findings name who should own each fix. The assurance provider does not implement the fixes, so its view stays independent.

Done well, the review helps the integrator too. A Conditional Go with clear conditions, owners and dates is easier to deliver against than a Green status that nobody fully believes, and it gives the integrator a defensible record of what was agreed before go-live.