Start with the site address, utility provider and exact missing item: a main map, issued right-of-way (ROW) permit or inspection result. Use the City’s Maps and Records page to identify the custodian, then match drawing and permit identifiers. Keep the connection record and both inspection outcomes with the same project. Each answers a different question about the file.
This route applies to water and sewer systems operated by the City of San Diego. A City address can have a different utility provider, so confirm the provider before using this chain.
Build a five-part utility record chain
Keep these objects in separate rows of your notes:
- Main or as-built source: the location source and drawing reference.
- Issued ROW permit: the authorization document to match.
- Connection responsibility: the party identified for the connection.
- Pre-connection inspection: the earlier inspection outcome.
- Final inspection: the later result named for the project.
The City’s March 2026 Information Bulletin 166 supports this sequence. Its construction-plan description includes street names, main location, size, material, the as-built drawing number, and proposed service or lateral details. These are strong matching keys when an address search alone is inconclusive.
Use maps and as-builts as location evidence
The Public Utilities page lists GIS data for sewer mains, manholes, water mains, and hydrants. It also describes help locating a water service connection or sewer lateral and routes copies of City as-built construction plans to Development Services Records.
That scope has boundaries. The City says it does not hold the location of private water lines within private property. It also states that an owner maintains the sewer lateral to its connection with the City main. Record the exact segment in question before asking for a map, as-built, permit, or inspection.
A line on a map is useful location evidence. It is not the issued permit or an inspection result. Write down the map layer or drawing number and move to the next record in the chain.
Separate permit issuance from connection work and inspection
IB 166 requires a ROW permit for public-right-of-way or water/sewer-easement work. It assigns different work to different parties. Public Utilities performs water and fire service connections to a water main and installs water meters. A licensed contractor may connect a sewer lateral. Other permitted work remains the permittee’s responsibility.
The bulletin also separates an issued ROW permit from later activity. It describes a post-issuance sales-order step for proposed water connection items, then requires an inspection after trenching and before connection. A final inspection follows after the work is complete.
Treat each stage as its own dated entry. An issued permit establishes authorization for its stated scope. A sales-order reference tracks a later administrative step. The two inspection results answer different construction-stage questions. For help interpreting a final status, use the final inspection status guide.
Carry one identity packet through each custodian
Prepare a compact packet before contacting a records office. These are editorial matching keys, not verified live form fields:
- Site address and City utility provider.
- APN, if already known from a reliable property source.
- Street name and the public main involved.
- Water service, fire service, or sewer lateral.
- Main size and material, if shown on the plan.
- As-built drawing number.
- ROW permit or project number.
- Approximate permit, connection, and inspection dates.
- Exact missing item and the segment it covers.
If the City/APN or current-versus-legacy permit identity is unclear, the San Diego ZAPP and Zone History guide explains how to preserve the parcel and permit clue before following the underlying file. Do not substitute a zoning summary for the utility record.
Reconcile a mixed file without filling the gap
Imagine a fictional file with a City GIS main, an as-built drawing number, an issued ROW permit, and a water-connection sales-order reference. The packet has no pre-connection inspection result and no final inspection result.
The mapped main answers where the public system is recorded. The permit answers what work was authorized. The sales-order reference belongs to the connection process. None supplies the two missing inspection outcomes. Request those outcomes by the ROW permit or project number and the approximate work dates.
Now change the example to a sewer lateral. The licensed contractor may make that connection, while the inspection sequence still matters. Keep the contractor and permit reference with the lateral record. Do not transfer a water-service work record into the sewer file merely because both serve the same site.
Recover the named record and preserve the limits
The Development Services Records page says not every property-record type may be available. It offers self-research for City permits and applications from 2003 forward and routes archived plans or records to Records Review. That project-status date is not a start date for utility maps, as-builts, service records, or inspection files.
Ask for one missing object at a time. Include the identity packet, name the custodian suggested by the City pages, and explain whether you need location evidence, the issued permit, the connection record, or a particular inspection result. If the first route has no result, verify the utility provider and ask Records staff which City collection holds that record class.
A missing online entry does not prove that no permit or inspection record exists. It leaves the record unresolved. Determine authorization from the issued permit and completion from the applicable inspection evidence. Assess the present condition of a private line from evidence about that line itself.
Official City of San Diego Public Utilities GIS/records, Information Bulletin 166, and Development Services Records guidance checked October 5, 2026 (UTC). No address, APN, map, as-built, project, permit, connection, inspection, account, query, appointment, contact, payment, form, or records request was used.