The Case Compiler: Turning Mixed Case Material Into One Briefing

A new client rarely arrives with a clean file. More often it is a phone photo of a notice, a scanned agreement, a WhatsApp voice note explaining the background, and an email thread that has the actual dates buried somewhere in the middle. The Case Compiler exists for exactly that moment: it takes the bundle as it actually is and returns one readable briefing, rather than asking you to read every piece separately before you can even start.

What it accepts

The Compiler takes PDFs, DOCX files and audio, together, in a single submission. PDFs are handed to the engine as they are. DOCX files are read for their text, up to a large character limit per file, so a lengthy agreement or a long correspondence thread is not a problem. Audio is passed through as uploaded, so a voice note explaining the matter in the client's own words is a legitimate input alongside the documents.

What happens when one file in the bundle is bad

A bundle of client material almost always has at least one problem file in it: a scan too large to process, a corrupted export, a document in the wrong format. The Compiler does not fail the whole submission over one bad file. Each input is checked on its own, and a file that cannot be used is recorded as an exclusion rather than treated as a reason to stop. The briefing is still produced from everything that could be read, and the exclusion is stated plainly rather than silently dropped.

If nothing in the submission is usable at all, the Compiler does not run the model on an empty bundle and charge for it. It stops before that point and nothing is deducted.

What comes back

The output is a single briefing, not a set of file-by-file summaries stitched together. It opens with an executive summary and a docket card, "The Matter," built from the party names, the court, the cause and a key date computed from the material rather than lifted from a loosely worded timeline paragraph. That last distinction is deliberate: a free-text summary of events can say "last month" or "shortly before the hearing," which is not a date a briefing can be built around, so the key date shown is one the platform has actually resolved to a real day.

Beneath that sits the substance: the facts pulled from across the bundle, organised into one account rather than left as separate summaries of the PDF, the DOCX and the audio.

It reads the bundle for the jurisdiction you have selected

The jurisdiction set in the switcher reaches the Compiler the same way it reaches drafting and review. A bundle compiled with Sindh selected is read with Sindh's forum and statute context in mind, not a generic one.

Where it sits next to the other tools

Generate Document starts from a structured form and produces a new instrument. Matter Reviewer takes a document you already have and reviews it against the law. The Compiler sits before both of those, at the point where the material is still raw and mixed, and its job is to turn that pile into something you can actually read and act on, whether that next action is drafting, review, or a conversation with the client about what the file actually shows.

One compilation, however many files it draws from, costs one instrument.

This post replaces an earlier one written before the briefing carried a docket card or a computed key date: Legalise Case Compiler: Briefing Tool for Mixed Client Material, which remains available and is marked as archive.