rokan.

What should be on a go-live checklist for an AI agent?

An AI agent go-live checklist covers the access requests on day 1, an owner for the security review, DPA and BAA, an export of past calls or tickets, a written replay pass bar, shadow mode, a 10%, 50%, 100% rollout with an approver for each step, and a fallback drill and a kill-switch drill. After launch, it adds a 30-day watch.

Updated · No sign-up · Ticks stay on this page and are not saved or sent

AI agent go-live checklist

rokan.computer/golive/checklist

01 Day 1: access requests

Send all of them the day the contract is signed. Approvals are the long pole.

02 Paperwork owners

Name one owner on each side for each item.

03 History export

Test on what really happened at this customer, not on made-up cases.

04 Replay pass bar

Agree it before the first run, so launch isn’t argued after.

05 Shadow mode

Real traffic, zero risk: the agent drafts, people act.

06 10% → 50% → 100%

Move up only when the checks pass and the approver says go.

07 Fallback drill

A fallback nobody has called is not a fallback.

08 Kill-switch drill

One action sends new traffic back to today’s route.

09 30-day watch

Most breakage comes from changes around the agent, not the agent.

Markdown version

How to use it

  • Print it the day the contract is signed. Use your browser’s print dialog; it fits one page on Letter or A4. Choose “Save as PDF” to share it.
  • Fill in the blanks with names, not teams. “Security will handle it” is how a go-live waits three weeks.
  • Don’t skip the drills. The fallback and the kill switch are what let the customer say yes to 10%.

Where each item comes from

Every line maps to a risk in Rokan’s risk catalog, which is checked by hand against vendor documentation. The reasons, with sources, are in the guides: where the weeks go, Salesforce access, Epic and athenahealth, consent and disclosure and staged rollout.