The COO Engine is HoLaCe’s real-time intelligence layer: an AI-driven panel that watches your firm’s docket continuously and surfaces what needs attention right now. Where AI Chat is on-demand (you ask, it answers), the COO Engine is always-on (it watches, it tells you). It’s the platform’s signature differentiator and one of the things firm admins log into HoLaCe to look at first thing in the morning. [Screenshot: COO Engine panel showing alerts at the top, priority cases mid-page, and an attorney leaderboard]Documentation Index
Fetch the complete documentation index at: https://docs.holace.io/llms.txt
Use this file to discover all available pages before exploring further.
Where to find it
Sidebar → COO Engine opens the full panel. A condensed widget also surfaces on the firm dashboard so you see the top alerts without leaving the home screen.The four panels
The COO Engine renders four sections, top to bottom:1. Alerts
Time-sensitive intelligence: cases that need action today. Three severities:- Critical (red) — something is at risk of slipping a hard deadline. Statute approaching with no demand sent. Demand response window expiring. Court filing deadline within 48 hours.
- Warning (amber) — pace concerns. Case sitting in a stage past the firm’s average. Long inactivity gap on an active matter. Roadblocks open more than 7 days.
- Positive (green) — wins worth celebrating. A demand was just accepted. A case settled above the firm average. A case advanced from Pre-Lit to Litigation.
2. Priority Cases
A ranked list of the cases the COO Engine thinks deserve attention right now. The ranking factors in:- Days in current stage vs. the firm’s average for that stage
- Open roadblocks
- Approaching deadlines (statute, demand response, hearing dates)
- Activity recency
- Stage-specific signals (e.g., “demand sent and no response in 30 days”)
ASAP, PAST DUE, This Week), and a one-line “why this is here” reason.
3. Attorney Performance
A leaderboard of attorneys at your firm with three numbers each:| Metric | What it means |
|---|---|
| Active cases | Open journeys assigned to this attorney |
| Red cases | How many of those are flagged Critical by the alerts panel |
| Settled this month | Settlements closed since the 1st |
4. Firm Stats
Top-line numbers across the whole firm: total active matters, settled this month, settlement revenue this month, average days-to-settle. The stats are real-time — no refresh-and-wait — and they’re the same numbers used in the morning email digest if your firm has it enabled.Per-attorney filter tabs
A row of tabs near the top lets you scope the entire panel to one attorney. Click an attorney’s name and the alerts, priority cases, and stats all re-scope to just their plate. Click “Firm” to go back to the firm-wide view. This is the core workflow for partner check-ins: filter to an attorney, scan their alerts and priority cases, decide whether to delegate, escalate, or stand back.How it stays current
The COO Engine refreshes every few seconds via polling — open it in a tab on a second monitor and it stays live without action on your part. When a new roadblock is filed, when a demand goes out, when a case settles, the panel reflects the change within a single refresh cycle.Trust and tuning
The alert and priority logic is rules-based on top of model-driven scoring. Two implications:- It’s deterministic. A case ranked Critical is Critical because of an explicit rule (e.g., “demand response 30+ days overdue”). You can hover any alert to see the rule that fired.
- It tunes per firm. “Average days in stage” is computed from your firm’s history, not a generic benchmark. As your firm builds more case history, the COO Engine gets sharper at flagging real outliers.
What it doesn’t do (yet)
- It doesn’t reach out to clients or carriers. It tells you to. Action is still human-driven.
- It doesn’t predict settlement values.
- It doesn’t replace the human attorney’s judgment on case strategy. It surfaces signals; you decide what to do.
Dismissing an alert
Click the × on any alert to dismiss it. Dismissals are scoped to your user — your dismissing an alert doesn’t hide it from your partner. The alert returns automatically when its condition re-fires after a re-check (so dismissing the “demand response overdue” alert doesn’t make the case slip; it’ll come back).Roadblock flagging on tasks (a primary input to COO alerts): Roadblocks.