Technology and AI

Choosing practice management software: a buyer's checklist

Questions to put to practice management vendors before you sign: SRA accounts, UK GDPR processor terms, security, client contact, support and exit.

Ava research teamPublished 7 min read

On this page
  1. How to use this checklist
  2. Before you speak to any vendor
  3. Accounts and SRA compliance
  4. Data protection and processor terms
  5. Security, mapped to recognised principles
  6. Client communication features
  7. Support, training and roadmap
  8. AI features and add-ons
  9. Commercial terms
  10. Exit and data portability
  11. Running the selection
  12. Example: spotting red flags in a reply
  13. Frequently asked questions
  14. References

Key takeaways

  • Send vendors written questions before demos so answers can be compared side by side and kept on file.
  • Test SRA accounts features live: five-weekly reconciliations, bill records and accountant's report support.
  • UK GDPR requires a processor contract covering specific terms; ask for the vendor's agreement early, not at signature.
  • Exit terms matter as much as features: insist on a full, documented export of matters, documents, ledgers and logs.

How to use this checklist

Vendor demos are designed to impress. A written checklist sent before the demo changes the conversation: every supplier answers the same questions, you can compare replies side by side, and the answers become part of your due diligence file if a regulator or insurer later asks how you chose the system. Send the questions as a document, ask for written replies within two weeks and score the replies before you watch anything.

The questions below are grouped by risk. Not every firm needs every question; delete the ones that do not apply, but think twice before deleting anything in the accounts, data protection or exit sections.

Before you speak to any vendor

  1. List the practice areas, matter volumes and users you need to support now and in three years.
  2. Write down the five tasks the new system must make faster or safer, with today's rough hours.
  3. Decide who signs off: usually the managing partner, the COFA and whoever will run the system day to day.
  4. Agree a budget range covering licences, migration, training and a period of running both systems.
  5. Choose one anonymised real matter to use as a demo script for every vendor.

Accounts and SRA compliance

The SRA Accounts Rules set the minimum your system must support. Firms must obtain bank statements and complete a reconciliation for all client accounts at least every five weeks, keep accurate, contemporaneous and chronological records, keep a readily accessible central record of bills, and correct any breach promptly on discovery[1]. Ask each vendor to show, not tell:

  • How a three-way reconciliation is produced, and how an unexplained difference is flagged and cleared.
  • How the system prevents a payment from client account that would overdraw a client ledger.
  • Where the central record of bills sits and whether it can be exported for the reporting accountant.
  • How transfers from client to office are linked to a bill or other written notification of costs.
  • Whether audit logs show who posted, edited or reversed every entry, and whether they can be switched off (they should not be).

Data protection and processor terms

A cloud practice management supplier processes client personal data on your behalf, so UK GDPR applies directly to the relationship. Controllers may only use processors that give sufficient guarantees of appropriate technical and organisational measures, and the contract must cover set points, including acting only on documented instructions, confidentiality of staff, security, rules for sub-processors, help with data subject requests, deletion or return of data at the end, and audits[2].

  • Please send your standard data processing agreement and list of sub-processors with their locations.
  • Where is our data stored and backed up, and can we choose the location?
  • How will you notify us of a personal data breach, and how quickly?
  • How do you support subject access requests that need data from matters, emails and call records?
  • What happens to our data, including backups, after the contract ends?

Security, mapped to recognised principles

The National Cyber Security Centre publishes 14 cloud security principles designed to help organisations choose a cloud provider that meets their security needs[3]. You do not need to audit a supplier yourself; use the principles to frame questions and ask for evidence such as certifications or independent test summaries.

Five of the 14 principles most relevant to a small firm's first conversation with a supplier.
NCSC principleQuestion to askGood signRed flag
Data in transit protectionHow is data encrypted between our browsers and your service?Current encryption standards described plainlyVague or marketing-only answer
Separation between customersHow is our data kept apart from other firms' data?Clear technical description and testingNo answer, or reliance on passwords only
Identity and authenticationCan we enforce multi-factor sign-in for every user?Enforced by policy, with single sign-on optionsOptional or extra-cost add-on
Audit information and alertingWhat logs can we see, and for how long?Self-service logs of sign-ins and data accessLogs only on request
Secure user managementHow do we remove a leaver's access immediately?One-step deactivation, reportedRequires a support ticket

Client communication features

Clients use several channels, and the system should record them all against the matter. In the Legal Services Consumer Panel's 2026 tracker, 79% of consumers were happy to meet face to face for an initial meeting, 66% by telephone and 64% by email, while email was the preferred channel for progress updates[4].

Consumers happy to use each channel for a first meeting with a lawyerLegal Services Consumer Panel tracker, 2026
Consumers happy to use each channel for a first meeting with a lawyerBar chart. Face to face: 79%; Telephone: 66%; Email: 64%.Face to faceFace to face: 79%79%TelephoneTelephone: 66%66%EmailEmail: 64%64%Consumers happy to use each channel for a first meeting with a lawyerBar chart. Face to face: 79%; Telephone: 66%; Email: 64%.Face to faceFace to face: 79%79%TelephoneTelephone: 66%66%EmailEmail: 64%64%

Source: Legal Services Consumer Panel, 2026[4]

Show the data
ItemValue
Face to face79%
Telephone66%
Email64%

That matters because communication failures drive complaints: poor communication was the single most common complaint type brought to the Legal Ombudsman in 2025/26, at 24%[5]. Ask whether calls, emails, portal messages and texts are logged in one matter timeline, whether clients can see progress without phoning, and whether supervisors can report on matters with no client contact in the last 30 days.

Support, training and roadmap

  • What are support hours, and what response time applies to a problem stopping a completion?
  • Is training included, and is it delivered live, recorded or both?
  • How often are updates released, and how much notice do you give of changes to screens?
  • Which features on your roadmap are committed, with dates, and which are aspirations?
  • Can we speak to two customers of our size and practice mix, chosen from a list?

AI features and add-ons

Most practice management products now advertise AI features such as matter summaries, drafting help or automatic time capture. They can be useful, but they change the data protection picture, because client information may be sent to another provider to be processed. Ask the vendor to answer these in writing before anyone switches a feature on:

  • Which AI features are switched on by default, and can an administrator turn each one off?
  • Which third parties process our data when an AI feature is used, and are they on your sub-processor list?
  • Is any of our data, including prompts and outputs, used to train or improve models for other customers?
  • Are AI outputs labelled as such in the matter record, and is there a log of who used which feature?

A firm remains responsible for the work produced with these tools, so keep the answers with your AI policy and review them whenever the vendor announces a new feature.

Commercial terms

  • Is pricing per named user, per concurrent user or per fee earner, and how are part-time and support staff counted?
  • Which modules are included, and which features in the demo are extra?
  • What notice is given before price increases at renewal, and is there a cap?
  • Are migration, workflow builds and training fixed-price, or charged by the day?

Exit and data portability

Most firms only think about leaving a system when they are already unhappy with it. By then, the export terms in the contract decide how painful the move will be. Ask now:

  • What formats are matters, documents, ledgers, time entries and audit logs exported in?
  • Is a full export included in the licence, or charged as a project?
  • How long do you keep our data after termination, and can we request deletion with a certificate?
  • Can you provide a sample export from a test account before we sign?

Running the selection

  1. Send the questions

    Issue the checklist to three vendors with a two-week deadline for written answers.

  2. Score the answers

    Mark each section red, amber or green before any demo, so the presentation does not colour your judgement.

  3. Run scripted demos

    Each vendor walks through your anonymised matter, including an accounts reconciliation and an export.

  4. Take references

    Call two firms per vendor and ask what they would do differently.

  5. Negotiate and record

    Fix the processor agreement, exit terms and workflow build costs in the contract, and keep the file with your risk records.

Example: spotting red flags in a reply

Example (fictional): a vendor replies that its data processing agreement is available on request after signature, that exports are available in a proprietary format, and that multi-factor sign-in is planned for next year. Each answer on its own might be negotiable. Together they suggest a supplier that has not sold to many regulated firms. The firm in this example asks for the agreement and a sample export before going further; when neither arrives within the deadline, it drops the vendor from the shortlist and saves a demo afternoon.

For background on the types of system you are likely to compare, see case management systems for UK firms compared, and for hosting choices read cloud vs on-premise legal software. The accounts questions above are expanded in legal accounting software and the SRA Accounts Rules.

Frequently asked questions

What should I ask a practice management software vendor?

Ask about SRA accounts features, the processor agreement and sub-processors, data location, multi-factor sign-in, audit logs, support hours, roadmap commitments and how you get a full export of your data if you leave.

Do I need a data processing agreement with my software supplier?

Yes. Where a supplier processes personal data for you, UK GDPR requires a written contract with specific terms, including acting on your instructions, security, sub-processor rules and returning or deleting data at the end.

How many vendors should we invite to demo?

Usually three. Score their written answers first and only book demos with vendors whose answers on accounts, data protection and exit are acceptable.

Should the COFA be involved in choosing software?

Yes, where the system handles client money or accounts. The COFA should test reconciliation and bill record features before the firm commits.

References

  1. Solicitors Regulation Authority (2019). SRA Accounts Rules (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 28: Processor (opens in a new tab) ↑

  3. National Cyber Security Centre (2025). The cloud security principles (opens in a new tab) ↑

  4. Legal Services Consumer Panel (2026). How consumers are using legal services (Tracker Survey 2026) (opens in a new tab) ↑

  5. Legal Ombudsman (2026). Legal Ombudsman 2025/26 annual complaints data and insight (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo