Who owns the lead
An enquiry with no named owner is not a lead. The assignment rules have to be written before the first dispute, because moving a lead moves money.
An enquiry that belongs to nobody in particular is not a lead. It is a phone number in a file.
Every other question about a sales process — follow-up discipline, conversion counting, why a good enquiry went cold — resolves back to this one. If you cannot name the single person responsible for an enquiry at any given moment, nothing downstream of it can be measured or corrected.
The rules that have to exist before they are needed#
There are five, and each one will be argued about eventually. The only real choice is whether they are decided in advance and written down, or invented during the argument, in front of the people affected.
- How a new enquiry is assigned. Round robin across the team, by source, by project, by the language the buyer speaks, or by who is on shift. All of these are defensible. Round robin is the fairest and ignores fit. Assignment by language or by project is better for the buyer and produces uneven workloads that then need managing. Pick one, say why, and write it down.
- What happens when the owner is on leave. Enquiries do not pause for chhutti. Either the lead moves and comes back, or a cover person acts on it while ownership stays put. Both work. What does not work is nothing, which is what happens by default, and the buyer who called on a Tuesday hears from nobody until the following week.
- When ownership lapses. If nothing has been done on an enquiry for a defined period, it should return to the pool and become available. Without this rule, ownership is permanent and hoarding is free.
- What happens to a lead that returns after a year. The old owner may have left, changed projects or forgotten the buyer entirely. Is it a new enquiry or a revival of the old one? This must be decided once. The record should keep both histories either way.
- Who decides a transfer. Not the two people involved. A named role, with the decision recorded. Transfers agreed privately between executives are the ones that produce a claim at booking, from a third person who was never told.
Why this is not an administrative matter#
Ownership is compensation. That is the whole reason these questions are hard.
A rule that moves a lead moves money, from a named person to another named person, in an office where everyone knows both. This is why arguments about assignment are more heated than arguments about anything else in a sales office, and why they cannot be settled by whoever is senior in the room on the day.
It also means the rules must be published before the first dispute rather than after. A lapse rule introduced the week after a large booking looks like a decision about that booking, whatever the intention. The same rule announced at launch, when nobody knows who it will affect, is just a rule. This is one specific case of the general principle in who is allowed to decide: the authority for a decision has to be settled before the decision is contentious.
The failure modes#
Assigned to a team. The enquiry sits with "the Sunday team" or "site office". Every member sees it, each assumes another has called, none has. This is the ordinary way work dies between people, and the mechanism is exactly the one described in why tasks stall between people — responsibility that is shared is responsibility that is unheld.
Two owners. Usually the result of a transfer done in one place and not the other, or of a duplicate record. The buyer receives two calls with two versions of the price, and finds out that the office does not talk to itself.
An owner who has left. Nobody removes departed staff from assignments, and a portion of the pipeline is now assigned to a person who does not come to work. These leads receive no calls and appear in no queue, because a queue is usually built per active user.
Silent reassignment. The manager moves a lead without telling the previous owner. He finds out when the booking is announced. Whatever the merits of the move, the cost is paid in trust and collected for years.
Hoarding. An executive holds a stack of enquiries he has not called in weeks, because holding them costs nothing and releasing them means somebody else might convert one. This is the direct consequence of no lapse rule, and it is a rational response to the incentives, not a character defect.
Making a lapse rule that people accept#
A lapse rule is the one that decides whether the whole arrangement is seen as fair, because it is the one that takes something away. Three properties make the difference.
A visible countdown. The owner can see, on the record, how long he has before it lapses. Not a policy in a circular — a number on the screen he is already looking at. A lapse somebody can see coming is usually a lapse that does not happen.
A warning before the event, to the owner and to nobody else. A private nudge first. If the lapse rule's first announcement is public, it functions as a reprimand, and people will start making a token call on every stale lead to reset the clock. What you get then is worse than hoarding: activity performed for the counter. Warnings work when they are early, quiet and addressed to the person who can still act, which is the design argument in escalation without shame.
A record of who took it, and when. When a lapsed lead is picked up, the transfer is written with a date and a name. If that lead books, the history shows exactly when ownership changed and under which rule, and the commission conversation is a reading exercise instead of an argument.
None of this works unless something in the system is actually watching dates and acting on them without being asked, which is the machinery described in follow-up as a schedule. A lapse rule enforced by a manager remembering to check is not a rule.
The same questions arrive from outside the payroll when a channel partner claims a buyer. The vocabulary changes and the structure does not — working with brokers is the external half of this problem.
The short version#
Name one person per enquiry, always. A lead owned by a team is owned by nobody.
Decide assignment, leave cover, lapse, revival and transfer authority in writing before the first dispute, because after it any rule looks like a verdict.
Make lapses visible in advance, warn privately, and record every change of owner with a date and a name.