When to reassign leads on a real estate team

A lead should be reassigned the moment its expected next touch is overdue by more than the lead can tolerate — which means the answer differs by lead type, and it should be a timer, not a judgment call. Teams that reassign by gut feel get politics; teams that reassign by published clock get conversion.

The windows, by lead type

Working defaults, tightened or loosened to your market:

The steep top rows reflect how fast internet-lead value decays; the bottom rows reflect that a six-month nurture tolerates a slow week. The last row prevents the rule from poisoning culture — reassignment governs team-generated leads, not relationships an agent brought with them.

One caution on the clocks themselves: if the team runs them in business-aware time, say so in the published rules and be honest about the cost. Internet leads do not stop shopping at 9 p.m., and a team that counts evenings as free pause time is quietly granting itself the response windows its competitors are beating.

Reassignment is a system event, not a confrontation

The reason most teams under-reassign is that doing it manually feels like an accusation. The fix is to remove the human from the trigger: first-to-claim offers with expiry timers reroute unclaimed leads automatically, follow-up SLAs live in the CRM as tasks with due dates, and an overdue task past its grace window moves the lead without anyone drafting an awkward message. On BrokerFold, claim timers and routing handle the front of this chain out of the box, and every assignment and timeout is logged — so when an agent asks why they lost a lead, the answer is a timestamp, not an opinion.

Where reassigned leads should go

Two good destinations. Fresh, hot leads reroute to the next eligible agent under your normal distribution rules — the lead never knows anything happened. Aged or ambiguous leads drop into a shared pond where any agent can claim them by doing actual work. The pond matters more than it looks: it converts reassignment from a punishment into a market, and it keeps the team lead out of the redistribution business.

Publish the rules before you need them

Every window above belongs in the team’s written rules of engagement, agreed to at onboarding: what the SLAs are, what counts as a contact attempt (a logged call or message — not opening the record), what happens on vacation (rotation paused, coverage assigned), and what a reassigned lead is worth if it later closes. Two failure modes kill these systems. Rules that exist but aren’t enforced teach everyone they’re decorative. Rules enforced retroactively — invented after a lead went stale — teach everyone they’re weapons. Published first, applied mechanically, they read as what they are: the team defending its pipeline, not its lead defending favourites.

The metric that tells you it’s working

Watch two numbers monthly: the share of leads hitting their first-touch SLA, and the conversion rate of reassigned leads. The first should climb as agents internalize the clock. The second is the uncomfortable one — reassigned leads that convert at a healthy rate are proof the original assignment was the bottleneck, and that your reassignment windows are recovering revenue that silence would have buried.