Amicus · Legal document and case workflows
A court document enters. The case organizes itself.
Amicus is built for Philippine legal practice. It reads scanned court documents, identifies cases, parties, dates, document types, and deadline rules, and organizes the extracted information into working legal workflows that the firm can verify.
What it does
Court documents arrive as scans. Amicus treats them that way.
Philippine practice runs on paper that has been photographed, scanned, forwarded, and filed under a name nobody agreed on. Amicus reads the pages, works out what the document is, matches it to the case, and holds anything uncertain for a person.
Vision on every page
Court documents are scans, not text files. Each page is read as an image so parties, case numbers, dates, and document type come off the page itself rather than out of an unreliable text layer.
A confidence gate, not a guess
A filing attaches to a case automatically when the match is confident enough. Below that line it lands in a review queue and waits for a person. The threshold is a product decision, not an accident.
Deadlines computed, not estimated
The model identifies which rule applies — file an answer within fifteen calendar days from receipt. Deterministic code computes the actual date against weekends, regular holidays, and special non-working days.
Citations are mandatory
Every extracted fact keeps the document, page, and span it came from, so a summary, a chat answer, and a deadline can all be traced back to the paragraph that produced them.
Cases grouped the way firms think
Related case numbers with the same parties at the same court are handled as one group, so documents, deadlines, and history stay together instead of splitting across near-identical matters.
Built for court days
The iOS app caches what a lawyer needs to open when there is no signal, gates the app behind Face ID, and sends the day's hearings and deadlines to the phone.
Deadlines
A rule on a page becomes a date on a calendar.
This is the part of the workflow that cannot be approximately right. The extraction is a language problem; the date is an arithmetic problem; the date of receipt is a question for a person. Amicus keeps the three separate.
- Extracted rule
- Answer · 15 calendar days from receipt
- Date of receipt
- 10 July 2026
- Computed
- Filing date
- Monday, 27 July 2026
July 2026
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
The system, in Amicus
Where each chapter lands in the product.
Web upload, iOS capture, connected drive, and email intake into one queue.
Per-page vision extraction, legal-document classification, and page-level citations for every fact.
Match-confidence gate, review queue, and a document verification workflow with permissions.
Case linking, computed deadlines, hearings, tasks, filing tracker, and notifications on web and iOS.
Lawyers and paralegals work from the web workspace; the iOS application carries the same cases, hearings, deadlines, and review queue into the courthouse, including documents cached for when there is no signal.
Legal operations
Show us the filing that keeps getting retyped.
We’ll look at how it arrives, what has to come off the page, which dates it creates, and who has to be accountable for them — then say plainly whether this is worth building.