Courts & Law Firms
An IT expert can examine technical facts, system states, properties, processes and reproducible relationships. A defensible question therefore needs a technically identifiable subject of examination and criteria that can be addressed with available evidence, while legal evaluation and judicial assessment remain separate.
Short answer
A suitable technical question states what technical fact is to be examined, which system, data or version state it concerns and which records, data or test conditions can support an answer. Questions that already contain legal responsibility, unlawfulness or judicial evaluation must be separated into examinable technical components.
The expert answers the technical question within the assigned field and evidence base. Legal subsumption, procedural decisions and evaluation of evidence remain with the competent legal decision-maker.
1. Separate the evidentiary issue, technical question and examination object
A court or party may describe a broad disputed issue. Identify which concrete points fall within the IT field and can be examined technically. German ZPO § 403 is relevant to identifying the points to be examined by an expert.
The technical question should lead to observable or testable properties: a system state, measured behaviour, identifiable software version, data transformation or documented technical relationship.
The examination separates preserved material, directly observed technical findings, reconstruction and professional inference. Missing historical states or provenance are reported as limitations rather than filled by assumption. A technical expert finding does not decide procedural admissibility, legal responsibility, burden of proof or the court’s evaluation of evidence; those questions remain outside the technical conclusion.
2. Translate value judgements into testable sub-questions
Questions such as whether software is “bad,” “defective” or “unlawful” contain standards or legal evaluations that are not themselves pure technical facts.
A technical sub-question can instead ask whether a named release produces a defined output, whether an observed behaviour is reproducible under specified conditions or which source-code properties are present under an identified reference criterion.
The examination separates preserved material, directly observed technical findings, reconstruction and professional inference. Missing historical states or provenance are reported as limitations rather than filled by assumption. A technical expert finding does not decide procedural admissibility, legal responsibility, burden of proof or the court’s evaluation of evidence; those questions remain outside the technical conclusion.
3. Respect judicial direction and professional competence
In court-appointed work, ZPO § 404a is relevant to judicial direction, factual assumptions and the scope of the expert activity. Disputed factual assumptions should not be silently resolved by choosing one party’s version as the sole basis.
The expert should also verify that the question lies within the relevant professional field. Where content or scope remains unclear, ZPO § 407a is relevant to clarifying doubts rather than expanding the assignment by assumption.
The examination separates preserved material, directly observed technical findings, reconstruction and professional inference. Missing historical states or provenance are reported as limitations rather than filled by assumption. A technical expert finding does not decide procedural admissibility, legal responsibility, burden of proof or the court’s evaluation of evidence; those questions remain outside the technical conclusion.
4. Determine the examination basis and reference criterion
Even a precise question may be unanswerable if the relevant system state, data or artefacts are missing. Record which version, records, repositories, logs or other evidence actually support the examination.
Where a comparison is required, identify the technical reference: specification, documented requirement, test case, manufacturer documentation or other stated benchmark. If the benchmark is legally selected, that selection is separate from the technical comparison.
The examination separates preserved material, directly observed technical findings, reconstruction and professional inference. Missing historical states or provenance are reported as limitations rather than filled by assumption. A technical expert finding does not decide procedural admissibility, legal responsibility, burden of proof or the court’s evaluation of evidence; those questions remain outside the technical conclusion.
5. Move from finding to bounded professional conclusion
First state what was observed, measured or reconstructed. Then explain what that finding means for the technical question and which alternative explanations remain compatible with the evidence.
A measured deviation can support a technical requirements comparison without deciding whether the deviation constitutes a legal defect, breach or other legal consequence. Judicial evaluation under ZPO § 286 remains separate.
The examination separates preserved material, directly observed technical findings, reconstruction and professional inference. Missing historical states or provenance are reported as limitations rather than filled by assumption. A technical expert finding does not decide procedural admissibility, legal responsibility, burden of proof or the court’s evaluation of evidence; those questions remain outside the technical conclusion.
6. Document the technical question structurally
Record object, time or version, factual basis, reference criterion and requested technical determination. This creates a traceable link between the assigned question, the evidence examined and the conclusion.
Where a question contains several layers, split them into sub-questions for state, reproducibility, cause and scope. Each layer may require different evidence and may have a different statement boundary.
The examination separates preserved material, directly observed technical findings, reconstruction and professional inference. Missing historical states or provenance are reported as limitations rather than filled by assumption. A technical expert finding does not decide procedural admissibility, legal responsibility, burden of proof or the court’s evaluation of evidence; those questions remain outside the technical conclusion.
Examination checklist
- Is the technical subject of examination identifiable?
- Does the question ask for a technical finding rather than a legal conclusion?
- Are factual assumptions and disputed facts explicit?
- Is the required evidence available and attributable?
- Is the technical reference criterion identified?
- Are professional competence and assignment scope clear?
- Is the conclusion separated from judicial evaluation of evidence?
Constructed example
A court-related question asks whether a named software release produced exports in accordance with a specified technical document. The examination records the release, input data, environment, test procedure and output structure. Any conclusion about contractual breach or legal defect is expressly left outside the technical finding.
The example is entirely constructed and does not describe a real engagement, client matter or historical case.
Sources and technical basis
- Official legal sourceGerman Code of Civil Procedure (ZPO), § 286. Official text relevant to distinguishing technical expert findings from judicial evaluation of evidence. Open source.
- Official legal sourceGerman Code of Civil Procedure (ZPO), § 403. Official text relevant to identifying the points to be examined by an expert. Open source.
- Official legal sourceGerman Code of Civil Procedure (ZPO), § 404a. Official text on judicial direction of expert activity and the factual basis of the examination. Open source.
- Official legal sourceGerman Code of Civil Procedure (ZPO), § 407a. Official text on further duties of an expert, including clarification of doubts concerning scope. Open source.
- Methodological basisSources & Methodology documents source hierarchy, counter-hypothesis control and statement boundaries for the English knowledge base.
Further reading
- Formulating a Precise Technical Expert Question
- Preserving Documents and Digital Evidence for Technical Questions
- Sources & Methodology
Critical review and methodological limitation
Party submissions, document statements and the expert’s own technical findings should remain distinguishable. A plausible party explanation is not adopted merely because it is coherent; where possible it is checked against the technical evidence and competing explanations.
The strongest answer may sometimes be that the available basis does not support the requested degree of certainty. Reporting an evidence gap or alternative explanation is methodologically preferable to converting uncertainty into a legal-sounding technical conclusion.
Translation and methodological scope
This English article is based on the reviewed German V1 source article. The translation preserves the technical meaning, methodological distinctions, source status and stated limitations. It does not strengthen technical findings into legal conclusions and does not treat technical references as proof of compliance or suitability for a specific system.
Author's technical literature and publications
The following works provide additional technical and methodological context. They do not replace required primary sources, standards, manufacturer documentation or other independent specialist sources. Unpublished manuscripts, drafts and teaching materials are deliberately not presented here as public sources.
Technical Expertise for Courts & Law Firms
Neutral technical examination of software, IT projects, data and AI questions in court and legal contexts.
Explore this assessment service