Skip to main content
Back to The Qase Journal

Why Spreadsheets Are Holding Your Referral Service Back

Why Spreadsheets Are Holding Your Referral Service Back

Spreadsheets are genuinely good tools. They are flexible, accessible, and familiar to almost every administrative professional. For a lawyer referral service processing a handful of matters per week, a well-maintained spreadsheet can do most of what needs to be done. This article is not an argument against spreadsheets as a category — it is a specific argument about what happens when a referral service scales beyond the point where spreadsheet-based tracking is sustainable, and why the problems that emerge are not just operational inconveniences but compliance risks.

The inflection point is usually somewhere around thirty to fifty active referrals per week, though it depends heavily on staff capacity and the complexity of the service's panel. Below that threshold, a disciplined coordinator can maintain accurate records manually. Above it, the failure modes become systematic rather than occasional.

The Failure Modes Are Structural, Not Human

When administrators at growing referral services describe their tracking problems, they often frame them in terms of individual errors: a row that was updated incorrectly, a formula that broke when a column was inserted, a version of the file that was emailed to the wrong person and edited in parallel. These are real problems, but they are symptoms of a structural limitation rather than a personnel problem.

Spreadsheets are not designed for multi-step workflow tracking. A referral is not a static record — it is a series of events. A caller contacts the service. An intake form is completed. A lawyer is matched and contacted. The lawyer accepts or declines. If they decline, a re-referral is made. The client is notified. The lawyer completes the consultation. A forwarding fee invoice is generated. Payment is made. The matter is closed. Each of these events needs to be recorded in a way that is attributable, timestamped, and linked to the same underlying record.

In a spreadsheet, representing this lifecycle requires either a very wide row with status columns for each step — which becomes unreadable — or multiple linked sheets that need to stay synchronised manually. Neither approach scales gracefully, and both create opportunities for records to diverge from reality in ways that are not immediately visible.

The Forwarding Fee Reconciliation Problem

Of all the tracking failures that referral services encounter, forwarding fee reconciliation is the one with the most direct compliance consequence. Under law society rules, the fee arrangement between the referral service and panel lawyers needs to be documented, the amounts need to be within the approved schedule, and the service needs to be able to account for fees collected against referrals made.

In a spreadsheet model, the forwarding fee lifecycle is typically tracked in a separate column or a separate sheet from the intake record. When a coordinator matches a caller to a lawyer, they make a note in the referral log. The fee becomes payable when the lawyer accepts. An invoice is expected from the lawyer or generated by the service. Payment arrives eventually. The payment is noted somewhere — perhaps in the spreadsheet, perhaps in an accounting system, perhaps in an email thread.

By the time a law society reporting period ends and someone needs to reconcile referrals against fees collected, the data exists in three or four places that were never designed to be reconciled with each other. A growing referral service in Ontario, for example, might find that it has a referral log with 400 entries, a fee invoicing record with 350 entries, and a payment confirmation file with 310 entries — and no clean way to determine which 50 referrals never generated an invoice, or which 40 invoices were never paid, without reading through each record individually.

That gap — between what the service believes it has collected and what it can actually document — is where compliance risk lives.

Panel Roster Currency: The Problem Nobody Notices Until It Matters

A referral service's panel roster is its core operational asset. The quality of every match depends on the accuracy of that roster — which lawyers are currently accepting referrals, in what practice areas, in which languages, with what geographic scope, and with what capacity constraints. In a spreadsheet model, this roster is almost always maintained by one person and updated reactively — when a lawyer calls to update their information, when an email bounces, when a referral is declined and the coordinator notes that the lawyer seems unavailable.

This means the roster is perpetually a few weeks behind reality. Lawyers who have reduced their capacity but not yet notified the service continue to appear as fully available. Lawyers who have updated their practice focus continue to receive referrals in areas they no longer handle. The mismatch rate — referrals that are declined because the matched lawyer cannot actually take the matter — is a direct measure of panel roster inaccuracy, and it has a real cost: the caller has to wait for a re-referral, the service coordinator has to make additional contacts, and the panel lawyer's confidence in the service's matching quality erodes.

We are not saying that purpose-built systems eliminate panel management complexity — they do not. Managing a panel of forty or sixty lawyers with varying availability, practice areas, and linguistic capacity is genuinely complex regardless of the tools. The question is whether that complexity is managed through a system that surfaces discrepancies proactively or one that allows them to accumulate until they cause a problem.

Reporting: The Quarterly Scramble

Many lawyer referral services are required to submit periodic reports to their governing bar association or law society covering referral volumes, matter type distribution, panel composition, and fee collection. These reports serve an accountability function: they demonstrate that the service is operating within its mandate and handling public trust appropriately.

Under a spreadsheet model, producing these reports is a manual assembly exercise. The coordinator or administrator pulls data from the referral log, the fee tracking sheet, the panel roster, and any supplementary records, reconciles inconsistencies, and produces a summary. The time this takes depends on how cleanly the underlying data was maintained — in practice, it often takes two to three days of focused work to produce a report that could, with structured data, be generated in an afternoon.

More problematically, the accuracy of the report is limited by the accuracy of the underlying records. If the referral log is missing three entries from a busy period in November, those referrals will not appear in the annual report. The service may not know what it does not know.

What a Purpose-Built System Changes — and What It Does Not

The transition from spreadsheet tracking to a purpose-built referral management system does not change the fundamental work of running a referral service. Coordinators still conduct intake interviews. Panel rosters still need to be managed. Lawyers still need to be contacted when a referral match is made. Forwarding fees still need to be invoiced and collected.

What changes is the infrastructure around that work. Intake notes are structured rather than freeform, so the attorney brief is generated automatically. Panel status is updated in the system rather than in a spreadsheet column, so the roster is accurate in real time. Fee records are linked to referral records from the moment a referral is accepted, so reconciliation is not a retrospective exercise. Reporting queries run against a consistent underlying dataset, so the outputs are accurate without manual assembly.

The organisations that make this transition most smoothly are those that resist the temptation to build a perfect spreadsheet-replacement spec before migrating. The right approach is to start with the core workflow — intake, panel lookup, referral logging — get it running cleanly, and then expand to fee tracking and reporting once the foundation is stable. The cost of maintaining inconsistent data across a migration is higher than the cost of a phased transition.

The organisations that stay on spreadsheets the longest are usually not doing so because they believe the spreadsheet is better. They are doing so because they have not yet reached the point where the cost of the status quo is obviously higher than the cost of the transition. For most growing referral services, that calculation is closer than it appears.

See how Qase handles this for your service.

Book a 30-minute demo with Dan Zollmann, Founder & CEO.

Request a Demo