What you need to know

Make the assumptions explicit, ask for evidence and test the handover. A buying decision is easier to defend when the trade-offs are written down.

01

Start with applicability

These frameworks have different scopes. Establish which obligations apply to your organisation and service before turning them into contract language.[2]

02

Ask for an operational exit plan

Require named responsibilities, a transition schedule and usable data-return formats. Have qualified counsel verify the applicable switching and resilience obligations.[2]

03

Test continuity

Identify critical functions and the dependencies that could interrupt them. Agree how evidence of continuity and exit testing will be provided.[2]

Your vendor checklist

  • Record the metering unit and the maximum commitment.
  • Test access, review and recovery with your own use case.
  • Open the export in another environment.
  • Get the transition obligations in writing.
  • Agree a date to review the evidence again.
Put the guide into practice →

More field guides

Sources & assumptions

  1. App Build Index sample research model, 14 October 2026. Prices and scores illustrate the interface and are not verified vendor offers.
  2. European Commission · AI Act framework. Reviewed 14 October 2026. Apply the rules to your exact use case with qualified advice.