Ask ten agents to make a list of what slows down a landlord policy and most of them will have "underwriting." on their top-5. Ask the underwriters and you'll get a different answer. It's not the risk itself that eats the days; it's the back-and-forth that happens when the file doesn't say enough on its own. We asked our underwriting team what they wish every agent knew before hitting submit, and the pattern was consistent enough that it's worth writing down.
A landlord risk lands on referral on a Tuesday. Underwriting pulls the file, checks the public records, and finds a listing photo showing a sagging roof next to a kitchen mid-demolition. A question goes back to the agent. The agent reads it Wednesday afternoon, calls the owner Thursday, has photos in hand by Friday, and forwards them Monday morning. The decision comes back that afternoon. Six days, for a question that had an answer the whole time. It just hadn't been written down yet.
Here's the thing about that six-day loop: nobody in it did anything wrong. Underwriting asked a fair question about what the photo showed. The agent tracked down the owner and got the answer. But every one of those handoffs costs something. Multiple exchanges back and forth cost underwriting time they could be spending analyzing risk instead of chasing documentation. It costs you a chunk of your closing window. And it costs the owner, who is sitting there wondering why a policy is taking a week to bind when the actual work on the house wrapped up two months ago.
Speeding that loop up isn't about being a better negotiator or knowing some secret handshake with underwriting. It's mostly about sequencing: getting the right things into the file before anyone has to ask for them. That's the whole idea behind this piece.
You're not submitting an application. You're submitting proof.
Underwriting is going to reach a decision on your risk using whatever evidence exists, not the evidence you have in your head from talking to the owner. That evidence is public records, aerial imagery, prior listings, and loss history reports. If the internet's picture of the property is eighteen months old and wrong, the file starts out wrong, and it's on you to close that gap before anyone has to ask. That's a strange position to be in, if you think about it. You might know the property cold. You've talked to the owner, maybe even driven by it. None of that reaches the underwriter unless it shows up as something they can look at.
Think about what a stale listing actually shows. It's photos taken to sell a distressed property, staged to be brutally honest about its flaws because the buyer was an investor looking for exactly that kind of deal. Curling shingles. A bathroom stripped down to the studs. That listing is the most detailed information anyone outside your office has about the property, and it's a portrait of the house on the worst day of its life. Your owner then spent four months and $40,000 fixing all of it. Nobody on the underwriting side knows that unless you say so, with proof, in the submission.
The four situations that generate the avoidable back-and-forth
These four come up constantly, and in every case, the underlying risk is usually fine. What's missing is the paperwork that would let underwriting see that.
Recent renovations
If the owner completed work before coming to you, send current photos showing the finished condition. If there are invoices, send those too. A note in the submission saying the property was recently remodeled does not do this job. It creates a question rather than answering one. Underwriting can't rate a claim they can't see.
This is the most common, preventable delay we see. An agent writes "recently renovated" in good faith, underwriting looks at a listing showing the opposite, and now there's a discrepancy that has to be resolved before anything else can happen. Nobody's lying. The listing is just older than the truth.
Roof replacement
Same principle, higher stakes, because roof age affects eligibility itself, not just pricing. If the roof has been replaced, share the documentation: an invoice from the roofer, a permit, dated photos. Roof age is one of the few inputs where documentation alone can move a risk from ineligible to bindable, so it's worth the phone call to go get it. A five-minute conversation with a contractor can be the difference between a decline and a bound policy.
Claims, open or recent
If there's an open claim, send the loss experience letter or the loss runs confirming it's closed. Send the story: what happened, what was damaged, what got repaired. A line item in a loss history report tells underwriting that money moved; it doesn't tell whether the underlying condition still exists. That's the thing underwriting actually needs to know, and it's the one piece of context a loss run will never give them on its own.
Prior cancellation or non-renewal
This one has a narrow path. If the applicant was cancelled or non-renewed for underwriting reasons, send a copy of the cancellation documentation along with proof the issues have been mitigated. Without that, there's nothing to review. With it, there's something to review. There's no middle option here worth pursuing; either the file has both pieces or it doesn't move.
In each of these four cases, agents already know the good news. The problem is that the good news is invisible to everyone else in the file, and invisible good news doesn't count for much in underwriting.
Three structural things that trigger a referral all by themselves
The situations above are about proof. These are about how the submission itself gets built, and they're the ones that produce a request for information rather than a decision, no matter how clean the property's history is. You can have flawless documentation and still land in referral if one of these three is off.
Every named insured has to be on the deed
Confirm this before submitting rather than after. If a spouse, a business partner, or an LLC is going on the policy, verify they actually hold title. A few related items are worth catching at intake, too: entities work for premises liability if they're on the deed and have no operations beyond owning and maintaining rentals, but not for personal liability; ownership split among more than two individuals, spouses excepted, needs pre-approval; and a property carrying more than two mortgage interests is ineligible outright.
None of these are exotic scenarios. They come up in ordinary intake conversations, which is exactly why they're worth a checklist rather than memory.
ADUs and detached dwellings get scheduled as separate dwellings
Standard practice at most insurance providers is to let a detached structure fall under other structures coverage, typically capped at 10% of the dwelling limit. That's fine for a shed. Is it fine for a 600-square-foot unit with a kitchen and a bathroom that might generate its own rent under its own lease? Not even close.
An ADU being rented under a separate lease is a second dwelling. It needs its own dwelling line, its own loss-of-rent calculation, and its own occupancy treatment; it cannot be folded into the main dwelling limit, and it isn't included in private structures coverage either. The test is straightforward: is the unit generating rental income under its own lease? If yes, it's a dwelling. If it's unrented and being used for storage or as a guest space, private structures is the right home for it. Getting this wrong doesn't just slow the file down. It can leave the owner underinsured on the one structure generating the most income.
Verify the rating details and the replacement cost estimate
Do this before you submit, not after underwriting flags it. Property data pulled from third-party sources is frequently close but not right; square footage, year built, and construction type can all drift from reality. An RCE built on wrong square footage produces a coverage amount the owner will argue with and an underwriter will question, and now you're fixing two problems instead of zero. A ten-minute gut check against the county record or a recent appraisal is cheap insurance against a much longer conversation later.
Collect proof at intake, not at referral
Here's a sequencing point that matters more than it looks like it should. The moment to ask an owner for roof invoices and renovation photos is the first conversation, while they're motivated and the quote is the thing they actually want. Two weeks later, once that urgency has drained out of the process, that same request lands as homework instead.
So fold it into intake. When an owner mentions work they've done, ask for proof in the same breath, before you've even hung up. Most of them have it on their phone; contractors text photos, and invoices arrive as PDFs the same day the job wraps. Get it while you're on the call, and it's sitting in your file whether you end up needing it or not. That's the entire difference between a document you have and a document you have to go get later, under a deadline, from someone who's already moved on mentally.
For agents who have already tightened the front end of the quoting process, underwriting is usually where the remaining lag is hiding. It's the same discipline, applied one step later in the pipeline: ask for the proof while the conversation is already happening, instead of opening a second conversation later to get it.
What good looks like
Strip everything above down and the standard is simple enough to keep on a sticky note: before you submit a landlord risk, ask what a stranger would conclude about this property from the internet alone. Then ask what you know that contradicts it. Attach that.
Concretely, that means:
- Current photos any time the online record shows a condition that no longer exists
- Invoices or permits for renovations and roof work
- Loss runs or a loss experience letter for any claim, with a plain-language note on what was repaired
- Cancellation documentation plus mitigation proof if the applicant has been non-renewed for underwriting reasons
- Named insureds verified against the deed
- ADUs scheduled as separate dwellings when they're rented under their own lease
- Rating details and the RCE checked against reality
None of this is complicated once it's written out. It's just easy to skip when you're moving fast and the deal in front of you looks routine, and the seven items above take longer to read than they do to actually collect.
The information requested is what the decision actually turns on. The faster it arrives, the faster you get an answer, and an approved quote or a clean decline are both better outcomes than a file sitting in limbo while your owner's closing date quietly moves. You can find the full documentation checklist by product line, plus what a complete submission looks like end to end, inside your agent dashboard. And if you want the broader playbook this fits into, the agent hub is worth bookmarking.
.jpg)
.png)