Case study
Legal Atoms — Legal Intake Portal: 60% Less Manual Input
60% less manual case input · 200ms faster responses. Legal case support portal with dynamic questionnaire logic for faster case intake.
Rails 6 · Angular · .NET
The problem
Legal intake burned hours on repetitive questionnaire work and slow server responses during peak filing periods.
What we did
- Modeled questionnaire branches so staff skip irrelevant steps.
- Cut redundant writes on the case intake path.
- Tuned hot endpoints until average response time fell by about 200ms.
Why intake was the bottleneck
Legal case intake is repetitive by nature: the same questions, asked in slightly different orders, for cases that mostly follow a few patterns. When the questionnaire treats every case the same, staff answer questions that do not apply and re-enter information the system already has. That is where the hours went, and it got worse during peak filing periods when the server also slowed down.
Branching questionnaires
The questionnaire was modeled as branches, so each answer decides which questions come next. Staff skip whole sections that are irrelevant to the case in front of them. This is the change aimed squarely at manual input, because the fastest question to answer is the one you never see.
Making the intake path faster
On the performance side, redundant writes on the intake path were removed, and the hottest endpoints were tuned until average response time fell by about 200ms. Two hundred milliseconds sounds small, but intake is a sequence of many steps, and the saving repeats on every one of them during the busiest hours.
Applying this to your forms
Map which questions apply to which case types before redesigning any screen. Turn that map into branching logic, and prefill anything the system already knows. Then profile the endpoints behind each step during peak load, not on a quiet afternoon, and remove writes that do not need to happen on that request.
Outcome
Manual case input fell 60%, and the portal answered intake requests about 200ms faster.
Need the same kind of result on your product? Hire a software architect who has already shipped it, or hire a full-stack developer in Pakistan for remote delivery.
More case studies
- ATC (Air Traffic Controller) — Reliable high-volume job scheduling with Hangfire
- Cercle — 30% less cart abandonment · 20% faster TTI
- Go Green Together — 40% better operational efficiency
All projects · Hire a Software Architect · Start a conversation