Skip to content

Version 1.0 · November 2026

Go-Live Gate Checklist

The conditions an AI system should meet before it enters live operations.

Get the file
Format
PDF · A4 · Arabic and English
Practices
  • Operations re-engineering
  • Governance & regulatory readiness
  • Data, platforms & sourcing

Who it's for

Business owners, IT and risk teams preparing a go-live decision.

What's inside

  • A named person accountable on the business side, and a support model
  • A fallback path for when the system is wrong or down
  • Tests on real cases, in Arabic and English, in the production hosting setup
  • Data, hosting and risk class confirmed against PDPL, NCA controls and SDAIA's principles
  • Audit log, error reporting and a first review date
  • Baseline recorded, cost per transaction known, first value report scheduled

Print it, or fill it in on screen.

Where should we send it?

We'll email you the download link.

How to use it

  1. Open it at the start of Lead the build.
  2. Name the person accountable on the business side, the support model and the fallback path.
  3. Test real Arabic and English cases in production hosting.
  4. Confirm data, hosting and risk class with legal and security.
  5. Record baseline and cost per transaction, book the value report, sign.

Where it fits in the Live Path

Lead the build

The Live Path
More detail

Why each step

  1. Start early, not the week before launch, so every condition has an owner and a date. Conditions found late, such as an unsigned support contract or an untested fallback, are what push launch dates.
  2. The fallback is usually the manual process the system replaces. Keep it documented and staffed for the first weeks.
  3. Keep the results. Include the hard cases: scanned documents, messages that mix the two languages, dialect and incomplete records.
  4. Check them against PDPL, NCA controls and SDAIA's principles. Record who confirmed each item and on what date, so the evidence is ready if an auditor asks.
  5. If a condition is not met, write down the decision: continue with a dated fix, change course, or stop.

Where it fits in the Live Path

Gate: The Go-Live Gate Checklist, signed.

The checklist is the gate at the end of Lead the build. A system that has not met every condition does not enter live operations: you continue, change course or stop. Use it for any AI system that will touch live data, customers or decisions, including a vendor product switched on inside a system you already run. For a contained internal pilot, use it as a planning list instead: it shows early what the pilot will need before it can go live. Signing it is a joint decision of the person accountable on the business side, IT and risk, not a formality at the end of the project.

Read with: Arabic AI today: what works and what to check

All tools
  • Result on screen · report by email

    AI Readiness Check

    Eighteen questions in six areas, built on SDAIA's National AI Index, NCA's controls and the PDPL. See where you stand and your next three steps.

    Interactive web tool

  • Workflow Redesign Canvas

    One page to redesign a workflow around AI, starting from the approval chain and delegation of authority.

    PDF · A3 landscape · Arabic and English

  • AI Value Ledger

    A spreadsheet that ties each AI use case to a baseline, a KPI line and value signed off by finance.

    XLSX

Want help using these tools on your own initiatives?