There is a moment every court-appointed expert knows well.

It usually arrives late at night, a few days before a report deadline. You are scrolling — scrolling — through a WhatsApp group that has accumulated 847 messages over four months. You are looking for the document a lawyer sent sometime in March. Maybe it was the plaintiff's lawyer. Maybe it was the defendant's. You cannot quite remember, because both sides are in the same chat, and the conversation has been a chaotic mix of pleasantries, questions, follow-ups, the occasional legal argument, and a photograph someone sent by accident.

The document is in there somewhere. You know it is. You just cannot find it.

This is the state of court and arbitration expertise work across much of the world today. And it is not a small problem.

The gap no one talks about

Court-appointed experts occupy a specific and serious role in the justice system. When a judge or arbitral tribunal needs an independent technical opinion — on a construction defect, an accounting dispute, a medical question, a real estate valuation — they appoint an expert. That expert becomes an officer of the court. Their report carries legal weight. Their process must be defensible.

And yet the tools most experts use to manage that process are the same ones people use to plan birthday parties and share family photos.

The result is predictable: scattered document trails, no clear record of what was requested from whom, informal communications that blur the line between the expert and the parties, and reports that have to be reconstructed from memory and fragments rather than assembled from a clean, organized case record.

It is not that these experts lack professionalism. They are often deeply skilled, highly credentialed, and trusted by the courts that appoint them. The problem is that no one has ever built them a proper tool.

Until now.

What Khebra is

Khebra (خبرة — Arabic for expertise) is a bilingual web platform built specifically for court and arbitration experts in the Arab world and the world .

It is not a general project management tool with a few custom fields bolted on. It is not a document repository with a chat feature. It is a purpose-built platform designed around one specific workflow: the lifecycle of an expertise appointment, from the moment an order is issued to the moment a final report is submitted.

Here is what that looks like in practice.

When an expert receives an appointment, they open a case in Khebra and enter the case details. They invite all parties — plaintiff, plaintiff's lawyer, defendant, defendant's lawyer — and each joins their own role. From that moment, the expert controls everything: who can see what, who can speak when, and what gets recorded.

Document requests are formal and tracked. When the expert needs a specific document from a specific party, they send a tracked request. The system records when it was sent, when it was fulfilled, and what was submitted. No more "I never received that request" from a lawyer. No more "I did send that document" from a party. The record is unambiguous.

Communication is structured. The expert can open a directed conversation with just one party — privately, without the other side seeing it — or address all parties in the shared case channel. Messages are timestamped and permanently logged. Nothing disappears.

Minutes of meetings are drafted, signed, and stored inside the case. On a tablet at a site visit, parties can sign directly on screen. Remote attendees can sign through a temporary link. The signed MOM becomes part of the case record immediately.

Reports are drafted inside the platform, using the expert's own templates or the platform's standard bilingual structure. The preliminary report goes to all parties for their objections period. Objections come back as structured submissions. The final report responds to each one. The entire two-stage process is managed in one place.

And when the case is done, everything — every message, every document, every request, every MOM, every report version — is there. Organized, searchable, exportable. A complete legal record.

Built for the region, not translated for it

Most legal software is built in English, for Western legal systems, and then (sometimes) translated into Arabic as an afterthought. The Arabic version gets a right-to-left layout and a font swap, and the team calls it localized.

Khebra is different. Arabic and English are equal from the first line of code. Every screen, every label, every document template exists in both languages simultaneously. The platform switches between right-to-left and left-to-right layouts seamlessly. Arabic legal terminology is built in — not approximated.

Court and arbitration expertise procedures follow broadly consistent patterns across the Arab world. The workflow in Khebra reflects that reality. Whether a case is filed in the Gulf, the Levant, or North Africa, the process is the same — an appointment is issued, an expert investigates, and a report is submitted. Each case carries a jurisdiction setting that adjusts the right labels and fields for the local context, so the platform feels native wherever you work.

Private by design

Legal cases contain sensitive information. Documents submitted under court proceedings. Financial records. Medical details. Communications between lawyers and their clients' adversaries.

Khebra is built on a "Private by Design" principle: no internal tool or support workflow allows Khebra staff to access case content. Not the messages. Not the documents. Not the reports. Case data is encrypted in transit and at rest. National IDs are stored only as one-way hashes — not even Khebra can reverse them.

When you connect your Google Drive or OneDrive to mirror your working files, the OAuth permission is scoped only to Khebra's own folder in your drive. Nothing else is touched.

Your cases are yours. The platform is the infrastructure, not a party to the proceedings.

AI that works the way you actually work

Khebra includes an AI integration — but not the kind that reads your case data and does something unpredictable with it.

The model is simple: you bring your own API key from OpenAI or Anthropic, and Khebra acts as the secure bridge that injects your case context into AI requests on your behalf. You pay your AI provider directly. Khebra does not charge extra for AI, does not see your AI costs, and does not use your case content to train any model.

What you get is an AI assistant that actually knows your case. It can summarize documents you have just reviewed, draft a formal letter in Arabic and English from your bullet points, analyze the objections submitted to your preliminary report and surface the key themes, or help you draft a section of your final report from your investigation notes.

Every AI output is a suggestion. Nothing enters your case record without your explicit approval. The expert is always in control.

The waiting list is open

Khebra is in final development. We are building toward a launch, and we are opening our waiting list now.

If you are a court or arbitration expert — or if you work with experts in a legal, advisory, or institutional capacity — we want to hear from you. Early access members will be the first to try the platform, and their feedback will directly shape what ships.

The WhatsApp group is not a case file. It never was. You deserve a tool built for the work you actually do.

Join the waiting list.

Share