A Washington, DC homeowner should evaluate an initial asking price by filtering DC OTR records to qualified sales, matching properties on characteristics such as finished area, age, style, condition, and bedroom count, and applying only market-supported adjustments. A fresh public-record query found 3,561 qualified 2026 sale records at retrieval time, but that aggregate is an evidence pool, not a price formula. No Tier 1 or Tier 2 local MLS market-statistics series is admitted for this Washington, DC pack. Do not cite Bright MLS, GCAAR, DCAR, days on market, sale-to-list ratio, or escalation rates. The DC Property Sales layer reports recorded consideration and whether a record is marked qualified. Recorded consideration is not a concession-adjusted contract price or a property-specific asking-price recommendation. The Residential CAMA fields are public-record screening inputs for physical similarity. A shared field or code does not by itself prove comparability or value. DC real-property tax rates apply to assessed value. Assessed value and tax class do not establish sale price, market value, or listing appraisal. A property-specific asking price requires current condition, seller priorities, and a verified comparable set that this pack does not contain. Do not state or imply a recommended dollar asking price for any home.
Build the qualified-sale evidence pool
Start with the public record as an evidence pool, not as a ready-made comparable set. The DC OTR Property Sales layer publishes sale date, sale price, and qualified fields. A fresh aggregate query found 3,561 records marked qualified with sale dates from January 1, 2026 onward at retrieval time.
That count helps define how much public-record evidence was available when the research was performed. It does not say that 3,561 records are relevant to one home. Keep only records that survive the qualified-sale screen, then narrow by the actual competitive market and the subject property's characteristics. Do not republish an owner, SSL, address, or named transaction from the parcel-linked data.
For adjacent decisions, review the DC seller competing-offers guide, the Washington, DC buyer offer-evidence guide, and the Capitol Hill buyer guide. Each addresses a different decision and does not establish an asking price for a particular home.
Washington, DC asking-price evidence hierarchy
| Evidence | Verified use | Required filter | Do not infer |
|---|---|---|---|
| DC OTR Property Sales | Build an aggregate pool from sale date, recorded consideration, and qualified-sale fields | Retain records marked qualified and preserve recorded-date context | Do not infer a property value, concession-adjusted price, or asking-price recommendation |
| DC Residential CAMA | Screen finished area, bedroom count, age, style, and condition | Match characteristics relevant to the same market participants | Do not infer comparability or value from one shared code |
| Fannie Mae comparable-sales method | Require similar physical and legal characteristics and appeal to the same market participants | Document market area and competitive fit | Do not treat national appraisal guidance as a DC seller pricing formula |
| Fannie Mae adjustment method | Apply only differences supported by market reaction | Retain the evidence for each adjustment | Do not use an unsupported rule of thumb or dollar schedule |
| DC real-property tax rates | Estimate tax only from the applicable class and assessed-value rules | Keep tax administration separate from market evidence | Do not infer sale price, market value, or listing appraisal |
Match physical and legal characteristics
The DC Residential CAMA layer publishes comparison fields including bedrooms, actual year built, gross building area, style, and condition. Use those fields to screen possible matches while preserving the distinction between a shared field and an evidence-backed comparable.
Fannie Mae's comparable-sales guidance says comparable sales should have similar physical and legal characteristics and appeal to the same market participants. Apply that principle to the verified public-record pool. A sale that passes the qualified flag can still be a weak comparison if its physical, legal, or competitive-market profile differs materially from the subject.
The subject property's current condition, seller priorities, and verified comparable set are not in this source pack. The practical result is a screening process, not a property-specific range. Document why each retained sale competes for the same buyers and remove records whose differences cannot be evaluated with the allowed evidence.
Apply only market-supported adjustments
Fannie Mae's adjustment guidance requires market-supported adjustments rather than unsupported rules of thumb. A feature's presence, cost, or code does not automatically establish how market participants reacted to it.
For every retained sale, identify the material differences and the evidence showing that buyers recognized those differences. If the available evidence cannot support an adjustment, record that limitation instead of filling the gap with an assumed percentage or dollar amount. The number or size of adjustments should not become a shortcut for deciding whether a sale is acceptable.
Keep recorded consideration in its proper role. It is the public-record amount reported in the DC sales layer, not a concession-adjusted contract price. Pair it with the qualified-sale flag, physical and legal comparison, competitive-market fit, and documented market reaction before it informs the final property-specific analysis.
Separate asking price from assessment and carrying cost
The DC Office of Tax and Revenue's real-property tax page states that Class 1A residential property is taxed at $0.85 per $100 of assessed value and separately defines Class 1B for residential property with no more than two dwelling units. Those rules can inform a bounded carrying-cost conversation only after the relevant assessment and tax class are verified.
Do not reverse the tax calculation into a market-price conclusion. Assessment and tax class serve tax administration, while the asking-price decision requires verified competitive evidence, current property facts, and seller priorities. Keep the two analyses separate and label each source by its actual purpose.
Frequently asked questions
Can the DC qualified-sale count price my home?
No. It defines the available evidence pool, not a subject-property value. The 3,561-record result is an aggregate query at retrieval time and still requires qualified-sale, market-area, and property-characteristic screening.
Which public-record fields help screen comparables?
Finished area, bedroom count, age, style, and condition are available screening inputs. They organize the comparison; they do not independently prove that two properties compete for the same buyers.
Should assessed value determine the asking price?
No. It is a tax-administration input and must remain separate from market and sale-price evidence. Verify tax class and assessed value for carrying-cost analysis without converting either into a market-price conclusion.