A phased build that runs entirely inside your own environment. Your family, immigration, and personal injury files never leave the firm. We start with the repetitive work that slows your team down, and we prove each piece works before we move to the next.
Carraig runs seven lawyers and four support staff across family law, commercial litigation, wills and estates, personal injury, sports law, administrative law, and immigration and refugee protection, on Clio. The goal you set is specific: take the repetitive admin off support staff first, before any wider change. This proposal holds to that. Everything below automates work your team already does by hand today, and nothing changes how a lawyer runs a matter.
A lawyer calls in and dictates the matter number, time spent, and a description. The system transcribes it, structures the entry, and writes it into the correct matter record in Clio. Time and notes captured on the move, no manual data entry.
Incoming documents are read, classified, and filed to the correct client and matter folder automatically. The manual sorting that support staff do today is handled before it reaches their desk.
Scheduling, reminders, and calendar upkeep handled with far less manual input, integrated with the calendar that sits alongside Clio.
For family law asset division, the system extracts income, assets, debts, and dates from F8 financial statements and supporting documents, then populates a Scott's Schedule for a lawyer to review. The most document-heavy task on your list, prepared automatically.
You raised client privacy repeatedly, and it is the right instinct for family, immigration, and personal injury work. So privacy is not an add-on here, it is the foundation the whole build sits on.
Everything runs inside your own environment. The voice pipeline transcribes and structures dictation locally rather than through a public transcription service. Document extraction for F8s runs locally. Client data stays on infrastructure you control, which is what keeps the build defensible under your professional obligations.
Clio provides an open API and supported integration paths. That means the logging assistant and file routing write into your matter records and folders programmatically, mapped to Clio's own fields for matter number, time, and description. No fragile screen automation, and no change to how your team already uses Clio day to day. Confirming the exact scope of Clio's API against your plan is the first step of Phase 1, so the integration is validated before build.
The two pieces with the clearest, fastest relief for support staff. We stand up the local foundation, build both, and get them running in your environment.
Once Phase 1 is live and proven, we add calendar management and the Scott's Schedule automation, the most differentiated and technically involved piece, specific to your family law practice.
All figures in CAD. Phase 2 can begin once Phase 1 is delivered and running.
You asked to see it working. This is the Phase 1 voice logging flow, running live in your browser. Dictate a matter entry with your microphone, or play a sample, and watch it get transcribed, structured into the fields Clio expects, and written into a matter time entry. In your firm this runs locally, on infrastructure you control.
We will arrange reference calls with existing clients who have a live implementation and have agreed to speak with you, so you can hear how the build runs in practice before you commit. We will confirm those introductions ahead of the proposal meeting.