Court-Appointed Experts in Israeli Software Cases

When the court appoints an expert

This page describes procedure in the Israeli courts specifically. If you are instructing from abroad, the mechanics below will differ from what you are used to, and the differences matter most in exactly the place software cases live: how the expert gets access to the material.

Where the decision turns on a question outside ordinary judicial knowledge, the court may appoint its own expert, so it gets one agreed answer rather than two opinions that contradict each other. In software cases that happens when the dispute is about what the system actually did: whether the code does what the contract promised, whether one component infringes copyright in another, who accessed what and when, or why a system failed.

The appointment can come on the court's initiative or on a party motion. In practice, it pays to be the one who moves in a software case. Whoever drafts the motion shapes what the expert will examine.

The appointment motion: what belongs in it

A motion drafted too generally produces an opinion that helps nobody. In a software case three things drive the quality of the result more than anything else.

The questions. Skip "is the system sound." Ask questions with a testable answer: does function X compute Y by the formula in the specification, were the records in table Z deleted and when, is the code in version 3.1 substantially identical to the other side's code.

The field of expertise. "Computer expert" is not a field. Information security, software architecture, databases, digital forensics and project estimation are different specialisms held by different people. A motion that does not name the field gets an expert who may not be able to answer.

What answering will require. If the question needs source code to be read, say so in the motion. Otherwise you reach the point where the expert asks for access, the other side objects on trade-secret grounds, and the case stalls.

The appointment order in a software case

The appointment order is the document that fixes what the expert can and cannot do. In ordinary cases it is almost clerical. In software cases it is the single largest source of disputes, because the material does not sit in a binder but in a live system somebody controls.

The order should settle explicitly: which systems and environments the expert may access, whether access is to source code or only to outputs, who produces the copy and in what format, how chain of custody is preserved so the other side cannot later claim the material changed in transit, what happens to the material when the proceeding ends, the deadline for the opinion, and what follows if the material arrives late.

An order that is silent on these points looks economical at the drafting stage and costs months later.

The court expert lists

The courts maintain expert lists from which appointments are customarily made. Appointing from a list is not mandatory, and in narrow fields such as software engineering it is not always possible. The parties may agree on the identity of the expert, and where they agree the court usually respects it.

In a software case this stage is worth the investment. The difference between an expert who has read production code in the last ten years and one who has not shows up in every line of the opinion.

The expert fee and who bears it

The court sets the expert fee and how it is split between the parties, and may change the split in the judgment according to the outcome. In software cases it is worth asking for a cost estimate before the expert starts: the volume of digital material drives the fee far more than in other fields, and the gap between examining one module and examining a whole system is an order of magnitude.

Clarification questions

Once the opinion is filed, the parties may put clarification questions to the expert. It is the cheapest and fastest tool available, and it is used less than it should be.

A good clarification question in a software case is precise and closed: which version of the code was examined, which files were and were not covered, what tool was used and in what configuration, whether the test was repeated and with what result. An open question invites an answer that reinforces the opinion. A closed one surfaces what was never examined.

Cross-examining the expert

An expert who has filed an opinion can be cross-examined on it. In a software case the cross almost never succeeds on a professional judgment, because it is hard to beat an expert on a question inside their own field. It does succeed on methodology: what was examined and what was not, why that approach was chosen, whether the result is reproducible, and what would have happened had the omitted component been examined too.

Good preparation means cross-checking the opinion against the raw material instead of just rereading the opinion. That is exactly what we do in expert opinion challenge: weak points ranked by strength, and questions written to be asked in the room.

Grounds for disqualifying an expert

Disqualification is exceptional and the courts do not lean toward it, partly because it resets the proceeding. The grounds usually argued are a conflict of interest or closeness to one of the parties, exceeding the scope set in the appointment order, and conduct that harms the appearance of justice, such as one-sided contact with a litigant.

What is usually not enough on its own: dissatisfaction with the conclusion, or an isolated professional error. Those have other routes.

Challenging the opinion

There is no separate appeal against the opinion itself. The tools are the ones listed here: clarification questions, cross-examination, a motion to appoint an additional expert, and attacking the conclusions in closing submissions.

A court-appointed expert opinion does not bind the court, but in practice Israeli courts tend to adopt it, particularly where it has not been contradicted. So the effort pays off far more at the drafting stage of the appointment order than after the opinion is in. Once it is on the table, examine its sources, its methodology and whether it reproduces, before deciding whether there is anything worth attacking at all. If what you need is a primary opinion in a software case, that is here.

Frequently asked

Who pays the court-appointed expert?

The court sets the expert fee and how it is split between the parties, and may change the split in the judgment according to the outcome. In a software case it is worth asking for a cost estimate up front, because the volume of digital material drives the fee more than it does in other fields.

What should the appointment order specify in a software case?

The questions the expert must answer, the material that will be handed over, how source code and runtime environments will be accessed, the delivery format, and the deadline. An order that is silent on code access creates a later dispute that stalls the opinion.

Can you appeal a court-appointed expert opinion?

Not by way of a separate appeal against the opinion itself. The accepted tools are clarification questions, cross-examining the expert on the opinion, moving to appoint an additional expert, and attacking the conclusions in closing submissions. The opinion does not bind the court, but in practice Israeli courts tend to adopt it.

How does a court-appointed expert differ from a party expert?

A court-appointed expert is selected by the court, and the opinion serves both sides. A party expert is retained by a litigant and files an opinion on that party's behalf. Both are subject to cross-examination.

This page is general information for professional orientation. It is not legal advice and is no substitute for advice on a specific case.