What a Good Lead Handover Summary Contains

It is easy to describe a managed enquiry workflow in terms of the reply that goes out to the enquirer. That is the visible part, and it is what a prospective client asks about first.

But the reply is not really the product. The enquirer gets a prompt, useful answer, which matters — yet the thing the business receives, and the thing that determines whether any of this changes their week, is the handover summary: the message that arrives in the team's inbox saying here is who contacted you, here is what they want, and here is what to do about it.

A weak handover summary turns a well-handled enquiry back into work. A good one means the first thing a negotiator, broker, or practice manager does each morning is act, rather than read.

In short: A handover summary should tell the team who enquired, what they want, how urgent it is, what evidence supports that judgement, and what to do next — with the reasoning behind any score attached. A score without its reasoning is worse than no score, because it invites either blind trust or blanket dismissal.

What belongs in a handover summary

The components below are the ones that consistently earn their place. A summary carrying all of them fits comfortably on a phone screen.

• Who they are, and how to reach them. Name, preferred contact method, and the times they said they were available. The last of these is routinely omitted and routinely useful.
• What they actually want. Stated plainly, in specifics rather than categories. "Two-bedroom flat, E17, up to £425,000, wants to view Saturday" rather than "sales enquiry".
• Their position. The qualifying facts relevant to the trade — chain position and finance for a property enquiry, treatment and timeframe for a clinic, lender stage for a mortgage case, job type and access for a trade. This is the part that determines whether a callback is worth making now.
• A score, with its reasoning. Hot, warm, or cold — and immediately after it, the sentence explaining why.
• Direct quotes from the enquirer. One or two verbatim lines, not paraphrase. How someone phrases their situation carries information that summary strips out, and it lets the person picking up the phone match their language.
• The recommended next action. Call before midday. Send the brochure. Book into the Tuesday clinic. A summary that stops at description leaves the prioritising to be done again.
• What was not established. The gaps. If finance was not confirmed because the enquirer did not know, say so. A summary that quietly omits what it failed to find is the most dangerous kind, because it reads as complete.
• Anything escalated, and why. If the workflow declined to answer something and routed it to a human, the summary should say what and why — that is the oversight layer working, and it needs to be visible.

Why a score without reasoning is worse than none

This is the point worth dwelling on, because it is where most lead-scoring systems fail.

A summary that says "Hot" and nothing else asks the recipient to take it on faith. There are only two ways they can respond. They can trust it, in which case they are outsourcing a commercial judgement to a process they cannot inspect. Or they can distrust it, in which case they re-read the whole enquiry themselves and the score has saved nobody anything.

Neither is good, and the second is what usually happens after the first bad call.

A score with its reasoning attached — "Hot: has an agreement in principle, no chain, asked to view this weekend" — is a different object. The recipient can see the basis, agree or disagree with it in a second, and act. It also makes the system correctable: when a score turns out to be wrong, the reasoning shows whether the facts were wrong or the weighting was, and the qualification criteria can be adjusted accordingly.

The same principle underpins why human oversight is part of the design rather than a reassurance. A judgement nobody can inspect is a judgement nobody can improve.

What does not belong

Three things commonly appear in handover summaries and should not.

The full transcript, as the summary. Attach it, by all means — it should always be available. But a transcript is a record, not a handover. If the recipient has to read the conversation to know what to do, the summary has failed at its only job.

Confidence percentages. "87% likely to convert" reads as precision and is not. Unless a number is derived from a real, validated model with a known error rate, it dresses a judgement as a measurement. A stated reason is more honest and more useful.

Marketing language. A handover summary is an internal operational document. It should read like a note from a colleague, not like a pitch. "Excellent opportunity" tells the recipient nothing; "wants to view Saturday, has AIP" tells them everything.

Getting the format right for the person receiving it

The best summary in the world fails if it arrives in a form nobody reads. Two things matter here.

Length. One screen. A negotiator checking their phone between viewings will read six lines and will not read twenty. Everything else belongs in the attached detail.

Consistency. The same fields, in the same order, every time. The value of a consistent format compounds — after two weeks the recipient stops reading it as prose and starts scanning to the field they need. That only works if the field is always in the same place.

It is also worth being deliberate about channel and volume. Individual emails per enquiry suit low volume. A consolidated morning digest with anything urgent broken out separately suits higher volume better. Getting this wrong is the most common reason a workflow that is technically working still feels like noise.

Frequently asked questions

How long should a handover summary be?

Short enough to read on a phone without scrolling much — six to ten lines for most enquiries. The full conversation record should be available underneath or attached, but the summary itself is a decision aid, not an archive.

Who writes it — the workflow or a person?

The workflow drafts it from the conversation; a person reviews it as part of the oversight layer. That review is what catches a misread situation or a score that does not match the evidence, and it is also what makes the escalation line real rather than nominal.

What if the score is wrong?

It will sometimes be. That is why the reasoning is attached: a wrong score with visible reasoning is a correctable error, because you can see whether the facts were misread or the criteria are miscalibrated. Scoring criteria should be reviewed against outcomes periodically rather than set once.

Can the summary be pushed into our CRM instead of email?

Often, depending on the system. Where a CRM supports structured inbound records, the handover can populate a lead record directly. Where it does not, email or a shared inbox remains a perfectly good delivery mechanism — the format of the summary matters considerably more than the pipe it arrives through.

What happens with enquiries that are clearly not worth pursuing?

They still get a summary, marked cold, with the reason. Two things make that worthwhile: the enquirer received a courteous reply either way, and the cold pile is genuine data about who is finding the business and what they expect — which is often more useful than the hot pile for decisions about marketing.