Start with the stage named on each paper. Flow input, capacity findings and connection evidence answer separate questions.
Separate the papers by stage
| File or stage | Question it can answer |
|---|---|
| SFFD sizing paper | Design input |
| SFPUC capacity result | Utility finding |
| Application or estimate | Proposed work |
| Connection file | Later work |
The fire-service connections page places SFFD sizing before application. Customer Service Bureau determines analysis need; City Distribution Division reports capacity. Those are distinct from installation.
Annotate the file before deciding what it proves
Create one note for every item in the packet. Copy the file title, visible date, sender or custodian, project or location wording, stage stated in the text, and any referenced file that is absent. Add a short “answers” line and a separate “does not answer” line. This prevents a favorable-sounding paper from silently filling a later gap.
Use location details already printed on the document. An address, cross street or proposed connection street may help reconcile two papers, but it is not proof that they concern the same design version. APN searching was not documented for these sources. If the street wording changes, preserve both versions and ask which one belongs to the target file.
Dates deserve the same treatment. Record a revision date, response date, estimate date and installation date under their own labels. Do not reorder undated items just because their filenames look sequential. If a note mentions an attachment you do not have, keep the cross-reference visible rather than summarizing the missing attachment as though it were present.
Give every cross-reference one of four states: present, missing, inaccessible or wrong stage. “Present” means the actual file is in hand, not merely named in an email. “Inaccessible” means a link or file was identified but could not be opened. “Wrong stage” means the returned item answers another row. This vocabulary keeps a request precise and prevents a broken link from becoming a claim that no record exists.
Use the dated SFFD form as an identity clue
The blank SFFD water-flow form, revised July 27, 2020, names address, cross streets, connection street and sketch; official-use data is separate. Use the labels for identity, not as a project result or current fee-and-timing source.
Compare copies by identifier and purpose. Keep the template, request and response separate.
Diagnose a fictional mixed packet
Imagine a fictional folder for Example Court. It contains a completed sizing sheet, an email that discusses available capacity and a cost estimate. A cover note says the service was installed, but no later connection paper is attached. The first three items can be logged under their own stages; the cover note remains an unverified pointer to the missing fourth-stage file.
Now suppose the email uses “Example Court at First Street,” while the estimate says “Example Court near Second Street.” Do not choose a match from proximity alone. Compare the project reference, date, sender, connection-street wording and any attachment name. Keep both papers in the research folder and mark the location relationship unresolved.
If a reply returns another estimate, compare its title, date and stated work with the requested later-stage record. Keep a wrong-stage return as a separate lead. Ask whether a later file exists and which reference links it to the earlier papers. A “not located” response differs from a file that exists but cannot be opened or delivered; record those outcomes separately.
Request the named SFPUC-held record
SFPUC's current contact page directs public-records requests to the City's NextRequest service or 628-246-1372. Name the item, stage, approximate period and location wording or SFPUC reference already in your papers. These are descriptors, not verified portal fields.
The page separately describes a utility-information route for water-line documents, not a fire-service archive. Ask which unit holds the item. No NextRequest page, field, account or request was opened, and no retention period, disclosure outcome or delivery time was verified.
Keep later approvals in their own files
The San Francisco fire-history coverage guide covers separate SFFD permit, inspection and property-record routes. The final-inspection status guide explains why a scheduled or partial inspection is not a passed final result. Use those records for their own questions rather than treating an SFPUC flow, capacity or connection paper as a fire-system approval.
A missing online result does not prove that a service was never installed. None of these preliminary records alone proves installation, fire approval, occupancy or present condition. Official sources were reviewed October 8, 2026 UTC. No property or project query, account login, application, contact or records request was made.