Records
Permit history with relationship scope intact.
Quoin connects Washington, DC building, occupancy, public-space, home-occupancy, and well-permit records to property research. Every record keeps its publishing agency and property-link scope.
Start freePermit sources represented
| Source family | Publisher | What it describes |
|---|---|---|
| Building permits, 2009–2026 | D.C. Department of Buildings | Construction and alteration permit records |
| Certificates of occupancy | D.C. Department of Buildings | Published occupancy documents and permits |
| Public-space permits | D.C. Department of Transportation | Activity involving public space, not building occupancy |
| Home-occupancy and well permits | DOB and DOEE | Source-specific permit records with their own limitations |
Exact facts versus context
An official SSL link with exact-property scope can support a parcel-specific assertion. Shared-building, multi-parcel, and proximity links remain contextual and are labeled that way in the response.
Quoin uses no fuzzy regulatory record-to-property matching. Ambiguous address associations above the release cap are excluded from serving rather than assigned to a convenient account.
What a permit does not prove
- Issuance does not prove work was completed or code-compliant.
- A public-space permit does not establish activity on a private parcel.
- Absence from the frozen release does not prove that no official record exists.
- Permit records do not replace physical, legal, zoning, or appraisal diligence.
Permit data FAQ
Are all linked permits exact property facts?
No. Only exact-property links are parcel-specific; other relationship scopes are explicit context.
Does an issued permit prove completed work?
No. A permit record is not proof of completion, inspection outcome, or overall code compliance.
How are records verified?
Evidence includes the publishing agency, frozen release, record identifier, and a display-ready official portal route with lookup steps.