How to choose practice management software for a UAE law firm

The short version

Choosing a system is less about features and more about whether your team will still be using it properly a year from now. Before you sign anything, make sure you can answer yes to each of these:

1. We listed the ten jobs the firm does every week and saw each one done in the product.
2. We know where every category of our data will be stored, and who can reach it.
3. We moved a real sample of our files in, and we know how we would get everything out again.
4. Our courts, working week, currency and VAT behave correctly without workarounds.
5. Arabic-speaking staff tried the Arabic screens and documents themselves.
6. People finished real tasks during the trial, not just logged in.
7. We ran five realistic scenarios end to end and wrote down what happened.
8. We compared the full cost over three years, not the monthly headline.

This guide is general information for firms evaluating software, not legal or procurement advice. It was last reviewed on 14 November 2026. Check current regulations, such as data protection and e-invoicing rules, against official sources like UAE Legislation.

1. Start from the work, not the feature list

Feature lists are written to look complete. Your firm's week is more specific: a new enquiry arrives by WhatsApp, a conflict check runs, an engagement letter goes out, a hearing is adjourned, time is recorded, an invoice is issued in AED with VAT, a payment arrives in part.

Write those jobs down in the order they happen and name who does each one. Then ask every vendor to show those exact jobs, in that order, using their product rather than slides. Anything they cannot show live should be treated as not yet available.

2. Draw the data map before talking about compliance

"We are compliant" is not an answer you can check. A data map is. For each type of information the firm holds, client identity documents, matter files, emails, invoices, backups and AI requests, ask where it is stored, which company stores it, and in which country.

Pay particular attention to features that send data elsewhere: AI assistants, translation, email delivery, e-signature and calendar sync. These are often where data leaves the main hosting region.

Questions to ask in writing

• Where are the application, the database, uploaded files and backups hosted, and by whom?
• Which features send data to another provider or another country, and what exactly is sent?
• Do any providers train models on our data?
• Who on your side can access our data, and is that access logged?
• How often are backups taken, and when was a restore last tested?
• What happens to our data if we stop paying?

3. Test migration and your future exit at the same time

Moving in and moving out are the same question seen from two sides. Give the vendor a real sample: a few closed matters, a few active ones with documents, and a client with several invoices and part payments. Check what arrives, what is lost and what is mangled, especially Arabic names and dates.

Then ask for an export of that same sample. You should get your records in a format you can open without the vendor, with documents attached and links between clients, matters and invoices intact. If the export is a support ticket rather than a button, write that down.

4. Define what "built for UAE firms" means to you

Most vendors in the region say their product is made for local firms. Turn that into checks you can run:

• The court structure you appear before (local courts, federal courts, DIFC or ADGM) is modelled, including stages from first instance to execution.
• The working week and public holidays are correct when deadlines are calculated.
• Invoices show AED and 5% VAT correctly, and can be issued in a second currency when a client needs it.
• Hijri dates appear where your documents need them.
• The vendor has a plan for the UAE's e-invoicing programme and can explain it.

5. Test the Arabic yourself

A translated menu is not an Arabic product. Ask the colleagues who work in Arabic to try it for an afternoon. They should check that the whole screen turns right to left, that Arabic names sort and search correctly, that documents and PDFs come out shaped properly, and that numbers stay readable.

Also check whether the language is chosen per person. In many firms a partner works in Arabic and an associate in English on the same matter, and both should be comfortable.

6. Measure adoption by completed tasks

Logins tell you very little. During any trial, count finished work instead: matters opened, hearings entered, hours recorded, invoices issued, documents filed against the right matter. If those numbers stay low after the first two weeks, the problem will not fix itself after you pay.

Ask who will train your people, in which language, and what happens when someone joins the firm next year.

7. Use a five-scenario pilot

A short, structured pilot shows more than a long, unstructured one. Run these five scenarios with real people and note who did what and how long it took.

New enquiry

A prospective client calls about a dispute. Record the enquiry, run a conflict check against existing clients and opponents, and send an engagement letter.

Active matter

A hearing notice arrives. Enter the next session, assign the lawyer, file the notice against the case and let the client know what happens next.

Billing

Turn recorded time and a court fee into an invoice with VAT, send it, and record a partial payment. Check what the client sees and what the accountant sees.

Permission check

Sign in as a junior team member and try to open a matter they are not on, a salary figure and a partner-only report. The system should refuse, and the attempt should be visible to someone who needs to know.

Management view

As a partner, find out what is unbilled, what is overdue, which hearings are coming this week and who is overloaded, without exporting anything to a spreadsheet.

8. Score the evidence and compare total cost

After the pilot, score each vendor only on what you saw working, not on what was promised. A feature on a roadmap scores zero until it ships.

Then compare cost over three years for your real headcount. Include setup, data migration, training, storage, AI usage, integrations, support plans and the price of leaving. A low monthly price per user can hide a large setup invoice or a higher tier you will need for basic reports.