TRUST ATLAS WORKSHEET
Exit plans
EU Data Act · Step 3 · Make cloud switching work in practice- Who prepares it
- Cloud operations + contracts
- When to prepare it
- Before relying on standard contract terms
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Purpose
- Identify failed production backup jobs and restore service data.
- Scope
- Production billing databases and backup vault
- Activity and timing
- On-call reviews daily job alerts and runs a quarterly restore test.
- Evidence and exception
- Keep job records and restore test output. Page the service owner if a job fails.
- Owner and approval
- Operations lead owns. Service owner approves.
Gather first
- Approved scope
- Governing requirements and risks
- Teams, service dependencies and review gates
How to prepare it
- State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
- For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
- Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.
Review
A person who receives the plan can tell when to act, what to check and where to save the result.
Handoff
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.