Enquiry handling

What to record on a new enquiry log

The fields a solicitors firm should record on its new enquiry log for conflict checks, follow-up, complaints and marketing reports, and what to leave out.

Ava research teamPublished 7 min read

On this page
  1. What the log is for
  2. Core fields
  3. Fields that protect the firm
  4. Outcome and reason codes
  5. Fields for marketing and reporting
  6. What not to record
  7. Extra fields by practice area
  8. Using the log every week
  9. Building the log in five steps
  10. Example entry
  11. Frequently asked questions
  12. References

Key takeaways

  • A good enquiry log does three jobs: runs each enquiry, protects the firm and shows where work comes from.
  • Record who the firm would act for, the other side, urgency, the conflict result and the outcome with a reason.
  • Use fixed lists for practice area, channel, source and outcome, or the reports will not add up.
  • Leave detailed facts out; they belong in the matter file after instruction.
  • The log is evidence if a complaint or retainer dispute arises, and complaints are concentrated in a few areas[1].

What the log is for

An enquiry log is the record of every new prospective client contact, from the first call or form to the final outcome. Whether it lives in a spreadsheet, a case management system or a CRM, the fields matter more than the tool. A log with the right fields lets reception run each enquiry, lets the firm show what it did and did not do, and lets partners see where new work comes from. A log with the wrong fields does none of those, however expensive the software.

Think of the fields in three groups: operational (what is happening now), protective (what the firm needs if something goes wrong) and analytical (what partners need to make decisions).

Working rule for the whole team: if a call-back, a price explanation or a decline is not in the log, treat it as not having happened. That rule alone fixes most gaps, because people start recording as they go rather than at the end of the day.

Core fields

Operational fields every enquiry needs.
FieldWhy it mattersFormat
Enquiry IDLinks every contact and document to one recordAutomatic
Date and time receivedMeasures response speed and spots out-of-hours demandTimestamp
ChannelShows which routes bring workFixed list: phone, form, email, chat, walk-in, referral
Prospective client name and contact detailsNeeded to respond and to search for conflictsText; preferred contact method
Acting forRecords who the firm would act for, if not the callerText
Practice areaRouting and reportingFixed list
One-line matter summaryNeutral description for routing and conflictsShort text, no detailed facts
Urgency flag and key dateEnsures deadlines are seenFixed list plus date
Assigned toOwnershipPerson
First meaningful responseSpeed to leadTimestamp
Next action and dateDrives follow-upText plus date

Paragraph 8.1 of the SRA Code requires you to identify who you are acting for in relation to any matter[2]. The 'acting for' field makes that explicit from the first contact, which is especially useful when a relative or business colleague makes the call.

Fields that protect the firm

  • Other side and connected parties: names searched for conflicts.
  • Conflict result: fixed list (clear, clear with note, hold, stop), who cleared it and when.
  • Information given: whether price information was provided, how, and a link to the written confirmation.
  • Advice boundary: a tick confirming that no legal advice was given at enquiry stage, or a note of what the solicitor said at consultation.
  • Non-engagement letter: date sent, if the person did not instruct after substantive contact.
  • Consent and contact preferences: whether it is safe to call or email, and any marketing consent given separately.

These fields matter because records are what settle disputes. Complaints to the Legal Ombudsman are concentrated in a few areas: residential conveyancing made up 36% of accepted complaints in 2025/26, with wills and probate and personal injury at 14% each[1].

Complaints accepted by the Legal Ombudsman by area of law, 2025/26'All other areas' is the remainder of the reported shares
Complaints accepted by the Legal Ombudsman by area of law, 2025/26Donut chart. Residential conveyancing: 36%; Wills and probate: 14%; Personal injury: 14%; All other areas: 36%.Residential conveyancing: 36%Wills and probate: 14%Personal injury: 14%All other areas: 36%Accepted complaints
  • Residential conveyancing 36%
  • Wills and probate 14%
  • Personal injury 14%
  • All other areas 36%

Source: Legal Ombudsman, 2026[1]

Show the data
ItemValue
Residential conveyancing36%
Wills and probate14%
Personal injury14%
All other areas36%

Many complaints never reach a formal decision. In 2025/26, 51% of complaints resolved by the Ombudsman were settled through early resolution[1]. A clear enquiry record, showing when the person first called, what they were told about price and what happened next, makes early resolution far easier.

Outcome and reason codes

Every record must end with an outcome, and every non-instructed outcome needs a reason from a fixed list. Free text cannot be counted.

  1. Instructed.
  2. Declined: not a practice area we offer.
  3. Declined: conflict of interest.
  4. Declined: capacity.
  5. Declined: legal aid needed and not offered.
  6. Declined: other risk reason (detail held in the restricted risk file).
  7. Lost: chose another firm on price.
  8. Lost: chose another firm, other reason or unknown.
  9. Lost: did not respond to follow-up.
  10. Lost: decided not to proceed with the matter.
  11. Information only: no matter to take on.

Review the list once a year, but avoid changing it often. If the categories change every quarter, year-on-year comparisons become impossible.

Fields for marketing and reporting

Two fields make attribution possible: the source (how the person heard of the firm) and the referrer, if there was one. Prior use by the client or family (21%) and recommendations from family or friends (18%) are the most common ways consumers choose a legal provider[3], so the source list must separate 'previous client', 'recommended by a client' and 'recommended by another professional'. A companion guide covers asking and cleaning source data in detail.

Add a value band field if partners want to report on likely fee value, and a fee earner field for consultation outcomes. Keep both simple, or they will be left blank.

What not to record

  • Detailed facts, allegations or the person's account of the other side's behaviour. These belong in a solicitor's attendance note after a conflict check, not in a log many staff can read.
  • Health information beyond what triage needs, such as 'injury: broken wrist' rather than medical history.
  • Opinions about the caller ('time waster', 'difficult'). They are personal data, can be requested by the person and do the firm no credit.
  • Bank details or identity documents. Collect those through the proper onboarding route after instruction.

Data minimisation is a legal duty as well as good sense. Remember that the person can ask to see what the firm holds about them, and under the Data (Use and Access) Act 2025 organisations must handle data protection complaints, for example by providing an electronic complaint form, and tell the person the outcome[4]. Write every log entry as if the enquirer will read it.

Extra fields by practice area

Some departments need one or two extra fields to route and quote properly. Add them behind the practice area choice so they only appear when relevant, and keep each to a fixed list or a date.

  • Conveyancing: purchase, sale or remortgage; tenure; price band; whether an offer has been accepted; estate agent or broker referrer.
  • Family: whether there are children; whether proceedings have started; a safe-contact flag.
  • Employment: employee or employer; date of the key event, such as dismissal; whether early conciliation has been mentioned.
  • Wills and probate: will or estate; date of death if relevant; whether there is a dispute.
  • Personal injury: type of accident; date of accident; whether medical treatment was needed.
  • Crime: police station, court or investigation; custody flag; next date.

Resist adding more. Each extra field costs time on every call and is usually the first to be left blank.

Using the log every week

A log that is only opened at month end does not protect anyone. Build three habits around it. Each morning, filter on next action dates that are today or overdue, and on open urgent enquiries; that list is reception's first job. Each Friday, the log owner closes stale records, chases missing outcomes and checks that every enquiry with a consultation but no instruction has a non-engagement letter recorded. Each month, the practice manager produces the same short report: enquiries by area and channel, response times, conversion with counts, and the top lost reasons.

Audits of enquiry logs tend to find the same gaps: outcome left blank, source recorded as 'other', the conflict result missing for web enquiries, and response times not recorded for email. Each gap points to a step in the process that nobody owns. Fix the ownership, not just the data.

Building the log in five steps

  1. Agree the fields

    Start with the core, protective and outcome fields above. Add others only if someone will use them in a report.

  2. Fix the lists

    Write the drop-down lists for channel, practice area, urgency, conflict result, source and outcome before anyone enters data.

  3. Make key fields required

    At minimum: channel, practice area, assigned to, conflict result and outcome before closing.

  4. Train with real examples

    Walk reception through five past enquiries and complete the log together.

  5. Audit monthly

    Pick ten closed records at random and check every required field is complete and sensible.

Example entry

Example (fictional). ID 2611-042. Received 6 November, 18:42, web form. Name: Alex Morgan, prefers email. Acting for: self. Practice area: employment. Summary: dismissal from retail job last week, wants advice. Urgency: time-sensitive, dismissal date recorded. Other side: Example Retail Ltd; conflict result clear, checked by reception 7 November 09:05. Assigned to: employment associate. First meaningful response: 7 November 09:20, phone. Price information: hourly rates and staged estimate explained, emailed 09:40. Next action: consultation 8 November 14:00. Source: search engine. Outcome: instructed, 11 November.

Frequently asked questions

What should a law firm enquiry log include?

Date and time, channel, the prospective client and who the firm would act for, practice area, a one-line summary, urgency, the other side's name and conflict result, who owns it, first response time, next action, source and a final outcome with a reason.

Should the enquiry log include the full facts?

No. Keep a neutral one-line summary. Detailed facts belong in a solicitor's note after a conflict check, with access restricted to those who need it.

Why use fixed lists instead of free text?

Fixed lists can be counted. Free text in fields like source or outcome makes monthly reporting slow and unreliable.

How long should we keep enquiry log entries?

Set a period in your retention policy for enquiries that did not become matters, keep conflict-relevant names as long as needed, and delete or anonymise the rest.

References

  1. Legal Ombudsman (2026). Legal Ombudsman 2025/26 annual complaints data and insight (opens in a new tab) ↑

  2. Solicitors Regulation Authority (2025). SRA Code of Conduct for Solicitors, RELs, RFLs and RSLs (opens in a new tab) ↑

  3. Legal Services Consumer Panel (2026). How consumers are choosing legal services (Tracker Survey 2026) (opens in a new tab) ↑

  4. GOV.UK (DSIT) (2025). Data (Use and Access) Act 2025: data protection and privacy changes (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo