📖 How to read this playbook (and how I read the FigJam)
Each page below is one decision point from the top-level map — one "play." The left pane recreates the FigJam tree exactly as drawn (same branch labels, same terminal boxes); the right pane is the same tree flattened into path → terminal state rows, so every route to an outcome can be checked line by line.
How I read each board: start at the entry decision, walk every arrow to a terminal box, and record the full condition path — then capture the sticky notes separately, because they answer a different question: not "what's the rule?" but "what do we do when the field is MISSING?" (look it up, assume a default, or follow up). Where two arrows overlap and the wiring is genuinely ambiguous, I did not guess — those became the questions at the bottom of the page.
Dashed-underlined terms open a ? glossary dialog — the shared vocabulary (UWing period, Knox Box, KYC, P(F), RCE…) captured while reading. Each page also notes where an agent helps: the exact spots a decision would stall on vague or missing info, and whether the unstick is a lookup, a derivation, the board's own assume-and-verify default, or one scoped question.
Protection Class 9 & 10
The deepest board: when public fire protection is weakest, insurability is engineered — water supply, access, response, staffing, and home size all interlock.
I read this in three passes. First the ENTRY split: a public hydrant within 1000' collapses the whole board to a response-time check. Second, the NO-HYDRANT half is really a water-engineering flow: find water (alternative source or tankers), prove a truck can reach it and the home (access, paved roads, turn-arounds, dry hydrant + fittings), then size the remaining risk with the staffing × home-size × sprinkler matrix. Third, the SHARED TAIL: every surviving path funnels through the same gate — physical barriers demand a Knox Box, otherwise a central-station alarm. The matrix repeats per response-time block; the tree below draws it per block and the tail once, exactly as the board's collector rails merge.
| Path | Terminal state |
|---|---|
| Hydrant ≤ 1000' → response time over 30 minutes | DECLINEDecline |
| … response within 15 minutes | OK / QUOTEOkay to write |
| … 15–30 minutes, home under 7500 sqft | OK / QUOTEOkay to proceed → shared tail |
| … 15–30 minutes, home 7500+ sqft | REQUIRERequire centrally monitored interior sprinklers → shared tail |
| No hydrant, no alternative water source, no tankers | DECLINEDecline |
| No hydrant → tankers → limited access / dead-end / no turn-around | DECLINEDecline |
| … multi-road access → response over 30 min | DECLINEDecline |
| … 15–30 min, VOLUNTEER station, home > 7500 sqft | DECLINEDecline |
| … 15–30 or <15 min, staffing × size matrix, mid/small homes | REQUIRERequire 10 or 20 gallons of water per sqft (20 without sprinklers, 10 with) → shared tail |
| … within 15 min, PAID station, home > 7500 sqft | REQUIRERequire 10 gal/sqft + monitored sprinklers → shared tail |
| Alternative source ≤ 1000' of dwelling → not accessible year-round | DECLINEDecline |
| … accessible → no dry hydrant | REQUIRERequire dry hydrant within UWing period |
| … dry hydrant without county + Cal Fire fittings | REQUIRERequire retrofit within UWing period |
| … fittings OK → paved roads not accessible all year | DECLINEDecline |
| … paved roads OK → road access → response/staffing/size matrix | NOTEsame matrix as the tanker path → shared tail |
| SHARED TAIL: gates or physical barriers present | REQUIRERequire Knox Box within UWing period |
| … no barriers, no central-station fire alarm | REQUIRERequire one within UWing period |
- Most of this questionnaire is pre-answerable from public/GIS data before anyone is asked anything: hydrant locations, nearest station + staffing type, drive-time response estimates, road access and turn-arounds from maps — an agent fills the tree and leaves only the property-specific facts (stored water, sprinklers, fittings) as scoped asks.
- The sticky is the playbook's own default rule: protection class missing → assume Class 9, run the full diagram, and carry the assumption as a flagged, verifiable fact.
- Because requirements STACK here (water + sprinklers + Knox Box + alarm), an agent can compose the complete requirements letter in one pass instead of the underwriter accumulating them by hand.
- The two children under “Central Station Fire Alarm” are drawn without Yes/No labels — I read “Yes = alarm present → proceed; otherwise require within the UWing period.” Correct?
- “Within 1000' of Dwelling — No” has no drawn branch: does a too-distant source fall back to the tanker path, or decline?
- In the 15–30-minute blocks, volunteer-staffed + >7500 sqft reads as a hard decline while paid-staffed gets the water+sprinklers requirement — confirming that's the intended asymmetry?
- County + Cal Fire fittings reads California-specific — is the playbook single-state today?