Key takeaways
- A well-run spreadsheet is fine for a small firm; most UK legal businesses employ four people or fewer[1].
- Move on when enquiries are lost between people, reports take hours, or you cannot control who sees what.
- Personal data in a spreadsheet carries the same UK GDPR duties as data in a CRM, including breach reporting[2].
- Choose a CRM on workflow, conflict search, reporting and data controls before features.
- Migrate in stages: clean the data, run both in parallel for a month, then switch.
The real question
Every firm tracks enquiries somehow: a paper diary, an email folder, a shared spreadsheet, an intake module in the case management system or a dedicated legal CRM. The question is not which tool is best in general. It is whether the tool you have still lets you answer three things reliably: who is dealing with each enquiry, what happened to it, and where your new work comes from.
A spreadsheet can do all three for a small firm with disciplined habits. It starts to fail as volume, people and practice areas grow. Most legal businesses in the UK are small: of 34,255 legal activities enterprises counted by the ONS in 2026, 78% employed four people or fewer, and 5,310 employed between five and nineteen[1].
Signs you have outgrown the spreadsheet
- Enquiries fall between people. Two people think the other has called back, or nobody owns the weekend web forms.
- Several versions exist. Someone saves a copy to their desktop, or each office keeps its own sheet.
- Follow-up depends on memory. There is no reminder when a call-back is due or a quote needs chasing.
- Reports take hours. The monthly figures for partners need manual cleaning, filtering and recounting.
- You cannot control access. Everyone who can open the file can see every enquiry, including sensitive family and crime enquiries.
- Conflict checks are separate. Reception searches the case management system for conflicts and the spreadsheet for enquiries, and the two never meet.
- Data is duplicated. The same details are typed into the spreadsheet, the case management system and an email.
One or two of these can be fixed with better spreadsheet habits. Four or more usually means the firm is paying in lost enquiries and staff time for the cost it is avoiding.
Three options compared
| Factor | Spreadsheet | Intake module in case management | Dedicated legal CRM |
|---|---|---|---|
| Set-up effort | Low | Medium; depends on supplier | Medium to high |
| Tasks and reminders | Manual | Usually available | Built in, often automated |
| Conflict search | Separate | Often integrated | Varies; check integration |
| Access control | File-level only | Role-based | Role-based |
| Reporting | Manual | Standard reports | Flexible dashboards |
| Marketing source tracking | Possible if disciplined | Basic | Usually strong |
| Data protection controls | Limited audit trail | Audit trail, retention rules | Audit trail, retention rules |
For many firms, the first step up is not a separate CRM but switching on the intake or enquiry module in the case management system they already use. It keeps conflicts and matters in one place and avoids another login.
Data protection applies either way
An enquiry spreadsheet is a record of personal data, often including special category or criminal offence data. UK GDPR applies just as it does to a CRM. If a spreadsheet is emailed to the wrong person or left on a lost laptop, that can be a personal data breach, and a notifiable breach must be reported to the ICO without undue delay and, where feasible, within 72 hours of becoming aware of it[2].
The Data (Use and Access) Act 2025 also requires organisations to handle data protection complaints from individuals, for example by providing an electronic complaint form, and to tell them the outcome[3]. Whichever tool you use, you need to be able to find everything held about a person quickly, correct it and delete it at the end of the retention period. A spreadsheet with ten tabs and three copies makes that hard.
If you are staying with a spreadsheet, run it properly
One file, one owner
Keep a single file in a shared, access-controlled location. One person owns its structure and quality.
Lock the structure
Use drop-down lists for practice area, channel, source, status and outcome, so data can be counted. Protect the header row and formulas.
Restrict sensitive detail
Keep only triage-level information. Detailed facts go in the matter file once the client instructs.
Add follow-up dates
Include a 'next action' and 'next action date' column, and filter on it every morning.
Clean weekly
Every Friday, close stale enquiries, fill missing outcomes and remove duplicates.
Apply retention
Delete or anonymise rows for enquiries that never became matters once your retention period ends.
What to look for in a legal CRM
- Intake workflow that matches your triage script, with required fields for urgency, conflict result and outcome.
- Integration with your conflict search and case management system, so an instructed enquiry becomes a matter without retyping.
- Tasks and reminders for call-backs, quote follow-up and non-engagement letters.
- Role-based access, so sensitive enquiries are visible only to the people who need them.
- Reporting by practice area, channel, source and fee earner, with exports for partners.
- Audit trails, retention rules and easy search and deletion for data subject requests.
- Clear answers on where data is hosted and who the sub-processors are, with a data processing agreement.
Firms are more likely to buy ready-made software than build their own tools. The ONS found that professional, scientific and technical businesses are more likely to access AI by buying external software or ready-to-use services than through free tools[4], and the same logic applies to CRM: buy a product that fits legal intake, then configure it, rather than customising a general sales tool from scratch.
Weighing the cost against the leak
The argument for staying with a spreadsheet is usually cost. To test it, put a rough value on what the spreadsheet is losing. Count, over one quarter, the enquiries that were never called back, the quotes with no follow-up recorded and the hours spent building reports. Multiply the lost enquiries by your usual conversion rate and average fee per matter, and the reporting hours by the cost of the person doing them. Compare that with the annual cost of the options, including set-up, training and the time it takes the team to change habits.
If the leak is small, invest in better spreadsheet discipline instead. If it is larger than the cost of a system, the decision is easier than it looked. Either way, the exercise produces a baseline you can use to judge the new tool a year later.
Questions to ask in a supplier demo
- Show us an enquiry arriving by phone, by web form and by email. How does each reach the right person?
- How does a conflict search work from the enquiry screen, and what does reception see if there is a match?
- What happens when an enquiry becomes a matter? Is anything retyped?
- Show us the report we would take to a partners' meeting: enquiries, conversion and source by practice area.
- How do we restrict family or crime enquiries to those teams?
- How do we find and delete everything about one person at the end of the retention period?
Bring a real, anonymised enquiry from last month and ask the supplier to process it live. Watching it happen is more revealing than any feature list.
Moving across without losing anything
- Freeze the spreadsheet structure and clean it: close old enquiries, standardise practice areas and sources.
- Decide what to migrate. Open enquiries and the last twelve months of closed ones are usually enough for reporting; older rows can be archived under your retention rules.
- Run both in parallel for a month, logging every new enquiry in the new system and checking the reports match.
- Switch off editing on the spreadsheet on a fixed date and tell everyone where enquiries now live.
- Review after three months: are outcomes being recorded, and are the partners using the reports?
Example: when the spreadsheet stopped working
Example (fictional). A seven-solicitor firm used a shared spreadsheet for four years. After opening a second office, each office started its own tab, and the Monday partners' report took the practice manager most of the morning. Twice in one quarter a web enquiry was called back by both offices. The firm switched on the enquiry module in its case management system, restricted family and crime enquiries to those teams, and set required outcome fields. The Monday report became a saved filter, and duplicate call-backs stopped.
Frequently asked questions
Is a spreadsheet good enough for tracking law firm enquiries?
For a small firm with one owner, drop-down fields, follow-up dates and a weekly clean, yes. It stops being good enough when enquiries are lost between people, reporting takes hours or you cannot control who sees sensitive enquiries.
Should we buy a legal CRM or use our case management system?
Check whether your case management system has an intake or enquiry module first. It keeps conflicts and matters together. A dedicated CRM makes sense when marketing reporting and automated follow-up matter more.
Does UK GDPR apply to an enquiry spreadsheet?
Yes. It holds personal data and often sensitive data. Access control, retention, breach reporting and data subject rights all apply.
How long should enquiry records be kept?
Set a retention period in your policy for enquiries that never became matters, keep the conflict-relevant names as long as needed, and delete or anonymise the rest at the end of the period.
References
Office for National Statistics (2026). UK business: activity, size and location, 2026 (Tables 2, 4, 9 and 17) (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 33: Notification of a personal data breach to the supervisory authority (opens in a new tab) ↑
GOV.UK (DSIT) (2025). Data (Use and Access) Act 2025: data protection and privacy changes (opens in a new tab) ↑
Office for National Statistics (2026). Artificial intelligence in UK businesses: 2023 to 2026 (opens in a new tab) ↑