Choose the law firm management system that matches the way your office works in Qatar, not the one with the longest list of features. Test it on files drawn from your office’s real work: a case through its degrees before the Qatari judicial bodies, an adjourned hearing, a judgment with an appeal deadline and a receipt voucher in Qatari riyals; then ask plainly about permissions, data isolation and the pricing model before you decide.
9-minute readLast updated: The Murafe team
Key takeaways
Write down your office’s real scenarios before any demo, and judge every system on them, not on its ready-made presentation.
Genuine Arabic shows in the details: entering dates, searching, printouts and amounts in words.
Qatari litigation degrees, courts and bodies under their official names, and appeal deadlines you can review are the core of daily work, not side details.
Ask frankly how your office’s data is isolated and backed up, and who can access it.
Read the pricing model in full: users, modules, storage, setup, data migration and training.
Before the demo: write down how your office works
The best way to choose law firm management software is to start from your office, not from the features brochure. Write down on a single page how work runs today: who receives the client, who registers the case, who attends hearings, who collects fees and issues vouchers, and how the client finds out what has happened in their case. Then write down the three problems that come up most often in your office: a hearing whose decision was forgotten, an instalment nobody chased, a document that could not be found in time. This page is the yardstick you measure every system against, so that you are not dazzled by a feature you will never use or blind to a need that comes up every day. Then turn it into short scenarios you ask to see carried out in front of you:
Register a case with two clients and one opponent, before a body chosen from the list of Qatari courts and bodies.
Record a hearing decision to adjourn, and check that the next hearing appears on that day’s roll.
Record a judgment, and see how the last day to appeal is proposed and who will be alerted before it runs out.
Open the appeal file from the case file after recording the judgment, and check which details carried over to it.
Issue a receipt voucher for an instalment of a fee agreement, and print it on the office’s letterhead.
Sign in with a secretary’s account, and check what it must not be able to see.
The evaluation table: twelve criteria and what to ask
Use the table below as a worksheet during demos: each criterion has a reason it matters to a law firm in Qatar and a specific question to put to any vendor. Note the answers as you heard them, ask to see them on screen rather than have them described, and compare the systems once all the demos are over, not after each one; the first impression of a polished demo can hide a gap that only shows up in comparison.
Criterion
Why it matters
What to ask
Quality of the Arabic and text direction
A translated interface confuses the team and produces printouts in clumsy wording
Were the screens and printouts written in Arabic, right to left, from the start, or translated later?
Litigation degrees and Qatari bodies
Each degree has its own hearings and judgments, and standard names are a precondition for accurate reports
Does each degree have a file linked to the one before it? Are the Qatari courts, prosecutions and committees set up in advance?
Appeal and grievance deadlines
Missing a single deadline is a loss no apology can make good
How is the deadline proposed? Who sets and reviews the periods? When does the alert arrive, and to whom?
Qatari riyals and amounts in words
Writing amounts in words by hand on vouchers is a constant source of errors
Are amounts written out in words in Qatari riyals automatically when a voucher is printed?
Client portal
A client who follows their own case calls less and worries less
What does the client see, and who decides? Can they view documents without downloading them?
Permissions and audit log
Not every employee needs every file or every figure
Are permissions set per section and per action? Are viewing, downloading and printing logged?
Data isolation and backup
Client data is held in trust and must be neither mixed up nor lost
Does my office have its own separate database? How often is it backed up? Can I create a backup and download it myself?
Working on a phone
A lawyer spends much of the day in court, not at the office
Does it work in a phone’s browser? Can it be installed as an app that receives notifications?
The office’s identity
The client sees your office’s logo in the portal and on vouchers, not the vendor’s
Does the system run at my office’s own web address, with its logo, colours and typeface?
Printing the office’s forms
Paper is still part of daily work at the office and in court
Are vouchers and forms printed in a tidy design that carries our office’s identity, and on the office’s pre-printed paper?
Setup and training
A system the team has not mastered is abandoned within weeks
Who sets up the system? How is our current data moved across? How is the team trained?
Pricing model
The real cost shows as the team grows, not in the first month
Is the price per user or per office? Are there extra charges for modules, storage or client accounts?
Fit for Qatar: Arabic, litigation degrees and deadlines
The first thing to test is the Arabic, because it is the language of every screen and every page that leaves your office. A system written in Arabic from the start shows in small details: a date typed as day/month/year without effort, a search that finds a client by name, Qatar ID (QID) number or phone, and printouts in sound Arabic, running correctly from right to left. A translated interface soon gives itself away: literal phrases, buttons in the wrong place, and tables whose order flips when printed.
Then ask how a case is structured. Litigation in Qatar moves through degrees: first instance, appeal, cassation and execution, as well as arbitration and settlement. A suitable system gives each degree a separate file linked to the other files of the same dispute, and opens the next degree from the case file itself without re-entering the parties. It comes with the names of the Qatari bodies ready, such as the Court of Appeal, the Economic Crimes and Money Laundering Prosecution and the Labour Disputes Settlement Committee, and lets you add any new body without duplicating names.
Finally, appeal deadlines: does the system propose the last day to appeal when a judgment is recorded? Where does it get the period from? Who is alerted before it runs out? A serious system lets the office’s lawyers set and review the periods, and does not present them as final truth. In Murafe, the periods are set under Settings → Appeal periods, by litigation degree and type of case; the office’s lawyers review the starting values and change them, and a reminder comes twice before each deadline passes: seven days before, then two days before. Legal responsibility for the deadlines stays with the office.
Data and security: questions to ask without holding back
Client files are held in trust, and asking how they are protected is not doubting the vendor but part of the office’s duty to its clients. Ask where the data is stored, whether your office’s data is isolated from other offices’ data, who on the vendor’s team can access it, how actions inside the system are logged, and how data is restored if something goes wrong. These are specific questions that deserve specific answers:
Does my office have its own separate database and its own file storage?
Can a lawyer be limited to the cases assigned to them, and confidential cases kept to their own team?
Is viewing a document a separate permission from downloading it?
Does the audit log record who added, edited, deleted, viewed or printed something, when, and from which device?
How often is the data backed up, and does the backup include uploaded documents?
Does the office control technical support’s access to its system?
What happens after repeated failed sign-in attempts, or when a device is left idle?
For comparison, this is what Murafe provides: a separate database, file storage and web address for each office; a daily backup of the database and uploaded files, with the option of creating a backup and downloading it from inside the system; permissions per section and per employee; an audit log that keeps every action, including viewing, downloading and printing; a temporary account lock after repeated failed sign-in attempts; and automatic sign-out on inactivity. The office can switch off technical support’s access from its settings, and every support visit is recorded in the audit log.
Daily use: the client, the phone and printouts
The client portal deserves careful testing, because it is the part of the system your client sees. Sign in with a test client account and ask: does the client see only what the office has allowed? Can they view the judgment without downloading it? Can they see what they have paid, what remains and what is due now? Can they message the office from inside the portal, with the message reaching the lawyer in charge? Ask about reminders too: do they reach the client by email or WhatsApp before the hearing and before an instalment falls due? Can the office edit the message texts itself?
Then try the system on your phone, the way you will use it in the court corridor, not on the meeting-room screen: can you open the case file and record the decision in a minute? Can it be installed on the home screen as an app with your office’s logo, and do its notifications arrive while the system is closed? Finally, print a receipt voucher, a statement of account and one of the office’s forms. Printouts are what the client carries out of your office: they should come out on the office’s letterhead, in a clear design worthy of it, with the option of printing on the office’s paper with the logo already printed on it.
Warning signs that call for a pause before signing
No system is perfect, but some signs deserve a pause before you decide, whoever the vendor is. They do not necessarily mean the system is bad, only that there are questions still unanswered, and those should be answered in writing before signing, not after; changing systems after a year of data is far harder than taking an extra week before choosing:
Vague answers about where the data is kept and who can see it.
A demo that refuses to leave its prepared script.
Appeal periods presented as final truth that the office’s lawyers cannot review or change.
Arabic printouts with flipped tables or word-for-word translated wording.
Fees that appear after signing, or a price that changes with every question.
Vagueness about who handles setup and training after you subscribe.
On the other hand, you can take comfort from a vendor who says a clear “no” when it lacks a feature you ask about, shows you on screen everything it claims, and gives you a trial period to test the system on files like yours. Frankness at the demo stage is a good sign of how you will be treated after subscribing, when you need someone to answer a real question on a real working day.
Setup and pricing: after the decision to subscribe
A good system can stumble after a bad start. Ask before subscribing: who sets up the system with your office’s identity and your team’s accounts? How does your current data move across from spreadsheets and notebooks? How is the team trained, and will they find step-by-step explanations inside the system when they need them? Do not settle for general promises: ask for a written statement of what setup, data migration and training include, who handles each part, and what is expected of your office at each stage.
As for pricing, read it in full, not just its first line. Ask: is the price per user, so the cost rises with every new employee? Do some modules, such as accounts or the client portal, cost extra? Is document storage limited? Do client accounts in the portal count as users? Are setup, data migration and training included in the price or charged separately? And is there a trial period on the system itself before you commit?
For clarity, the Murafe model is a single package covering every module and feature of the system, with no limit on the number of users or on document storage, and clients in the client portal do not count as users. The price is set on request, in Qatari riyals, according to the office’s size and needs, and the system can be tried before subscribing. Setup, data migration and team training are arranged as agreed, after which the team turns to the user guide built into the system, which sets out the steps for every section.
Choose the system your team will use next Sunday morning, not the system that impressed you in the demo.
Questions on this topic
How well it fits the way work is done in Qatar: a genuinely Arabic interface, litigation degrees in linked files, the Qatari judicial bodies under their official names, appeal deadlines reviewed by the office’s lawyers, and Qatari riyals on vouchers. After that come permissions, data isolation and pricing.
Try three things: type a date and search for a client by name or phone; print a voucher and a statement of account; and read the texts of the alerts and messages. Literal wording and flipped tables in printouts are the clearest signs of translation.
It varies between systems, so ask about it directly before comparing prices. In Murafe, clients do not count as users, and the number of users on the office’s team is unlimited in the all-inclusive package.
Ask for the system to be shown on scenarios from your office: a case through its degrees, an adjourned hearing, a judgment with an appeal deadline, a receipt voucher, and an employee account with limited permissions. Then try the same steps yourself during the trial period before subscribing.
