A lead record has two jobs that are easy to muddle together. It has to show which conversations need attention now, and it has to preserve the context behind them.
Put both jobs into one long list and the urgent work gets buried in history. Split them into two connected layers and each record has a clearer purpose.
Layer one: the active view
The active view is for conversations that need a decision or action. Keep it small. An owner, current stage, next action, due date and stable contact ID are enough to make the work visible.
Write down what moves a record into this view and what takes it out again. A contact with no current action should not compete with a proposal due tomorrow.
Layer two: the reference record
The reference record holds the contact history the business is entitled to retain. It is not a daily task list.
When a dormant contact returns, the stable ID reconnects the live conversation with the context that was kept. That context is only as good as the record behind it.
The link between them
Use one stable ID in both layers. Names and email addresses can change or be entered differently. The ID gives the process something consistent to follow.
Document what happens when records are merged, corrected or deleted. The link is useful only if the maintenance rule is clear.
The follow-up trigger
A scheduled brief, filtered view or task queue can surface records when the next action is due. Set the cadence around the speed of the pipeline and the commitments made to prospects.
The trigger reduces the burden on memory. It does not guarantee that the right person appears or that anyone follows up. Check it against the CRM and watch for failed or overdue actions.
What stays human
Relevance, timing and tone still need human judgement. Automating the message as well as the reminder can turn a useful control into unwanted outreach.
Use automation to surface the record and the agreed action. Let the person responsible decide what to say and whether the context has moved on.
How to test the structure
Choose a representative period and record:
- live conversations with no owner;
- next actions with no date;
- overdue follow-ups;
- actions completed;
- records the brief failed to surface.
Measure the same fields after the change. That will show whether the structure made follow-up easier to see in this pipeline. It says nothing about a universal conversion rate or a promise that no lead will be missed.
Common questions
Where should I look for a follow-up gap?
Check whether every live conversation has an owner, a next action, a date and a visible trigger. A missing field gives you a specific gap to repair.
Do I need a particular CRM?
No. The two layers can run in a spreadsheet or a CRM if the active view stays current, the reference record follows the applicable retention rules and a stable ID links the two.
How often should the brief run?
Match the cadence to the speed of the pipeline. It should surface an agreed action before it becomes overdue without creating another feed the team learns to ignore.
Is this just being more organised?
It is a process control. The record and trigger reduce reliance on memory, while ownership and review remain with the team.
Start with the record you have
Add owners, dates and next actions before adding more automation. Then see whether the active view and trigger make overdue follow-up easier to spot.
If you want to map the process directly with Shaun, book a Clarity Session.
