The week after AI time tracking cutover
The day of cutover is not the end. The first week is when you find out whether Capture is still the default, whether people can still pause, whether approval stayed on, and whether sampled Clio entries still hit the right matter. Write continue, or reopen. A savings figure does not force continue. The calendar ending the week is not a result.
LegalTime AI is built for privacy-conscious firms on Clio, ideally about 10 to 30 lawyers, comfortable up to about 50, with headcount up to about 100. It sits beside the practice system. Capture is local-first on the attorney device by default. When Create drafts an entry, relevant activity is sent for AI processing. Drafts stay with the attorney until release. The attorney approves before release. Pause exists. This is not a monitoring tool. A SOC 2 Type II examination is in progress. LegalTime AI is not SOC 2 certified. Pricing is quote-only. A directory note sometimes cites about $125 per seat per month. Get a firm quote.
The cutover runbook is the day itself. The acceptance test plan is what you ran before firmwide. This list is the first week after. A failed gate reopens the cutover rollback, the exceptions brief, or the control-failure playbook.
The first week
| When | What you check | It holds when | Owner |
|---|---|---|---|
| The morning after | Did cutover end with a written go? | The written go is on file, or a dated waiver a partner signed | Partner and operations |
| The morning after | Is Capture still local-first on every in-scope device? | Still the default. Timers still optional. Install still logged | Capture owner and IT |
| That day, or day 2 | Can every in-scope attorney still pause without IT? | Pause and resume logged again, once per attorney, in week one | Capture owner |
| Day 2 | Can attorneys restate Create processing without surprise? | When Create runs, relevant activity is sent for AI processing | Create owner |
| Each day of the week | Is approval still on? | Unsupervised posting stays off through week one | Create and Connect |
| Day 2 or day 3 | Do sampled releases still hit the intended Clio matter? | Beside Clio Manage. The sample is correct | Connect owner |
| Day 3 to day 5 | Has a quality sample been published? | A released-only sample rate is named. No raw-activity feed for partners. See the quality sampling brief | Partner and operations |
| Any severe exception | Is the exceptions path usable? | The exception list and the severity ladder are available, with owners already named | Partner and operations |
| End of week one | Continue, or reopen? | A partner signs continue, or a dated reopen with an owner | Partner and operations |
| Across the week | Did timers stay optional? | Capture stayed the default. Timers did not become the real workflow again | Capture owner and a partner |
Keep these open: security, subprocessors, the FAQ, pricing, the Clio integration, about, passive time tracking, and the home page.
Say the SOC 2 sentence in the week-one kickoff: examination in progress, not certified.
What continue requires
| Control | Continue | Reopen |
|---|---|---|
| Cutover go | The written go is on file | "We think cutover worked," with nothing written |
| Capture local-first | The default held on in-scope devices | A silent move off the device, with no memo |
| Create processing | Attorneys can restate it | Surprise when Create runs |
| Approval | On through week one | Unsupervised posting turned on |
| Clio matter | Sampled releases are correct | Wrong-matter releases start to harden |
| Quality sample | A rate, and released entries only | Partners browse raw Capture "to validate" |
| Exceptions path | Owners named. A severity ladder exists | No path when something severe hits |
| SOC 2 honesty | Examination in progress, not certified | A "certified" claim |
| Pricing honesty | Quote-only | A fabricated savings number used to force continue |
| Not monitoring | Explicit | A raw-activity dashboard built for "validation" |
| Named owners | Capture, Create, Connect, IT, and a partner | "Someone will validate" |
| The memo | Written continue or reopen | The week ends because Friday arrived |
The same week on other tools
| Product | What it does | What to confirm in week one |
|---|---|---|
| LegalTime AI | Local-first Capture, Create, Connect after approval, beside Clio. | Security, subprocessors, FAQ, pricing, Clio, about, and passive time tracking |
| Ajax | Screen and content capture, with drafts for release. Security page states SOC 2 Type II certified. | Clio depth and midsize week-one packaging, on a demo |
| PointOne | Passive capture across email, documents, calls, and meetings. Custom pricing. | A Clio-only day, and support for the week-one gates |
| Laurel | Enterprise time intelligence. | Whether a midsize firm is in the packaging. An enterprise motion may be larger than this week |
| Billables AI | Workflow and API-style capture, with attorney review. Published mid-market tiers. | Live capture versus reconstruction, on a demo |
| Clio Manage AI | Suggestions from activity already inside Clio. | Many firms still add a capture layer. Confirm terms with Clio |
| MagicTime, Memtime, WiseTime, Timing | Timelines or light passive capture. | Score the same week-one gates |
| BigHand, Intapp, TimeSolv, Chrometa, Smokeball | Passive capture or practice-system time tools. | Confirm the Clio send path and privacy before the continue memo |
Daytimed and MyCase belong in the same "confirm on their materials" group when they are still on the table.
How the week maps to the product
- Capture stays local-first. Pause is rechecked, not assumed. See passive time tracking and security.
- Create stays an attorney-only draft. When Create runs, relevant activity is sent for AI processing. See the FAQ and subprocessors.
- Connect stays approval into Clio Manage. See the Clio integration.
Quality sampling is released narratives, at a published rate. It is not a reason to watch raw activity.
Names to keep straight
LegalTime AI (legaltime.ai) is timekeeping beside your practice system. "Legaltime" in directories can mean an unrelated practice-management product, sometimes listed near $24 a month. See about.
Sources
Related
- Cutover day
- Acceptance tests
- Readiness before install
- When a control fails
- Quality sampling
- Exceptions after go-live
Run the week, then write continue or reopen before you call validation done. Start a 30-day free trial or book a 15-minute demo.
Frequently asked questions
What do we recheck after cutover day?
What is a quality sample allowed to include?
What if a check fails?
What should the week-one kickoff say about SOC 2 and Create?
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.