User acceptance testing and sign-off
You will be able to: Plan and run UAT with the client's key users; Triage defects daily and retest fixes; Obtain a meaningful UAT sign-off.
- Read not done yet
- Self-check: not taken not done yet
- Lesson complete not done yet
User acceptance testing (UAT) is where the business, not the consultant, confirms that the system supports daily work. The consultant prepares and supports, but the client's key users execute the scripts with their own judgement.
A five-day UAT plan
| Day | Focus | People |
|---|---|---|
| 1 | Briefing, access check, sales scripts | Sales manager, reps, accountant |
| 2 | Purchase and stock scripts | Purchasing manager, storekeepers |
| 3 | Finance, VAT, bank and role tests | Accountant, finance manager |
| 4 | Free-play with real examples, outputs and printing | All key users |
| 5 | Retest of fixes, results review, sign-off meeting | Sponsor and process owners |
Running it
- Check entry criteria: configuration frozen, test users created, migration rehearsal reconciled.
- Brief the testers: how to run a script, how to log a defect, what counts as Pass.
- Hold a 15-minute triage every morning. Classify each defect as a bug, a configuration issue, a training issue or a change request.
- Fix and retest. Retest the failed script and a few related ones to catch side effects (regression).
- Close with a results review and the sign-off meeting.
The sign-off
The UAT sign-off form states: scripts executed and passed, open defects with severity and agreed date, the statement that the system is accepted for go-live subject to the listed items, and signatures of the sponsor, finance lead and process owners. Sign-off does not mean the system is perfect. It means the business accepts the known state.
Some clients ask for a parallel run, entering real transactions in both the old and the new system for a short time. It doubles the work and often hides problems, so use it only for a limited high-risk process, such as the first month-end close, and agree an end date in advance.
Practise in the demo
- Plan a UAT week for six key users and list the scripts per day.
- In the demo, practise logging a defect: write the title, steps, expected and actual result, and severity.
- Open https://demo.zeyto.app/demo-app/ and sign in with the demo login. This is a public demo with sample data, so nothing you do there affects a real business.
Public demo company, sign in as admin / demoAdmin123. Data refreshes nightly.
- The client's key users execute UAT; the consultant supports.
- Triage daily and retest fixes with a few related scripts.
- Sign-off records the known state, including accepted open items.
Check yourself
4 questions on this lesson. Not timed, not the exam, and you can try again. Score 60% or more, and read the lesson, to complete it.