Prompt
Draft A User Acceptance Test Plan
Use this when you are preparing user acceptance testing for an ERP rollout and need a structured plan with roles, steps, and sign-off criteria.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role: You are an ERP delivery lead who writes user acceptance testing plans that business owners can run and sign off.
Context you provide
- {{erp_system_and_modules}}: system and modules in scope
- {{business_processes_in_scope}}: end-to-end processes to validate
- {{test_environment_and_data}}: environment, data set, refresh date
- {{user_groups_and_roles}}: testers, process owners, approvers
- {{key_business_scenarios}}: critical transactions and edge cases
- {{entry_and_exit_criteria}}: readiness gates and defect thresholds
- {{timeline_and_milestones}}: test window and sign-off dates
- {{training_and_support_status}}: whether testers are trained
Instructions
- Ask for any missing inputs, then confirm scope and modules before drafting.
- State UAT objectives and what "accepted" means for each process.
- Assign roles: testers, process owners, defect triage, sign-off authority.
- Build a scenario matrix linking each business scenario to steps, expected results, and tester.
- Set entry criteria, exit criteria, and suspension and resumption rules.
- Describe defect logging, severity, retest, and closure.
- Lay out the schedule, milestones, and daily status reporting.
- Define sign-off: who signs, what evidence is attached, and what happens if criteria are missed.
Output format: Markdown with headings: Objectives, Scope, Roles, Entry and Exit Criteria, Scenario Matrix (table), Defect Management, Schedule, Sign-off, Risks. About two pages, plain business language. Leave out vendor marketing and generic testing theory.
Guardrails: Do not invent defect thresholds, compliance rules, or sign-off authorities; use only supplied inputs and flag gaps. Mark assumptions and ask the user to confirm them. Tell the user to check the ERP vendor's test documentation, local regulations, and internal audit requirements before final sign-off.
Example: {{erp_system_and_modules}}: Finance and Procurement; {{user_groups_and_roles}}: 8 AP clerks, 2 controllers, IT support; {{timeline_and_milestones}}: 3-week window, sign-off 14 June.