How to choose law practice management software
How to choose law practice management software: list the work your firm does every week, turn it into ten weighted criteria, and test the systems on your short list on your own matters before you sign. This guide gives each criterion with why it matters, how to test it and the warning sign to watch for, the figures to ask for in writing, and a scoring sheet you can copy.
This guide is written by jaah, which makes law practice management software. It names no other product, and the part about jaah law stands apart at the end. Every figure links to the page of the organisation that published it.
The short answer, by type of firm
- A lawyer working alone: fit with your own day comes first, with deadlines, hearings and invoices in one place, usable on a phone, and little to set up.
- A small firm: add access rights for each person, one calendar of hearings for the team, and invoices issued from the files.
- A larger firm: give more weight to security, the history of changes, reports, and the way data comes in from your current system.
- An in-house legal department: look for requests from the business, contract tracking and reports for management; billing matters less.
Ten criteria for law practice management software
Give each criterion its weight before you see any demonstration, so that no demonstration sets the weights for you.
1. Fit with the work your firm does
Software earns its cost only when the files you open every day live in it: client requests, consultations, cases and hearings, contracts, enforcement files, deadlines and invoices. ISO/IEC 25010:2023, the international model of software product quality, calls this functional suitability, one of the nine characteristics of its model.
- How to test it: take three real matters from last month, with their dates and documents, and enter them from start to finish yourselves, not the vendor.
- Warning sign: every gap is answered with "we can build that later", or the demonstration uses only the vendor's own sample data.
2. Security of client information
A firm holds information its clients trust it with, and the cost of losing it is measured: in their Cost of a Data Breach Report 2026, IBM and the Ponemon Institute put the average cost of a data breach worldwide at 4.99 million US dollars, 12% more than a year earlier.
Sign-in is the first defence. In a 2023 study of Microsoft cloud accounts, a second sign-in step reduced the risk of an account being taken over by 99.22%, and by 98.56% when the password had already leaked. NIST SP 800-63B-4, the US federal guideline on sign-in, describes how strong each such method is.
If the software offers AI features, ask what client data they send, where, and whether it is used to train models. The American Bar Association's Formal Opinion 512 of 2024 asks lawyers to understand such tools, protect client confidentiality and check what the tools produce.
- How to test it: turn on the second sign-in step for every user; sign in as a junior employee and try to open a file kept for partners; open the history of a record and check that it shows who changed what, and when.
- Warning sign: shared logins, no history of changes, or security described only as "bank-level", with nothing in writing.
3. Where the data lives and who can reach it
The UK National Cyber Security Centre publishes 14 cloud security principles to help buyers choose a cloud provider. Among them are the protection of data in transit, the separation between customers, and the protection of the provider's own administration of the service.
- How to test it: ask in writing where the data is stored, which companies process it for the vendor, how one customer's data is kept apart from another's, and whether every connection uses TLS 1.2 or later, the version that NIST SP 800-52 Rev. 2 requires of US government systems.
- Warning sign: no written answer, or a country of storage the vendor cannot name.
4. Availability, backups and recovery
An availability figure is a budget of downtime. The table turns each common figure into the downtime it still allows.
| Availability | Downtime per year, in hours | Downtime per month, in minutes |
|---|---|---|
| 99% | 87.6 | 438 |
| 99.5% | 43.8 | 219 |
| 99.9% | 8.76 | 43.8 |
| 99.95% | 4.38 | 21.9 |
| 99.99% | 0.88 | 4.4 |
Two more numbers matter when something goes wrong: the recovery point objective, which is how much recent work may be lost, and the recovery time objective, which is how long the service may stay down. Backups that can be restored matter more each year: Verizon's 2026 Data Breach Investigations Report finds ransomware in 48% of breaches.
- How to test it: ask for the availability figure in the contract and what you receive when it is missed, how often backups run, where they are kept, and when the vendor last restored one.
- Warning sign: an availability promise with no remedy, or backups that have never been restored.
5. Updates and security fixes
The same Verizon report finds that 31% of breaches now start with a software vulnerability, ahead of stolen passwords. How fast fixes reach your system matters as much as the features it has.
- How to test it: ask who applies updates and how often, whether you must install anything on a server or a computer, and where the record of each release is published.
- Warning sign: updates that the firm must install itself, or no record of what changed.
6. Your data, and leaving with it
On the day you change software, your files must leave with you, in formats that other programs open.
- How to test it: during the test, export a client's full file and a list of matters to a spreadsheet, print a matter's documents to PDF, and check that the contract says the data is yours and how it is returned at the end.
- Warning sign: export only as a paid service, or in a format that no other program reads.
7. One system, or many joined together
Each tool that does not share the client's record means typing the same name, number and date twice, then checking which copy is right.
- How to test it: import your current list of clients from a spreadsheet, then follow one client from the first request to the invoice without typing anything again.
- Warning sign: connections that exist only on a plan for later, or that cost extra one by one.
8. Billing and the firm's finances
Work that is not invoiced from its file is easily forgotten. Where the law requires electronic invoices, the software must issue them in the format the tax authority asks for. Where the rules require client money to be held in a trust account, the software must keep that ledger apart from the firm's own.
- How to test it: issue an invoice from a case and from a contract instalment, register a payment, and find the amount still due on the client's file.
- Warning sign: invoices typed again in a separate accounting program.
9. Ease of use, languages and phones
A system the team avoids holds records that are out of date. ISO/IEC 25010 treats ease of use as a quality characteristic of its own. Check the languages your team and your clients read, on screen and in printed documents, and every screen on a phone.
- How to test it: ask the least technical person in the firm to record a hearing or a consultation without help, on a computer and on a phone.
- Warning sign: training sold by the hour as the only way in, or no written user guide.
10. Total cost and the vendor behind it
The subscription is one line of the cost. Add the setup, moving the data in, training, add-ons and your team's time, over three years.
- How to test it: ask for a written quote for your exact number of users and apps, the notice period, how prices may change, the support hours and response times, and two firms of your size you may call.
- Warning sign: a price given only after a sales call, or essential features sold separately.
How to run the selection
- Map the work: who opens which file, which deadlines it carries, and what you print and send.
- Write the requirements, mark those you cannot do without, and weight the ten criteria on the sheet below.
- Keep a short list of three systems at most.
- Send each vendor the same scenarios, and ask to see those rather than a prepared tour.
- Test the two systems that came out ahead in the demonstrations, with the people who will use them, on your own matters.
- Review security and the contract: the questions of criteria 2 to 6, answered in writing.
- Score, decide, then plan the move: the data, the training, and the date the old system stops.
A weighted scoring sheet
After the test, score each system from 1 to 5 on each criterion. Multiply each score by its weight, add the results and divide by 5: the total is out of 100. The weights below suit a small firm; move them to match yours, keeping their sum at 100.
| Criterion | Weight |
|---|---|
| 1. Fit with the work your firm does | 20 |
| 2. Security of client information | 15 |
| 3. Where the data lives and who can reach it | 10 |
| 4. Availability, backups and recovery | 10 |
| 5. Updates and security fixes | 5 |
| 6. Your data, and leaving with it | 10 |
| 7. One system, or many joined together | 5 |
| 8. Billing and the firm's finances | 10 |
| 9. Ease of use, languages and phones | 10 |
| 10. Total cost and the vendor behind it | 5 |
For example, a system that scores 4 on the first criterion adds 20 × 4 ÷ 5 = 16 points to its total.
Types of solutions compared
| Type | Updates and security fixes | Work away from the office | Fit for legal work | Main risk |
|---|---|---|---|---|
| Cloud practice management software | Applied by the vendor | In a browser and on a phone | Built for files, hearings and deadlines | Rests on the vendor's security and contract |
| Software installed on the firm's own server | Applied by the firm | Needs a remote connection set up | Built for legal work | The firm carries backups, updates and hardware |
| A general business system adapted | Depends on who runs it | Usually in a browser | Legal files must be built and kept up | Custom work that only one supplier knows |
| Spreadsheets and shared folders | None to apply | Wherever the files are shared | No deadlines, access rights or history | Lost versions, and no record of who changed what |
How jaah law answers these criteria
This part is about our own product; each line states a fact of the product itself.
- Client requests, consultations, cases, contracts, enforcement files, powers of attorney and invoices in one system.
- Access rights for each legal app (read only, own files, or every file), and the legal records log their changes.
- A second sign-in step, a code sent by WhatsApp after the password, which the firm turns on.
- A database of its own for each firm.
- jaah runs each system and applies its updates: the firm installs nothing on a server or a computer.
- Deleted records go to a recycle bin, where they can be restored for 30 days by default.
- Records come in from spreadsheet files.
- A user given the export right exports any list to an Excel or CSV file.
- Invoices are issued from cases, consultations, enforcement files and contract instalments.
- The same data and access rights in a phone's browser.
- A user guide for the legal apps.
Which apps each plan includes is on the pricing page, and every app is described on the law firm management software page.
When jaah law is not the right choice
- You need the software to file at court: jaah law records hearings, judgments and decisions, and it is not connected to a court system.
- You must keep client money in a trust account: jaah law keeps no trust ledger apart from the firm's own accounts.
- You bill by the hour from timesheets: jaah law logs hours on each file, but its invoices are amounts, not hourly bills.
Questions about choosing law practice management software
What matters most when choosing law practice management software?
Fit with the work your firm does every week, then the security of client information. Weight both before any demonstration, and score every system on the same sheet.
Is cloud software or software on our own server better for a law firm?
Cloud software leaves updates, backups and remote access to the vendor; software on your own server keeps them with you, with the staff and hardware they need. Decide on the vendor's written answers about storage, separation and recovery.
How should a firm test software before buying it?
With the people who will use it, on three real matters from last month, entered from start to finish on a computer and on a phone. Ask the vendor to show your scenarios, not a prepared tour.
What should we ask a vendor about security?
Where the data is stored and who processes it, how customers are kept apart, whether sign-in has a second step, how changes are logged, how often backups run and when one was last restored, and how fast security fixes are applied.
Can we move our existing data into a new system?
Usually through spreadsheet files: export your clients and matters from the current system, import them during the test, and check a sample of records. Ask who does the move and what it includes.
Should law firm software include AI features?
Only once you know what client data they send, where, and whether it is used to train models. The American Bar Association's Formal Opinion 512 asks lawyers to understand such tools, protect client confidentiality and check what the tools produce.
Sources
- IBM and the Ponemon Institute, Cost of a Data Breach Report (2026)
- Verizon, Data Breach Investigations Report (2026)
- Meyer and others, How effective is multifactor authentication at deterring cyberattacks? (2023)
- UK National Cyber Security Centre, the cloud security principles (2023)
- NIST SP 800-63B-4, Authentication and Authenticator Management (2025)
- NIST SP 800-52 Rev. 2, Guidelines for TLS Implementations (2019)
- ISO/IEC 25010:2023, Product quality model (2023)
- American Bar Association, Formal Opinion 512, Generative Artificial Intelligence Tools (2024)
Each source was read on its publisher's own page on 6 November 2026. General information, not legal advice.