DC Water's unusually direct language about cleanup responsibility gives Washington a strong trust-support and owner-risk wedge.
Buyer, seller, or older-home uncertainty -> inspection-first pages Start with the buyer and inspection pages when the next smart move still depends on better footage or a calmer pre-closing read.
Report finding or backup clue -> interpretation-first pages Use defect pages before the cost conversation hardens around one scary phrase or one symptom.
Known issue and money question -> cost pages Move into repair-versus-replacement or price-direction pages only when the line story is stronger.
Local rule, boundary, or program signal -> support pages Use local responsibility pages when the city signal materially changes the answer, not as the default first stop.
Housing signal:The city signal here is official responsibility language rather than unusually old sold-home stock.
Local system:DC Water says owners are typically responsible for cleanup and many maintenance-related backup causes, and that the utility generally does not pay damages.
Next-step bias:Use responsibility pages to move uncertain users into estimator or inspection-first logic, then quote once the problem is evidence-backed.
Start With the Tool
Get the next move with Washington, DC context already carried forward
Use the tool before you browse the whole local cluster. The estimator will start with this city context in place, then continue from the first missing step.
Start Here in Washington, DC
These are the clearest local entry pages in acquisition order: buyer and inspection first, defect interpretation next, cost comparison after that, and local rule pages only when the city signal materially changes the call.
Use these starting points when you need to share one city page with a buyer, seller, owner, or agent without sending them through the whole cluster first.