About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Go-live decisions fail when "we tested it" means three admins logged in. User acceptance testing (UAT) scripts are short, repeatable business tasks — create a sale, approve a quote, post a journal, scan a referral — executed by real role holders on the hosted environment with pass/fail criteria. They translate migration risk into evidence sponsors can sign.
Material difference from published coverage: Acceptance criteria before decommissioning the old system after migration focuses on tear-down gates and owner checklists. Designing a pilot that actually predicts production migration risk covers who samples the system and pilot success criteria. This article's contribution is a worked script template: rows with role, preconditions, steps and pass criteria, explicit negative-path rules scoped to role and tenant boundaries, and sponsor sign-off before cutover — not decommission law, pilot sizing or pilot statistics. Pair scripts with the business acceptance decision step in Migration cutover runbook: lag, DNS TTL and rollback.
Why it matters
Hosted cutover hides dependencies until the person who does the task daily tries it. Scripts force those people onto the path early. They also define rollback triggers: if task seven fails at 02:00, the sponsor knows whether that failure blocks revenue on Monday.
Named scenarios with expected results echo exercise-planning discipline described in NIST SP 800-84 (guide to test, training and exercise programmes for IT plans). This article does not claim NIST or ISO compliance — it adopts the pattern as editorial practice only.
How it works
Each script row should include:
- Role (accounts payable clerk, not "IT").
- Preconditions (test user, test company file, sample PDF).
- Steps in business language, not SQL.
- Expected result observable without log access.
- Evidence (screenshot ref, document number, ticket id).
- Owner sign-off.
Example skeleton (illustrative only — caption):
| ID | Task | Role | Pass criteria (examples) | Evidence (examples) |
|---|---|---|---|---|
| UAT-01 | Morning login from home NBN | Standard user | MFA completes; hosted app opens within agreed time | Screenshot of session |
| UAT-02 | Raise invoice for synthetic company and email PDF | AR clerk | PDF prints; nominated test recipient receives email (not a live customer) | Invoice number; mail trace |
| UAT-03 | Import scanned mail batch | Mailroom | All pages attached to correct matter | DMS reference |
Include negative paths with explicit coverage limits: test actions that should fail for the wrong role or tenant boundary, record the expected denial, and note what the script does not prove (for example, one permission-denied case does not demonstrate that authorisation is not broadly excessive). Document rules in the script version, not only the happy path.
Run scripts on the same access channel production will use. Clipboard, drive and printer redirection notes that browser client printing is not equivalent to native redirection — align channel choice with your print/UAT rows. Re-run after dress rehearsal data refresh.
What to choose and why
Choose ten must-pass tasks for wave-one cutover; add nice-to-have tasks separately so scope creep does not block signing (expand to twenty only with sponsor agreement).
Choose business owners as executors; IT facilitates. Editorial view: IT-only UAT proves hosting health, not business readiness.
Choose dated script versions when configuration changes; stale scripts that reference retired menus waste cutover night.
Read next
Related articles you may want next.
- HostingAcceptance criteria before decommissioning the old system after migrationWhat evidence the migration board needs before the predecessor environment is powered down — distinct from RPO/RTO proof drills and from cutover-night technical gates.Read article
- HostingDesigning a pilot that actually predicts production migration riskHow to choose pilot users, workloads and success measures so a green pilot is not a false signal before production cutover.Read article
- HostingClipboard, drive and printer redirection: choose the channels users needA practical policy and pilot checklist for RDP clipboard, local files and printers, including restrictive-setting precedence and client-specific support.Read article
Risks and limits
Synthetic data gaps. Tasks needing regulated patient or financial data may require anonymised fixtures; legal review is customer responsibility.
Parallel-run confusion. If old and new both exist, scripts must state which environment is authoritative for each run.
Not decommission gates. Acceptance before tearing down the old system is a related published topic with different legal weight.
No lab run. Scripts here are templates; execution is customer responsibility.
Sources
- Editorial: organisational UAT script template for hosted cutover (role/preconditions/steps rows and negative-path rules).
- NIST SP 800-84 — Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities — exercise-planning vocabulary (catalogue abstract; not quoted).
- Migration cutover runbook: lag, DNS TTL and rollback — business acceptance gate.
- Clipboard, drive and printer redirection — browser versus native client behaviour.
Learning notes
- UAT scripts are business tasks with pass/fail criteria and evidence, not admin checklists.
- Editorial view: a small set of signed tasks beats many undocumented logins.
- Use the same client and network path as production.
- Business owners execute; IT enables.
- Failed tasks need explicit go/no-go rules.
This article was originally published on .