An application comes in at 7:10pm on Monday. The approval goes out Thursday afternoon.

Ask anyone involved what happened in between and you will get a shrug and the word screening. Ask them to account for the hours and the answer thins out fast, because the actual decision-making may occupy only a small fraction of those three days.

Everything else was waiting.

That distinction matters more than it sounds, because the two are fixed by completely different things. Decision time is fixed by better criteria and clearer authority. Waiting time is fixed by knowing what you are waiting for and who is chasing it. Most operators try to solve the second problem with tools built for the first.

What the three days are actually made of

Apartments.com publishes an operator-facing breakdown of application processing that is unusually specific, and it is worth reading against your own numbers. Their guidance puts a complete application at one to three days, made up of:

Look at the right-hand column and notice what kind of time it is.

Credit scoring is automated and fast. The completeness review is genuinely your work and is typically a same-day step. Criminal and eviction screening runs on someone else's clock. Employment verification and landlord references depend entirely on a third party picking up a phone.

Apartments.com identifies employment and income verification plus landlord references as often the slowest variable, because you are waiting on people outside your organisation. And the two biggest causes of delay they identify are incomplete applications, missing SSN, prior addresses, employer information or consent, and slow third-party responses.

Neither of those is a screening problem. One is an intake problem and one is a chasing problem.

The variance is worse than the average

There is a second thing hiding in that table, and it causes more damage than the durations do.

Credit might return in seconds. It might take 24 hours. Background screening might take one day or three. Verification might come back the same afternoon or after the weekend.

So the timeline can vary substantially from one application to the next, with that variation coming from third-party response times, screening turnaround and the completeness of the application itself. Only the last of those is fully yours.

Which means you cannot promise an applicant a decision date, and if you cannot promise a date, you cannot manage their expectations, and an applicant with no expectation to hold onto keeps looking.

This is the part that costs leases. Not the length of the wait. The unpredictability of it.

Some of that delay is load-bearing

Before the obvious conclusion, the necessary counterweight.

Not all of this time is waste, and an article telling you to compress every hour of it would be giving you bad advice.

Verification exists because self-reported income is not evidence. Consistent criteria applied to every applicant, in the same sequence, with the same questions, is what makes your decisions defensible and comparable. Documentation requirements create a record of why each decision was made. Apartments.com's own guidance points the same way: request references upfront, use a consistent set of questions, and document your steps so decisions remain fair and repeatable.

Speed achieved by skipping verification is not speed. It is a cost you have deferred to your collections team, and it arrives with interest.

So the exercise is not compressing the whole thing. It is separating the delay that protects you from the delay that is just disorganisation, and removing only the second kind.

A simple test on any hour in your process: if this wait ended right now with no new information, would the decision be worse? If yes, it is load-bearing. If no, it is queue time.

A significant part of the time between Monday evening and Thursday afternoon can be queue time.

Why one SLA number does not work

Here is where most operators go wrong when they try to fix this. They set a target, usually 48 hours, apply it to every application, and then discover it is met about half the time with no clear pattern.

The reason is that four genuinely different situations are being measured with one clock.

• A complete file with a salaried applicant and a responsive employer. Everything can move in parallel. This is your fast case and it should be fast.

• A file missing documents. The clock now belongs to the applicant, not you. It should be measured separately or your average becomes meaningless.

• A file with a guarantor or co-signer. Two people to verify, two sets of documents, and a signing sequence that has to hold them both.

• A self-employed or non-traditional-income applicant. Bank statements, tax returns, an accountant's letter. Longer by nature, and not a failure.

Averaging those four produces a number that describes nobody's experience and explains nothing. We made the same argument about funnel metrics in the four conversion rates behind your lead-to-lease number: a blended figure hides the thing you needed to see.

An SLA that actually holds

Set the clock per situation, and state what you are waiting for. The targets below are a starting framework rather than an industry standard, and they should be set against your own screening policy, staffing and verification process.

Three rules make it work.

• Stop the clock explicitly, and say so. "Waiting on applicant" and "waiting on employer" are different states from "in review," and they need to be visible as such. A single "processing" status is how three days disappear without anyone noticing.

• Set an internal deadline on third parties. Apartments.com suggests 24 to 48 hours, then a backup plan: request alternate contacts, accept additional documentation such as recent pay stubs, an offer letter or bank statements where appropriate, or proceed on other verifiable criteria applied consistently. The important word is consistently. A backup path used for some applicants and not others creates a different problem than the one you were solving.

• Give the applicant a date, not a duration. "You will hear from us by 5pm Wednesday" is a commitment somebody owns. "Two to three business days" is a range that starts from an unclear moment and can always be interpreted generously.

What to instrument

Four numbers, reported monthly.

• Time from submission to complete file. Your intake quality. If this is long, the problem is your application form, not your screening.

• Time from complete file to decision. Your actual processing speed, which is the only part fully within your control.

• Share of applications that arrive incomplete. One of the highest-leverage numbers in this process. Reducing it removes follow-up work from the stages downstream.

• Time spent in each waiting state. Waiting on applicant, waiting on third party, waiting on approver. The third one is usually small and the most embarrassing.

Most operations can produce the first and last dates and nothing in between, which is the same measurement gap we covered in why your response time number is probably wrong. Without the intermediate timestamps you know the approval took three days and you cannot say which day to attack.

What this is worth

Application to approval sits near the end of the funnel, which is exactly why the time there is expensive.

By the point somebody applies, you have paid for the lead, answered it, run the tour and held the unit. Every cost is already incurred. A day lost here is not a day of marketing inefficiency, it is a day of rent on a unit you have effectively taken off the market while an applicant decides whether to keep waiting.

And the applicant is not waiting exclusively. Renters apply to more than one place. The operator who says Wednesday at 5pm and means it is competing against one who said a few days and went quiet.

Common mistakes

• Blaming screening. The automated components are mostly fast. The slow parts are third-party verification and incomplete intake, and neither improves by changing screening vendors.

• Measuring the average. One weekend-spanning application skews it, and the average moves in ways that feel meaningful and are not.

• Leaving "waiting on applicant" unowned. It is the state where applications go quiet. It needs a person on your side, a chase schedule and an expiry, not just a status.

• Compressing the verification. Covered above. The wait that produces information is not the wait to remove.

• No named approver. When approval authority sits with one person and that person is on leave with no delegate, a file that was ready Tuesday goes out Friday. Our piece on the four joins where lead-to-lease quietly breaks covers this failure at the approval stage in detail.

Back to Monday evening. The application arrived at 7:10pm, and it was reviewed on Tuesday morning, screened by Tuesday afternoon, and then sat until Thursday because a previous landlord had not called back and nobody had decided what to do about that.

A few decision points, spread across three days, because the waiting had no owner, no deadline and no visible state.

That is one of the operational problems RIOO is designed to address. RIOO connects applications, screening and lease execution rather than running them as separate steps with gaps in between, and tenant acquisition and screening keeps the application and its status attached to the prospect, so where a file is sitting is a question with an answer.

Pick your last ten approvals and mark, for each one, the hours where something was being learned and the hours where nothing was. The second number is the one worth attacking.

Frequently asked questions

Q1. How long should application to approval take?
Published operator guidance puts a complete application at one to three days, with the range driven mainly by criminal and eviction screening and by third-party verification. A reasonable internal target is 24 hours from complete file to decision for a standard application, with longer targets for guarantor and non-traditional income cases.

Q2. What is the slowest part of the rental application process?
Employment and income verification together with landlord references, because you are waiting on people outside your organisation. Screening reports often return faster than the verifications around them.

Q3. Why do our approval times vary so much?
Usually because several different application types share one clock. A complete salaried file, a file missing documents, a guarantor case and a self-employed applicant have genuinely different timelines, and averaging them produces a figure that describes none of them.

Q4. What should we do when an employer or reference will not respond?
Set an internal deadline, commonly 24 to 48 hours, then move to a documented backup path: alternate contacts, additional documentation such as pay stubs or bank statements where appropriate, or a decision on other verifiable criteria. Apply that path consistently to every applicant and record the steps taken.

Q5. Should we speed up approvals by reducing verification?
No. Verification is the part of the delay that produces information. The time worth removing is queue time, meaning hours where nothing is being learned and nobody is acting.