Case studies

The publication gate

Every case listed in the programme has to clear four checks before it becomes a page: the primary judgment has been read rather than a headnote or a commentary, the citation and court are verified, the appeal and subsequent treatment are checked, and the note is written from the judgment rather than from anybody else’s article.

That is a slow way to build a case library, and it is the only way to build one that a professional reader can rely on. The alternative, a hundred summaries assembled from secondary sources, is how citation errors propagate through an industry.

The template every case note follows

1. The 90-second case: project, parties, dispute, outcome.
2. Authority card: exact citation, court, date, jurisdiction, appeal history, status and a link to the judgment.
3. The contract: form, edition and decisive bespoke clauses, saying so where the wording is unavailable.
4. What happened: a neutral chronology taken from the judgment.
5. What each side had to prove.
6. The evidence: programmes, notices, diaries, costs and expert methods.
7. The decision, keeping liability, causation, time and quantum separate.
8. Why it matters: three operational lessons.
9. What it does not decide: no extrapolation beyond the wording and the jurisdiction.
10. Source trail: judgment first, then legislation and contract, then guidance and commentary.

The GCC shelf is different on purpose

Because public judgments and awards are uneven across the GCC, that material is published as legal mechanism and teaching dossiers rather than as case notes, each carrying a banner saying it is code analysis and not a reported binding precedent.

Where the programme stands

The case programme and its verification status are published on the editorial roadmap, along with every other page in the plan. Nothing is hidden: you can see what is written, what is being verified and what has not been started.