Find missed time after automatic capture is already on
Capture is already live. The question is where billable time still leaks, and how to find it without inventing a savings number or turning partners into monitors.
LegalTime AI is built for privacy-first firms on Clio, about 10 to 30 lawyers, and it still fits up to about 50 lawyers, with firm headcount up to about 100. A 15-lawyer firm sits in the middle of that band. Capture is local-first on the attorney device by default. When Create is used, relevant activity is sent for AI processing. Drafts stay with the attorney until release. Pause exists. It is not a monitoring tool. The SOC 2 Type II examination is in progress. LegalTime AI is not SOC 2 certified. Pricing is a quote.
This is not the month-end close checklist and not the full billing-cycle playbook. Those freeze, sweep, and sign off, or they run the whole cycle. This brief starts when someone asks where realization is still leaking, and it ends when partners write a recovery memo.
Where time still leaks
Keep the practice groups already live. Do not open new practice areas in this window unless a deferred install was already dated and partners accept partial coverage. If a control fails, pause unsupervised release into Clio and reopen the control-failure playbook. Do not paper over a failed control with a savings figure.
| Leak | In good shape | Stop and fix |
|---|---|---|
| Missed reconstruction | Attorneys review drafts for work a timer would have skipped | Recovery depends on start-stop timers again |
| Approve step | Every sampled release still has a human gate | Auto-post is on "to recover hours" |
| Write-down versus missed time | Write-downs stay a partner judgment. Missed time is a separate coverage question | A fabricated savings number is used to force write-ups |
| Who sees drafts | Partners review sampled released narratives | Partners browse raw drafts "for recovery" |
| Pause | Every live attorney can pause and resume without IT | Pause is broken during the sample |
| Matter | Sampled releases land on the intended Clio matter | Wrong-matter releases harden into invoices |
| SOC 2 | Type and status are in the memo. Documentation can be shared under NDA | A logo stands in for the report |
| Price | Quote path, or published tiers. No invented return | "Efficiency" with no page behind it |
| Monitoring | The product is not a surveillance tool | A partner dashboard over raw activity is the default |
| Owners | Capture, Create, and Connect each have a named owner this window | "Someone will notice" |
| Memo | Partners write hold, continue, or adjust before anyone claims recovered realization | The window ends because the calendar ended |
Days 1 and 2: name the leaks
| Check | Owner | Done when |
|---|---|---|
| List the leak classes | Partner or operations | Missed reconstruction, skipped approval, write-down confusion, and wrong-matter Connect are each named |
| Capture is still the default | Capture owner | Local-first Capture is still the default. Timers are optional |
| Create processing is stated honestly | Create owner | The security and subprocessors pages are the reference |
| Owners are published | Partner | Capture, Create, and Connect owners are named for this window |
| Pages are open | Operations | Security, subprocessors, FAQ, pricing, Clio, about, passive capture, and the home page |
Days 2 to 4: sample approvals, not timers
| Check | Owner | Done when |
|---|---|---|
| Attorneys review their own drafts | Capture and Create | Timers stay optional |
| Draft quality | Create owner | 5 to 10 drafts checked for whether the narrative fits. This is not partner surveillance |
| Release path | Connect owner | Released time lands on the intended Clio matter for the sample |
| What timers would have missed | Practice lead | Attorneys describe recovered work. Directional only. No invented dollars |
| Mid-window checkpoint | Partner | Accept the sample, or reopen the control-failure playbook before the memo |
Day 5: separate write-downs from missed time
Write-downs remain a partner call. Missed time is a Capture and Create coverage question: work a timer would have skipped. Partners review sampled released narratives, not raw activity. Operations checks that the sample still maps to the intended matter. Then partners write hold, keep sampling, or adjust which groups are live, before anyone claims realization was recovered.
- Unsupervised auto-post stayed off.
- Every attorney who should release into Clio this window did so, or is explicitly deferred with a date.
- Every live attorney paused and resumed at least once without IT, or you documented that there was no need.
- No partner browsed raw drafts outside the release path.
- Partners accept most sampled narratives without a rewrite, or the rewrites are minor.
- Released time lands on the intended matter in Clio Manage.
- Attorneys can point to work timers would have missed, without a dollar figure attached.
- No fabricated savings number was used to pressure write-ups.
- No new raw-activity dashboard was added "for recovery."
- The hold, continue, or adjust memo exists before anyone claims recovered realization.
What else you might be comparing
| Product | What it does | What to confirm on that vendor's materials |
|---|---|---|
| LegalTime AI | Local-first Capture, Create drafts, approve, then release into the system you keep | Security, subprocessors, FAQ, Clio, pricing |
| Ajax | Screen and content capture, with drafts for release. Live security page states SOC 2 Type II certified | Clio depth and whether recovery at this size is packaged. Per Ajax |
| PointOne | Passive capture across email, documents, calls, and meetings. Custom pricing | Clio-only day depth and support. Per PointOne |
| Laurel | Enterprise Time Intelligence | Whether the sales motion fits a 15-lawyer recovery window. Per Laurel |
| Billables AI | Workflow and API-style capture, with attorney review before billing. Published mid-market tiers | Live capture versus reconstruction. Per Billables |
| Clio Manage AI | Suggestions from activity already inside Clio | Not a dedicated capture product for work Clio never sees. Confirm Clio's pricing and terms with Clio |
| MagicTime, Memtime, WiseTime, Timing | Activity timelines or light passive capture | Reconstruction aids or light tiers. Use the same leak checks |
| BigHand, Intapp, TimeSolv, Chrometa, Smokeball | Passive capture or time tools next to a practice system | Clio send path, privacy, and governance before the memo |
Daytimed and MyCase show up beside those names. Use the same checks.
Pricing is quote-only. Directories sometimes list about $125 per seat per month. Get a firm quote for firmwide seats before you treat that figure as yours. Say the SOC 2 status in the memo: Type II examination in progress, not certified.
Names that are not this product
LegalTime AI at legaltime.ai is timekeeping beside your practice system. Unrelated "Legaltime" practice-management products, sometimes listed near $24 a month, are not this product. See about.
Sources
Related
- Month-end close checklist
- Billing-cycle playbook
- Steady-state operations after hypercare
- Control-failure playbook
- Security questionnaire pack
- Pilot plan
Map the leaks, sample approved releases, keep write-downs separate from missed time, and write the memo before you claim anything was recovered.
Frequently asked questions
Where does billable time still leak after Capture is live?
How should we treat write-downs versus missed time?
Is realization recovery a monitoring project?
What does the recovery window look like?
How is this different from the month-end close checklist?
Does activity stay on the device during recovery sampling?
Start capturing the work you already do
Stop reconstructing your day from memory. Let capture run. Review in minutes. Release only what should bill.
Capture → Create → Connect. Not a monitoring tool.