Start with the retired square, suffix and lot exactly as printed on the old record. Then build a dated bridge to every successor key before deciding which permit file belongs to the earlier parcel configuration.
A historical District evaluation explains that an SSL represents one parcel configuration. A split or combination retires that identifier and assigns new identifiers. This can explain why an older permit and a current parcel use different keys; how a specific permit is indexed has to be checked in the permit file itself.
Link the retired SSL to each successor SSL with a dated record
| Evidence point | Record exactly | Keep separate |
|---|---|---|
| Old identity | Printed key, document title, source and date | Address spelling on the same paper |
| Configuration event | Plat or other named reference, event date and source | A later billing or mailing change |
| Successor identity | Each new key, source and first confirmed date | The permit document still being sought |
Keep the old square, suffix and lot in your notes beside each successor key. If either side lacks a dated source, label the connection unproven.
Use Master Address Repository matches as clues
The District’s Master Address Repository data dictionary describes the address-to-SSL cross-reference as many-to-many. Its fields include address ID, square, suffix, lot and lot type. One address can therefore participate in several relationships, so an address match points to candidates; the split date and the successor that inherited an old permit come from dated parcel records.
Record the lot type with each match, because a tax-lot billing change can leave the record lot the same.
That distinction changes the next request. If the evidence shows only a tax-lot change while the record lot stayed the same, the question belongs with the Office of Tax and Revenue rather than the Surveyor. Ask OTR which dated tax-identity record applies and whether that record survives.
What DC Surveyor plats show about a lot change
The current Surveyor FAQs describe SurDocs searches by square and lot. They explain that a recorded subdivision plat creates record lots for configuration changes, while a tax-lot change leaves the record lot unchanged. A deed or Office of Tax and Revenue address can supply a current square and lot. The Surveyor holds land plats; house plans sit with permit records.
The Surveyor Services page links to the public SurDocs plat tool. Check its search fields and earliest online year there. If the retired key leads nowhere, ask the Surveyor which recorded plat or related item documents the transition.
The District’s special instructions say the Surveyor draws only active lots in the current tax database. A new building plat therefore shows today’s lots; retired SSL history and old permits have to be traced through earlier plats and permit files.
How DOB eRecords matches addresses and SSLs
The dated eRecords upgrade FAQ describes street-address and partial-house-number searching. It says the search examines metadata rather than document content and describes SSL and standardized-address connections as a later plan. Read that as a description of that release; today’s controls may differ, and the FAQ describes no public old-to-new crosswalk.
The official eRecords route opens at an Explorer sign-in page. A metadata miss can coexist with an old key written only inside a scanned document. A metadata match tells you where to look, and the document itself tells you what it says.
Example: matching one old permit to two successor SSLs
Suppose an old permit bears the fictional key OldSSL and a later plat names NewSSL-A and NewSSL-B. A current address appears beside NewSSL-B in one export, and the old permit names only OldSSL.
Keep three questions separate: does the plat connect OldSSL to both new keys; which later file cites the old permit; and does the document contain the old key or merely appear under new metadata? The address remains a lead, not transition evidence.
If the plat establishes both successors but neither permit file cites the old record, note that result. Ask for the permit by its old key, document type and date range, and include the plat reference only as a locating clue. Keep the permit filed under OldSSL until a document ties it to NewSSL-B; a familiar address is only a lead.
Route a missing old permit narrowly
The DOB records-management page covers permits, applications, plans and certificates of occupancy and provides a missing-record route. Its summary and detailed records-information page describe different offsite-year ranges; the detailed page also points some 1949–1962 research toward NARA and notes possible 1995–1998 plan gaps. Quote the range from the page that matches your year instead of assuming one archive floor.
For a targeted request, supply the retired SSL, document type, approximate year, printed address, known permit reference and the dated configuration record. Ask which custodian and copy route apply to that named object. Distinguish five outcomes: access unavailable, no metadata match, identity transition unproven, wrong document returned and known copy missing.
Use the DC lot-identity guide for the current tax-lot versus record-lot distinction. Use the address-history recovery guide when spelling or numbering changed.
Bring the retired SSL, the dated plat and the permit reference to any request so staff can search the old key directly. Once you have the permit, its own inspection and closeout records show whether the work was completed and passed inspection; a successor SSL only shows where the lot went.
District sources reviewed October 9, 2026 UTC.