Write a user acceptance plan

Control principle

Accept operating outcomes and controlled exceptions, not a polished walkthrough.

The system works in a demonstration, but the nonprofit has not defined who will test real work or what evidence supports acceptance.

Use it in the active phase

Start with these controls

1. Choose representative tasks, roles, accessibility needs, integrations, reports, and failure cases.
2. State the expected result, test data boundary, tester, evidence, severity rule, and retest path.
3. Protect staff time and record defects separately from training or change requests.
4. Require the named authority to accept, defer, or reject with visible evidence.

Pause point

Do not let schedule pressure erase nonprofit ownership

Testing cannot prove every future condition. High-impact workflows may require specialized security, accessibility, financial, clinical, legal, or sector review.