Spreadsheet replacement
Replace the legal operations spreadsheet with a connected AI workflow.
Move law firms using spreadsheets for non-legal operational tracking from fragile spreadsheet handoffs into a focused workflow with clearer ownership, live context, and connected execution.
Introduction
Matter administration held in one fee earner’s memory.
Almost every legal operations process starts in a spreadsheet, and for a while that is the right call. A sheet holding matter intake status, document checklists, key operational dates, and responsible fee earners costs nothing, takes an afternoon, and fits the process exactly — because the person who built it is the person who runs it.
The operational tracker sits alongside the practice management system rather than inside it, so the two disagree and the sheet is the one people actually look at. The sheet works while each fee earner holds their own caseload. It fails when cover is needed, because the administrative state of a matter — what is outstanding, what date is next — is written nowhere a colleague can read.
What follows covers that transition for law firms using spreadsheets for non-legal operational tracking: what the sheet holds, why it fails, what the replacement records instead, and — set out plainly further down — the case for leaving it where it is.
The problem
Four ways a matter sheet fails the firm.
Matter administration is a set of dates and outstanding items across a caseload, and a sheet models it per matter. The failures happen in the aggregate — the document requested and never chased, the date approaching with nothing prepared — and the aggregate is exactly the view a per-matter row cannot produce.
Two fee earners maintain the shared matter sheet on their own rhythms and neither can tell whether the other has already chased a client for the same document.
The sheet holds matter intake status, document checklists, key operational dates, and responsible fee earners, and the authoritative version of most of it already lives in Google Drive or Gmail. The matter file says documents requested, the client says they sent them three weeks ago, and both are looking at different mailboxes.
You're likely here because
- Covering a colleague’s matter starts with reading their email
- The operational tracker sits alongside the practice management system rather than inside it, so the two disagree and the sheet is the one people actually look at.
- When a row is stale, an administrative date is missed because the row holding it was never updated
The operating problem
Why the current process stops scaling.
Move law firms using spreadsheets for non-legal operational tracking from fragile spreadsheet handoffs into a focused workflow with clearer ownership, live context, and connected execution.
Failure mode 1
No cross-matter view
Outstanding items exist per matter and the pattern exists nowhere. Nobody can produce the list of everything that is waiting, which is the only list that would get anything cleared.
Failure mode 2
Administrative dates have no lead time
A date in a cell does nothing until it arrives. Preparation is triggered by somebody remembering, which is a control that fails silently and only occasionally.
Failure mode 3
Correspondence is not linked
What a client actually sent is in a mailbox and the matter record is a tick box. Disputes about what was provided cannot be settled from the file.
Failure mode 4
The state lives with a person
Cover means reading somebody’s email. That is not a workflow, and it is the point at which a caseload becomes a personal dependency rather than a firm asset.
The record model
What the replacement holds that the sheet cannot.
- Administrative state
- Held separately from any legal analysis. This system tracks dates, documents, and ownership; the separation is the design rather than a caveat.
- Outstanding items with age, across matters
- The aggregate view is where the failures live and is exactly what a per-matter sheet cannot produce.
- Key date with preparatory steps and lead time
- Surfaced in advance rather than on arrival, which is the difference between a plan and a scramble.
- Responsible fee earner and supervisor
- Because supervision is a regulated obligation and a cross-matter view that omits it is not usable by the firm.
- Client correspondence received
- Observed from the mailbox, so what a client says they sent and what the file records can be reconciled without an argument.
- Confidentiality and barrier scope
- Enforced per matter, since a cross-matter view is precisely the artefact most likely to breach an information barrier.
- Retention and destruction rule
- Per your regulator and the firm’s policy rather than a general default, because file retention carries dates with consequences.
How it works
From a matter list to tracked administration.
Step 01
Describe the legal operations process
Model the administrative lifecycle of a matter as distinct from the legal work. Everything here sits on the administrative side of that line and stays there.
Step 02
Connect the systems of record
Email supplies client correspondence and what has been received, the document store holds files, the calendar holds dates. Reading email makes outstanding items observable rather than remembered.
Step 03
Build the operating surface
The cross-matter view of outstanding items by age. It is where the value concentrates and it requires no change to how anyone practises.
Step 04
Migrate the workflow, not just the data
Live matters move with their administrative state. Closed files stay in the existing system under their retention rules.
Step 05
Route the exceptions
An administrative date approaching without the preparatory step complete surfaces to the fee earner and the supervisor, because the cost of missing one is not proportionate.
Step 06
Measure operational deadlines met without escalation
Outstanding requests older than expected turnaround, and administrative dates met without a late scramble. Both are countable and neither touches legal work.
Implementation path
Tracking matters without touching legal judgement.
- 01
Write the boundary between administrative tracking and legal analysis, and have it reviewed. It is the design constraint rather than a disclaimer added afterwards.
- 02
Build the cross-matter outstanding view first. Per-matter information already exists somewhere; the aggregate does not, and that is where the failures hide.
- 03
Have supervision, confidentiality, and retention requirements reviewed before go-live. These are regulated obligations rather than configuration preferences.
- 04
Baseline outstanding document requests and their age across the caseload. Most firms have never seen this number and find it uncomfortable.
- 05
Run it alongside the sheet for one full cycle, then retire the file only after the parallel run holds.
Controls
Controls that matter.
Control 01
A hard boundary against legal advice or analysis — this tracks administration and every question of judgement stays with the qualified professional
Control 02
Confidentiality and access enforced per matter, including information barriers where the firm operates them
Control 03
Retention and destruction handled per your regulator’s requirements rather than by a general default
Build with Launch
Turn the operating requirement into working software.
- • Build a legal operations app
- • Add forms, views, status, and workflow logic
- • Create role-specific dashboards
Operate with Grow
Keep the workflow connected after the interface exists.
- • Attach follow-up where the workflow touches revenue
- • Keep customer context connected
- • Measure activity through the same context
Connected context
Keep systems of record. Fix the gaps between them.
These are representative connections. UbiGrowth supports 700+ connections across business systems. Connection availability and permissions depend on workspace configuration.
The case against
When the spreadsheet is still the right answer.
If one fee earner holds a small caseload and never needs cover, the sheet is a personal aid and that is enough. The trigger is cover, or a caseload that outgrows one memory.
Examples
Three administrative failures that stop recurring.
The document requested and never chased
A cross-matter view of outstanding requests by age turns a per-matter oversight into a visible queue, which is the only form in which it gets cleared.
Covering a colleague’s caseload
Administrative state on the matter rather than in a mailbox means cover starts from a readable position rather than from an afternoon of reading correspondence.
The date that arrived sooner than expected
Key dates with preparatory steps surfaced in advance is the difference between a plan and a scramble, and lead time is the field a spreadsheet never holds.
Measurement
Measure the workflow, not the demo.
Choose a baseline before implementation so speed, quality, exceptions, and downstream impact can be compared using the same definitions.
Model the value of moving repetitive spreadsheet work into a connected workflow.
Use the ROI calculator with your own workload, lead volume, close rate, and deal assumptions. The result is illustrative, not a guaranteed outcome.
Open the ROI calculator →Limitations and considerations
What this deliberately does not do.
- This tracks administration and must not be used for legal advice, analysis, or any judgement reserved to a qualified professional. That is the design boundary rather than a disclaimer.
- Limitation periods and court deadlines carry consequences no tracking system should be solely relied upon for. Treat it as a supporting record alongside existing controls.
- Client confidentiality, conflicts, information barriers, and file retention are regulated obligations that vary by jurisdiction. Configuration can support them; the assessment belongs with whoever is accountable at the firm.
- Connector coverage varies: Google Drive, Gmail, Google Calendar are representative rather than guaranteed, and the fields exposed depend on your workspace permissions.
Keep people in control of consequential decisions.
Automate bounded, observable work first. Keep explicit approvals, escalation paths, permissions, and auditability around financial, legal, clinical, employment, coverage, or other consequential decisions. The goal is faster execution with clearer control—not unbounded autonomy.
FAQ
Questions teams ask before moving off the sheet.
Does this give legal advice?
No, and it is designed so that it does not. It tracks administrative state — outstanding items, dates, documents, ownership — and every question of legal analysis remains with the qualified professional handling the matter.
Can we rely on it for limitation dates?
Not solely. Use it as a supporting record alongside the controls you already have. The consequence of a missed limitation date is severe enough that a single point of reliance is inappropriate regardless of the system.
How does it handle confidentiality between matters?
Access is scoped per matter and supports information barriers where the firm operates them. Whether a given configuration satisfies your regulator is an assessment for whoever is accountable, and it belongs before go-live.
Will it work alongside our practice management system?
That is the usual arrangement. Practice management stays authoritative for time recording and billing; this holds the administrative matter state those systems model weakly and that currently lives in email and a spreadsheet.
Do we still need Google Drive?
Yes. Google Drive stays authoritative for what it owns, and the new surface reads it through a governed connector rather than storing a second copy.
How do we know whether it actually worked?
Measure operational deadlines met without escalation against the baseline you took before switching, alongside manual updates removed and how often a record turns out to be stale.
Start with ARIA
Ask ARIA to build the replacement.
Describe what the spreadsheet is really doing. ARIA plans the operating surface, connects the systems that stay authoritative, builds it, and keeps it running.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Rebuild the legal operations workflow, not the file.
Build the cross-matter view of outstanding items first, keep the boundary against legal judgement explicit, and have retention reviewed before go-live.