Quick answer
Protection is a PerilScore address-access signal. It does not calculate ISO, PPC, or FSRS classifications, and FireProtectionScore has no affiliation with those organizations or programs. Its number uses routed road miles, estimated drive time, and a station-name heuristic for one US street address.
Why the words cause confusion
A number only makes sense with its rules. Strong covers 1 through 3, Adequate covers 4 through 6, Limited covers 7 through 8, and Remote covers 9 through 10. Lower is stronger. Other systems may use different evidence, geography, polarity, reviews, and updates. Official classification work can consider water supply, communications, capability, and other records outside Protection.
What Protection answers
Distance gates run first: above 7 road miles gives base 10, and above 5 road miles gives base 9. At 5 miles or less, estimated time gives base 1 at 3 minutes or less, 2 at 4, 3 at 5, 4 at 6, 5 at 7, 6 at 8, 7 at 10, and 8 above 10 minutes. A volunteer signal in the public station name adds one, capped at 10. This narrow result describes modeled station access. It does not become an official class.
Worked route one
E1 is illustrative: 2.1 miles and 4 minutes with no volunteer signal gives base and final 2 Strong. No water, building, or equipment fact enters that arithmetic.
Worked route two
E4 is illustrative: 5.2 miles with no volunteer signal gives base and final 9 Remote. Minutes do not control the base beyond 5 miles. The 9 cannot be converted into an official class.
Choosing the right source
Use Protection when the question concerns the disclosed modeled route. Use the responsible official source when a record request calls for an official classification. Keep the system name and version attached to every value.
Local context
The Pittsburgh hub highlights bridges, slopes, and connectors. The Cape Coral hub highlights canals and bridge routes. Both show station inventory context and neither publishes an area number.
Common misreads
A station count cannot become a class. A ZIP centroid cannot become a property route. A map pin cannot establish road miles. A name keyword cannot verify staffing. Strong Protection cannot establish water capacity or building performance.
Canonical guide
Read Protection versus official classifications for the canonical comparison and what Protection excludes for scope.
Sources and next step
HIFLD station records and modeled routing support the narrow access signal. Protection excludes hydrants, water supply and flow, building construction, sprinklers, alarms, apparatus, detailed staffing, mutual aid, live dispatch, current traffic, and incident conditions. It cannot predict response or loss. A station name signal is a heuristic and does not certify staffing. Read the sources and methodology, then check a US street address.
A repeatable review checklist
First name the system whose value appears. Second identify its geography and polarity. Third list the inputs that actually enter. Fourth identify the source date and methodology version. Fifth state the exclusions in plain language. This sequence prevents a familiar label from carrying claims that belong to another system.
For Protection, the geography is a US street address and lower is stronger. The inputs are routed miles, modeled minutes, and the station-name type signal. Missing route data produces no number. Area inventories remain context. Hydrants, water, buildings, apparatus, verified staffing, dispatch, traffic, and outcomes stay outside the calculation.
Why transparent arithmetic matters
A reader can recreate the base from the visible route inputs. That makes boundary cases inspectable and lets someone distinguish a formula change from a source or routing update. It also exposes category errors quickly. If an explanation depends on a city count, postal average, straight-line pin, hydrant, or official label, it is explaining something beyond Protection.
Final interpretation guardrails
Strong means stronger modeled access under this method. Remote means the route is beyond the first distance gate or remains at the upper end after the disclosed adjustment. Neither band guarantees what happens during an incident. A separate source should answer every separate question.
Questions this page can answer
This page can explain the published formula, show why address routing matters, identify source limitations, and point to the canonical curriculum. It cannot verify local operations or replace records maintained by an official authority. It also cannot infer excluded facts from a final band.
A careful answer names the route inputs and the boundary that controlled the base. It states lower-is-stronger polarity, identifies any name adjustment, and keeps place inventory facts separate. When route data is absent, it reports missing information instead of improvising a value.
Change over time
A property result may change because an address resolves differently, the station snapshot changes, a public station name changes, the road network is edited, or routing estimates update. A methodology revision is another possible cause and should carry its own version. Recording the date, version, and inputs makes these causes distinguishable.
Takeaway
Protection is useful when it stays attached to its narrow address-access question. The number becomes misleading when it is expanded into an official classification, a postal-area claim, a staffing conclusion, a water-supply claim, or an outcome prediction. Use each source for the question it can actually answer.
When sharing a result, include the words Protection access signal, the US street address, the route inputs, and the version. That context keeps the value distinct from an official record and lets another reader reproduce the published arithmetic.