For ERP Implementation Consultants ·
What you'll accomplish
Every UAT test script currently starts from a blank page, and the format drifts depending on who wrote it last. Set up a Claude Project once with your test script template and a few already-approved scripts as reference, and every new script comes back in the same format without you re-explaining it each time.
What you'll need
Gather the test script template and two or three approved scripts from the module you're working in. Replace the client's company name, real customer or vendor names, and any approval thresholds tied to a specific client with generic placeholders (Client Co, Vendor A, a round approval limit). Process design documents and approved test scripts are confidential client deliverables under the engagement's NDA, so check the client's AI policy before uploading anything more specific than that, and use fabricated examples for anything the policy does not clearly cover.
What you should see: An empty project workspace with a place to add instructions and files.
What you should see: Your files listed in the project's knowledge panel, with a capacity bar showing how much of the project's space they use.
Troubleshooting: If the capacity bar fills up fast, trim sample scripts down to one or two representative pages each rather than uploading a full module's worth. A project holds roughly 500 pages, but shorter, focused reference files produce more consistent output than a large pile of loosely related ones.
In the project's instructions panel, click the edit icon and add something like:
You are drafting UAT test scripts for an ERP implementation. Match the format of the approved scripts in this project's knowledge base exactly: numbered steps, an action column, an expected result column, and a pass/fail field. Use the process design document I paste in as the source of truth for what the process actually does. If a step in the process design document is ambiguous, flag it as an open question instead of guessing.
Save the instructions.
Paste in the process design document for your next process and ask for a draft script.
Example prompt to copy-paste:
Using the same format as the approved scripts in this project, draft a UAT test script for the three-way match exception process described here: [paste process design document text or summary].
What good output looks like: A numbered script that mirrors your approved examples step for step in structure, with every action tied to something the process design document actually describes.
Draft a UAT test script for [process name] using the same format as the approved scripts in this project.Add three negative test cases to this script: what happens when [specific failure condition]?Check this draft script against the process design document and flag any step that isn't actually described there.Convert this script into a row-by-row tracker format with columns for tester name, date, and pass/fail.This module has five process variants. List them from the process design document and then draft one script per variant using the approved format.