Free guides and tools for IT disputes, technical assessment, and expert witness instruction.
Whether you’re a business facing a software dispute or a solicitor preparing a case, these resources help you navigate IT disputes with clarity.
For Businesses Facing IT Disputes
Why Early Technical Assessment Matters in IT DisputesHow pre-litigation technical discovery clarifies facts before positions harden, informs strategy before costs escalate, and points to settlement before proceedings issue.
Did Your IT Supplier Follow Industry Standards?Reference guide to 30+ software-engineering standards across the development lifecycle. The benchmarks expert witnesses cite to assess whether a supplier followed accepted practice in an IT dispute.
Software Standards Assessment ChecklistA free 12-page checklist of 144 evidence checkpoints, mapped to SWEBOK knowledge areas and named professional standards. A pre-action scoping tool for solicitors and businesses needing to inventory the technical record of an IT dispute.
For Solicitors Instructing IT Experts
A Solicitor’s Guide to Instructing Software Expert WitnessesComprehensive guide to working effectively with software engineering experts in IT disputes; from when to engage them, through evidence gathering and technical assessment, to expert discussions and trial preparation.
How to Examine Source Code in an IP DisputeHow expert witnesses examine source code in IP and copyright disputes. A technical methodology guide covering forensic analysis, git history, and court reporting.
Forensic Evidence Gathering in a Supplier Software DisputeHow expert witnesses gather forensic evidence in a supplier software dispute: what the system records, preserving it before it decays, reading the delivery timeline, and what the record can and cannot prove.
How to Assess a Failed Software ProjectHow expert witnesses assess failed software projects: requirements failures, development practice, supplier duties, and forming an opinion under CPR Part 35.
Reading Git Commit History as Forensic EvidenceHow expert witnesses read git commit history as forensic evidence in supplier delivery disputes: cadence, message quality, author distribution, history integrity, and reporting under CPR Part 35.
Software Requirements as Evidence in IT DisputesHow expert witnesses assess software requirements as evidence in IT disputes: disclosure surfaces, recurring failure patterns, the standard of care, and what good documentation looks like under CPR Part 35.
How to Assess Technical Debt in a Software DisputeHow expert witnesses assess technical debt as evidence: the codebase and its history, industry benchmarks, the supplier's standard of care, and reporting under CPR Part 35.
AI-Assisted Development and the Standard of CareHow expert witnesses assess AI-assisted development in a software dispute: the standard of care, the limits of proving code provenance, automated verification and where it fails, and forming an opinion under CPR Part 35.
About Expert Witness Practice
Software Expert Witness for Software Engineering DisputesIndependent software expert witness for IT and software development disputes — technical discovery, root-cause analysis, and CPR Part 35 reports from pre-action to trial.
Fees and ChargesTransparent pricing for pre-litigation advisory and CPR Part 35 expert witness services. Hourly rates, court attendance fees, indicative case-stage totals, and how to arrange a no-obligation initial discussion.
Terms and Conditions PDFStandard terms of business that apply when you instruct me for technical discovery or expert witness services in a software or IT dispute.
Background & Further Reading
Better Software RequirementsThe author's own handbook on software requirements — gathering, writing, reviewing and implementing them across agile, offshore and legacy work.
How I Became a Software Expert WitnessThe personal story behind my expert witness work — 27 years of software engineering combined with lived experience of legal proceedings, and why expert witness work finally fits after decades of roles that didn't.