08 — Criminal Workflow Orientation

A reader who has never worked around criminal law often imagines a criminal case as something much simpler than it really is. There is a crime, an arrest, a trial, and a verdict. That is the movie version. It is clean, compressed, and dramatically convenient. Real criminal workflow is slower, messier, more procedural, and far more dependent on records than most outsiders realize.

That matters because SUMMA is not being built for the movie version. It is being built for the real workflow.

A criminal case usually begins with an allegation, an investigation, and some form of police or state response. That part may happen quickly or slowly, and it may produce very different kinds of records depending on the nature of the case. Some matters generate relatively little material at the beginning. Others generate a flood: police notes, occurrence reports, witness statements, scene photographs, surveillance material, warrants, seizure records, forensic submissions, interviews, digital records, and later technical reports. Already, before the case has matured, the record may begin splitting into different evidentiary forms that do not behave the same way.

That is one of the first important ideas for the reader to grasp: a criminal file is not just “documents.” It is a mixed record.

Once charges exist and the matter begins moving through the court system, another major force begins shaping the case: disclosure.

Disclosure is one of the central realities of criminal workflow. In simple terms, it is the body of material the prosecution is obliged to provide to the defence. But that simple definition hides how large the concept really is in practice. Disclosure is not one thing, one folder, or one clean delivery. In many serious cases it becomes an entire evolving environment. It may contain reports, statements, notes, transcripts, media, digital evidence, forensic material, search-warrant packages, follow-up productions, and corrections. It may also arrive unevenly, late, or in forms that are technically delivered but not easy to think with.

That is why disclosure is one of the main engines of difficulty in criminal-file work.

A new reader should understand something that is not obvious from the outside: defence-side review is often shaped less by one dramatic courtroom event than by long periods of reading, sorting, comparing, revisiting, and trying not to lose the thread of a changing file. The work is not glamorous in the cinematic sense. It is structural. It is cognitive. It is cumulative. A lawyer or review team may spend enormous amounts of time simply trying to preserve a stable understanding of what the file is, what has changed, what matters, and what must be revisited now that new material has arrived.

This is why disclosure arriving in stages matters so much.

Many people imagine disclosure as if it were delivered all at once, neatly, at the beginning. In real cases that is often not how it behaves. Disclosure may arrive in batches. Some parts may be missing at first. Some parts may be corrected later. Some materials may turn out to matter much more after later productions arrive. Some issues that looked settled may become unstable again. A witness statement may gain new significance because of a later forensic report. A timeline that looked coherent may start breaking down once communications records or surveillance files are added. The file therefore evolves not only by getting bigger, but by changing shape.

That changing shape is one of the main reasons SUMMA becomes necessary.

If the file only grew in volume, ordinary tools would still struggle, but the problem would at least be simple to describe. The deeper problem is that the file grows unevenly and meaning changes with it. Material is added. Material is corrected. Importance shifts. Contradictions emerge. Some parts of the record become anchor zones. Some become noise. Some become strategically dangerous. The reviewer is no longer just reading; the reviewer is trying to maintain orientation inside a moving structure.

That moving structure creates different kinds of legal work at different stages.

Early in the case, the work may be more focused on initial orientation: what exists, what kind of case this is, what the broad disclosure shape looks like, whether the accused is in custody, what the immediate procedural pressures are, and what needs urgent attention first. At that stage, triage matters a great deal. The problem is not knowing everything immediately. The problem is figuring out where to begin without getting buried.

As the file matures, the work becomes more comparative and more strategic. The reviewer has to think about contradictions, omissions, witness instability, search issues, timeline pressure, admissibility questions, Charter questions, and other issue-centered problems that are no longer visible from raw file names alone. Some of these problems may later become motions, applications, voir dires, or trial points. Others may shape resolution discussions or affect whether the case posture has changed. The point is that the file stops being just a body of materials and starts becoming a field of live issues.

This is where many outsiders badly underestimate the burden on defence-side work.

From the outside, it can look as if the real legal work happens only when people stand up in court and speak. In reality, a huge amount of the work happens before that, underneath that, and around that. It happens in the maintenance of understanding. It happens in repeated return to source. It happens in comparing versions, rebuilding timelines, noticing contradictions, testing reliability, and trying to separate what is merely present in the file from what is actually dangerous. If the file is large enough, that burden can become punishing even for intelligent and disciplined professionals.

That is the environment SUMMA is meant to improve.

The system is not trying to replace legal judgment. It is trying to reduce the avoidable pain of working inside evolving criminal records. It is trying to preserve structure where the ordinary file tends to become flat, preserve continuity where time and later disclosure tend to break understanding, preserve exact return to source where summaries tend to drift, and preserve issue-centered handling where raw document mass tends to overwhelm attention.

A new reader should also understand that not every criminal file is the same.

Some matters stay comparatively small. Some become procedurally complicated but not evidentially massive. Some become disclosure-heavy in a way that changes the whole rhythm of review. Some become strategically dense because of one or two critical issues rather than thousands of pages. Others become brutal because they combine all the problems at once: many productions, many witnesses, mixed media, technical reports, multiple issue zones, evolving theory, and a record large enough to defeat ordinary memory. The product therefore has to be useful across different scales while becoming especially valuable when the file crosses into serious structural difficulty.

This is why criminal workflow cannot be understood only as a sequence of court dates.

The visible procedure matters, of course. Bail matters. Hearings matter. Motions matter. Trials matter. Appeals matter. But underneath those visible stages sits the file itself, changing, accumulating, and pressuring the people who have to live inside it. A system like SUMMA is designed for that underlying reality. It is designed for the part of criminal workflow where the quality of thought depends heavily on the quality of structure.

The reader should leave this chapter with one central understanding: criminal workflow is not just accusation followed by courtroom drama. It is an evolving record environment shaped by disclosure, procedure, timing, and repeated review. SUMMA exists because that environment becomes too difficult to handle well with ordinary tools once the file reaches serious scale or complexity.