A prospect inquires in June. Two bedrooms, needs parking, moving in November for a job that starts after Thanksgiving.

Your agent replies honestly. Nothing available in November is listed yet, and anything showing now will be long gone. Come back in September.

The prospect says thanks. The lead sits in the system for three weeks, receives a couple of follow-ups aimed at people moving next month, responds to neither, and gets marked dead.

In October they rent a two-bedroom with parking four blocks away.

Here is what makes that particular loss worth thinking about. You may already have had some visibility in June into what could become available in November. It was in your lease expiration data. Nobody put the two facts in the same place.

Most renters search late, which is why the early ones get dropped

Start with what renters are actually told.

Apartment List's guidance says most renters start looking at least two months before their planned move-in date, with four months or more in particularly competitive cities, and that most find an apartment two to three months ahead of their preferred date.

Other renter guidance is more emphatic about not starting early. Units available more than sixty days out are usually still occupied and only anticipated, so a renter searching in June for November finds very little to apply for and gets told to come back.

That advice is correct for renters. The problem is what it does to your funnel.

Because your follow-up cadence was designed for the people who follow that advice. Same day, 48 hours, day 7, day 14, day 30. Perfect for somebody moving in six weeks. Almost worthless to somebody moving in five months, who cannot act on anything in it and will not respond to any of it.

So the early cohort enters a sequence built for a different problem, fails to engage with it, and exits through the same door as a bad lead. If both are given the same status, the system cannot tell the difference between a prospect who was not interested and one who was simply not ready.

Why this cohort exists at all

The early inquirer is not necessarily a browser. In many cases they have a date, and the date came from somewhere outside their control.

A job starting in the autumn. A degree programme with a fixed term. A lease they already know expires in March. A house sale in progress. A relocation somebody else decided on.

Which means an early prospect should not automatically be treated as a weaker prospect. Their timing may simply be different from your available inventory.

That is a timing mismatch, not a qualification problem. Treating it as a qualification problem is the error.

The asymmetry nobody exploits

Here is the part that turns this from a nurture argument into an operational one.

You have some forward visibility of supply. Your lease expiration data tells you, months in advance, which units reach a renewal decision and when. Our article on lease expiration management covers reading that profile for capacity planning.

You also have forward visibility of demand, in the form of prospects who told you their move date.

Both exist. They sit in different places, get used for different purposes, and are almost never set against each other.

A prospect who wants a two-bedroom with parking in November, and a two-bedroom with parking whose lease expires in October, create a potential match worth watching. Someone looking at both lists can see the possibility in June, even though the unit is not guaranteed to become available. Instead one becomes a dead lead in July and the other becomes a vacancy in November.

What to capture at inquiry

None of this works without one field: intended move date. If that information is buried in a note or never captured at all, it becomes very difficult to use operationally.

With it, you can route by timeline rather than by enthusiasm, which is the only routing most leasing teams currently have.

Three more fields make the later match possible:

Unit requirements that matter to them. Bedrooms, and the one or two things they said were non-negotiable. Parking, ground floor, pets, in-unit laundry.

Their price ceiling. Not to disqualify them, but so that when a match appears you know whether it actually is one.

Contact preference. Since you will be reaching back out in four months, and the channel they chose in June is the one they will still recognise. Our article on why a four-minute reply can still lose the lease covers why that matters.

Four fields. Two minutes at intake. They are the difference between a prospect you can find again and a name in a list.

A cadence for people who are not ready

The short cadence does not work here, and the answer is not to run it more gently. It is to run a different one.

At inquiry. Be straight with them, and make it useful.

Thanks for getting in touch. You mentioned a November move, so nothing available now will still be there by then. What I can do is watch for two-bedrooms with parking coming up for that window, which we usually know about six to eight weeks ahead. Want me to do that?

That message does three things. It tells the truth, which they will respect and remember. It sets an expectation with a timeframe. And it asks a question that gets a yes or no, which tells you whether this is a real prospect or a casual look.

Then almost nothing, until there is something to say. A monthly note with no content trains them to ignore you. A note saying a matching unit has come up is worth sending.

Then set a reach-back point around the prospect's expected search window. For this example, that could be around sixty days before the move. This is the message the whole thing exists for.

Hi XYZ, checking in as promised. Two 2BRs coming available in early November, one with the parking space you asked about at $1,650. Want the details, or shall I keep watching?

Then move them to the normal cadence, because at that point they are a normal prospect.

The total contact volume is much lower than a short-cycle cadence, because you are not sending repeated touches simply to keep the prospect active. That difference matters at portfolio volume, which is the argument we made in the follow-up sequence you designed is one you cannot run.

Be honest about the limits

This is worth writing plainly, because an article that oversold this would be doing you no favours.

• The cohort is not large. Most renters do search inside sixty days. The early group is a minority of your inquiries, and an elaborate programme built for them would cost more than it returns.

• Plans change. A November move becomes a January move, or does not happen. Some of these prospects will be unreachable when you come back, for reasons that have nothing to do with you.

• You cannot promise a specific unit. A lease expiring in October does not guarantee a vacancy, because the resident may renew. Anything you say to the early prospect has to be framed as what you are watching for, not what you are holding.

What makes it worth considering anyway is the relatively low contact frequency. The reach-back can be tied to information the team already maintains, the prospect's intended move window and potential future availability, rather than requiring a separate programme to sustain it.

What to measure

• Share of inquiries with a move date beyond sixty days. You probably do not know this number. It is worth knowing before deciding how much to invest here.

• Reach-back rate. Of the long-horizon prospects from four months ago, how many actually received the message? This is the number that will be uncomfortable the first time you run it.

• Conversion from reach-back. Whether the message produces tours. If it does not, the problem is usually that the match was not real or the message was generic.

• Leads closed as "not ready" versus "not interested." If your system only has one reason code, you cannot see this cohort at all, and that is the first thing to fix.

Common mistakes

• Running one cadence for every timeline. A sequence built for imminent movers will not engage someone five months out, and their non-response will be read as disinterest.

• Not capturing the move date as a date. Free text in a notes field is not a filter, and it will not trigger anything.

• Nurturing with nothing to say. Monthly check-ins with no new information teach the prospect to ignore your name. Reach out when there is something specific.

• Promising a unit you do not have. The resident whose lease expires in October may renew. Watch for, do not hold.

• Treating no response as no interest. Someone who cannot act on anything you sent has no reason to reply.

Back to XYZ, who inquired in June and rented four blocks away in October.

Nobody in your organisation made a mistake. The agent gave an honest answer. The cadence ran as designed. The lead was closed because it had not responded, which is a reasonable rule.

The loss came from the two facts never meeting. He told you when he was moving. Your own lease data hinted at what might be available then. Both were true in June, sitting in different systems, doing nothing.

That is one of the operational problems RIOO is designed to address. RIOO's leasing workflow provides structured inquiry and follow-up tracking alongside unit availability visibility, while its lease and renewal tracking gives visibility into upcoming expiries. That gives teams a stronger foundation for looking at future prospect demand alongside potential future supply.

Start by counting how many of last month's inquiries had a move date beyond sixty days, and how many of them are still in your system. That number will tell you whether this is worth building.

Frequently asked questions

Q1. How far in advance do renters start looking for an apartment?
Published renter guidance puts the typical window at two to three months before a move, with four or more in competitive markets, and much renter advice discourages starting earlier because units more than sixty days out are usually not yet listed.

Q2. Should you follow up with prospects who are not ready to move?
Yes, but on a different cadence. A short sequence built for imminent movers gives an early prospect nothing to act on. A single honest reply at inquiry, followed by a reach-back closer to their move date, costs far less effort.

Q3. What should you capture from a prospect with a distant move date?
Their intended move date as an actual date, their unit requirements, their price ceiling and their preferred contact channel. Those four fields are what make it possible to find them again when something matches.

Q4. How do you know what will be available months out?
Your lease expiration data gives you a forward view of which units reach a renewal decision and when. It does not guarantee those units will become vacant, because residents may renew. It gives the team a future availability signal to watch, not a promise to make.

Q5. Is long-horizon nurture worth the effort?
It depends on what share of your inquiries have distant move dates, which most operators have never measured. The prospects may still be valuable even though they cannot act today. Their intended move date and requirements give the team information it can use later, particularly when suitable availability begins to emerge.