.svg)
.svg)
.svg)
A sales lead tracker is a shared record of potential buyers, their latest contact, current status, owner, and next action. Give each lead a stable ID and one accountable owner. After a meaningful event, update the evidence, make a separate status decision, and set the next action and date. A reply does not automatically qualify a lead. When an account executive accepts a deal, record the new owner and deal ID, then close the lead's completed action.
In short: Download the 500-row starter workbook, follow a lead from first outreach to a buyer reply, apply the accepted-deal handoff rule, and run weekly checks for overdue work, missing fields, possible duplicates, and stalled decisions.
Download the editable sales lead tracker (.xlsx). It includes a fictional example, a status dropdown, and a review flag for incomplete, invalid-status, invalid-date, or overdue rows. It does not send reminders, detect duplicate contacts, or sync with a CRM.
What Is a Sales Lead Tracker?
A tracker can be a spreadsheet or a CRM view. Its useful question is: “What happened, who owns this person now, and what should happen next?” HubSpot's lead tracker template records contact details, source, stage, last contact, and follow-up action; Smartsheet's lead templates offer separate lead and sales pipeline views.
The boundary matters. A lead row records a person or prospecting contact and the path toward qualification. A deal record represents an accepted sales opportunity, with its own buying process, value, and close outcome. A team may use one CRM for both, but it should still define when the handoff happens. If several people at the same company influence one purchase, an account map helps record their different roles; a lead tracker should not turn every contact into a separate forecasted deal.
What Should a Sales Lead Tracker Include?
Start with the fields the team will actually update. A sheet full of unused scoring and forecast columns hides overdue work. OnePageCRM's free tracker puts next action and due date at the center of its sheet. The workbook accompanying this guide uses the following exact columns.
The Minimum Fields to Copy
The template uses one row per lead. If the same person arrives through another campaign, check the existing ID, contact, and company before adding a second row. Keep the original source and record the later event. If two people at one company are both relevant, they can have separate lead rows while the account map or deal record connects the buying group.
Status, Response, and Next Action Are Different Fields
Use a short status vocabulary. These definitions are a suggested operating convention for the downloadable tracker; adjust them only when your team agrees on the transition rule.
A response is an event; status is the team's current decision. A question about a trial may justify “Engaged” and a new action, while leaving fit, authority, and timing unknown. No response by itself does not prove poor fit. Decide whether the lead remains Working, moves to Nurture with a stated review date, or stops under your contact policy. If someone asks you to stop contacting them, honor that in the sending system too; a spreadsheet label alone does not stop messages.
Copy the Sales Lead Tracker Template
The editable Excel tracker includes the exact columns above, a status dropdown, an example row, and a review flag across 500 prepared lead rows. Download a copy, clear the fictional row's input cells A:M without deleting the row or its formula in N, and give the working file one team owner. The fictional example has a fixed October 2026 due date, so its flag may later show Overdue; that is expected until you clear its input cells. If you import it into another spreadsheet tool, check the dropdown, date cells, and review formula there. Before adding a 501st lead below worksheet row 504, extend the Excel table, dropdown, review formula, and date formatting; otherwise the new row will not have the same controls.
If building from scratch, put these comma-separated labels into a CSV file and import it so each label becomes a separate column:
Lead ID,Company,Contact,Email,Source,Owner,Status,Last event date,Last event and evidence,Next action,Due date,Outcome or deal ID,Handoff notes,Review flag
Make Lead ID unique, use real date cells for both date columns, and filter by Owner, Status, and Due date. If you build your own sheet, leave the review flag to a formula; do not type “Current” manually. In the supplied workbook, the flag checks:
- Missing information: A populated row needs an ID, company, contact, email, source, status, owner, event date, and event evidence. Active rows also need a next action and due date.
- Invalid values: An unlisted status shows “Fix status.” Text in the event-date cell shows “Fix event date”; text in an active row's due-date cell shows “Fix due date.” A real past due date on an active row shows “Overdue.”
- Closed rows: Converted and Disqualified need an outcome and no leftover lead action or due date. The flag asks for a missing outcome first. Once an outcome is present, a leftover action or due date shows “Clear lead action.”
The flag shows one issue at a time, so check the row again after each fix. For non-email contacts, adapt the Email field and its review-flag requirement to the contact method you use. The flag cannot judge whether an action is relevant or whether two rows refer to the same person.
How to Update a Lead After Each Event
After each meaningful event, record what happened, decide whether the status changes, and leave one owner with a dated next action—or a documented stop. The following company, person, conversation, and dates are fictional; they are not an Alore customer result. Jordan Vale at Birchwood Labs registers for a seller's webinar. The seller creates a lead and later receives Jordan's question about testing without connecting prospect data.
A New Lead and First Outreach
The seller creates EX-001, records Webinar as the source, assigns A. Seller as owner, sets status New, and schedules a relevant first email for 21 October 2026. After that email is sent, the seller records the send as the latest event and sets Working with a specific, policy-consistent next review date. The original source stays Webinar. A send is activity, not evidence that Jordan saw or wanted the offer.
A Reply That Changes the Next Action
On 21 October 2026, Jordan asks: “Can we try this without connecting our prospect data?” That fictional question is the event evidence. The seller also copies the question and date into Handoff notes, so a later event cannot erase them. The question does not establish budget, product capability, or trial approval. The seller's next action is to verify trial and data options with the product owner and answer Jordan by 23 October; the seller can ask which workflow Jordan wants to test if that is needed for a useful answer. The row is Engaged, not Qualified.
EX-001 / WebinarEX-001 / Webinar, unchangedThe workbook's fictional example row shows the second state. It does not claim that the buyer agreed to a meeting, that security review is unnecessary, or that the product supports a no-data trial. Those questions still require a buyer and product answer.
No Reply, Nurture, and Stop States
When a buyer does not reply, log the last send and follow the team's outreach policy. The cold email follow-up sequence guide explains how to add a new reason to a subsequent touch and when to move on. Keep the lead Working while an appropriate next action is due.
If the permitted sequence ends without a reply, make a separate policy decision. If a later relevance and permission review is allowed, set Nurture, record “sequence complete; fit unknown,” and give the owner a dated action to reassess before any new contact. If policy calls for no further contact, set Disqualified as an administrative stop, put “outreach stopped under policy; no reply; fit unknown” in Outcome, and clear the action and due date. Neither route treats silence as proof of poor fit.
A buyer-given future time is a stronger Nurture reason and should be recorded as such. If the address bounced, resolve contact data before sending again; an opt-out must also be honored in the sending system.
When Does a Qualified Lead Become a Deal?
Set your qualification rule before asking the spreadsheet to label a lead Qualified. Under the fictional seller's illustrative rule, Jordan would need to confirm an active evaluation of outbound sequencing for the SDR team and agree to a working conversation with the assigned account executive. Jordan's no-data trial question alone meets neither condition. A different team may use a different qualification rule; write it down beside its operating process.
The seller remains the lead owner while arranging the introduction. The lead becomes Converted only after the named account executive accepts the handoff and creates or identifies the opportunity record. Keep Jordan's exact question and 21 October date in the lead row's Handoff notes while qualification and acceptance are pending. Once the deal record exists, copy those notes into it with the original source, known use case, unresolved buying roles and data-access constraints, and the agreed next action and date. Label unverified points as open questions.
On acceptance, set the lead row Status to Converted, Owner to the receiving account executive, Last event date/evidence to the acceptance and deal creation, and Outcome or deal ID to the new deal ID. Clear the completed lead Next action and Due date; put the receiving owner's agreed action and date in the deal record. The lead sheet's review flag will say Closed when these fields are consistent, but it cannot verify that the account executive accepted or that the handoff note is complete. This handoff works whether the team keeps the lead sheet or uses a CRM.
Review the Tracker Without Letting Rows Go Stale
Give one person responsibility for a weekly review. First filter Review flag to anything other than Current, Closed, or blank, and resolve the exceptions. This view surfaces overdue work, missing fields, invalid values, and closed rows that still carry a lead action or due date. Then clear the review-flag filter. Filter Status to New, Working, Engaged, Qualified, or Nurture, and sort all active rows by Due date. This second view includes work due today or later even when its flag says Current. The flag cannot judge whether an action is useful or find duplicates or stalled buyer decisions.
Second, sort Lead ID to find repeated IDs. For a separate possible-person check, temporarily add a helper column containing =LOWER(TRIM(D5))&"|"&LOWER(TRIM(B5)), fill it down, and sort it; adjacent identical email/company keys need manual inspection. Ignore blank email keys, compare the underlying records, and do not merge two different people at one company. The workbook does not deduplicate for you. Resolve suspected duplicates before reporting counts or handing a lead off.
Third, filter Qualified rows and ask whether the receiving owner has accepted a deal and supplied its ID; if not, keep an owned handoff action and date rather than marking Converted. Filter Engaged rows and inspect whether the buyer question has an answer or a dated follow-up. Filter Nurture rows with review dates due or past and decide whether to resume, reset the review date for a stated reason, or stop. Record the resulting owner, action, date, or stop reason. These are manual judgment checks; a row can say Current while its decision is stale.
When reporting why leads stopped, keep administrative no-reply policy stops separate from evidence-based poor-fit decisions. Both can use the Disqualified status in this starter sheet, but their Outcome reasons answer different questions.
When Should You Move From a Spreadsheet to a CRM?
A spreadsheet is reasonable while a small team can keep one trusted file current and follow its owner/action rules. HubSpot's template guidance and Smartsheet's lead and pipeline templates show both spreadsheet and system options. Their exact numeric switch points are vendor suggestions, not universal thresholds.
Move the working process into a CRM when the file repeatedly loses ownership, conversations, permissions, handoffs, or a dependable record of changes. Also consider it when several people need to update the same leads and the team needs reliable activity history or reporting. Before migrating, agree on status meanings, identify a lead ID, deduplicate contacts, map current owners and next actions, and test a small sample of transferred records. A CRM does not repair vague statuses or missing next steps on its own.
Use Tracked Context in the Next Outreach
The tracker should inform the next message, not supply an automatic pitch. If Jordan asked about a no-data workflow, answer or clarify that point rather than sending a generic follow-up. If the buyer names a second reviewer, record that person and verify their role before writing as though they approved the project. For a fuller map of the buying group, use the account mapping guide.
Once a team has chosen a relevant follow-up plan and stop rules, Alore's Drip Campaigner describes personalized sequences, follow-up reminders, and response analytics. Use those capabilities for outreach execution and response review. Keep the tracker or CRM as the accountable record for lead status, owner, and handoff unless your team has separately verified an integration. Start by opening your current list and finding one active lead with no clear owner or next action; make that row usable before adding more columns.
