Professional practice
Technical assessments based on documented evidence and disclosed method rather than the desired outcome of a party.
Principle of independence
Independence and a traceable approach to potential conflicts of interest are foundations of expert work. The technical assessment is not aligned to a desired result. Relevant relationships or conflicts are reviewed before acceptance; an assignment is declined where independent professional work would be impaired.
Objectivity and methodological transparency
Each assessment is supported by disclosed criteria and technical evidence. Methods, data sources, reference standards, counter-hypotheses and material limitations are documented. Objectivity is therefore made reviewable rather than merely asserted.
Typical situations
- Technical assessment in project conflicts or contractual disputes.
- Technical work in out-of-court clarification, mediation or internal investigation.
- Independent second opinion on an existing technical report.
- Assessment of software, systems or AI methods for technical defects or performance deviations.
Professional and personal integrity
Potential conflicts are reviewed before and during the work. Professional conclusions are tied to technical evidence, documented facts, disclosed assumptions and the boundaries of the assignment.
Trust through traceability
The objective is a transparent, professionally reviewable and outcome-open report. Trust should arise from method, evidence, counter-testing and explicit limitations rather than from a blanket claim of objectivity.
Example scope of an assessment
- Independent technical examination of IT systems, software or projects.
- Assessment against documented, reviewable criteria.
- Neutral presentation of findings and limitations.
- Optional second assessment of an existing technical report.
Indicative fee range: approximately €1,000–€3,000 net, depending on scope, documentation effort and required detail. The amount is for orientation only and is not a binding offer.
Related technical knowledge
Constructed case study: neutrality and independence
Making independence reviewable through conflict checks, disclosed method and evidence rather than through assertion alone.
Constructed examination scenario: This is a methodological example, not a real mandate, a real court appointment or a report of actual findings.
Diagnosis – identify potential conflicts of interest
Review existing relationships, prior involvement and other circumstances that could affect independent technical work before accepting the assignment.
Objectives – define assessment principles
Set documented criteria, evidence requirements and the separation between factual finding and professional assessment.
Analysis – perform an evidence-based examination
Base conclusions on reproducible technical evidence and disclosed methods. Keep the presentation independent of the desired outcome of any party.
Expert synthesis – transparent reasoning and limitations
Document the reasoning, counter-evidence and limitations so that third parties can critically review how the technical conclusion was reached.
Methodological inspiration: Nicolai Andler, Tools für Projektmanagement, Workshops und Consulting – Kompendium der wichtigsten Techniken und Methoden, 6th revised and expanded edition, Publicis, Erlangen, 2015, ISBN 978-3-89578-453-8. The examination sequence and expert synthesis used here are independently formulated for technical expert work.
Initial technical classification of an enquiry
Before accepting an assignment, the technical question, subject of examination, available records, potential conflicts of interest and the required scope are reviewed. An individual non-binding proposal can then be prepared.
Contact Mathias Ellmann