A thin resort market does not produce enough recent sales to build a comp set the way a larger metro area would, and pricing a replacement candidate on assumption instead of evidence is how an exchange overpays or underestimates financeability. This service assembles a defensible comparable set for Park City candidates, pulling in outside data where the local record alone is not enough.
Why Local Comps Alone Often Fall Short
Main Street commercial condos, Kimball Junction retail pads, and Deer Valley or Canyons-area condo-hotel units each trade infrequently enough that a strict same-corridor, same-asset-type comp search can turn up only one or two usable transactions inside a reasonable lookback window. Treating that thin a sample as conclusive pricing evidence is not a sound basis for an identification or offer decision.
A workable comp set for this market typically blends true local sales with listings, under-contract data, and income-based comparisons drawn from the broader Wasatch Back and, where the asset class supports it, the Salt Lake City valley.
The lookback period itself needs a wider window in Park City than it would in a market with more transaction volume, since a comp that closed eighteen months ago may still be the most relevant data point available for a given corridor, provided the market conditions behind it are noted rather than assumed to still hold.
Adjusting Comps Across Different Market Drivers
A Park City comp is not a simple price-per-square-foot match to a Salt Lake City comp, since seasonal occupancy, HOA structure, and resort proximity all affect value in ways a flatland commercial property does not carry. Adjustments have to account for lease quality, building condition, remaining useful life on major systems, and whether the comparable property's income is stabilized or still ramping, alongside its location and size.
Cap-rate context matters here too, since a rate that looks attractive on a resort-adjacent property may reflect real seasonal income volatility rather than a genuine pricing discount.
A Kimball Junction retail comp and a Main Street storefront comp can carry very different cap rates even at similar price points, since one is driven by drive-by commercial traffic and the other by tourist foot traffic tied to the ski season calendar; treating those two corridors as interchangeable in a comp set produces a misleading pricing range.
Comp Package Line Items
- Closed sale comparables within a defensible lookback period
- Active listing and under-contract data where closed sales are scarce
- Income and cap-rate comparison adjusted for lease quality
- Physical condition and capital expenditure notes for each comp
- Broker opinion of value supporting the final pricing range
Each line item in this package should note the date it was pulled, since Park City pricing can move noticeably between the start of a search and the day an offer is actually written.
Using the Comp Set to Support Identification Decisions
The comp package should be finished before a candidate is finalized on the identification list, since it directly affects the value figures that matter for 200%-rule aggregate math and for lender underwriting. Pricing a candidate too high on a thin comp set can also complicate a boot calculation, since replacement value assumptions feed directly into that worksheet.
A comp set built on an overly optimistic pricing assumption can also affect the 200%-rule math on the whole identification list, since a single candidate valued too high can push the aggregate closer to the cap than the actual market supports, leaving less room for the rest of the list.
When a Wider Geographic Comp Set Is the Right Call
For an asset class with almost no local trading history in Park City, such as small-bay industrial or a specialized commercial condo, the more defensible comparison is often a wider set of similar properties across the Wasatch Back or the Salt Lake City corridor rather than a forced match to the two or three closest resort-market sales. That broader comp set should still be reviewed with the investor's broker and, where the pricing decision affects the exchange structure, the investor's tax advisor.
Common 1031 Exchange Questions
Why can't a Park City comp set rely only on same-neighborhood sales?
Trading volume in specific corridors like Main Street or Kimball Junction is often too thin to produce enough recent, comparable sales, so a defensible comp set typically pulls in listings, under-contract data, and sales from the broader Wasatch Back.
How does seasonal occupancy affect comp adjustments for resort-area property?
Income and cap-rate comparisons need to account for whether a comparable property's revenue is driven by peak-season short-term rental activity or stabilized long-term leases, since those income profiles are not directly comparable.
Should active listings be used in a comp set if closed sales are scarce?
Yes, active listing and under-contract data can supplement a thin closed-sale record, though they should be clearly labeled as such rather than treated with the same weight as a completed transaction.
Does the comp analysis affect the boot calculation on an exchange?
It can, since the replacement property's assumed value feeds directly into the debt-and-equity worksheet used to check for boot exposure, so an unrealistic comp-based value can distort that calculation.
When should the comp package be finished relative to identification?
Before the candidate is finalized on the written identification list, since the comp-supported value affects both the 200% or 95% rule math and any lender underwriting tied to the acquisition.
