ERPat Module Guide
Law Office
The Law Office module runs a legal practice inside ERPat: confidential client intake with a recorded conflict-of-interest check, matters with team-based access control, a court docket with lawyer-verified deadlines and automatic reminders, matter tasks, and a document file per case.
Who this module is for
- Managing / supervising partners — decide intake acceptance, monitor the deadline verify queue, read the portfolio reports.
- Handling lawyers — run their matters, verify deadlines against the source document, keep the docket current.
- Paralegals & legal staff — encode intakes, run conflict searches, maintain parties, upload documents, work tasks.
- Firm administrators — grant permissions, maintain practice areas and matter types, configure reminder ladders.
The problems it solves
- Missed court deadlines — the single biggest malpractice risk. Deadlines are drafted, then verified by a permitted lawyer against a cited source; verified deadlines are immutable, reminded on a configurable ladder, and block a matter from closing while open.
- Undetected conflicts of interest — every prospective client and adverse party is searched against the firm's whole party corpus (including declined intakes) with exact, partial, token and phonetic passes; every search, hit and human disposition is recorded permanently.
- Confidentiality leaks — intakes are visible only to their owner, the intended lead and conflict reviewers; matters can be restricted to their team, enforced in the database query layer everywhere (lists, calendar, reports, widgets, APIs), with permitted views access-logged.
- Scattered case files — parties, hearings, deadlines, tasks, documents and a full activity timeline live on one matter workspace.
Guide map
| Page | Read it when… |
|---|---|
| Getting Started | You are enabling the module for the first time: migrations, permissions, reference data, demo data. |
| Operations | You work in the module daily: intake SOP, conflict check, matter workspace, docket & verification, tasks, documents. |
| Administration | You manage access, settings, restricted matters, the reminder cron, the demo seeder, and the APIs. |
| Reference | You need the exact screens, permissions, tables, routes, jobs, widgets and API endpoints. |
| Research | You want the evidence trail — what was verified against the live module files when this guide was written. |
| FAQ | Something is not behaving as expected, or you want the confidentiality/conflict-search limitations spelled out. |
⚠
Honest scope. The conflict checker is a search assist, not clearance automation — a lawyer
always makes the call, and the module records that decision. Deadline dates are encoded by people, not
computed from procedural rules. Read the FAQ for the full limitation statement.