Xcelerate
Menu
Get in touch
All articles on software design and procurement

Software design and procurement

What to ask for in a software supplier exit plan

Define a usable data export, operational handover and a witnessed restore before appointing a supplier for a public service application.

An operator checks exported files and attachments on a laptop during handover.
AI-generated editorial image.

A spreadsheet full of application numbers is little comfort if the next operator cannot open the attachments or tell which decisions are still pending. An exit plan should describe how a replacement team will resume the service. Agree the handover evidence while suppliers are still competing for the work.

Pick a record with a history

Choose a fictional facilities booking that staff have amended, approved and invoiced. Ask what the buyer receives for that one record at exit. It might include the booking identifier, version history, evidence of approval, attachments and the finance reference. Specify formats and the relationships that must survive an export.

Add a list of open work. A new operator needs to know which bookings are awaiting a response and which invoices have already been sent. Agree how the final extract will treat changes entered after an initial rehearsal. Decide who can sign off the last reconciliation and when the previous service may be closed.

Hand over the means to operate it

Ask where the domain, hosting subscription, code or licence rights, build instructions, monitoring and support queues sit. Assign an owner and a transfer action to each. A hosted subscription and a custom application have different handover needs. Record any contractual or technical dependency that would stop another team operating the service.

Request an estimate for exit assistance with assumptions about volumes, people and timing. Check the obligations with the organisation’s procurement team. The NZ Government Procurement guide to a procurement plan includes contract management and exit strategy. Use that planning stage to resolve expensive ambiguities.

Make the replacement operator do the rehearsal

Give an authorised colleague who did not build the software the handover pack and an isolated environment. Ask them to locate the example record, read its attachments and identify the next action. For a custom system, include a restore and a routine deployment using the documented process. For a hosted product, test whether the export can be used by the intended receiving system.

Keep a list of anything the original supplier had to explain verbally. Fold those details into the handover and repeat the failed parts. The final acceptance record should name the evidence reviewed, the outstanding dependencies and the person who can authorise closure.

Sources and further reading