"No Permits Found" vs. "No Results": The Distinction Behind the Note in Your File

The note you are about to type

You are working a renewal on a 1970s house and the carrier wants support for roof age. You pull up what looks like the city's permit portal, run the address, and get an empty screen. The note you are tempted to type into the file is short: no permits found.

Whether that note is accurate depends entirely on what happened during the search, and an empty screen can mean at least several different things. Only one of them is anything like a negative finding, and even that one carries limits. Getting this wrong is how a submission ends up asserting something nobody actually checked.

Two different statements

No results is a statement about your search. No permits found is a statement about the property. Underwriting reads the second one, acts on it, and may price or decline on it, so the words in the file need to match what the search actually established.

At least six situations produce the same empty screen: the search completed and the official source itself returned a no-record answer; the search ran but did not match the portal's stored address format; the portal searched had no jurisdiction over the parcel; the source was unavailable or would not accept the search; the jurisdiction has no online records at all; or records exist but predate the portal - a limit that applies even to a genuine no-record answer. Each calls for a different note in the file, and only the first can honestly be summarized as the source reporting no permits.

Case one: the source itself said no records

The cleanest outcome is a completed search where the portal responded normally and returned its own no-record answer for the address. That is a dated statement from an official source, and it belongs in the file as exactly that: on this date, this jurisdiction's portal returned no permit records for this address.

Before you write even that, confirm you searched the authority that actually issues permits there. City and county jurisdiction is a routine trap: an address can carry a city name in its mailing address while sitting in unincorporated territory, where the county building department, not the city, holds the records. A no-record answer from a portal that never had jurisdiction over the parcel tells you nothing.

Case two: the source was unavailable or blocked

A search can also fail to execute at all. The portal demands an account before it will show anything, a bot wall or outage stops the page from loading, the search accepts permit numbers but not addresses, or the link on the city's website is stale. In each of these you learned nothing about the property, because no source ever answered.

PermitProof's statewide catalog suggests how often the login version of this happens: of the 539 California permitting authorities it has cataloged, 80 are recorded as requiring an account and sign-in before permit records can be searched. A further 51 are recorded as public portals that automated search has not worked against. Most of those record a limit in PermitProof's own connectors, and several record bot walls aimed specifically at automated clients - a person at a desk can often search both kinds directly. The rest record portal outages, stale links, or no public address search at all, where a person is stopped too - and PermitProof has a portal link recorded for only some of the bucket.

Telling underwriting that no permit exists after an inaccessible-portal search is precisely the error this distinction prevents. The honest note is different and just as short: portal inaccessible on this date, search not completed. A CSR who writes that has documented diligence; one who writes no permits found has documented a claim the search cannot support.

Case three: the jurisdiction has no online records

Some jurisdictions are recorded as not publishing permit records online at all. Any history the department holds comes out through a records request, usually by phone or email, and PermitProof's catalog records a set of California authorities in exactly this state.

Finding no portal is not finding no permits. The practical move is to contact the department's records desk, ask for permit history by address or parcel number, and note the request and its date in the file. Turnaround varies by department, so on a time-sensitive quote the note may honestly read: records available by request only, request submitted, response pending.

Case four: the records predate the portal

Even a genuine no-record answer has a floor under it. A portal may publish records only from when its current system went live, older paper files are not always digitized, and a department may publish only certain permit types. A house built decades ago can have a real permit history that simply never made it into the system you searched.

So a permit record is hedged evidence, not proof, in both directions. A re-roof permit supports a roof-age discussion without proving the work matched the permit; the absence of one does not prove the roof is original or that work went unpermitted. Where a portal publishes its coverage dates, note them; where it does not, the file should say the search reflects what the source publishes today.

What to put in the file instead

The fix is to write down the search, not a conclusion. Name the source, the date, and the exact outcome: searched the city permit portal on this date and the portal returned no records for this address; or portal requires a login, search not completed; or jurisdiction takes records requests only, request sent this date.

An underwriter can weigh a described search. A bare no permits found cannot be weighed, only trusted - and whether a given note helps in any later dispute is a question for your E&O counsel, not for a research tool. A described search is one a later reviewer can weigh on its own terms; a bare conclusion is not.

None of this decides eligibility, premium, or coverage, and neither does any search tool. How a carrier treats an open permit, an old re-roof, or an inaccessible portal is an underwriting judgment; the agent's job is to hand that judgment accurate raw material.

How PermitProof keeps the four cases separate

PermitProof is built around this exact distinction. When a search completes and the official source returns records, the report shows them with their original descriptions and links back to the source, leaving interpretation to you. An automated no-permits-found result is only reported where a certified negative test backs it, meaning the official portal itself returned a no-record answer during live acceptance testing for that jurisdiction.

When the search cannot complete, the report says which situation occurred instead. A login-required portal, a blocked public portal, and a records-request-only jurisdiction each get their own explanation, a link to the official source where one is recorded, and a plain statement that nothing in the result says whether the property has permits. An automated search that ran but could not reach a result it can stand behind is reported as exactly that, never rounded up to a negative.

That is the whole pitch, honestly stated: the same discipline this guide describes, applied faster. You can hold the line on no results versus no permits found with nothing but careful notes; a tool that refuses to blur the two just makes the careful version the default.