The 36 Group saves four working weeks and £50,000 in murder trial preparation with Luminance AI
The 36 Group had to review over 10,000 documents — including handwritten witness statements, police notes, and court orders spanning decades — within days for a historic murder trial, while working remotely during COVID-19. Their existing CCDCS system could not support real-time collaboration or efficient search.
The CCDCS platform lacked real-time collaboration and efficient search. Manual keyword searches through police files with unhelpful or cryptic filenames caused critical information to be missed.
source quote
source quote
source quote
source quote
source quote
The defense team saved four working weeks and £50,000 during the review and disclosure phase, and cross-examination bundles that would normally be time-consuming were compiled in minutes.
Compare to your context
Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.
Frequently asked questions
What did this team achieve with this AI workflow?
The defense team saved four working weeks and £50,000 during the review and disclosure phase, and cross-examination bundles that would normally be time-consuming were compiled in minutes.
What tools did this team use?
Luminance, CCDCS.
What results were reported?
Working weeks saved: four working weeks; Cost saved: £50,000; Documents reviewed: 10,000+; Cross-examination bundle compilation time: just minutes (source-reported, not independently verified).
What failed first in this deployment?
The CCDCS platform lacked real-time collaboration and efficient search.
How is this legal document review AI workflow structured?
Document set uploaded to platform → AI document analysis and visualization → Conceptual search across evidence → Adaptive review pattern learning → Cross-examination bundle compilation.
Related legal document review cases
Now compare it to your context
This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.