The issue is not that the firm uses spreadsheets. The issue is whether a spreadsheet is an analysis tool, or whether it has quietly become the operating system for revenue, billing, filing, client service, and staff accountability.
23+ manual trackers by owner — the labor behind them feeds the $150K–$250K redeployment lane below
When one person owns ten operating spreadsheets, that person is a department. The matrix below itemizes every tracker.
Not every spreadsheet is a problem. A spreadsheet is fine for temporary analysis, import/export work, or one-time validation.
It becomes a problem when it is the source of truth, the workflow queue, the handoff mechanism, or the only report leadership trusts. That creates duplicate entry, stale data, invisible bottlenecks, and reporting meetings where people debate numbers instead of fixing the work.
Useful for one-time review, imports, audit checks, finance modeling, or data validation. Owner and expiration date required.
If staff use the sheet to decide who does what next, it belongs in Zoho, a case workflow, a task queue, or a calendar.
If leadership uses it weekly or monthly, it belongs in a dashboard fed by trusted systems or the reporting bridge.
This is the exhibit to classify the spreadsheet risk. Each row is a place where operating truth may be living outside the system and depending on people manually updating, reconciling, or remembering the next action.
| Tracker | Owner | Business Function | Risk Created | Replacement Path |
|---|---|---|---|---|
| 7-tab billing Google Doc | Helene | Cash, checks, refunds, chargebacks, bounces, LawPay | Billing exceptions live in a manual control surface | Finance module + payment sync queue |
| Daily retains tracker | Anna Barajas | Daily hires by team member | Revenue attribution depends on manual counting | CRM retain-stage report by owner |
| Cancellations / rehires | Anna Barajas | Cancelled clients who return | Reactivated revenue can be missed or double-counted | Deal reopen status + reason code |
| Bounce tracking | Angie Morales | Payment failures and daily calls | Collections depends on spreadsheet follow-up discipline | Payment failure task automation |
| Hires / conversion reporting | Chris Garcia | Weekly conversion numbers | Leadership sees delayed or manually assembled performance data | Lead → set → show → hire dashboard |
| Monthly filing tracker | Selene Gonzalez | Filed and unfiled cases | Production backlog is not visible in real time | Case-stage report from date fields |
| Rescheduling reasons | Selene Gonzalez | Why signings move | Failure patterns are hard to coach or fix | Required reason field on reschedule |
| Signature page tracker | Betty Jo | Original documents in office | Physical-document status detached from case record | Checklist field on matter record |
| Discharge tracking | Betty Jo | Post-discharge notification and gift box | Client completion experience depends on manual memory | Workflow trigger on discharge stage |
| Reviews tracker | Betty Jo | 5-star clients and gift boxes | Reputation moments are handled outside the system | Review score → follow-up automation |
| New hire welcome packages | Betty Jo | Welcome kits for retained clients | Onboarding consistency varies by handoff | Retain-stage welcome workflow |
| 341 scheduling | Betty Jo | Case numbers, trustees, hearing dates | Court-event visibility is manually maintained | Calendar + trustee/date fields |
| PP incidents | Valeria Beltrán | Practice management issues | System failures are tracked away from accountability queue | Issue queue / desk module |
| FYF text categorization | Valeria Beltrán | Manual text sorting | Client communication history fragments across tools | Unified client messaging thread |
| CTM fax log | Valeria Beltrán | Daily fax check | Inbound documents depend on someone checking the log | Email parser + case-linked task |
| Escalated clients | Valeria Beltrán | Attorney response delays | Escalations can sit 24–48 hours without system enforcement | SLA timer + auto-escalation |
| Call performance | Valeria Beltrán | Answer rates and agent call metrics | Phone performance is not tied directly to client outcomes | Call analytics dashboard |
| Coaching log | Valeria Beltrán | Staff training notes | Coaching history is separated from performance trend | Staff coaching module |
| Attendance tracker | Valeria Beltrán | Staff attendance | Capacity planning is detached from workload data | People / attendance module |
| Sticky notes + Word doc | Ana Guerrero | Paralegal/attorney lookup by case type | Routing rules live in human memory and side documents | Assignment rules by case facts |
| Client retain form → Google Doc | Slack workflow | New retain intake | Retain handoffs become a document instead of a work record | Retain Desk control record |
| Marketing tracking doc | Helene | Lead/source performance since 2016 | Marketing decisions depend on manually maintained history | Analytics fed by pipeline source data |
| Signing checklist | Paralegals | Pre-signing preparation | Readiness varies by checklist discipline | Stage transition checklist |
Billing, filing, client service, marketing, and 341 work each have their own manual operating layer.
Names, case details, payment status, filing status, and next actions move through multiple side systems.
The firm is paying experienced people to reconcile data that should already be live.
Recoverable annual impact by lane — conservative to aggressive, from the Blueprint math
Total recoverable impact: $850K–$1.57M annually. Each lane’s math is itemized in the Plan (step 03).
This is why the Blueprint matters. We are not proposing “more software.” We are deciding which spreadsheets stay as analysis tools, which move into Zoho workflows, and which require the Iron Noodle reporting bridge.