Underwriting a Seattle DSCR Loan: What Belongs in the Rent Roll and
A debt-service-coverage ratio loan lives or dies on the quality of the revenue figure behind it, and short-term rental revenue is unusually easy to inflate or blur without meaning to. A host pulling numbers from three different sources, a market average here, a peak-month rate there, a neighboring town's figure somewhere else, can end up presenting a lender packet that looks generous on paper and falls apart the moment an underwriter starts asking where each number came from.
This page works from a single dataset for a single market: AirROI's extract for Seattle, filed for the twelve months running August 2025 through July 2026, covering 5,479 active listings. On that extract, the typical Seattle short-term rental earned about $33,351 in annual revenue, built from an average daily rate of $256, an occupancy rate of 46.3 percent, and a revenue-per-available-night figure of about $119. Every number in this page's underwriting discussion traces back to that one set, and nothing else gets blended in. This is not legal advice.
The Four Numbers That Belong Together
Treat $33,351, $256, 46.3 percent, and $119 as a single unit, not four separate facts a host can mix and match. A $256 average daily rate looks strong in isolation, but it only produces $33,351 in annual revenue because occupancy is 46.3 percent, not because every night of the year books at that rate. The $119 RevPAR figure is the number that reconciles the rate and the occupancy into a single realistic per-night average, and it is the number a lender's own underwriting model is most likely to reconstruct independently, so it should match what a host presents rather than being left out of the packet.
A lender packet that leads with the $256 ADR and omits the 46.3 percent occupancy figure is presenting an incomplete picture, whether or not that omission is intentional. An experienced underwriter will ask for occupancy regardless, and a packet that already includes it, framed honestly, reads as more credible than one that has to be pressed for the number that puts the rate in context.
Why the Extract's Time Window Matters to a Lender
These comps sit on the August 2025 through July 2026 extract specifically, not a blended, multi-year sound rent roll assembled from whatever data happened to be easiest to find. That distinction matters to an underwriter because a rent roll built on a single, clearly dated twelve-month window is verifiable and reproducible in a way that a blended multi-source estimate is not. If a lender's own analyst pulls a comparable extract for the same window, the numbers should match what the packet presented, and any mismatch becomes the host's problem to explain, not the lender's problem to overlook.
Lead time on this sample runs about 45 days, and typical stay length is about 6.5 nights. Neither of those figures is a revenue number on its own, but both describe the turnover and booking-pattern assumptions embedded in the $33,351 figure, and a sophisticated lender packet includes them as supporting context rather than leaving the revenue figure to stand alone without any explanation of the booking pattern that produced it.
What Does Not Belong in the Column That Has to Pay the Note
Keep tourism copy, market-growth narratives, and neighborhood color entirely out of the column that has to service the debt. A lender's decision rests on whether the property's demonstrated revenue supports the loan payment, and general statements about Seattle's popularity as a destination do not move that calculation in either direction. If a packet spends more space describing the city's appeal than it does documenting the property's actual comparable revenue, that is a sign the packet is compensating for a weaker underlying number rather than presenting a strong one clearly.
The same discipline applies to Tacoma. Tacoma listings on this same extract earned about $22,092 in typical annual revenue across 762 active listings, a meaningfully different market at a meaningfully different scale than Seattle's $33,351 across 5,479 listings. They do not share a licensing office, a guest profile, or a listing count, and blending the two into a single regional average produces a number that describes neither market accurately. Keep Tacoma on its own separate line in any packet that happens to reference it, and never let it quietly inflate or deflate a Seattle-specific revenue figure.
The Ordinance Details a Lender Packet Should Also Carry
A lender packet built around $33,351 in projected revenue is incomplete if it does not also address whether that revenue is legally available to collect. Seattle short-term rentals sit under a two-unit operator cap, and an operator license costs 75 dollars per unit through the Seattle Services Portal. A property that cannot obtain or maintain that license cannot legally operate as a short-term rental, which means the entire revenue projection underlying the loan request depends on a licensing status that has to be confirmed, not assumed.
Confirm remaining 2026 tax obligations through the primary city pages rather than presenting an estimated tax stack in the packet; this page is not going to guess a specific percentage it cannot verify in this sample, and a lender packet should apply the same restraint. Confirm remaining 2026 license display rules on the ordinance directly, and be prepared to show that confirmation as part of the loan file, not just reference that it exists somewhere.
A complete lender packet, in other words, carries four things together: the $33,351 revenue figure itself, confirmed remaining registration status, confirmed remaining tax obligations, and Tacoma's numbers kept on a clearly separate line if they appear at all. Leaving any one of those four out weakens the packet, and blending them together in a way that obscures which number came from where weakens it further.
Reading the Trend Line Before Projecting Forward
Year over year in this sample, revenue is up about 0.1 percent, essentially flat, while the number of active listings is up 12.3 percent. A lender packet that projects meaningful revenue growth for a new or refinanced property should account for that backdrop directly, because a market where supply is expanding faster than revenue is a market where a new entrant faces more competition for a similar-sized pool of demand than existing operators faced a year earlier.
That does not mean a Seattle short-term rental cannot support a DSCR loan in this sample's numbers. It means the projection presented to a lender should be grounded in the current $33,351 figure rather than an assumed growth trajectory that the trend data does not support. A conservative projection that holds up under scrutiny serves a borrower better than an optimistic one that an underwriter discounts on sight.
Where February Fits Into a DSCR Conversation
Occupancy in this sample is weakest in February, and a DSCR calculation that assumes even monthly revenue across all twelve months will overstate cash flow in the market's slowest stretch and understate it in the strongest. A packet that shows monthly or seasonal detail, rather than a flat annualized average divided by twelve, gives a lender a more accurate picture of when the property's cash flow is tightest, which matters directly to a coverage ratio calculation that is often stress-tested against a slow-month scenario rather than an annual average.
None of this is a reason to avoid financing a Seattle short-term rental. It is a reason to present the numbers with enough honesty and specificity that an underwriter can trust them on first read, rather than needing to reconstruct the real picture from a packet that blurred the distinctions this page has just walked through.
How This Differs From a Traditional Long-Term Rental Comp
A DSCR lender comfortable with traditional long-term rentals may not automatically know how to evaluate short-term rental income, and that gap is worth addressing directly in the packet rather than assuming the underwriter will bridge it unprompted. A long-term lease produces a single, stable monthly figure that barely moves across the year. A short-term rental's $33,351 annual figure is an aggregate of nights that vary enormously by season, and presenting it as if it behaved like a flat monthly lease payment invites confusion the moment an underwriter starts modeling monthly debt service against monthly income.
The clearer approach is to present the annual figure alongside an explanation of how occupancy varies across the year, with February identified specifically as the weakest month in this sample and June, July, and August identified as the strongest. A lender evaluating coverage in the property's worst month, rather than its average month, is applying a more conservative and more defensible standard, and a borrower who volunteers that seasonal breakdown rather than waiting to be asked for it signals exactly the kind of preparedness an underwriter is looking for in a short-term rental file.
It is also worth stating explicitly, in the packet, what is not being claimed. This page does not assert a specific tax percentage, because none is confirmed in this sample, and it does not project revenue growth beyond what the flat year-over-year trend supports. A packet that draws that same line, stating clearly what is confirmed and what still needs verification with the relevant city office, reads as more trustworthy than one that fills every gap with an optimistic guess.
Documenting the Comparable Set Itself
Beyond the headline revenue figure, an underwriter reviewing a short-term rental file will often want to understand what made up the comparable set behind that number. AirROI's extract for Seattle draws from 5,479 active listings across the twelve-month window ending July 2026, and a packet that can speak to that scale, that it is not a handful of hand-picked comps but a broad market sample, gives the $33,351 figure more credibility than a narrower or unstated data source would. A lender is far more likely to accept a number they can trace to a large, dated sample than one attributed vaguely to "market research" or "comparable listings" without further detail.
The same applies to the $256 ADR, the 46.3 percent occupancy figure, and the $119 RevPAR. Each of these should be presented as coming from the same dated extract, not stitched together from different sources at different points in time. A packet that mixes an ADR pulled from one source with an occupancy figure pulled from another, months apart, is presenting a synthetic number that does not actually describe any real twelve-month period, and that kind of inconsistency is exactly what a careful underwriter is trained to catch.
Consistency across the whole packet, one dataset, one time window, one clearly stated source, is ultimately the strongest thing a borrower can offer a DSCR lender evaluating a Seattle short-term rental. It will not turn a genuinely weak property into a strong loan candidate, but it removes the friction and follow-up questions that come from a packet that looks assembled from mismatched pieces, and it lets the underwriter evaluate the property on its real merits rather than on how well the paperwork holds together.
Related Reading
Washington years already live on Crest and Cove: file Anacortes, Poulsbo, and Forks on their own lines before you underwrite Seattle.
Frequently Asked Questions
What is the core revenue figure to use in a Seattle DSCR loan packet?
About $33,351 in typical annual revenue on 5,479 active listings, built from a $256 average daily rate, 46.3 percent occupancy, and about $119 RevPAR, all from AirROI's extract for August 2025 through July 2026.
Why does occupancy matter if the ADR is already strong?
Because a $256 ADR only produces $33,351 in annual revenue at 46.3 percent occupancy. Presenting the rate without the occupancy figure gives an incomplete and potentially misleading picture to an underwriter.
Should Tacoma's numbers be included in a Seattle lender packet?
Only on a clearly separate line, never blended in. Tacoma earned about $22,092 on 762 listings on the same extract, a different market at a different scale that should not be averaged with Seattle's figures.
What licensing detail should a lender packet address?
Seattle short-term rentals sit under a two-unit operator cap, and an operator license is 75 dollars per unit through the Seattle Services Portal. Remaining 2026 registration status should be confirmed and documented in the loan file.
Does this page state a specific 2026 tax rate for Seattle short-term rentals?
No. Remaining 2026 tax obligations should be confirmed directly through the primary city pages; this page does not guess a percentage it cannot verify on the current extract.
Should tourism or market-growth narrative be included in the underwriting packet?
No. The column that has to service the debt should contain the property's actual comparable revenue figures, not general statements about the city's appeal as a destination.
How should February's weak occupancy factor into a DSCR calculation?
A packet showing seasonal or monthly detail, rather than a flat annualized average, more accurately represents the property's cash flow during its slowest month, which matters for a coverage ratio stress test.
What is happening with supply and revenue trends in this market?
Revenue on the current extract is roughly flat year over year, up about 0.1 percent, while active listings are up 12.3 percent, a backdrop that should temper any assumed revenue growth in a loan projection.
What time window does this sample cover?
The twelve months running August 2025 through July 2026, and any lender packet built from this data should be dated and referenced to that specific window rather than presented as a generic average.
What four things should a complete Seattle lender packet include together?
The $33,351 revenue figure, confirmed remaining registration status, confirmed remaining tax obligations, and Tacoma's numbers kept on a clearly separate line if referenced at all.
Is a 30-night minimum stay relevant to a DSCR underwriting packet?
About 46.5 percent of Seattle listings in this sample carry a 30-night minimum, but typical stay length is still about 6.5 nights. A packet should not model occupancy as if a 30-night filter automatically fills a month; that filter is not the same as filled occupancy.
What lead time does this sample show for Seattle bookings?
About 45 days on average, which describes the booking window rather than occupancy, and should be presented in a packet as supporting turnover context rather than as a revenue figure itself.
Work with Crest & Cove Creative
A DSCR file that borrows Emporia into Cottonwood Falls is already wrong. Start with the published local year and both desks.
Confirm remaining 2026 registration and tax status before finalizing any lender packet, and keep Seattle's $33,351/5,479-listing figures separate from Tacoma's in every line of the underwriting file. Name the failure mode the guest can check on the listing.
Reach out at crestcove.co or (256) 998-7502.
Comments