Published August 23, 2026.
Lead routing breaks down when a conclusion arrives without the facts behind it. An evidence packet fixes that gap by placing the relevant source, fit criteria, uncertainty, and requested next action together. The assistant prepares the record; the accountable owner still decides whether the prospect qualifies and where the lead should go.
Define the routing question
Qualification is not a personality judgment and it is not a substitute for sales strategy. Write the routing question first: who should review this record, what context do they need, and what would make the record unsuitable for the next step? A packet should answer that question with traceable observations. It should not manufacture urgency, infer budget, or turn a partial form into a confident profile.
Collect only decision-relevant facts
Use the minimum fields needed for the next handoff: stated problem, relevant page or source, requested timeframe if volunteered, role as described by the person, and a clear contact path. Preserve the original wording where it matters. Avoid copying sensitive personal details that do not affect routing. Less information can create a safer, more reviewable packet when the essentials are explicit.
Distinguish fit from readiness
A record may resemble the intended audience without being ready for a conversation. Keep fit signals separate from readiness signals. Fit can relate to the problem described; readiness can relate to a specific question or requested follow-up. Never treat silence, a job title, or a page view as consent or intent. The owner decides how those signals should influence outreach.
Record the source trail
Every claim in the packet should point to a form field, message, page, or approved internal record. Include capture time and note whether the value was supplied, inferred, or missing. This makes correction possible. An assistant can assemble and format the packet, but the person receiving it should be able to challenge a conclusion without searching through an opaque summary.
Use stop conditions
Stop routing when the record is contradictory, the requested action is unclear, consent is absent, or a required field cannot be verified. A stop is a valid outcome. Place the record in a review state with a short explanation and the next question needed. This prevents a desire for speed from causing an inappropriate handoff or an avoidable duplicate contact.
Make the owner’s decision explicit
End with a proposed route and a confidence note, not a final claim of qualification. Name the accountable reviewer and the decision deadline if one exists. If the owner rejects the proposal, retain the reason as a learning signal for the routing rule. Repeated corrections may justify changing the field definitions or examples, not simply telling the operator to be more careful.
Review the packet routine
Once a week, sample routed and stopped records. Look for missing evidence, overconfident language, inconsistent outcomes, and fields that no longer support decisions. Remove steps that produce no useful signal. A good packet is short enough to read, specific enough to act on, and humble enough to show where the evidence ends.
Keep the record usable
A daily growth routine becomes dependable when another operator can understand the question, inspect the evidence, and see who owns the decision. Keep the article’s source, date, boundaries, and next check close to the work. That discipline does not require elaborate tooling. It requires accurate labels, distinct page purposes, and enough context to prevent a quick SEO action from creating a larger problem. Use the method as a starting point, adapt it to the team’s actual workflow, and document the reason whenever the workflow changes. The result should make the next article or improvement easier to judge, easier to maintain, and more useful to the person who has to act on it.
Handle a changed request
A prospect may describe one problem and ask for a different follow-up later. Preserve the sequence rather than overwriting the first statement. Mark the latest request, the earlier context, and the time of each change. Routing should follow the current explicit request while allowing the reviewer to understand why it changed. If the record contains conflicting instructions, stop and ask the owner which one governs.
Keep packets comparable
Use the same headings for every packet even when some fields are empty: request, relevant context, evidence, unknowns, proposed route, owner, and next action. Consistency makes quality review possible without forcing every record into the same conclusion. Sample packets for missing evidence and unnecessary detail. The aim is a decision-ready handoff, not a longer profile.
Apply the method in a lean team
A packet can include a short “not established” section. This is where the operator records details that would be tempting to infer but were not supplied, such as budget, authority, urgency, or technical readiness. Making those absences explicit protects the reviewer from accepting a polished guess. It also improves the next question: ask for the missing fact only when it is necessary for routing or when the owner has approved that form of follow-up. If a record is not ready, preserve the packet without escalating its language. A stopped packet can be reviewed later if the person provides more context, but it should never be treated as permission to invent context in the meantime.
Keep the packet’s recommendation shorter than its evidence. The reviewer should see the proposed route quickly, then be able to inspect the supporting record and the limits of what is known.
