User acceptance testing (UAT) is when the people who’ll use a system every day test it before it goes live. For a Litify project, that means your staff work through real scenarios in a test copy of your new system and confirm it does what your firm needs.
It’s one of the most important parts of the project, and one of the easiest to underestimate. This guide explains how it works and how to do it well.
Why your staff’s testing matters
Your implementation team tests every feature before you see it. But only your staff know whether the system truly fits the way your firm works: whether the intake questions make sense, whether a matter moves through its stages the way it should, and whether the reports answer the questions leadership asks. UAT is where that knowledge shapes the final system.
How UAT is usually organized
- Testing happens in a sandbox, a separate copy of your system, so nothing affects real work. (See Salesforce sandbox types explained.)
- Work is grouped into releases, so your team tests one area at a time instead of everything at once.
- Each area has test scenarios describing what to do and what should happen, written from the point of view of the people doing the work.
- Testers record results for each scenario: passed, failed, or needs discussion.
How to test well
- Follow the scenario, then go off script. Complete each step as written, then try the variations you see in real life.
- Use realistic examples. Test with the kinds of matters, clients, and documents your team handles every day.
- Test as yourself. Log in with your own role, so you see what you’ll actually see after go-live.
- Check the whole flow. Don’t stop at one screen. Follow a record from beginning to end.
- Block the time. Put testing on your calendar like any other deadline. UAT is where most project schedules slip.
How to report an issue
A clear report gets fixed faster. Include:
- What you were doing, step by step.
- What you expected to happen.
- What actually happened, with a screenshot if possible.
- Which record you were working in.
- How much it matters: does it stop work, slow work, or is it a nice-to-have?
Bug or change?
Not every issue is a defect. If something doesn’t work as designed, it’s a bug and will be fixed. If it works as designed but the design doesn’t fit, it may be a change. That’s fine too. Changes are discussed, estimated, and prioritized, and some are saved for a later phase. Our guide to understanding change requests explains how that works.
When is UAT done?
Testing is complete when every scenario has been tested, must-fix issues are resolved, and your firm is confident the system is ready. That confidence is part of the go-live decision. See our Litify go-live checklist for what comes next.
Frequently asked questions
What is user acceptance testing?
User acceptance testing is when the people who will use a system test it with real scenarios before go-live, to confirm it meets their needs.
Who should do UAT on a Litify project?
Staff who do the work every day, such as intake specialists, paralegals, attorneys, and managers, should test the areas they use.
How do I report a UAT issue?
Describe what you were doing, what you expected, what actually happened, which record you were in, and how much the issue affects your work, with a screenshot if possible.
