Go/no-go gates. NO at an early gate costs the least.

#	Question	Threshold	Evidence	If NO
1	Has the funder signed an amendment accepting drill-based evidence for the Month 4 gates and the €750k partial-release rule, and has the municipality named who covers a €200-400k delay gap?	Signed funding amendment by Month 0.5 (target); Month 1 is the tripwire. The partial-release rule is €750k at Month 4, with the remainder after the Month 5 re-test. The gap is €200-400k (estimate), against €160k free tranche-1 contingency.	Signed amendment from a budget-authorizing officer at Month 0.5-1. Written source for any bridging amount, from the municipal budget or the funder. A credit line is excluded by the no-debt model.	No sign-off by Month 1 means a freeze on discretionary commitments only. Tranche-1 orders that the €2.0M already covers should not be frozen. No sign-off and no bridge by Month 2 means re-scoping to the tranche-1 minimum (FM1 stop rule). Do not assume debt financing.
2	Are the kit supply chain and the first call-off locked?	First call-off of 600-800 kits (30-40%) placed by Month 1.2 with a signed delivery SLA. At least 2 suppliers committed to February delivery. 2-3 backup suppliers per category pre-qualified by Month 1. The expedite premium (€50-100k, estimate) sits inside the €800k kit category.	Firm supplier quotes, signed call-off and backup agreements at Month 1-1.2. Supplier market sounding at Month 0.3 and specs at Month 0.8.	Fewer than 2 suppliers can deliver in February, or the call-off is not placed by Month 1.2: activate the backup supplier within 2 business days. If kits reach <40% delivered by Month 4, cut scope to 1,000-1,500 homes and protect refuges and transport. Under 1,000 installed by Month 7.3 means stop new kit purchases.
3	Is the outreach model legally and operationally viable?	GDPR opinion at Month 1. At least 4 partner DPAs signed by Month 1.5. Combined partner capacity of at least 4,000 attempts/month (5,000 planned, estimate). Mock-call success of at least 60% in 50-100 calls at Month 1.5. A result of 55-59% triggers a defined correction.	Legal opinion, signed DPAs, partner capacity survey and written commitments, mock-call results at Month 1-1.5.	Delay enrollment and add backup partners. If counsel finds no valid lawful basis, or success stays below 60% after the Month 5 re-test, stop the intermediary model and redesign outreach. Door-knock capacity must then be added before the Month 4 gate.
4	Does the Month 2 readiness gate pass?	At least 8 of 10 sites signed with named managers. At least 50% of places accessible. Taxi retainer signed (capped at €80k). At least 20 volunteers vetted. Heat line mock passed. Outreach and escalation training completed (test ≥80%). 100% of tranche-1 orders placed.	Gate checklist and signed contracts at Month 2. Volunteer pipeline checked at Month 1.5 (<20 triggers a proportional retainer scale-up).	Fix unmet items by Month 2.5. If more than 4 weeks behind at Month 3, hold a funder restart or re-scope review. Fewer than 6 accessible signed sites at Month 2.5 means redesigning the network before the drill.
5	Does the full-system drill and after-action close pass all four scale gates, so the €1.5M can be released?	Drill at Month 3.2. At least 80% of planned centre hours delivered. At least 60% contact success from at least 300 attempts. Mean pickup under 45 min over at least 30 requests, including at least 5 wheelchair users. After-action report done and 100% of corrective actions closed by Month 3.9, before the Month 4 decision.	Independent observer's drill data and after-action report (draft Month 3.5, actions closed Month 3.9). The planned-hours basis and drill staffing must be defined before the drill.	A failed gate means no release; fix and re-test at Month 5. A second failure means scaling back to the tranche-1 minimum. If evidence is unmeasurable, release €750k at Month 4 and the remainder after the Month 5 re-test.
6	Is a Year-2 funding source committed by Month 9?	At least 1 letter of intent by Month 9. Full footprint is ≈€2.3M/year (estimate). The reduced scope must be a single defined range.	Funding letter from EU climate grants, national health budget or municipal mainstreaming. Mayoral continuity commitment by Month 11. Equity audit at Month 9.	Publish a reduced Year-2 scope (refuges and transport first, kits deferred) and obtain written mayoral commitment by Month 11. Otherwise the Month 12 roadmap must say the infrastructure will not continue, which weakens the peer-city case.

What you need to decide, and by when.

4 open decisions: 2 high and 2 medium severity. The most urgent are gap financing (by Month 1 = 2026-11-08) and the staffing basis for the Month 3.2 (2027-01-14) drill (by Month 2.5 = 2026-12-23), because both affect release of the €1.5M. The staffing roster is needed by Month 0.5 (2026-10-23). Year-2 scope can wait until Month 9 (2027-07-08). Until they are decided, the plan can safely proceed with tranche-1 orders within €2.0M, GDPR counsel, site contracting and supplier sounding, and hold discretionary commitments.

#	Decision	Severity	Owner	Decide by	Blocks
1	Gap financing for delayed tranche-2 release	🔴 High	Heat Response Steering Committee with the funder's budget-authorizing officer.	Month 1 (2026-11-08) (tripwire). Month 0.5 (2026-10-23) is the target. Month 1.2 (2026-11-14) call-offs and Month 1.5 (2026-11-23) orders depend on it.	Month 1.2 (2026-11-14) kit call-off, Month 2 (2026-12-08) readiness gate and the Month 4 (2027-02-08) tranche-2 release.
2	Staffing basis for the Month 3.2 (2027-01-14) drill	🔴 High	Heat Response Steering Committee, with the funder consulted on gate evidence.	Month 2.5 (2026-12-23), when the drill protocol is finalised. Hiring changes would need to start before Month 3 (2027-01-08).	Month 3.2 (2027-01-14) drill and the Month 4 (2027-02-08) gate decision on €1.5M.
3	Full staffing roster and reserve	🟡 Medium	Incident commander, approved by the Heat Response Steering Committee.	Month 0.5 (2026-10-23), because the roles are needed from Month 0 (2026-10-08) and the HR coordinator is also needed.	Month 2 (2026-12-08) readiness gate staffing and the first hiring cohort at Month 3 (2027-01-08).
4	Year-2 scope and funding	🟡 Medium	Mayor and municipal council, with the funder.	Month 9 (2027-07-08) for a letter of intent, so the roadmap and equity audit can use it. Month 11 (2027-09-08) for mayoral commitment.	Month 12 (2027-10-08) Year-2 roadmap and the scaling cost model.

1. Gap financing for delayed tranche-2 release (🔴 High)

Decision: Who covers the €200-400k cash gap if the €1.5M release is delayed to Months 5-6 (2027-03-08 to 2027-04-08), given the 100% grant-financed, no-debt model?

Why it is open: Self-audit, Premortem FM1 and Pitch assume a €200-400k credit line. The financing model excludes debt. Free tranche-1 contingency is only €160k, leaving €40-240k unowned.

Option	Consequences	What changes in the plan
A. Municipal budget advance, repaid from tranche 2.	Covers the gap without debt. Needs council or budget-officer approval. Keeps hours and transport at plan.	Financing model note; Premortem FM1; Pitch Risks; budget lines.
B. Funder agrees an earlier partial release (€750k at Month 4 = 2027-02-08).	Narrows the gap. Needs a signed funder amendment by Month 0.5-1. Aligns with the partial-release rule.	gate4_partial_release_rule; funder agreement; Premortem FM1.
C. Pre-agreed service-cut order, kits deferred first.	Gap shown as unfunded. Fewer kits; refuges and transport protected. No new money needed.	Kit scope (2,000 homes); stop rules; Premortem FM1.

• If nobody decides: No sign-off by Month 1 (2026-11-08) freezes discretionary commitments. No bridge by Month 2 (2026-12-08) triggers re-scoping to the tranche-1 minimum.
• Owner: Heat Response Steering Committee with the funder's budget-authorizing officer.
• Decide by: Month 1 (2026-11-08) (tripwire). Month 0.5 (2026-10-23) is the target. Month 1.2 (2026-11-14) call-offs and Month 1.5 (2026-11-23) orders depend on it.
• Blocks: Month 1.2 (2026-11-14) kit call-off, Month 2 (2026-12-08) readiness gate and the Month 4 (2027-02-08) tranche-2 release.

2. Staffing basis for the Month 3.2 (2027-01-14) drill (🔴 High)

Decision: How is the Month 3.2 (2027-01-14) full-system drill staffed, and what does 'planned hours' mean, when only 40% of staff are hired by Month 3 (2027-01-08)?

Why it is open: Hiring is 40% at Month 3 (2027-01-08), with the drill six days after the first cohort starts. The Month 4 (2027-02-08) gates need ≥80% of planned hours, ≥60% contact success and pickup <45 min. No document defines the drill staffing or hours basis.

Option	Consequences	What changes in the plan
A. Pull the first hiring cohort earlier.	More representative drill. Raises early payroll within tranche 1. Needs a faster HR process; the HR coordinator is only 0.5 FTE.	hiring_and_rota; drill schedule; tranche-1 cashflow.
B. Staff the drill with seconded municipal staff, volunteers and contractors; define planned drill hours on that basis.	Keeps the hiring schedule. Gate evidence measures a reduced staffing base. Needs an observer-agreed hours definition before the drill.	Drill protocol (final Month 2.5 = 2026-12-23); gate definitions.
C. Treat the drill as proof of procedures only; re-test at Month 5 (2027-03-08).	Honest about staffing. €750k partial release at Month 4 (2027-02-08), remainder after the Month 5 (2027-03-08) re-test. Raises cash-gap risk.	gate4_partial_release_rule; month4 (2027-02-08) gates; funder amendment.

• If nobody decides: The drill runs with partial staff. Gates are likely failed or unmeasurable, giving a €750k release or none.
• Owner: Heat Response Steering Committee, with the funder consulted on gate evidence.
• Decide by: Month 2.5 (2026-12-23), when the drill protocol is finalised. Hiring changes would need to start before Month 3 (2027-01-08).
• Blocks: Month 3.2 (2027-01-14) drill and the Month 4 (2027-02-08) gate decision on €1.5M.

3. Full staffing roster and reserve (🟡 Medium)

Decision: Which added roles are approved, and from which budget line, within the 43 FTE plan?

Why it is open: Reviews add a PMO lead, partner liaison, risk officer, engineering lead, comms monitor, epidemiologist and playbook officer from Month 0 (2026-10-08). The plan has 3 coordination and ~1.5 specialist FTE, with hiring from Month 3 (2027-01-08). Documents promise a '20-30% reserve' and '40 FTE by Month 3 (2027-01-08)'.

Option	Consequences	What changes in the plan
A. Fit all roles inside 43 FTE plus 1.5 specialists or the €400k governance line.	Budget cap unchanged. Some roles part-time or later. Needs a role table with FTE, start month and budget line.	staffing_plan; governance budget line; Self-audit; Review 12.
B. Add roles by cutting another category (e.g. kits).	Month 0 (2026-10-08) capacity is covered. Fewer kits or less contingency.	budget_allocation_by_category; kit scope.
C. Defer non-essential roles to Month 3 (2027-01-08) or later.	Lower early cost. Weaker Month 0-3 (2026-10-08 to 2027-01-08) delivery of the GDPR, procurement and partner work.	hiring_and_rota; Month 2 (2026-12-08) gate risk.

• If nobody decides: Roles are filled informally from Month 0 (2026-10-08), creating unbudgeted cost. The reserve is stated as 4 of 14 centre staff.
• Owner: Incident commander, approved by the Heat Response Steering Committee.
• Decide by: Month 0.5 (2026-10-23), because the roles are needed from Month 0 (2026-10-08) and the HR coordinator is also needed.
• Blocks: Month 2 (2026-12-08) readiness gate staffing and the first hiring cohort at Month 3 (2027-01-08).

4. Year-2 scope and funding (🟡 Medium)

Decision: Which Year-2 scope will be funded: same footprint, city-wide expansion, or one defined reduced scope?

Why it is open: ≈€2.3M/year is the same-footprint estimate, with no funder identified. The Pitch uses it for city-wide scale with 15-20 sites. Reduced scope is €1.5-2.0M in one review and €1.2-1.5M in others. Kits are double-counted in places.

Option	Consequences	What changes in the plan
A. Same footprint at ≈€2.3M/year (estimate).	Needs a funding letter of intent by Month 9 (2027-07-08). Preserves evidence continuity.	Year-2 roadmap; year2_recurring_cost_estimate.
B. One reduced scope (refuges and transport first, kits deferred) with a single stated range.	Lower cost. Fewer residents covered. Needs mayoral commitment by Month 11 (2027-09-08).	Pitch; Reviews 11 and 14; Self-audit; roadmap.
C. City-wide expansion, costed as a separate labelled estimate.	Higher cost than €2.3M. Weaker evidence base after one season.	Pitch Long-term Vision; scaling cost model.

• If nobody decides: No range is chosen. The Month 12 (2027-10-08) roadmap may say the infrastructure will not continue.
• Owner: Mayor and municipal council, with the funder.
• Decide by: Month 9 (2027-07-08) for a letter of intent, so the roadmap and equity audit can use it. Month 11 (2027-09-08) for mayoral commitment.
• Blocks: Month 12 (2027-10-08) Year-2 roadmap and the scaling cost model.

Choices made on your behalf

Set when the scenario was selected, not by you. Confirm or change them.

Lever	Chosen	Strongest alternative	Why it matters	Revisit by
Alert Trigger Ladder	National warning plus a low-cost advisory tier (phone check-ins and pre-positioned supplies only).	Locally calibrated thresholds weighting hot nights (Pioneer's Reach).	Sets when centres open and how many site-hours are spent.	After the Month 7 (2027-05-08) second drill and the first season (Month 12 = 2027-10-08).
Cooling Refuge Network Shape	About 10 small neighborhood refuges in libraries, parish halls and community centers.	A few large anchor sites with overnight hours (Consolidator's Safeguard).	Drives the €850k refuge category, supervision cost and walking access.	Month 2 (2026-12-08) readiness gate (fewer than 6 accessible signed sites means redesign).
Consent-Light Identification Routes	Intermediary-held lists; partners call on the city's behalf and only aggregates reach the city.	Opt-in registry via GPs and pharmacies (Consolidator's Safeguard).	Determines GDPR risk and whether isolated residents are reached.	Month 1 (2026-11-08) GDPR opinion and the Month 1.5 (2026-11-23) mock-call test.
Mobility Support Delivery	Vetted volunteer drivers (target 40) with a taxi standby retainer capped at €80k.	Taxi contract with guaranteed capacity (Consolidator's Safeguard).	Drives the 45-minute pickup gate and the taxi-only fallback cost of +€150-250k.	Month 1.5 (2026-11-23) volunteer pipeline check.
Command Seat Allocation	Incident commander in the mayor's office with a public-health deputy.	Rotating heat desk with delegated declaration (Pioneer's Reach), or clinical command (Consolidator's Safeguard).	Affects speed of procurement and alert declaration, and political exposure.	Month 1 (2026-11-08), when the delegation of authority is signed.

Key numbers and dates.

Kind: user constraint = from your prompt; decision = chosen in this plan; proposed threshold = a pass/fail line proposed in this plan, to be confirmed; estimate = not verified.

Fact	Value	Kind	Basis
pilot_city	Castellón de la Plana, Spain (~170k residents)	decision	Chosen from Castellón, Poznań and Modena for Mediterranean hot nights, ~20% aged 65+, poorly insulated social housing, NGO networks and a nearby university evaluation partner; Poznań and Modena rejected as pilots (usable only as scaling references; the 'Soviet-era blocks' wording applies to Poznań, so Castellón blocks are 1960s-1980s).
target_population_estimates	65+ ≈34,000; living alone ≈25,500; top-floor/poorly insulated housing ≈42,500 (estimates, unverified)	estimate	Recomputed: ~170k × 20% = 34,000; × 15% = 25,500; × 25% = 42,500 (shares come from the assumptions, pending census and housing survey); the groups overlap and must not be summed.
budget_total_cap	€3.5M total for Months 0-12 (2026-10-08 to 2027-10-08) (hard cap)	user constraint	Stated by the user; every program-financed item and every fallback is tested against this cap.
tranche_1_initial	€2.0M available from Month 0 (2026-10-08)	user constraint	User-specified initial funding; covers set-up, procurement, hiring, drills and €160k of contingency (€1,840k of allocations + €160k = €2,000k).
tranche_2_conditional	€1.5M released at Month 4 (2027-02-08) only if all four scale-gate criteria are met	user constraint	User-specified; funds most of the summer operating season (Months 6.8-11.8) and €120k of contingency (€1,380k of allocations + €120k = €1,500k); €2.0M + €1.5M = €3.5M.
contingency_reserve	€280k = 8% of €3.5M (€160k in tranche 1 + €120k in tranche 2)	decision	Source 8-10% per phase (8% × €2.0M = €160k; 8% × €1.5M = €120k; sum €280k = 8% × €3.5M); the separate '€150-200k reserve' alternative is rejected as a duplicate because €160k already falls in that range and must not be added on top.
contingency_exposure_and_free_contingency	Free contingency = €280k (€160k before Month 4 = 2027-02-08, €120k after), because no item is pre-committed inside it; identified draws are alternatives, not additive: taxi-only fallback +€150-250k; delayed-release cash gap €200-400k; if both occurred the €350-650k exposure would exceed €280k by €70-370k (estimate)	estimate	Recomputed: 150+200 = 350; 250+400 = 650; 350-280 = 70; 650-280 = 370. Expedited-delivery premium sits inside the €800k kit line and GDPR counsel (≤€30k) inside the governance line, so neither reduces the contingency; any excess beyond €280k would need kit deferral to Year 2 (Risk 12 priority order) or a funder advance, so a priority decision is needed.
budget_allocation_by_category	Refuge network €850k; transport €380k; outreach/phone/street €450k; home kits + installation €800k; health coordination €120k; worker protection €50k; communications + language €170k; governance/PMO/legal/evaluation/playbook €400k; contingency €280k	decision	Recomputed: 850+380+450+800+120+50+170+400 = 3,220; + 280 contingency = €3,500k. Tranche 1 (€1,840k + €160k contingency): 400/200/190/650/60/20/110/210 (sum 1,840). Tranche 2 (€1,380k + €120k contingency): 450/180/260/150/60/30/60/190 (sum 1,380). Each category's two tranche amounts add to the category total.
financing_model_no_revenue	100% grant-financed; no fares, no user charges, no revenue, no debt, no debt service	decision	Cooling access, transport, calls and home kits are free public-health services, so revenue = €0 and the full €3.5M Year-1 cost is a subsidy; no coverage ratio applies, and the gap is the funding source for Year 2.
year2_recurring_cost_estimate	≈€2.3M per year to continue the same footprint (estimate, no inflation); funding source not identified (open decision)	estimate	Recomputed: €3.5M − €280k contingency − ~€650k one-off kit purchase (tranche-1 kit line) − ~€270k one-off set-up (legal, fit-out, baseline, playbook) = €2.3M; no source commits Year-2 money, so the municipality or a funder must decide before Month 12 (2027-10-08).
refuge_network_size	10 refuge sites (range 8-12), ~40 places each ≈ 400 places; target ≥70% of enrolled residents within 800 m (10-min walk)	decision	Pragmatic Foundation (many small neighborhood refuges in libraries, parish halls, community centers); 10 × 40 = 400; program finances staffing, security, signage and minor fit-out, while premises are existing municipal/partner assets under facility-use MOUs with no construction; capacity per site and 800 m/70% are proposed values, coverage measured from partner-reported neighborhood aggregates.
refuge_hours	10:00-20:00 at Level 2 and 3; 3 fully accessible sites extend to 24:00 at Level 3 only	proposed threshold	Source minimum 10:00-20:00 with extension to 24:00 where infrastructure allows; overnight cover limited to Level 3 to protect the budget while addressing hot-night risk.
refuge_site_standards	≥50% of places in fully accessible sites; ≥1 first-aid-certified staffer + AED per site; remediation per site ≤€10k and ≤4 weeks, else defer or drop	proposed threshold	Accessibility audit due Month 1 (2026-11-08) (before facility MOUs); the €20-40k per-site remediation estimate exceeds the €10k cap, so such sites are dropped rather than funded.
refuge_activity_and_unit_cost	Season Months 6.8-11.8: 25 full-activation days (10 at Level 3) + 8 advisory-only days ≈ 2,620 planned site-hours; ≈€324 per planned site-hour fully loaded	estimate	Recomputed: 10 sites × 10 h × 25 days = 2,500 + 3 sites × 4 h (20:00-24:00) × 10 Level-3 days = 120 → 2,620 h; €850k ÷ 2,620 = €324.4; includes fixed costs (training, fit-out, standby), so the scaling model must split fixed from variable cost.
alert_advisory_level	Level 1 Advisory: forecast high ≥33°C or night low ≥20°C on ≥2 consecutive days, or national yellow warning → phone check-ins and pre-positioned supplies only	proposed threshold	Provisional low-cost advisory tier from the Pragmatic Foundation; values are proposed, reviewed after the first season (Month 12 = 2027-10-08), with false-alarm and missed-event rates tracked.
alert_levels_2_and_3_and_standdown	Level 2 Alert: forecast high ≥35°C and night low ≥22°C for ≥2 consecutive days (centers open). Level 3 Emergency: same thresholds for ≥3 consecutive days, or national red warning (extended hours, 24h phone line). Declaration ≤1 h after forecast trigger; partners/public informed 24 h ahead; stand-down when forecast is below thresholds and temperatures normal for 48 h, order communicated ≤2 h	proposed threshold	The source '≥35°C / ≥22°C for three consecutive days' is placed at Level 3; Level 2 at 2 days is added; local calibration is rejected for Year 1 because history is too thin and is deferred to the post-season review; declaration, 24-hour advance publication and 48-hour stand-down rules come from the assumptions and risks (merged with the former separate declaration/stand-down fact).
command_structure	Incident commander in mayor's office with public-health deputy; operations lead from civil protection; communications lead from municipal communications office; partner-coordination lead = partner liaison officer; delegation of authority signed by Month 1 (2026-11-08)	decision	Command Seat option 1 (mayoral office + health deputy) selected for procurement speed; alert declarations are non-delegable to political advisors, with the deputy empowered if the mayor's office is unavailable.
communications_cadence	Daily SITREP 08:30; partner briefing 09:30; public update by 11:00 on Level 2-3 days; Level 1 = partner notice only	proposed threshold	The brief requires a daily situation report, partner briefings and public updates; the times are proposed.
transport_model	Volunteer drivers target 40 (range 30-50) run by 2 dispatchers + 1 backup coordinator (3 dispatch FTE); taxi/accessible-transport standby retainer capped at €80k with ≥10 vehicles within 20 min, ≥3 wheelchair-capable	decision	Volunteer-plus-taxi-backup option; retainer estimate €50-80k, so the cap is the top of the range; volunteers are unpaid and program-financed costs are vetting, insurance, mileage and dispatch; the 3 dispatch FTE equal the dispatch line in the staffing plan.
transport_contract_timing	Retainer signed Month 1.2 (2026-11-14); ≥20 volunteers (50% of 40) vetted by Month 2 (2026-12-08), remainder by Month 3 (2027-01-08); if <20 recruits in pipeline at Month 1.5 (2026-11-23), retainer scaled up proportionally	proposed threshold	Retainer signing must precede the Month 2 (2026-12-08) gate, so the 'signed by Month 3.7 (2027-01-29)' item is rejected; quotes by Month 1 (2026-11-08), signing Month 1.2 (2026-11-14).
taxi_only_fallback	+€150-250k; 500-1,000 fewer kits; fits the €3.5M cap by cutting kits from 2,000 to 1,000-1,500, or by drawing 54-89% of the €280k contingency (of which only €160k is available before Month 4 = 2027-02-08)	estimate	Recomputed: €150-250k ÷ €250-300 per kit = 500-1,000 kits; 150/280 = 54% and 250/280 = 89% of total contingency, but 150/160 = 94% and 250/160 = 156% of the tranche-1 contingency, so the top of the range cannot be absorbed before Month 4 (2027-02-08) and competes with the delayed-release gap (see contingency_exposure_and_free_contingency); no schedule delay if triggered at Month 1.5 (2026-11-23), otherwise the Month 4 (2027-02-08) transport gate is at risk.
month2_readiness_gate	Month 2 (2026-12-08) gate passes only if: ≥8 of 10 sites signed with named managers; ≥50% places accessible; retainer signed; ≥20 volunteers vetted; heat line live (08:00-22:00; 24h at Level 3) with mock (5-8 requests, 3-5 escalations) passed; outreach/escalation training of all outreach staff then in post and 25-35 partner/street staff (test ≥80%); 100% of tranche-1 procurement orders placed	proposed threshold	Gate criteria are user-given; counts are proposed. 'Staffed' means site managers plus signed staffing agreements, since seasonal cohorts are hired in Months 3-5 (2027-01-08 to 2027-03-08) and later cohorts are trained at onboarding; before then the heat line runs on contracted or repurposed municipal health-line capacity; helpline mock moved before the gate, rejecting the later source date.
month4_gate_center_hours	≥80% of planned cooling-center hours delivered in the full-system drill	user constraint	User gate; the plan sets 'planned hours' as the drill protocol's hours (4-6 h activation of all 10 sites); real heat events cannot exist at Month 4 (2027-02-08), so drill evidence is used.
month4_gate_outreach_contact	≥60% contact success for enrolled high-risk residents, from a sample of ≥300 attempts	user constraint	User threshold of 60%; the sample size is proposed (95% interval half-width ≈ ±5.5 points at n=300: 1.96×√(0.6×0.4/300) = 0.055); success means a completed live conversation or documented door-knock response.
month4_gate_transport_time	Mean request-to-pickup time <45 min over ≥30 simulated requests incl. ≥5 wheelchair users; internal target 30 min for mobility-limited priority cases	user constraint	User gate of 45 min; the sample (≥30, replacing the 5-10 request stress test) and the 30-minute priority target are proposed.
month4_gate_after_action	After-action report completed and 100% of its corrective actions closed before the Month 4 (2027-02-08) decision	user constraint	User gate; timetable sets the draft at Month 3.5 (2027-01-23) and closure by Month 3.9 (2027-02-04).
drill_and_rehearsal_schedule	Drill protocol final Month 2.5 (2026-12-23); full-system drill Month 3.2 (2027-01-14); after-action draft Month 3.5 (2027-01-23); actions closed Month 3.9 (2027-02-04); gate decision Month 4 (2027-02-08); second full drill, transport stress test and stand-down drill Month 7 (2027-05-08)	decision	Source drill dates of 'April/May before the Month 4 (2027-02-08) gate' or 'Month 5 (2027-03-08)/Month 7 (2027-05-08)' contradict the order of events; gate evidence must come from the Month 3.2 (2027-01-14) drill, while Month 7 (2027-05-08) is a pre-season rehearsal (May = Month 7 = 2027-05-08).
gate4_partial_release_rule	Failed gate = no release. Unmeasurable/insufficient evidence = €750k (50%) at Month 4 (2027-02-08), remainder after a Month 5 (2027-03-08) re-test. Full release delayed to Months 5-6 (2027-03-08 to 2027-04-08) leaves a cash gap of €200-400k, €40-240k above the €160k tranche-1 contingency	decision	Source proposed '50% now, rest on June data', but June is Month 8 (2027-06-08), so the re-test is a drill at Month 5 (2027-03-08); 50% × €1.5M = €750k; since it modifies the user's 'only if gates are met' rule it needs funder approval; gap recomputed as €200-400k − €160k = €40-240k (the gap figure is for a full delay; the 50% release reduces it), bridged by deferring kit installation spend or a funder advance.
outreach_model_and_targets	Intermediary-held lists (housing associations, social services, NGOs, pharmacies); 3,000 enrolled high-risk residents by Month 7 (2027-05-08) (≈9% of 65+); 5,000 contact attempts/month in season; no-wrong-door via heat line and in-person at refuges	estimate	Intermediary route avoids city-held health data; 3,000 ÷ 34,000 = 8.8%; 5,000 attempts/month from the partner-capacity risk; €450k outreach line ÷ 3,000 = €150 per enrolled resident (planned cost-model unit; the line also funds street NGO grants and phone line).
street_contact_unhoused	NGO-delivered alert-day rounds (water, shade, referral cards, transport trigger) + drop-in cool points at existing day centers; no municipal street team in Year 1; teams of ≥2, never solo	decision	Street-contact options 1 and 3 chosen to keep trust and scarce nurses/social workers in housed outreach; funded as NGO grants from the outreach line; NGO agreements must set insurance, consent and incident debriefing.
gdpr_milestones	GDPR counsel engaged Month 0.5 (2026-10-23) (≤€30k); legal opinion Month 1 (2026-11-08); DPIA/screening + partner DPAs signed Month 1.5 (2026-11-23); 50-80 partner staff briefed Month 2 (2026-12-08); partner audit Month 9 (2027-07-08); only aggregates reach the city; data deleted ≤30 days after Month 12 (2027-10-08) unless re-consented	decision	Source dates for partner MOUs (Month 1 = 2026-11-08 vs Month 1.5 = 2026-11-23) are resolved to Month 1.5 (2026-11-23) so they follow the legal opinion; the claim that no DPIA is needed is not relied on because the heat line logs personal data; counsel cost is carried in the governance line.
language_access	Spanish + Valencian plus 4-6 non-official languages (candidates: Arabic, Romanian, Portuguese, to be confirmed Month 0 = 2026-10-08); 8-12 paid ambassadors (10-15 h/week) in place Month 2 (2026-12-08); language budget ≈€67k (≈€70k rounded); ≥5% of outreach calls in non-official languages	decision	Recomputed: translation ~€20k + interpretation ~€6k (€200-300/day × ~25 days = €5-7.5k) + ambassadors ~€41k (10 × 12.5 h × 22 weeks × €15/h = €41,250) = ~€67k; the source's €15-25k covers translation only; materials focus-tested Month 1 (2026-11-08).
home_kit_scope_and_cost	2,000 homes at ≈€300 each (≈€250 hardware + ≈€50 installation) = €600k, plus ≈€200k for expedite premium, storage, buffer stock, QA and hydration supplies = €800k	estimate	Recomputed: 2,000 × 300 = 600k; 600k + 200k = 800k. Program-financed; the source target of 5,000-6,500 homes is rejected because €800k ÷ 5,000 = €160 per home is below the ~€250-300 per kit implied by the 500-1,000 kits per €150-250k risk figures; tranche-1 kit line €650k = hardware €500k + €150k of the extras, so all hardware orders fall before the Month 4 (2027-02-08) release; tranche-2 kit line €150k = installation €100k + €50k of the extras; no construction; landlord co-funding not counted; lending deferred to Year 2.
kit_delivery_and_install_schedule	First call-off 30-40% (600-800 kits) at Month 1.2 (2026-11-14); 40-50% delivered by Month 4 (2027-02-08); 80% by Month 5 (2027-03-08); 100% by Month 6 (2027-04-08); 10-15% buffer stock held at Month 4 (2027-02-08); 100% installed by Month 7.3 (2027-05-17) by 10 handypersons from Month 4 (2027-02-08)	proposed threshold	Source delivery profile (Feb/Mar/Apr = Months 4/5/6 = 2027-02-08, 2027-03-08, 2027-04-08); 30-40% × 2,000 = 600-800; install rate 2,000 ÷ (10 × ~14 weeks × 5 days = 700 person-days) ≈ 2.9 per person-day; handypersons are contracted through procurement, with 2 h heat-safety training before the first installs (by Month 2, 2026-12-08, and at the latest before Month 4 = 2027-02-08); 10-20% of installs inspected.
home_kit_selection_rubric	Score 0-100: top-floor/poor insulation 30; age ≥75 (or 65+ with self-declared chronic condition) 25; living alone 20; built before 1980 15; no air-conditioning 10; full kit at ≥60	proposed threshold	Rubric from the Home Kit decision; weights sum 30+25+20+15+10 = 100 and are proposed; health status is self-declared through partners because the city holds no health records; top-floor and social-housing units are the priority segments.
staffing_plan	43 FTE at peak: coordination 3, cooling centers 18 (14 + 4 reserve), outreach 6, dispatch 3, phone line 3, handypersons 10 (Months 4-7 = 2027-02-08 to 2027-05-08.3 = 2027-02-08 to 2027-05-17); plus ~1.5 FTE part-time specialists	decision	Within the 35-50 FTE source range: 3+18+6+3+3+10 = 43; handypersons overlap the operating season (Months 6.8-11.8) only in Months 6.8-7.3, so in-season headcount is 33 after installs end; centers carry 4/14 ≈ 29% reserve (source 20-30%); specialists = HR 0.5, safeguarding lead 0.25, compliance monitor 0.25, playbook officer 0.5 = 1.5 FTE, all in the governance line; language ambassadors (~3 FTE-equivalent: 10 × 12.5 h ÷ 40) are paid from the language budget and not counted in the 43.
hiring_and_rota	HR coordinator 0.5 FTE Months 0-4 (2026-10-08 to 2027-02-08); hiring 40% Month 3 (2027-01-08), 40% Month 4 (2027-02-08), 20% Month 5 (2027-03-08); all in post by Month 6.7 (2027-04-29); shifts ≤3-4 consecutive alert days then 1-2 rest days; fatigue training by Month 3 (2027-01-08)	proposed threshold	Cohort split and dates from the staffing assumptions (40+40+20 = 100%; Jan/Feb/Mar = Months 3/4/5 = 2027-01-08, 2027-02-08, 2027-03-08; April 29 = Month 6.7 = 2027-04-29); volunteer recruitment launches Month 0 (2026-10-08).
procurement_route	Hybrid: specs Month 0.8 (2026-11-01); framework call-offs/below-threshold first wave of €500-700k by Month 1.5 (2026-11-23); all tranche-1 orders by Month 2 (2026-12-08); lot-based competitive tender for tranche-2 items after Month 4 (2027-02-08); 2-3 backup suppliers per category by Month 1 (2026-11-08)	decision	Combines Procurement options 1 and 3; no order splitting to avoid thresholds, price benchmarking against ≥3 quotes (proposed), and the expedited premium of 10-15% (€50-100k) is accepted inside the €800k kit line; the first wave fits within the €650k tranche-1 kit line plus early transport/handyperson orders.
health_data_loop	MOU by Month 1 (2026-11-08): daily aggregate heat-related EMS/ED counts by 10:00 next day (weekly fallback); validation pilot from Month 1.8 (2026-12-02); nurse triage line live by Month 2 (2026-12-08); notify commander at ≥1.5× historical average heat-related volume, mutual-aid review at ≥2×	proposed threshold	No identifiable records are shared; the 1.5×/2× thresholds are proposed and need calibration with the clinical partners; the 2-week pilot ends about Month 2.3 (2026-12-17) and is not a gate item.
baseline_estimates	80-120 heat-related EMS calls and 15-25 heat-attributable excess deaths per summer (provisional); data requested Month 0 (2026-10-08), audit Month 1 (2026-11-08), coding agreed by Month 2 (2026-12-08), usable baseline by Month 4 (2027-02-08)	estimate	Assumption-document estimates from temperature-mortality regression, not verified against municipal EMS or mortality records; coding noise of 10-30% is possible.
evaluation_design_and_limits	Pilot vs matched districts and prior years, temperature-adjusted, aggregate counts only, university partner under a data-processing agreement; no mortality-reduction target is set as a gate	decision	With 80-120 calls a season, a 10-20% change (8-24 calls) cannot be separated from year-to-year variation, so claims carry uncertainty ranges; mortality coding takes 4-8 weeks, so the Month 12 (2027-10-08) report is provisional and a final addendum follows by Month 14 (2027-12-08).
worker_protection	Municipal crews: shifted hours, mandatory breaks, water and shade at Level 2-3; heat clauses in new municipal contracts; one compliance monitor visits ≥50% of active contracts, corrective notice ≤48 h; private-employer guidance pack by Month 1 (2026-11-08) (non-binding)	decision	Worker Duty option 2 within normal municipal powers; the private-employer pack is guidance only, and uptake below 30% is a stated risk; the compliance monitor is a 0.25 FTE part-time role in the staffing plan.
public_communications	Messages focus-tested Month 1 (2026-11-08); trusted-messenger briefings (pharmacists, GPs, caretakers, faith leaders) by Month 6 (2027-04-08); pre-season campaign launch Month 6.5 (2027-04-23) via radio, flyers, pharmacy posters, door hangers, opt-in SMS; misinformation corrected ≤4 h	decision	Channels reach offline residents; the Month 6.5 (2027-04-23) launch is proposed, and the source corrects unsafe advice within 2-4 hours; myth-busting covers alcohol and fan use in extreme heat.
deliverables_timeline	Playbook drafting from Month 8 (2027-06-08); peer-city test and draft playbook Month 11 (2027-09-08); final playbook, scaling cost model, evaluation report and Year-2 roadmap at Month 12 (2027-10-08)	decision	Deliverables are user-defined; playbook officer 0.5 FTE for Months 8-12 (2027-06-08 to 2027-10-08) (the source's Months 9-12 = 2027-07-08 to 2027-10-08 conflicts with drafting from Month 8 = 2027-06-08); the cost model reports €/enrolled resident, €/site-hour and €/transport trip.
stop_and_restart_rules	Month 2 (2026-12-08) criterion unmet → fix by Month 2.5 (2026-12-23); >4 weeks behind (Month 3 = 2027-01-08) → funder restart/re-scope review. Month 4 (2027-02-08) failed gate → no release, fix and re-test Month 5 (2027-03-08); failure again → scale back to the tranche-1 minimum	proposed threshold	Pre-project assessment says restart if procurement or staffing lags by more than 4 weeks; the Month 5 (2027-03-08) re-test follows the contingent-release rule, and tranche-2 summer spend is not committed before a pass.

Focus and Context

A heat-response pilot in a 170k-resident Mediterranean city faces a structural timing mismatch: Month 4 (2027-02-08) gates must validate operations before real summer heat arrives, creating unfalsifiable evidence risk and €200–400k cash-flow exposure if the funder rejects drill-based proof. Simultaneously, three operational risks—supply-chain delays (4–8 weeks on kits), volunteer recruitment shortfall (15–25% attrition mid-season), and intermediary outreach reach (9% of vulnerable seniors, 91% unreached)—could collapse service during peak-mortality July–August if unmitigated early. The pilot's credibility, Year-2 scaling prospects, and €3.5M investment hinge on resolving these cascading dependencies by Month 1 (2026-11-08).

Purpose and Goals

Operationalize a replicable, gate-driven heat-response system (Months 0–12 = 2026-10-08 to 2027-10-08) meeting four scale gates at Month 4 (2027-02-08): ≥80% refuge hours, ≥60% outreach contact success, <45-min transport, after-action closure. Deliver a playbook, cost model and evaluation report for EU peer-city scaling. Success requires: written funder pre-agreement on drill-based evidence and partial-release rule by Month 0.5 (2026-10-23); procurement orders locked by Month 1.2 (2026-11-14); volunteer pipeline ≥20 by Month 2 (2026-12-08); outreach reach expanded from 3,000 enrolled to roughly 5,000 including one-time contacts (door-knock pathway) by Month 7 (2027-05-08).

Key Deliverables and Outcomes

Heat Response Playbook (SOPs, checklists, cost model, partner MOUs); evaluation report with baseline validation and temperature-adjusted attribution; Year-2 roadmap with funding recommendations; heat-related EMS calls tracked as an outcome with confidence ranges (baseline 80–120 per summer, provisional; no reduction target); 3,000 enrolled residents + 1,500–2,500 one-time contacted (total 5,000 reach estimate); 2,000 homes fitted with cooling kits; ≥8 operational refuge sites; ≥40 active volunteer drivers; ≥60% contact success under drill stress; <45-min mean transport time.

Timeline and Budget

12 months (Month 0 = 2026-10-08 to Month 12 = 2027-10-08); €3.5M hard cap (€2.0M tranche 1 immediate, €1.5M released at Month 4 = 2027-02-08 if gates met). Critical path: Month 0.5 (2026-10-23) (funder confirmation), Month 1 (2026-11-08) (legal/GDPR/baseline), Month 1.2 (2026-11-14) (procurement lock), Month 2 (2026-12-08) (readiness gate), Month 4 (2027-02-08) (scale gate), Month 7 (2027-05-08) (kit completion), Month 12 (2027-10-08) (playbook/evaluation). Contingency €280k (€160k before Month 4 = 2027-02-08). Year-2 funding ≈€2.3M/year (unfunded).

Risks and Mitigations

Risk 1: Cool-season gates (drill-only evidence, no real heat by Month 4 = 2027-02-08) risk €1.5M non-release if funder rejects gates; mitigation: obtain written funder sign-off on partial-release rule (€750k at Month 4 = 2027-02-08 if unmeasurable, remainder after Month 5 = 2027-03-08 re-test) by Month 0.5 (2026-10-23). Risk 2: Supply-chain delays (4–8 week exposure) push 60–80% of kits into June–July, missing peak-risk May; mitigation: place binding first-tranche orders (600–800 units) by Month 1.2 (2026-11-14) with backup suppliers; the expedite premium (€50–100k, estimate) is a line within the €800k kit category. Risk 3: Intermediary outreach reaches only 9% of vulnerable 65+ (3,000 of 34,000), leaving about 31,000 unreached; mitigation: add door-knock + sentinel outreach (2–3 temporary staff, Months 5–7 = 2027-03-08 to 2027-05-17, €50–80k) to reach additional 1,500–2,500, giving roughly 13–16% coverage (estimate) and about 29,000 unreached; 20–25% is a Year-2 target.

Audience Tailoring

Municipal decision-makers (mayor, CFO, health officer) and EU funder requiring gate-based accountability and risk transparency. Operational tone: direct statement of critical-path risks (cool-season gates, supply-chain compression, volunteer shortfall) with decision triggers and contingency rules. Avoids jargon; uses concrete €-amounts and month-offsets for clarity.

Action Orientation

Immediate (Month 0.1 = 2026-10-11): Incident commander and PMO lead brief funder, obtain written acceptance of drill-based gates and partial-release rule, secure in signed amendment by Month 0.5 (2026-10-23). By Month 0 (2026-10-08): request baseline health data. By Month 0.5 (2026-10-23): engage GDPR counsel. By Month 0.8 (2026-11-01): Issue detailed procurement specs to 5+ suppliers. By Month 1.2 (2026-11-14): Place binding first-tranche kit orders (primary + backup split, delivery SLA locked). By Month 1.5 (2026-11-23): Execute all partner DPAs; check volunteer pipeline (<20 in pipeline triggers retainer scale-up); first procurement wave placed; complete accessibility audit; finalize cooling-center facility MOUs. By Month 2 (2026-12-08): ≥20 volunteer drivers vetted and all tranche-1 orders placed. By Month 2 (2026-12-08): Month 2 (2026-12-08) readiness gate: verify all procurement, staffing, accessibility, systems live. By Month 3.2 (2027-01-14): Execute full-system drill; track gate metrics (center hours, contact success, transport time). Immediate escalation if any item slips >1 week beyond plan; activate contingency (taxi scale-up, kit expedite, budget reallocation) within 48 hours.

Overall Takeaway

The pilot can meet its gates and demonstrate harm reduction if three cascading risks are mitigated immediately: (1) secure funder's written commitment to drill-based evidence and partial-release rule by Month 0.5 (2026-10-23); (2) place the first procurement wave by Month 1.5 (2026-11-23), all orders and ≥20 vetted volunteers by Month 2 (2026-12-08); (3) expand outreach reach from 9% to roughly 13–16% (estimate) of vulnerable population via targeted door-knock (20–25% is a Year-2 target) by Month 7 (2027-05-08). Success delivers a replicable playbook for EU peer cities, establishes foundation for Year-2 scaling (€2.3M/year recurring, funding source TBD), and generates credible harm-reduction evidence. Failure on any single critical path (funder rejection, supply-chain collapse, volunteer shortfall without taxi scale-up) triggers mid-summer service cuts, harms enrolled residents, and destroys Year-2 viability.

Feedback

1. Strengthen funder-alignment narrative: frame cool-season gates as a feature (early operational validation before real heat) not a liability; emphasize that drill-based evidence is standard in EU climate-resilience pilots. 2. Quantify equity explicitly: replace '9% reach' with explicit coverage targets by neighborhood deprivation index (≥30% in top-3 deprived areas by Month 12 = 2027-10-08); include post-event equity audit as a gate. 3. Pre-commit Year-2 funding: allow the draft to slip to Month 12 (2027-10-08) only if necessary to secure ≥1 Year-2 funding source; incomplete Year-2 plan undermines peer-city interest. 4. Add volunteer contingency detail: specify reserve pool size (15–20 pre-vetted standby volunteers, 30–40% above active target) and activation triggers (Level 3 alerts or active roster <20). 5. Simplify gate measurement: replace 'drill + real event' ambiguity with explicit definition by Month 2.5 (2026-12-23): drill passes iff center hours ≥80%, contact ≥60%, transport <45 min all measured concurrently in one 12-hour or 24-hour simulated alert; no mixing of drill and piecemeal real data.

Unoptimized waterfall. Parallel work not modelled here.

Persuasive elevator pitch.

Castellón de la Plana Heat-Response Pilot: Life-Saving Infrastructure for Vulnerable Residents

Project Overview

Every multi-day heatwave leaves older, isolated, and poorly housed residents in life-threatening conditions. Castellón de la Plana faces 15–25 (estimate) heat-attributable excess deaths per summer, pending audit. This €3.5M, 12-month pilot operationalizes a replicable heat-response system that aims to reduce harm and tests the model through tiered alerts, 10 walkable cooling refuges, GDPR-safe outreach to 3,000 high-risk residents, home safety kits for 2,000 homes, and health-system coordination—all without new legislation or major construction.

Built on established practice from Barcelona, Paris, and Ahmedabad, tested by drills before summer, and governed by clear gates, the pilot delivers a playbook and scaling cost model for other EU cities to adopt. Gates (proposed, to be locally calibrated): ≥80% refuge hours delivered, ≥60% outreach contact, <45-minute transport, and 100% of corrective actions closed. The pilot aims to reduce harm and tests the model, offering municipal credibility, and a replicable blueprint for climate-resilient cities.

Target Audience

• Municipal decision-makers: Mayor, chief health officer, budget director
• Public-health authorities: Regional and national agencies; EU climate-resilience funding bodies
• Peer municipalities: Cities in Spain and other EU nations considering heat-response pilots
• Health systems: Hospitals, emergency medical services, primary care providers
• Community leaders: Representatives of older, isolated, and migrant residents in Castellón

The pitch emphasizes measurable gates, replicability, and legal defensibility for officials; equity and harm reduction for health and community sectors; and the scaling playbook for peer cities and funders seeking transferable models.

Risks and Mitigation Strategies

• Cool-season gates depend on drills, not real heat. Contingency: pre-specify the drill protocol by Month 2.5 (2026-12-23). If evidence is insufficient, release €750k (50%) at Month 4 (2027-02-08) and the remainder after a Month 5 (2027-03-08) re-test, accepting a cash gap of €200–400k.

• Procurement slips past the December 2026 deadline. Mitigation: issue specs by November 2026; place first-tranche orders by November 2026; pre-qualify 2–3 backup suppliers per category; hold €160k contingency in tranche 1.

• Volunteer recruitment shortfall. If <20 recruits are in the vetting pipeline by November 2026, scale the taxi retainer up (capped at €80k), trading cost for reliability.

• GDPR challenge or partner withdrawal. Mitigation: engage legal counsel by October 2026 (cost ≤€30k); sign partner data-processing agreements by November 2026; audit partners at Month 9 (2027-07-08).

• Staff fatigue during multi-day heat events. Mitigation: limit shifts to 3–4 consecutive alert days, hold a 20–30% staff reserve, and train all staff in fatigue management by January 2027.

Metrics for Success

Primary gates (user constraints):

• ≥80% of planned cooling-center hours delivered in the full-system drill (January 2027)
• ≥60% outreach contact success from ≥300 attempts
• Mean request-to-transport time <45 min over ≥30 simulated requests (including ≥5 wheelchair users)
• After-action report completed with 100% of corrective actions closed

Operational measures:

• ≥8 of 10 sites signed with named managers; ≥50% of places accessible by Month 2 (2026-12-08)
• Heat line live with mock-call test passed
• ≥50 partner staff trained on escalation
• 100% of tranche-1 procurement orders placed on schedule

Reach and equity:

• 3,000 enrolled high-risk residents by May 2027
• ≥70% of enrolled residents within 800 m (10-min walk) of a refuge
• ≥5% of outreach calls in non-official languages
• 2,000 homes with kits installed by May 2027

Health outcomes (not a gate):

• Baseline heat-related EMS calls (80–120 estimated) and excess deaths (15–25 estimated)
• Comparison to prior years and matched districts
• Heat-illness misinformation corrected within 4 hours

Stakeholder Benefits

For the municipality: A tested, auditable response system that meets national heat-warning obligations, reduces reputational risk from a failed summer response, protects the health system from surge, and positions Castellón as a climate-leader peer city for EU funding.

For residents: Reduced heat-illness risk through refuge access within walking distance, phone support and transport for mobility-limited people, cooler homes via installed kits, and clear escalation if heat illness occurs.

For health systems: Daily aggregate data on heat-related EMS calls and ED visits to guide escalation; a nurse triage line that diverts mild cases from EMS; and lower surge demand during multi-day events.

For employers: Clarity on municipal heat-protection rules and recognition for compliance.

For peer cities: A complete playbook, scaling cost model (≈€2.3M/year estimated for repeat), and evidence from drills and the first season, reducing their own pilots' uncertainty.

For funders: Demonstrable harm reduction, gate-based accountability, a clear scaling pathway, and low-risk replication potential across EU cities.

Ethical Considerations

The pilot keeps personal health data out of municipal hands by using intermediary-held lists (housing associations, social services, NGOs) that contact residents on the city's behalf; only aggregate results are shared, complying with GDPR without requiring new legislation. Vulnerable residents (older, isolated, migrant) are explicitly prioritized in outreach, home-kit targeting, and transport, with language access for ≥4 non-official languages via paid community ambassadors.

Unhoused residents are reached via NGO-led street rounds and drop-in cool points, not surveillance. Volunteers undergo safeguarding and insurance checks; all street staff work in teams of ≥2. Alert thresholds are evidence-based (national forecast + local consecutive hot nights) to avoid false alarms that waste budget or erode trust. The evaluation design reports uncertainty ranges honestly and does not claim unverifiable mortality reductions. All operational policies are published and subject to public and data-protection oversight. After-action incident reports are completed transparently; corrective actions are tracked.

Collaboration Opportunities

• Housing associations and social services: Enroll and contact residents directly, avoiding municipal data-handling risk.
• Pharmacies, GPs, and faith leaders: Serve as trusted messengers and enrollment referral points.
• Hospitals and EMS: Contribute daily aggregate heat-related call and visit counts to guide escalation; in return, the city shares nurse-line triage and worker-protection guidance.
• NGOs serving unhoused people: Lead street rounds and cool-point management; the city funds their alert-day shifts and transport triggers.
• Taxi and accessible-transport operators: Sign a standby retainer to guarantee response capacity; volunteer drivers augment capacity at lower cost.
• Schools and community centers: Loan their libraries and civic halls as refuge sites during summer, freeing municipal maintenance.
• University epidemiologists: Pre-register the evaluation design and conduct independent analysis under a data-processing agreement, strengthening credibility.
• Peer cities (Barcelona, Valencia, Murcia): Test the playbook at Month 11 (2027-09-08) and contribute data to refine the scaling cost model; 2028 is the wider rollout.

Long-term Vision

The pilot is the foundation of a city-scale heat-resilience system that scales to all of Castellón's 170,000 residents by Year 2 (estimated €2.3M/year recurring cost; funding source to be identified). Year-2 investments focus on durable home retrofits (exterior shading, insulation) in high-priority social-housing blocks, expanding the cooling-refuge network to 15–20 sites, and embedding heat-response skills into municipal operations, health systems, and employers' routine work.

The Playbook becomes a template for adoption by 5–10 peer EU cities by 2030, creating a network of cities with interoperable alert thresholds, shared evaluation methods, and common procurement leverage. By 2035, the pilot model informs a binding EU directive on municipal heat-health action plans, and heat-response funding is mainstreamed into city budgets and the health budget rather than treated as emergency spend.

The deeper vision: a region where heat is no longer a mortality event, where vulnerable residents are known, supported, and safe, and where municipal and health systems operate as integrated climate-resilience infrastructure.

Call to Action

• Approve the pilot by October 2026 and authorize the mayoral delegation of authority by November 2026 so that procurement, partnership agreements, and staff hiring can meet the December 2026 readiness gate.

• The funder should confirm the drill-based evidence rule and partial-release protocol in writing.

• Prospective partner cities (Barcelona, Valencia, Murcia) should signal intent to test the playbook at Month 11 (2027-09-08); 2028 is the wider rollout.

• Municipal departments should assign incident commanders and nominate cooling-center managers now.

• Health systems should designate data liaisons for the MOU by November 2026.

Delay past Month 1 (2026-11-08) risks slipping the Month 2 (2026-12-08) procurement gate and losing the first season's evidence window.

Goal Statement: Run a 12-month heatwave-response pilot in Castellón de la Plana, Spain (~170k residents) within a €3.5M hard cap (€2.0M initial, €1.5M released at Month 4 = 2027-02-08 only if all four scale gates are met), to reduce heat-related harm among vulnerable residents without major construction, and deliver a repeatable playbook by Month 12 (2027-10-08).

SMART Criteria

• Specific: Reduce heat-related harm in Castellón de la Plana through tiered alerts, about 10 cooling refuges, transport support, GDPR-compliant outreach to high-risk residents, home kits for 2,000 homes, health-system data loops, worker protection and public communications. The result is a Heat Response Playbook, scaling cost model, evaluation report and Year-2 roadmap.
• Measurable: Month 4 (2027-02-08) gates (user constraint): ≥80% of planned refuge hours delivered in the drill; ≥60% outreach contact success from ≥300 attempts; mean pickup under 45 min over ≥30 requests; after-action actions 100% closed. Also track heat-related EMS calls (baseline 80-120, estimate), ED visits, excess deaths (15-25, estimate) and equity coverage. No mortality-reduction target is a gate.
• Achievable: Uses existing libraries, community centers and parish halls, intermediary-held contact lists, volunteer drivers with taxi backup, and 43 peak FTE that can be hired or contracted. The €280k contingency covers some risks but not both the taxi-only fallback and a delayed release (exposure €350-650k, estimate). Cool-season gates rely on drills.
• Relevant: Multi-day heat events with hot nights are increasing and hit older, isolated, poorly housed, outdoor-working, unhoused and migrant residents hardest. The pilot gives a tested, auditable model other EU cities can adopt, and a basis for a Year-2 funding decision (≈€2.3M/year, estimate; source not identified).
• Time-bound: Project starts Month 0 (2026-10-08) and runs 12 months to Month 12 (2027-10-08). Readiness gate at Month 2 (2026-12-08); drill at Month 3.2 (2027-01-14); scale gate at Month 4 (2027-02-08); season Months 6.8-11.8; playbook drafting from Month 8 (2027-06-08); final deliverables at Month 12 (2027-10-08).

Dependencies

• Mayoral delegation of authority signed and incident command roles named by Month 1 (2026-11-08)
• GDPR counsel engaged, legal opinion and partner data-processing agreements signed by Month 1.5 (2026-11-23)
• Procurement of refuge fit-out, transport retainer, home kits and handyperson services completed by Month 2 (2026-12-08)
• Hiring and vetting of staff and volunteer drivers, with training completed before gates
• Hospital, EMS and primary-care MOU for aggregate heat data, and a university evaluation partner

Resources Required

• Home kits (shading, reflective blinds, fans, thermometer/hygrometers, hydration supplies) for 2,000 homes
• Taxi/accessible-transport standby retainer and volunteer driver insurance
• Refuge site fit-out: water, first-aid kits and AEDs
• Telephone interpretation, translation and printed materials (flyers, door hangers, posters)
• Heat helpline telephony and shared tracking spreadsheet

Related Goals

• Reduce emergency and hospital load during heat events
• Improve housing resilience for top-floor and social-housing residents
• Expand to city-wide and other EU cities
• Strengthen language access and equity of public services

Tags

• heatwave
• public health
• municipal
• Castellón de la Plana
• cooling centers

Risk Assessment and Mitigation Strategies

Key Risks

• Cool-season gates cannot be tested on real heat; drills are the evidence and the €1.5M release may be delayed, leaving a cash gap of €200-400k (estimate)
• Kit and transport procurement slips past Month 2 (2026-12-08), pushing installs beyond the season
• Volunteer recruitment or vetting shortfall pushes pickup times above 45 min or forces taxi-only (+€150-250k, estimate)
• GDPR challenge or partner withdrawal reduces outreach reach and the 60% contact gate
• Staff fatigue and absences in multi-day heat events degrade refuge hours and dispatch

Diverse Risks

• Reputational damage from an incident at a refuge or a failed response under media attention
• Volunteer and street-outreach safety, including assault and safeguarding failures
• Misinformation (alcohol, fan misuse) and weak reach to offline and migrant residents
• Budget overrun and no identified funding for Year 2
• Alert-trigger errors: false alarms burn budget, missed hot nights harm residents

Mitigation Plans

• Pre-specify drill protocol (final Month 2.5 = 2026-12-23) and full-system drill at Month 3.2 (2027-01-14); if evidence is insufficient, release €750k at Month 4 (2027-02-08) and the rest after a Month 5 (2027-03-08) re-test; hold €160k tranche-1 contingency
• Issue specs by Month 0.8 (2026-11-01), place the first 30-40% kit call-off at Month 1.2 (2026-11-14), and pre-qualify 2-3 backup suppliers per category; all tranche-1 orders by Month 2 (2026-12-08)
• Recruit volunteers from Month 0 (2026-10-08) in fortnightly vetting cohorts; if <20 recruits in pipeline at Month 1.5 (2026-11-23), scale the taxi retainer (capped at €80k)
• Obtain legal opinion by Month 1 (2026-11-08) and sign partner DPAs by Month 1.5 (2026-11-23); share only aggregates; audit partners at Month 9 (2027-07-08)
• Hold a 20-30% staff reserve, limit shifts to 3-4 consecutive days, and train in fatigue management by Month 3 (2027-01-08); require first-aid staff and AED per site, teams of ≥2, nurse triage line, and misinformation correction within 4 h

Stakeholder Analysis

Primary Stakeholders

• Incident commander (mayor's office) and public-health deputy
• Civil protection operations lead and communications lead
• Partner liaison officer and PMO/HR coordinator
• Refuge managers, dispatchers, phone operators, outreach staff and handypersons
• Volunteer drivers and community language ambassadors

Secondary Stakeholders

• Housing associations, social services, NGOs, pharmacies and GPs
• Hospitals, EMS and the national meteorological service
• Taxi and accessible-transport operators and kit suppliers
• Funder, university evaluation partner and data protection authority
• High-risk residents, unhoused people, migrant communities, faith leaders and employers

Engagement Strategies

• Primary team: daily SITREP at 08:30 on alert days, weekly progress reports during setup, prompt answers to information requests
• Partners: 09:30 briefing on alert days, signed MOUs/DPAs, monthly liaison contact, joint planning at Months 1, 4, 7 and 10 (2026-11-08, 2027-02-08, 2027-05-08, 2027-08-08)
• Health system: daily aggregate counts by 10:00, commander notified at ≥1.5× historical average volume
• Funder: gate reports at Months 2 and 4 (2026-12-08, 2027-02-08), plus immediate notice of scope or timeline changes
• Residents and community: radio, flyers, pharmacy posters, door hangers, opt-in SMS, trusted-messenger briefings, multilingual materials and focus-tested messages

Regulatory and Compliance Requirements

Permits and Licenses

• Facility-use agreements and insurance for each refuge site
• Public procurement approvals (framework call-offs, below-threshold and tenders)
• Volunteer driver insurance and background checks
• Municipal approval for exterior shading where building or heritage rules apply

Compliance Standards

• GDPR and Spanish data-protection law (lawful basis, retention, breach notice within 48 h)
• Disability accessibility requirements for refuge sites
• Occupational health and safety rules for outdoor workers and outreach staff
• EU/Spanish public-procurement rules and audit readiness

Regulatory Bodies

• Spanish Data Protection Agency (AEPD)
• Regional health authority and EMS
• National meteorological service (AEMET)
• Municipal legal and procurement departments

Compliance Actions

• Engage GDPR counsel at Month 0.5 (2026-10-23); opinion by Month 1 (2026-11-08); DPIA/screening and partner DPAs by Month 1.5 (2026-11-23)
• Run accessibility audit of all sites by Month 1.5 (2026-11-23); ≥50% of places in fully accessible sites
• Benchmark and document procurement files; avoid order splitting to stay under thresholds
• Train handypersons on safe fan use and installation; inspect 10-20% of installs
• Audit partner consent records at Month 9 (2027-07-08); delete data ≤30 days after Month 12 (2027-10-08) unless re-consented

Primary Decisions

The vital few decisions that have the most impact.

The Critical levers (Alert Trigger Ladder, Cooling Refuge Network Shape, Consent-Light Identification Routes, Mobility Support Delivery) cover the core trade-offs: sensitivity versus budget, access versus staffing, coverage versus GDPR exposure, and cost versus the 45-minute transport target. High levers cover governance, procurement speed, home kits and health integration. Missing dimensions: explicit staffing and volunteer-safety capacity, and surge and extreme-event contingency.

Decision 1: Alert Trigger Ladder

Lever ID: 051de1aa-88d5-466e-ae28-8ab0bc9001fd

The Core Decision: Defines the tiered heat-alert ladder (forecast daytime highs and night-time lows, consecutive hot nights) that converts a forecast into funded, pre-agreed actions. Success means few missed dangerous events, a controlled false-alarm rate, and clear spending authority per tier. Thresholds should be recorded as provisional (proposed) and reviewed after the first season, with the false-alarm and missed-event rate tracked as KPIs.

Why It Matters: The definition of each alert level decides when money, staff and volunteers are mobilised. Triggers set too low cause alert fatigue and burn the center-hours budget on marginal days. Triggers set too high miss the hot-night events that drive mortality among older residents. The ladder also decides who can authorise spending, which ties it to the governance structure.

Strategic Choices:

1. Adopt fixed forecast thresholds for daytime highs and night-time lows across three tiers, taking the national meteorological service forecast as the sole input and avoiding local calibration work.
2. Calibrate city-specific thresholds from local historical temperature and mortality records, with consecutive hot nights weighted more heavily than daytime peaks, and review them after the first season.
3. Combine the national warning with a low-cost advisory tier that triggers only phone check-ins and pre-positioned supplies, so full center activation is reserved for the upper tiers.

Trade-Off / Risk: Local calibration improves accuracy, but a small city may have too few historical heat events to calibrate against, so a sophisticated threshold can still end up as a rounded guess.

Strategic Connections:

Synergy: Feeds Command Seat Allocation by giving the alert declarer unambiguous criteria, and drives Cooling Refuge Network Shape and Mobility Support Delivery, since tiered activation lets overnight hours and standby transport be scaled only when needed.

Conflict: Tight, sensitive triggers strain the center-hours budget and Procurement Speed Route stock, while high triggers risk missing hot nights. Local calibration also competes with Attribution and Comparison Design for scarce analyst time and limited historical data.

Justification: Critical, Critical hub: it converts forecasts into funded actions and sets spending authority per tier. It drives refuge hours, transport standby, street rounds and procurement stock. It controls the core tension between alert fatigue and budget burn versus missed hot-night events.

Decision 2: Cooling Refuge Network Shape

Lever ID: 3f84fb80-bffd-45ce-baa6-960671698b0d

The Core Decision: Sets the footprint, hours and type of cooling spaces: small neighborhood refuges, large anchor sites, or a hybrid including sheltered housing common rooms and pharmacies. Key measures are the share of high-risk residents within a set walking distance (to be defined), utilization, hours delivered against the 80% Month 4 (2027-02-08) gate, and whether overnight cooling exists. Incident ownership and accessibility checks must be assigned per site.

Why It Matters: The shape of the network determines how many frail residents can actually reach a cool space and for how long. Many small neighborhood sites shorten walking distances but multiply staffing, security and accessibility checks. Few large sites are easier to run but depend heavily on transport. The choice also determines whether overnight cooling is offered, which matters most for hot-night risk.

Strategic Choices:

1. Contract many small neighborhood refuges in libraries, parish halls and community centers, accepting higher supervision costs per hour to keep most vulnerable residents within walking distance.
2. Contract a few large anchor sites such as sports halls and malls with extended and overnight hours, concentrating staff, medical cover and security while relying on the transport contract for access.
3. Build a hybrid network that adds cool common rooms in existing sheltered housing and social-housing blocks and pharmacy waiting areas as informal refuges, using spaces already air-conditioned and trusted by residents.

Trade-Off / Risk: Informal refuges in housing blocks and pharmacies cost little, but they sit outside the formal staffing, accessibility and liability framework, so quality varies and someone must still own incidents occurring there.

Strategic Connections:

Synergy: Works with Mobility Support Delivery, since shuttle loops and taxi retainers can be sized to the chosen site pattern, and with Street Contact Pathway, where outreach staff can enroll and refer people at sites.

Conflict: Many small sites multiply staffing and security needs, straining the budget and the Command Seat Allocation span of control. Few large sites raise dependence on Mobility Support Delivery and the 45-minute transport target.

Justification: Critical, Critical because the network footprint, hours and overnight offer determine who can physically reach cooling. It sets staffing, security and budget load, drives transport demand, and is directly tied to the Month 4 (2027-02-08) gate of 80% planned hours delivered.

Decision 3: Consent-Light Identification Routes

Lever ID: 08574780-bfb4-4c86-96af-ef1a149387f8

The Core Decision: Determines how high-risk residents are found without the city holding health records: opt-in registry, partner-held lists contacted by intermediaries, or building-level canvassing with local sentinels. Success is measured by coverage of the target groups, outreach contact rate (60% gate for enrolled residents), data-protection impact assessment completion, and reach among isolated residents. Legal basis and retention must be documented per route.

Why It Matters: The city cannot hold health records, so the way high-risk people are identified controls both coverage and GDPR exposure. Opt-in registries are the cleanest legally but tend to miss the most isolated residents. Partner-held lists reach more people but raise questions about the legal basis for contact. Geographic approaches avoid personal lists but cost more outreach time per person found.

Strategic Choices:

1. Build an opt-in heat registry enrolled through GPs, pharmacies and centers, with explicit consent and a short retention period, accepting that the most isolated residents are underrepresented.
2. Use intermediary-held lists, where housing associations, social services and NGOs make the calls on the city's behalf, so personal data never moves to the city and only aggregate contact results are reported.
3. Canvass by building rather than by person, with door-knock teams covering all top-floor and poorly insulated units in selected blocks, and recruit caretakers, postal workers and shop owners as trained neighborhood sentinels.

Trade-Off / Risk: Building-level canvassing avoids list-based GDPR risk and finds hidden residents, but it consumes staff hours on households that are not at risk and may feel intrusive without strong local trust.

Strategic Connections:

Synergy: Supplies the contact base for Street Contact Pathway and the household candidates for Home Kit Targeting and Fitting. Pairing with Language Access Architecture ensures enrolled residents are reached in a language they understand.

Conflict: Registry-based consent limits reach, in tension with the equity goals tracked in Attribution and Comparison Design. Building canvassing consumes outreach hours that compete with Street Contact Pathway capacity and the Home Kit Targeting and Fitting budget.

Justification: Critical, Critical because it governs the coverage-versus-GDPR trade-off and supplies the contact base for outreach and home kits. It decides whether isolated residents are found at all, and drives the 60% contact-success gate and equity outcomes.

Decision 4: Mobility Support Delivery

Lever ID: 3ec18596-3a00-4b69-8a84-895b6ce77872

The Core Decision: Chooses how mobility-limited residents reach cooling: contracted taxis and accessible vehicles, vetted volunteer drivers, or scheduled shuttle loops and mobile cooling. It decides whether the under-45-minute average time-to-transport gate can be met, including for wheelchair users. Key measures are requests served, wait times, cost per trip, safeguarding incidents, and the share of requests that could not be fulfilled.

Why It Matters: The 45-minute transport target depends on who provides rides and when they are called. Contracted taxis are fast and reliable but expensive per trip and often unsuitable for wheelchair users. Volunteers lower the cost but add safeguarding and insurance duties. Moving cooling to people can reduce the number of trips needed but narrows the services on offer.

Strategic Choices:

1. Sign an on-call contract with taxi and accessible-transport operators with guaranteed alert-day capacity, paying a standby retainer to secure response times and wheelchair-capable vehicles.
2. Recruit and train vetted volunteer drivers coordinated by a dispatcher, covering insurance and safeguarding checks, and keep taxi contracts only as a backup for failures and peak demand.
3. Schedule fixed shuttle loops between housing blocks and refuges on alert days and add mobile cooling vehicles for blocks with many housebound residents, reducing individual on-demand trips.

Trade-Off / Risk: Fixed loops are predictable and cheap per rider but serve only residents who can board and wait, so the least mobile residents, who most need help, may still depend on costly door-to-door rides.

Strategic Connections:

Synergy: Amplifies Cooling Refuge Network Shape by extending the effective reach of fewer, larger sites, and uses Alert Trigger Ladder tiers to time standby retainers and dispatch readiness.

Conflict: Standby retainers and wheelchair-capable vehicles take budget from Home Kit Targeting and Fitting. Volunteer models add safeguarding burdens that compete with Procurement Speed Route timelines before the Month 2 (2026-12-08) readiness gate.

Justification: Critical, Critical because the under-45-minute transport gate depends on it, and it determines whether larger refuge sites are usable by frail and wheelchair-using residents. It competes for budget with home kits and links to triggers, refuges and street teams.

Decision 5: Command Seat Allocation

Lever ID: 800f65e1-6777-4d46-b2be-6fac870126fd

The Core Decision: Assigns who declares alerts and who commands operations, communications and partner coordination, with written delegations and a clear accountability line. Success is measured by time from forecast trigger to declaration, absence of conflicting orders across departments, handover coverage during multi-day events, and clear public accountability if a response fails.

Why It Matters: Deciding which municipal office holds the incident commander role sets how quickly an alert is declared and how clearly operations, communications and partner coordination are separated. A seat close to the mayor speeds budget and cross-department decisions, while a seat in public health keeps clinical judgement central. The choice shapes who is accountable when a response fails in front of the press.

Strategic Choices:

1. Place the incident commander in the mayor's office with a deputy from public health, so cross-department orders carry political weight and procurement approvals move quickly.
2. Assign command to the municipal public health department, with civil protection supplying the operations section, so clinical judgement drives alert declarations and escalation rules.
3. Create a standing heat desk staffed by a rotating duty officer roster across departments, with a written delegation letter so any officer can declare an alert without waiting for a superior.

Trade-Off / Risk: Political-level command speeds decisions but can politicise alert declarations, while a health-led seat is credible but may lack authority over libraries, transport and public works; a rotating roster risks diffuse accountability when fatigue sets in.

Strategic Connections:

Synergy: Gives Alert Trigger Ladder a clear declaring authority so thresholds convert into action quickly. It also speeds Procurement Speed Route approvals when the commander can direct cross-department purchasing.

Conflict: A political seat risks politicising alerts, which clashes with the evidence-based thresholds in Alert Trigger Ladder. A rotating heat desk may blur accountability for Mobility Support Delivery and field operations during fatigue-heavy multi-day events.

Justification: High, Governs accountability and speed of alert declaration and cross-department action. It links to triggers and procurement approvals, and the politicised-versus-clinical authority trade-off matters. It is less of a budget hub than the operational delivery levers, so High rather than Critical.

---

Secondary Decisions

These decisions are less significant, but still worth considering.

Decision 6: Home Kit Targeting and Fitting

Lever ID: 983eaf4d-34f2-4e0c-82e9-f438cc3447f2

The Core Decision: Governs which homes receive shading, reflective blinds, fans, thermometers and hygrometers, and how they are installed without construction. A scoring rubric, landlord bulk deals, or a seasonal lending scheme each trade precision against cost and speed. Measures include installations completed, share of top-floor and social-housing priority units covered, fan safety checks, and resident-reported use. Consent and return logistics must be set up front.

Why It Matters: The home package has to reach the riskiest dwellings with a limited budget and no construction work. A rubric-based household selection concentrates spending but needs eligibility checks and consent. Bulk installation through landlords reaches more homes at lower unit cost but depends on landlord cooperation. Lending kits instead of giving them permanently stretches stock across seasons but needs storage and return logistics.

Strategic Choices:

1. Score households with a rubric using top-floor location, building age, age and living situation, then give the highest-scoring homes a full kit with handyperson installation and a safety check of fans.
2. Agree bulk installations with social-housing landlords, fitting exterior shading and reflective blinds to whole blocks at once, trading household-level targeting for lower unit cost and faster coverage.
3. Run a seasonal kit-lending scheme where shading, fans and thermometers are installed in May and collected in September, then cleaned and redeployed, so the same stock serves more households over the years.

Trade-Off / Risk: Lending extends the budget, but the collection and refurbishment burden falls on a handyperson team that is already stretched in summer, and residents may resist returning equipment they depend on.

Strategic Connections:

Synergy: Benefits from Consent-Light Identification Routes, which supply candidate households, and from Procurement Speed Route, which secures kits and handyperson capacity before the season. Trusted Messenger Channel Mix can raise uptake and correct fan-misuse.

Conflict: Competes with Mobility Support Delivery and Cooling Refuge Network Shape for the same limited budget and staff. Lending adds collection workload for handypeople, and landlord deals depend on cooperation outside municipal control.

Justification: High, High because it controls precision versus cost in the home-level package, and priority top-floor and social-housing coverage. It depends on identification and procurement, and competes with transport and refuge budgets. It is a delivery lever rather than a system hub.

Decision 7: Health Loop and Worker Duty Levers

Lever ID: c001d797-dbc8-4b19-a702-a159f7d8cf8e

The Core Decision: Defines how hospitals, EMS, primary care and employers connect to the heat response without new legislation or identifiable records. Success is measured by MOU signed before the Month 2 (2026-12-08) gate, daily aggregate counts received on alert days, escalation guidelines used consistently by call-takers and outreach staff, and municipal crews and contractors covered by heat-protection rules.

Why It Matters: The city has to use health and employment data lawfully and without new legislation. Daily aggregate signals from EMS and hospitals can inform escalation without exposing patient records. For workers, the city controls its own staff and contractors directly but private employers only by persuasion. How strongly it uses procurement and public pressure determines how far protection extends beyond municipal crews.

Strategic Choices:

1. Agree an MOU for daily aggregate counts of heat-related EMS calls and ED visits, with shared escalation guidelines for call-takers and outreach staff, and no sharing of identifiable patient records.
2. Write heat-protection clauses into municipal contracts and tenders, requiring schedule changes, breaks, water and shade from contractors, and publish a guidance pack and recognition scheme for private employers.
3. Pair outreach staff with a clinical nurse line that gives phone triage on suspected heat illness, so mild cases are managed at home and EMS capacity is reserved for severe cases.

Trade-Off / Risk: Contract clauses give the city real leverage over contractors, but enforcement relies on site inspections the municipality may not be able to staff, and private employers outside its tenders remain untouched.

Strategic Connections:

Synergy: Strengthens Street Contact Pathway by giving outreach staff clear escalation rules and a nurse line for suspected heat illness. It also supplies the aggregate EMS and ED counts that Attribution and Comparison Design needs for evaluation.

Conflict: Contract heat clauses compete with Procurement Speed Route, since added conditions slow tenders and narrow suppliers. Nurse-line and MOU work also draws scarce clinical and analyst time away from Mobility Support Delivery staffing.

Justification: High, High because it links hospitals, EMS and nurse-line triage to outreach escalation and protects healthcare capacity. It also supplies the aggregate outcome data for evaluation. Worker clauses add a second scope that conflicts with procurement speed.

Decision 8: Procurement Speed Route

Lever ID: 2b1e09e0-5071-4a61-959f-a1e15bb5ce8e

The Core Decision: Chooses the purchasing pathway for kits, handyperson services, transport, security and center fit-out so orders are placed by the Month 2 (2026-12-08) readiness gate. Key measures are days from specification to order, share of orders placed on time, price benchmarking against market quotes, audit-readiness of files, and whether the approach can be reused under other EU cities' procurement rules.

Why It Matters: The procurement pathway for kits, transport, security and center fit-out sets how fast orders are placed by the Month 2 (2026-12-08) gate and how much price and quality competition the city gets. Faster routes reduce schedule risk but narrow supplier choice and raise audit scrutiny. The route chosen also determines whether the playbook can be reused by other EU cities under their own rules.

Strategic Choices:

1. Use existing municipal or central-purchasing framework agreements with call-off orders for kits, vehicles and services, accepting limited product choice in exchange for placing orders within weeks.
2. Run a short competitive tender in lots, separating kits, handyperson installation and transport, so small local firms and social enterprises can bid and no single supplier failure stalls the program.
3. Place a small first order of pre-positioned stock through simplified below-threshold purchasing, then run a full competitive process for the second tranche once the Month 4 (2027-02-08) gate releases funds.

Trade-Off / Risk: Frameworks and below-threshold buying meet the schedule, but if call-off prices go unbenchmarked or orders are split to stay under thresholds, the city risks an audit finding that undermines the program's public credibility.

Strategic Connections:

Synergy: Enables Home Kit Targeting and Fitting by getting stock and installers in place before the first heat events. It also gives Mobility Support Delivery a signed transport contract in time for the Month 2 (2026-12-08) gate.

Conflict: Fast frameworks limit supplier choice, which constrains Home Kit Targeting and Fitting product fit and local social-enterprise participation. Speed also conflicts with the contract-clause requirements in Health Loop and Worker Duty Levers.

Justification: High, High because it governs schedule risk against the Month 2 (2026-12-08) readiness gate for kits, transport and installers. It enables home kits and transport contracts but conflicts with contract clauses, language work and supplier choice. Audit risk also affects public credibility.

Decision 9: Trusted Messenger Channel Mix

Lever ID: cd73026b-177e-48d6-a165-02682fb3c079

The Core Decision: Sets who carries heat-safety messages to residents who are offline or distrust official channels, and how limited communication budget is split between professional messengers, mass media and peer ambassadors. Success means briefed messengers, consistent scripts, reach among 65+, migrants and people living alone, and quick correction of unsafe advice such as alcohol use or misused fans.

Why It Matters: Because many at-risk residents are offline, who delivers the message matters as much as the channel. Using familiar figures such as pharmacists, GPs, building caretakers and faith leaders improves uptake and counters unsafe advice, but it requires training and consistent scripts. Spreading effort across many channels dilutes the budget, so the mix determines how much is left for field delivery.

Strategic Choices:

1. Invest most of the communications budget in pharmacist, GP-practice, caretaker and faith-leader briefings with printed leave-behinds, and keep mass media to radio and low-cost municipal channels.
2. Run a conventional pre-season campaign through local radio, posters, door hangers and flyers, with a lighter partner briefing layer and a rapid-response rebuttal channel for misinformation.
3. Recruit residents who have lived through past heat events, including older tenants and migrant community members, as paid peer ambassadors who deliver messages in building lobbies, markets and language groups.

Trade-Off / Risk: Peer and professional messengers reach people mass media misses, but they spread consistent messaging only with sustained briefing, and a single ambassador repeating unsafe advice like alcohol or misused fans can damage trust.

Strategic Connections:

Synergy: Amplifies Language Access Architecture, since trusted community messengers deliver translated content credibly. It also feeds enrollment into Consent-Light Identification Routes through pharmacists, GPs and caretakers who can refer residents.

Conflict: Heavy investment in messenger training and peer ambassadors reduces funds for Street Contact Pathway field staff and Home Kit Targeting and Fitting. Decentralised messengers also strain message consistency controlled by Command Seat Allocation.

Justification: Medium, Medium: it improves uptake, enrollment referrals and misinformation control among offline residents. It amplifies language access and identification, but it is an optimisation of reach and does not decide the core operational trade-offs. It competes for field budget.

Decision 10: Attribution and Comparison Design

Lever ID: dda15186-39ef-42c7-933c-0e007145ecff

The Core Decision: Determines how credibly the program can claim reductions in heat-related EMS calls, ED visits and excess mortality, and how defensible the scaling cost model is. Scope covers comparison groups, temperature adjustment, data-processing agreements, analyst capacity and plain-language statements of limits. Success is a pre-specified protocol, usable baselines by Month 4 (2027-02-08), and honest uncertainty ranges.

Why It Matters: The evaluation design determines whether reported reductions in EMS calls, ED visits and excess deaths can be credibly linked to the program rather than to a mild summer. Stronger comparison designs need more data access, partner cooperation and analyst time. Simpler pre-post comparisons cost less but are easily challenged, which affects the credibility of the cost model for other cities.

Strategic Choices:

1. Compare heat-day outcomes in pilot districts against matched non-pilot districts and prior years, adjusting for temperature, using aggregate EMS, ED and mortality counts only.
2. Use a pre-post comparison against a multi-year city baseline, report heat-attributable excess mortality with explicit confidence ranges, and state attribution limits in plain language.
3. Commission an independent university or public-health institute partner to pre-register the evaluation protocol and analyze data under a data-processing agreement, publishing results regardless of direction.

Trade-Off / Risk: Independent pre-registered evaluation increases credibility, but small-area counts in a mid-sized city are noisy, so even a well-designed comparison may be unable to detect real effects within one season.

Strategic Connections:

Synergy: Builds on Health Loop and Worker Duty Levers, whose aggregate EMS and ED counts supply the outcome data. It also supports Alert Trigger Ladder by testing whether thresholds correspond to real health impacts.

Conflict: Matched-district comparison conflicts with Cooling Refuge Network Shape and Home Kit Targeting and Fitting, which concentrate effort in the highest-need areas. Independent evaluation also consumes budget otherwise available for field delivery.

Justification: Medium, Medium: it sets the credibility of outcome claims and the scaling cost model, but it does not affect delivery within the first season. Small-area counts limit detection anyway. It conflicts mildly with concentrating effort in high-need areas.

Decision 11: Language Access Architecture

Lever ID: 6c3b08dc-5896-49e6-9070-a5aa9686a1a7

The Core Decision: Determines how alerts, enrollment scripts and heat-illness escalation guidance reach recent migrants and other residents with limited local-language skills. Scope covers the heat line, door-knock teams, cooling-center welcome desks and printed materials. Success metrics: share of enrolled residents contacted in their preferred language, language coverage of the heat line during alert hours, and enrollment parity across neighborhoods. Must be workable before the Month 2 (2026-12-08) readiness gate.

Why It Matters: Recent migrants with limited service access are a named priority group, and translated flyers alone rarely reach them. How the city delivers language support determines whether alerts, scripts and escalation guidance work in practice. A cheap, centralised approach may fail on trust, while community-based approaches take longer to build before the season.

Strategic Choices:

1. Contract a telephone interpretation service for the heat line and outreach staff, and translate core materials into the locally most common languages identified from municipal registers.
2. Recruit paid community language ambassadors from migrant associations to co-write messages, accompany door-knocks and staff cooling-center welcome desks in their own languages.
3. Build a pictogram-first message set for door hangers, flyers and center signage tested with residents, relying on images and short phrases so one design serves many language groups.

Trade-Off / Risk: Interpretation lines scale quickly but do little for trust, ambassadors build trust but depend on recruitment time and fair pay, and pictograms can be misread for nuanced safety advice such as fan use or medication.

Strategic Connections:

Synergy: Amplifies Trusted Messenger Channel Mix, since ambassadors double as community messengers, and strengthens Consent-Light Identification Routes by making NGO and community referrals credible and understandable to migrants who avoid formal registries.

Conflict: Competes with Procurement Speed Route, because ambassador recruitment and pictogram testing take longer than buying interpretation services before Month 2 (2026-12-08). Also draws budget and staff time from Home Kit Targeting and Fitting and Mobility Support Delivery.

Justification: Medium, Medium: it is essential for the migrant priority group and amplifies messengers and identification. It is mainly an enabling layer on other levers, and its overlap with the messenger mix lowers its standalone strategic weight.

Decision 12: Street Contact Pathway

Lever ID: 19aa58cd-6159-4122-9aef-58afa868db60

The Core Decision: Provides a dedicated route to unhoused people, who are absent from registries and rarely reachable by phone. Scope includes alert-day rounds, water and shade provision, referral cards, on-the-spot transport triggers and clear rules on consent and enforcement boundaries. Success metrics: distinct individuals contacted per alert day, share referred or transported, heat-illness events in this group, and partner reporting quality. Staffing needs to be realistic for a mid-sized city.

Why It Matters: Unhoused people rarely appear on registries or answer phones, so the usual enrollment route misses them. A dedicated street contact pathway shifts effort toward mobile teams and shelter partners, drawing resources away from housed outreach. It also raises questions about consent and enforcement boundaries when staff meet someone in clear distress.

Strategic Choices:

1. Fund existing homeless-service NGOs to run daytime mobile water-and-shade rounds with cooling vests and referral cards, keeping the city out of direct contact.
2. Deploy a small municipal street team, jointly staffed with a nurse and a social worker, that patrols known sites on alert days and can trigger transport on the spot.
3. Open drop-in daytime cool points at day centers and soup kitchens already trusted by the target group, with showers, storage for belongings and no identification required.

Trade-Off / Risk: NGO-led rounds preserve trust but depend on partner capacity and reporting, a municipal team gives control but may deter people wary of authorities, and fixed drop-in points miss those who will not travel.

Strategic Connections:

Synergy: Works with Mobility Support Delivery, because street teams can trigger transport directly to cooling centers, and with Alert Trigger Ladder, which can schedule rounds and drop-in hours by alert level for timely deployment.

Conflict: Diverts scarce nurses, social workers and budget from housed outreach under Consent-Light Identification Routes. A municipal team also complicates Command Seat Allocation, since it needs clear ownership, and may erode NGO trust.

Justification: Medium, Medium: it serves a narrow but high-risk group, the unhoused. It links to transport and alert tiers but affects a small share of overall mortality. It draws scarce clinical and social staff from housed outreach, and can be delegated to NGOs.

Choosing our strategic path.

The Strategic Context

Understanding the core ambitions and constraints that guide our decision.

Ambition and Scale: Moderate, city-scale public-health program in one non-capital EU city (150k–400k residents). EUR 3.5M (user constraint) over 12 months, released as EUR 2.0M up front and EUR 1.5M at Month 4 (2027-02-08) if gates are met. The brief asks for a practical pilot footprint that expands only after early success. It also asks for a repeatable playbook and a scaling cost model for other EU cities. The ambition is demonstrable harm reduction, not transformation.

Risk and Novelty: Low-to-moderate risk and low novelty. Heat-health action plans, cooling centers and welfare checks are established practice. The main risks are operational: the Month 2 (2026-12-08) and Month 4 (2027-02-08) gates fall in the cool season, so evidence must come from drills and simulated alert days. Other risks are GDPR exposure, volunteer safety, reputational damage after a failed response, and surge during extreme events. The brief explicitly says to avoid the most aggressive scenario.

Complexity and Constraints: High breadth, with seven workstreams: governance, cooling and transport, outreach, home kits, health coordination, worker protection and communications. Hard constraints: no new legislation, GDPR limits and no access to health records, no app-first design, realistic hireable staffing, and no major construction. Explicit gates: 80% of planned center hours delivered, outreach contact success of at least 60%, average time-to-transport under 45 minutes, and a closed after-action report. Procurement and contracting must finish by Month 2 (2026-12-08).

Domain and Tone: Public-health and municipal governance, written for immediate execution by a municipality. Operational and equity-focused, with clear owners, SOPs, a risk register and KPIs. Public money requires accountability and defensibility.

Holistic Profile: A pragmatic, gate-driven municipal pilot that must reach vulnerable and often offline residents. It has to stay inside normal municipal powers and GDPR limits, and it must pass early performance gates using drills. It needs moderate ambition, controlled risk, fast cross-department decisions, and a balance of reach, cost and legal safety. It does not need experimental or maximal-coverage designs.

---

The Path Forward

This scenario aligns best with the project's characteristics and goals.

The Pragmatic Foundation

Strategic Logic: Combines the national warning with a low-cost advisory tier, formal neighborhood refuges within walking distance, and intermediary-held lists that keep personal data with trusted organizations. Volunteer drivers with taxi backup and mayoral-level command balance reach, cost and speed of approvals. This path is the most likely to meet the Month 4 (2027-02-08) gate (80% of planned center hours, at least 60% outreach contact success, under 45 minutes to transport) without extreme risk.

Fit Score: 9/10

Why This Path Was Chosen: It matches the brief's mix of libraries, community centers and churches within walking distance. Intermediary-held lists (housing associations, social services, NGOs, pharmacies) fit the GDPR constraints, and the advisory tier controls cost and alert fatigue. Mayoral-level command speeds procurement before Month 2 (2026-12-08), and taxi backup protects the 45-minute transport gate. It is the most likely to meet the Month 4 (2027-02-08) gates at moderate risk.

Key Strategic Decisions:

• Alert Trigger Ladder: Combine the national warning with a low-cost advisory tier that triggers only phone check-ins and pre-positioned supplies, so full center activation is reserved for the upper tiers.
• Cooling Refuge Network Shape: Contract many small neighborhood refuges in libraries, parish halls and community centers, accepting higher supervision costs per hour to keep most vulnerable residents within walking distance.
• Consent-Light Identification Routes: Use intermediary-held lists, where housing associations, social services and NGOs make the calls on the city's behalf, so personal data never moves to the city and only aggregate contact results are reported.
• Mobility Support Delivery: Recruit and train vetted volunteer drivers coordinated by a dispatcher, covering insurance and safeguarding checks, and keep taxi contracts only as a backup for failures and peak demand.
• Command Seat Allocation: Place the incident commander in the mayor's office with a deputy from public health, so cross-department orders carry political weight and procurement approvals move quickly.

The Decisive Factors:

• Fit with ambition and risk: The plan is a moderate, gate-driven pilot that must avoid the most aggressive path. This scenario balances reach, cost and speed without extreme risk.
• GDPR and offline reach: Intermediary-held lists (housing associations, social services, NGOs, pharmacies) keep personal data out of city hands. They also reach people who are not smartphone users.
• Gate readiness: Many small walkable refuges in libraries, parish halls and community centers match the brief's asset list. Mayoral-level command with a public-health deputy speeds contracting and procurement before the Month 2 (2026-12-08) gate. Taxi backup protects the 45-minute transport target.
• Budget discipline: The advisory tier limits alert fatigue and center-hour spend.
• Why not the others:
  • The Pioneer's Reach adds staffing intensity, liability ambiguity and thin-data calibration, which makes the gates harder to meet.
  • The Consolidator's Safeguard is safe but leaves isolated and mobility-limited residents under-covered, and its retainers draw budget away from home kits.

---

Alternative Paths

The Pioneer's Reach

Strategic Logic: Prioritizes finding and serving the hardest-to-reach residents through local calibration, building-level canvassing with neighborhood sentinels, trusted informal refuges and mobile cooling, with a delegated heat desk for speed. It accepts higher quality variance, staffing intensity and liability complexity, so the Month 2 (2026-12-08) and Month 4 (2027-02-08) gates (user constraints) need close tracking. Because the first gates fall in the cool season (Months 2 and 4 = 2026-12-08, 2027-02-08), gate evidence will depend on drills and simulated alert days, which this option leans on heavily.

Fit Score: 4/10

Assessment of this Path: It maximizes reach to hidden residents, but building-level canvassing, informal refuges outside the liability framework, mobile cooling and local calibration with thin data are staffing-heavy and variable in quality. This conflicts with the instruction to avoid the most aggressive path and with the Month 2 (2026-12-08) and Month 4 (2027-02-08) gate timelines.

Key Strategic Decisions:

• Alert Trigger Ladder: Calibrate city-specific thresholds from local historical temperature and mortality records, with consecutive hot nights weighted more heavily than daytime peaks, and review them after the first season.
• Cooling Refuge Network Shape: Build a hybrid network that adds cool common rooms in existing sheltered housing and social-housing blocks and pharmacy waiting areas as informal refuges, using spaces already air-conditioned and trusted by residents.
• Consent-Light Identification Routes: Canvass by building rather than by person, with door-knock teams covering all top-floor and poorly insulated units in selected blocks, and recruit caretakers, postal workers and shop owners as trained neighborhood sentinels.
• Mobility Support Delivery: Schedule fixed shuttle loops between housing blocks and refuges on alert days and add mobile cooling vehicles for blocks with many housebound residents, reducing individual on-demand trips.
• Command Seat Allocation: Create a standing heat desk staffed by a rotating duty officer roster across departments, with a written delegation letter so any officer can declare an alert without waiting for a superior.

The Consolidator's Safeguard

Strategic Logic: Chooses the most proven and controllable options: fixed national-forecast thresholds, a few staffed anchor sites, a consent-based registry, contracted taxi capacity with guaranteed response, and clinically led command. This minimizes GDPR, liability and calibration risk and gives predictable costs and clear accountability for the Month 2 (2026-12-08) and Month 4 (2027-02-08) gates. The trade-off is lower coverage of isolated residents and reliance on transport to reach the sites.

Fit Score: 6/10

Assessment of this Path: It is low-risk and controllable, with clear clinical accountability and guaranteed taxi capacity. However, a few large sites and an opt-in registry under-serve isolated, mobility-limited and offline residents. A taxi-only model with retainers also diverts budget from home kits, and the design is less equity-oriented than the brief requires.

Key Strategic Decisions:

• Alert Trigger Ladder: Adopt fixed forecast thresholds for daytime highs and night-time lows across three tiers, taking the national meteorological service forecast as the sole input and avoiding local calibration work.
• Cooling Refuge Network Shape: Contract a few large anchor sites such as sports halls and malls with extended and overnight hours, concentrating staff, medical cover and security while relying on the transport contract for access.
• Consent-Light Identification Routes: Build an opt-in heat registry enrolled through GPs, pharmacies and centers, with explicit consent and a short retention period, accepting that the most isolated residents are underrepresented.
• Mobility Support Delivery: Sign an on-call contract with taxi and accessible-transport operators with guaranteed alert-day capacity, paying a standby retainer to secure response times and wheelchair-capable vehicles.
• Command Seat Allocation: Assign command to the municipal public health department, with civil protection supplying the operations section, so clinical judgement drives alert declarations and escalation rules.

Purpose

Purpose: business

Purpose Detailed: Public-health and municipal infrastructure/governmental initiative to cut heat-related deaths and serious illness at city scale. It covers heat alert governance, cooling centers and transport, GDPR-compliant outreach to high-risk residents, low-cost home interventions, health system coordination, worker protection, and public communications. It is funded with public money (€3.5M, released in two stages against go/no-go gates), has KPIs and equity metrics, and produces a repeatable playbook and a scaling cost model for other EU cities. This is a societal-scale, public welfare and governmental project, so it falls under business.

Topic: 12-month heatwave mortality and illness reduction program for a mid-sized non-capital European city (population 150k–400k), with a €3.5M staged budget, focused on vulnerable groups

Domain

Primary domain: Heat Health Action Planning

Secondary domains: Emergency Management, Data Protection Law, Public Health Outreach

Rationale: Heat Health Action Planning is the only outcome-role candidate and owns the main success criterion: reducing heat-related deaths and illness through alert-triggered municipal response. Public Health Outreach, Emergency Management and the others are subordinate methods or constraints.

Disciplines this project involves:

Domain	Importance	Specificity	Role	Reason
Heat Health Action Planning	5	5	outcome	Core success criterion is reducing heat-related mortality and illness through alert-triggered municipal response.
Public Health Outreach	5	5	method	Phone-tree, door-knock and enrollment of high-risk residents is the core delivery mechanism.
Emergency Management	4	4	method	Incident-command governance, alert levels, drills, surge planning and cooling-center operations rely on emergency management.
Data Protection Law	4	4	constraint	GDPR limits identification, registries, and health-data sharing for outreach to high-risk residents.
Public Procurement	4	4	method	Contracting cooling centers, transport and home-intervention kits within municipal rules and gate deadlines.
Urban Climate Adaptation	4	4	method	Heat-resilience measures like shading and cooling refuges for hot-night events in cities.
Epidemiological Surveillance	4	4	method	Baselines, excess mortality estimates and aggregate health signals for evaluation and gating.
Occupational Health	3	4	constraint	Outdoor municipal workers need heat-stress schedules, breaks, water and employer guidance.
Social Work	4	3	stakeholder	Social services lists, door-knock outreach and support for isolated, unhoused and migrant residents.

Plan Type

This plan requires one or more physical locations. It cannot be executed digitally.

Explanation: The plan is a 12-month municipal heatwave mortality-reduction program for a mid-sized European city. It is physical throughout and cannot be run online alone. Its core activities take place in the real world:

• Cooling centers: Libraries, community centers, malls, churches and sports halls must be contracted, staffed, secured and made accessible (wheelchair access, quiet rooms, water, toilets). Residents must physically travel to them.
• Transport: Taxi, paratransit or volunteer-driver services must physically move mobility-limited residents to the centers within a target time.
• Outreach: Door-knocking, in-person enrollment at centers and welfare checks on people living alone are face-to-face activities. They carry staff and volunteer safety considerations.
• Home interventions: Exterior shading kits, reflective blinds, window fans, thermometers and hygrometers, and hydration supplies must be procured, stored, distributed and installed. A handyperson service must visit top-floor flats and social housing.
• Health system coordination: Hospitals, EMS and primary care are physical services. Proactive check-ins are meant to keep ambulances and emergency departments free.
• Worker protection: Outdoor municipal workers need shaded rest points, water, adjusted schedules and mandatory breaks on real work sites.
• Communications: Flyers, pharmacy posters, door hangers, radio and faith and community leaders are used because many vulnerable residents are offline. This work needs physical distribution.
• Site-specific and staffing needs: The plan requires a specific EU city and its housing stock, plus hiring or contracting of coordinators, outreach staff, center staff and drivers. Drills and early-season heat days must be run on the ground to meet the Month 2 (2026-12-08) readiness gate and the Month 4 (2027-02-08) scale gate.

Some components are digital, such as the data dashboard, the SMS opt-in and the evaluation report. They support the physical operations and are not the primary solution, because the brief rules out an app-first approach. The plan clearly involves physical locations, materials, travel, installation and in-person work, so it is classified as physical.

Physical Locations

This plan implies one or more physical locations.

Requirements for physical locations

• Mid-sized non-capital EU city, population 150k–400k
• Existing municipal assets: libraries, community centers, churches, sports halls, malls suitable for cooling centers
• Social housing stock and top-floor flats to prioritize for home interventions
• Access to public health department, hospitals, EMS, primary care for coordination
• Accessible transport infrastructure and taxi/paratransit operator capacity
• Pharmacy and GP networks for enrollment and outreach partnerships
• Outdoor municipal work sites for worker-protection deployment
• Homeless services and NGO networks for street contact and unhoused support
• Radio, postal and community distribution channels for offline residents
• Administrative capacity for GDPR-compliant data handling and procurement

Location 1

Spain

Valencian Community, city of Castellón de la Plana

Castellón de la Plana (population ~170k), eastern Spain, Mediterranean coast

Rationale: Mid-sized non-capital city with high summer heat and humid nights, large elderly population (65+ ~20%), significant social housing in blocks prone to poor insulation, existing municipal sports halls and community centers. Mediterranean climate increases heat-night mortality risk, matching the program's focus. Strong municipal administration and existing NGO networks for homeless services and migrants (sub-Saharan and North African communities). Proximity to Valencia provides university partnership for evaluation and procurement expertise.

Location 2

Poland

Greater Poland region, city of Poznań

Poznań (population ~535k, but pilot districts ~200k population), west-central Poland

Rationale: Non-capital mid-sized city with increasing summer heat events and poor-insulation Soviet-era housing blocks. Large elderly population concentrated in social housing. Strong municipal health department and existing pharmacy and GP networks for enrollment. Established homeless-service NGOs and migrant communities (Ukrainian, Vietnamese) needing language access. City's administrative capacity and procurement experience supports rapid contracting before Month 2 (2026-12-08) gate. Positioning Poznań as a Central European pilot attracts EU scaling interest.

Location 3

Italy

Emilia-Romagna region, city of Modena

Modena (population ~185k), northern Italy, Po River valley

Rationale: Non-capital mid-sized city with extreme summer heat and hot nights, large aging population (65+ ~23%), significant elderly living alone. Dense historic center and peripheral social housing offer clear cooling-center site options (libraries, parish halls, municipal sports facilities). Strong municipal health and social services with established GP and pharmacy networks. Existing volunteer infrastructure and migrant communities (Eastern European, North African) with NGO support. River-valley geography poses heat-island risk, making program visible locally and relevant to regional scaling across the Po valley.

Location Summary

The plan requires a specific mid-sized non-capital EU city (population 150k–400k) with Mediterranean or continental summer heat, poor-insulation housing stock, substantial elderly and vulnerable populations, and established municipal assets (libraries, community centers, sports halls). Castellón de la Plana (Spain), Poznań (Poland), and Modena (Italy) are proposed as plausible pilot sites, each offering the combination of heat risk, social vulnerability, existing municipal and NGO infrastructure, and administrative capacity needed to meet the Month 2 (2026-12-08) readiness gate and Month 4 (2027-02-08) scale gate. The choice of city is critical: it determines the cooling-center network footprint, transport demand, outreach partnership routes, language access requirements, and the generalizability of the playbook to other EU cities in similar climates and housing contexts.

Currency Strategy

This plan involves money.

Currencies

• EUR: Primary currency for budgeting and reporting. The project is a €3.5M, 12-month municipal program in EU cities (Spain, Poland, or Italy), with staged funding (€2.0M initial + €1.5M at Month 4 = 2027-02-08 if gates are met). Cooling centers, transport contracts, home kits, staff and procurement are all cost items in euros.

Primary currency: EUR

Currency strategy: All transactions will use EUR for budgeting, procurement, contracts and reporting. The project is confined to a single EU city within the Eurozone or EU member states, so no foreign exchange risk management is required. All vendor contracts (cooling centers, transport operators, kit suppliers, handyperson services), payroll and grant disbursements will be conducted in EUR.

Identify Risks

Risk 1 - Regulatory & Permitting

GDPR compliance uncertainty despite intermediary-held lists strategy. Data-processing agreements with housing associations, social services, NGOs and pharmacies require legal review and may face delays if partners lack established data-governance frameworks. Regulatory interpretation of lawful basis for contact (consent vs. public task) varies across EU jurisdictions and may differ between Spain, Poland and Italy.

Impact: Legal challenge to enrollment or outreach methods could delay partner sign-off by 2–4 weeks. Withdrawal of a key partner (e.g., housing association) due to perceived GDPR risk could reduce enrollment reach by 15–25%. Estimated legal review and remediation cost: €15,000–30,000.

Likelihood: Medium

Severity: Medium

Action: Engage a specialist GDPR legal firm by Month 1 (2026-11-08) to pre-review data-processing agreements with housing associations, social services and NGOs. Draft template MOUs with clear lawful basis (public task, data controller/processor split) and retention limits. Obtain written legal clearance for the intermediary-held list model and consent protocols before Month 2 (2026-12-08) readiness gate. Build a 2-week legal-review buffer into the procurement timeline.

Risk 2 - Operational

Month 2 (2026-12-08) readiness gate (cooling centers contracted + staffed; transport contract signed; phone line operational; outreach training completed; procurement orders placed) compresses multiple parallel work streams into 8 weeks during the cool season, leaving no time for mock heat events or drill feedback loops before the gate.

Impact: Staff and volunteers may not be operationally ready on alert day despite formal training. Cooling-center opening-day incidents (accessibility failures, staffing gaps, poor signage) could harm public trust and damage credibility with partners. Estimated delay to full operational readiness: 2–3 weeks into the summer season. Reputational damage if media covers a preventable operational failure.

Likelihood: High

Severity: Medium

Action: Front-load cooling-center contracting and handover by end of Month 1 (2026-11-08) to allow 3–4 weeks of operational rehearsal (staffing placement, accessibility checks, security drills, signage installation) before the Month 2 (2026-12-08) gate. Conduct one full-system mock alert drill in March (Month 5 = 2027-03-08) with all centers, transport, phone line and outreach staff operating simultaneously. Use drill results to close gaps before June (Month 8 = 2027-06-08) summer season. Document drill findings and corrective actions formally to satisfy the Month 4 (2027-02-08) gate requirement.

Risk 3 - Financial

€1.5M second-tranche release at Month 4 (2027-02-08) is contingent on meeting three operational gates (80% center hours, 60% outreach success, <45 minutes transport time) measured during early-season heat days. If June and July temperatures are below historical norms or fall outside alert thresholds, gates cannot be tested fairly, and the scale release may be withheld despite operational readiness.

Impact: Without summer heat events by Month 4 (2027-02-08), gates cannot be validated, and €1.5M release may be delayed to Month 5–6 (2027-03-08 to 2027-04-08) or denied if metrics are unverifiable. Budget burn for May–July operations (center staffing, transport standby, outreach phone line) will exceed initial €2.0M if gates are not released on schedule. Estimated shortfall: €200,000–400,000 in operational costs.

Likelihood: Medium

Severity: High

Action: Redefine the Month 4 (2027-02-08) gate to include formal drills and simulated alert-day scenarios as acceptable evidence, not solely real heat events. Pre-specify a 'drill protocol' by Month 3 (2027-01-08) that mirrors alert-day operations (centers open, transport mobilized, outreach phone line active for 4–6 hours) and allows gates to be tested without waiting for weather. Document drill results and staffing performance metrics to support the Month 4 (2027-02-08) release decision. Include a contingency budget reserve (€150,000–200,000) to cover May–July operational costs if natural heat events are delayed.

Risk 4 - Operational

Volunteer driver recruitment and vetting (safeguarding, insurance, background checks) may fall short of target numbers by Month 2 (2026-12-08) if volunteer response is low or vetting takes longer than 6 weeks. Taxi backup contract alone will be inadequate if volunteer gaps exist, and standby retainers may exhaust budget allocated for home kits.

Impact: Fewer than planned volunteer drivers could increase average time-to-transport above the 45-minute gate target by 10–15 minutes, causing gate failure. Shift to taxi-only operation would increase transport costs by €150,000–250,000, forcing cuts to home-kit distribution (500–1000 fewer kits installed). Estimated delay in volunteer placement: 3–6 weeks.

Likelihood: Medium

Severity: Medium

Action: Launch volunteer recruitment immediately at Month 0 (2026-10-08), targeting retirees, charity staff and faith-group members through NGO and community networks in parallel with HR/staffing advertising. Conduct vetting in batches (fortnightly cohorts) rather than all at once, so early cohorts are trained and road-tested by Month 1 (2026-11-08). Establish a taxi-retainer contract by Month 1 (2026-11-08) with a lower threshold guarantee than initially planned, allowing gradual scale-up of volunteer numbers. Set a trigger threshold: if volunteer numbers fall below 50% of target by Month 1.5 (2026-11-23), increase taxi retainer proportionally rather than waiting until after the Month 2 (2026-12-08) gate.

Risk 5 - Supply Chain

Procurement of cooling kits (exterior shading, reflective blinds, window fans, thermometers, hygrometers) by Month 2 (2026-12-08) depends on supplier availability and delivery lead times. If primary suppliers are unavailable or backlogs exceed 4–6 weeks, orders placed in October–November may not arrive until February–March, delaying home-intervention rollout past the summer season.

Impact: If kits do not arrive until March, they cannot be installed before the first heat event in May–June. Target of priority top-floor and social-housing installations will slip to July–August at earliest, missing the peak-risk early summer period. Estimated delay: 4–8 weeks. Cost impact: if alternative suppliers charge premiums for expedited shipping, additional cost of €50,000–100,000.

Likelihood: Medium

Severity: High

Action: Issue procurement specifications by end of Month 0 (October 2026) to identify supplier availability and lead times. Place first call-off orders for 30–40% of total kit volume by mid-Month 1 (November 2026) to secure early stock. Negotiate expedited delivery for February arrival, accepting a 10–15% price premium. Arrange interim storage at municipal facility or a supply partner's warehouse. Keep a small stock of pre-positioned kits (shading and fans) by February to enable immediate deployment if a heat event occurs in March. Identify backup suppliers for each kit component to mitigate single-source delay.

Risk 6 - Operational & Safety

Door-knock and street-contact outreach teams will encounter residents in heat distress or acute illness during alert days. Teams lack clinical training and may misjudge escalation severity, leading to delayed EMS calls or inappropriate advice. Safety protocols for staff encountering aggressive or vulnerable residents are not yet defined.

Impact: Outreach staff may fail to recognize heat stroke or severe dehydration and delay critical EMS calls by 10–30 minutes. Alternatively, over-escalation could saturate EMS with borderline cases. Staff encountering hostile or distressed residents without clear de-escalation guidance risk injury or psychological harm. Potential litigation if a resident suffers preventable harm after staff contact.

Likelihood: Medium

Severity: High

Action: Partner with a municipal nurse adviser or occupational health service to co-design escalation protocols for outreach staff. Include a checklist for recognizing heat illness signs (confusion, loss of consciousness, core temperature >40°C indicators, severe weakness) and decision trees for when to call EMS, advise home management or refer to 111-style phone triage. Train all outreach and street-contact staff on the protocol before Month 2 (2026-12-08) gate, with refresher drills in May. Provide safety communication cards and a check-in system so teams can report incidents and receive same-day debriefing if they encounter acute cases. Establish peer support for staff exposed to distressing scenes.

Risk 7 - Operational

Intermediary partners (housing associations, social services, NGOs, pharmacies) will independently conduct phone outreach and enrollment on the city's behalf. Quality and consistency of outreach contact will vary; some partners may lack call-center capacity or training, leading to missed calls, poor enrollment retention or residents disengaging after the first contact.

Impact: Outreach contact success rate (targeting 60% for enrolled residents) may fall to 40–50% if partner call capacity is insufficient or if scripts are delivered inconsistently. Partner fatigue or turnover mid-season could drop success rate to 20–30% by July–August, failing the Month 4 (2027-02-08) gate. Estimated loss: 500–1000 contact attempts per alert day across all partners.

Likelihood: Medium

Severity: Medium

Action: Co-design a detailed outreach protocol and script with each key partner (housing associations, social services, NGOs, pharmacies) during Month 0–1 (2026-10-08 to 2026-11-08). Include call targets per alert day, escalation rules and sample language. Conduct joint training for all partner staff by end of Month 1 (2026-11-08), with role-play drills using realistic scenarios. Establish a shared call-tracking dashboard (via secure spreadsheet or partner-hosted system, not city-owned) where partners log calls, outcomes and escalations daily, reviewed by the city coordinator. Monitor partner call volumes and contact success weekly; provide real-time feedback and script adjustments if success drops below 60%. Schedule mid-season partner review at Month 6 (2027-04-08) to identify and resolve gaps before gate measurement at Month 4 (2027-02-08).

Risk 8 - Technical & Integration

The phone line (heat helpline) and transport-dispatch system will need to integrate with partner call-tracking and cooling-center occupancy data to avoid double-booking and ensure residents reach appropriate sites. If systems are not integrated (phone line is city-run, transport-dispatch is contracted, center capacity is reported manually), coordination failures will occur under peak alert-day demand.

Impact: Residents calling the heat line for transport may be unable to confirm center availability and wait times, leading to wasted trips or overcrowding at one site while others are empty. Transport dispatch and center staffing may not coordinate, causing residents to arrive at full sites. Estimated operational chaos: 10–20% of transport requests may be misdirected or cancelled. Reputational damage if media covers residents being turned away from overcrowded centers.

Likelihood: Medium

Severity: Medium

Action: Define a simple data-integration protocol by Month 1 (2026-11-08): phone-line staff log transport requests and center of choice in a shared spreadsheet (or low-cost ticketing system) updated in real-time, transport dispatch accesses the same feed to prioritize routing, and each center reports current occupancy and capacity every 15 minutes via phone or WhatsApp to the dispatch hub. Establish a 'duty coordinator' role who monitors the shared system during alert days and authorizes dispatch redirects if a site reaches capacity. Run this protocol in the March mock-alert drill to identify bottlenecks and fix them before June. Keep the system deliberately simple (spreadsheet-based, not a custom app) to ensure rapid setup by Month 2 (2026-12-08) and resilience if cloud systems fail.

Risk 9 - Operational

Cooling centers must meet accessibility standards (wheelchair access, quiet rooms, water, toilets) across multiple sites (libraries, parish halls, community centers, sports halls). Existing facilities may have accessibility gaps; remediation takes time and cost, and some sites may be unsuitable. If accessibility is not validated before opening, residents in wheelchairs or with sensory needs will be excluded.

Impact: Wheelchair-using or mobility-limited residents unable to access some sites will over-concentrate at the few fully accessible centers, breaching capacity and transport targets. Estimated exclusion: 5–10% of targeted mobility-limited residents. Potential disability-access complaint or lawsuit. Public criticism for excluding the most vulnerable. Estimated remediation cost: €20,000–40,000 per site (ramps, accessible toilets, signage). Delay: 2–4 weeks per site if structural work is required.

Likelihood: Medium

Severity: Medium

Action: Conduct an accessibility audit of all proposed cooling-center sites by end of Month 1 (2026-11-08), assessing wheelchair access, toilet facilities, water points, quiet/low-stimulus rooms, parking and signage. Categorize sites as 'fully accessible', 'minor modifications needed' and 'unsuitable'. Prioritize fully accessible sites for opening in May; defer sites requiring remediation to July or drop them if remediation exceeds €10,000 or takes >4 weeks. Ensure at least 50% of planned center capacity is in fully accessible sites. Publish accessibility info (accessible routes, toilet locations, quiet room availability) for each site in a simple leaflet and on the municipal website so residents can choose sites that meet their needs.

Risk 10 - Reputational & Social

Public communications campaign must counter misinformation about heat response (e.g., use of alcohol, incorrect fan use in extreme heat, distrust of cooling centers). If misinformation spreads unchecked, residents may adopt dangerous coping strategies and avoid the program. Poor messaging in multilingual communities could be misinterpreted or ignored.

Impact: Residents following unsafe advice (drinking alcohol, using fans during extreme heat without airflow) could experience preventable heat illness. Uptake of cooling centers and enrollment in the registry could drop by 10–20% if residents distrust the message or believe unsafe alternatives. Estimated reach loss: 1000–2000 residents in a city of 170k–200k. Media or social-media backlash if a preventable death occurs after resident ignored the program's guidance.

Likelihood: Medium

Severity: High

Action: Develop a pre-season communications strategy by Month 1 (2026-11-08) that includes positive messaging (cooling centers as safe, welcoming spaces), explicit myth-busting (alcohol does not help; fans can worsen extreme heat if airflow is stagnant) and trusted messengers (pharmacists, GPs, caretakers, faith leaders with pre-approved scripts). Test key messages with focus groups of older residents and recent migrants (Month 1 = 2026-11-08) to ensure clarity and uptake. Deploy messaging via radio (most common channel for 65+), pharmacy posters, door hangers and SMS (opt-in) in the city's main spoken languages plus visual guides (pictograms). Assign a communications officer to monitor social media and local forums during alert days and respond to misinformation within 2–4 hours with corrected facts and credible sources.

Risk 11 - Operational

The plan relies on municipal and contracted staff deployed across multiple sites and alert days with limited advance notice (heat forecasts are typically issued 3–5 days before an event). Staffing for centers, transport dispatch, phone line and street teams will face fatigue and absences during multi-day heat waves, especially if staff are not full-time or do not have standby reserves.

Impact: During a 5–7 day heat wave (Month 7–8 = 2027-05-08 to 2027-06-08), cooling centers may operate at reduced hours due to staff absences (sickness, fatigue, childcare conflicts). Transport dispatch may slow if dispatcher is overwhelmed or absent. Outreach phone line may have long wait times (>10 minutes) for vulnerable residents. Estimated service degradation: 10–25% reduction in center hours, 15–30 minute delays in transport dispatch, partial closure of phone line during peak hours.

Likelihood: High

Severity: Medium

Action: Hire or contract for 20–30% staffing reserve capacity (additional part-time center staff, backup dispatcher, on-call phone operators) to cover absences and multi-day surges. Cross-train staff across roles (e.g., center managers can back up phone dispatch) to allow flexible redeployment. Establish a rota system that limits consecutive alert-day shifts to 3–4 days per person and mandates 1–2 days rest between multi-day events. For transport dispatch, contract two dispatchers and a backup coordinator, not one. For the phone line, use a mix of municipal staff and a partnered call-center service (e.g., municipal health line) that can surge capacity during alerts. Conduct fatigue-management training with managers by Month 3 (2027-01-08), including recognition of burnout and peer-support protocols.

Risk 12 - Financial

The €3.5M budget is staged as €2.0M initial and €1.5M at Month 4 (2027-02-08), with no contingency buffer explicitly identified. Costs may overrun in procurement (supplier price increases), staffing (market wages higher than estimated), or transport (taxi retainer rates increase as summer demand peaks). Without contingency, overspends in one area force cuts to others.

Impact: If procurement or staffing costs overrun by 10–15%, the initial €2.0M will be exhausted before Month 3 (2027-01-08), forcing delays in hiring, kit distribution or center operations. If transport costs exceed budget by €100,000–200,000 (e.g., taxi rates spike in July), home-kit installations or outreach phone line will be defunded. Estimated budget shortfall under 15% overrun: €200,000–300,000.

Likelihood: Medium

Severity: High

Action: Reserve 8–10% of each phase as contingency (€160,000 from initial €2.0M, €120,000 from second tranche €1.5M, total €280,000). Pre-benchmark costs for kits, transport, staffing and procurement before Month 1 (2026-11-08) against market quotes to confirm budget adequacy. Track monthly spend against forecast and reforecast cash flow by Month 2 (2026-12-08) and Month 3.5 (2027-01-23) to identify overrun risks early. If overruns appear likely, prioritize: (1) maintaining center and transport operations for gates; (2) staffing for phone line and outreach; (3) home kits (can be partially deferred to Year 2 if needed). Negotiate fixed-price transport and kit-supply contracts (not cost-plus) by Month 1 (2026-11-08) to lock in rates and avoid summer spikes.

Risk 13 - Operational

Outreach to unhoused people (via street teams or NGO partners) involves contact with individuals in acute distress and creates duty-of-care ambiguities. Street teams may face hostility, and consent protocols for providing water, transport or cooling access to someone in acute heat illness who is not enrolled are undefined.

Impact: Street outreach staff may be assaulted or abused during alert-day contact; without clear safety protocols, psychological harm and staff turnover could result. Consent and safeguarding failures could lead to litigation (e.g., if an unhoused person is transported without clear consent or suffers harm in a cooling center). Estimated cost of staff incident response (counseling, leave, recruitment): €10,000–20,000.

Likelihood: Medium

Severity: High

Action: Co-design street-contact protocols with homeless-service NGOs and occupational health by Month 1 (2026-11-08). Define consent models for acute distress (e.g., assumed consent for water/shade if person is incoherent but alert enough to accept help), escalation rules for calling EMS, and clear off-duty procedures if staff are threatened. Provide all street-contact staff (city or NGO) with de-escalation and trauma-informed care training before Month 2 (2026-12-08). Pair each street team with a supervisor or co-worker, not solo outreach. Establish a rapid incident-reporting and staff-support system: any incident (assault, distressing scene) triggers same-day debriefing and access to occupational health. Ensure insurance and safeguarding liability are clarified in NGO partner agreements before work begins.

Risk 14 - Operational

The plan depends on reliable forecasts from the national meteorological service to trigger alert levels. If forecasts are uncertain, delayed or wrong, the city may fail to activate centers in time or over-activate on false alarms, wasting budget and eroding trust.

Impact: A late-issued forecast (24 hours before onset) could delay center opening by 6–12 hours, missing early-morning heat peaks. An incorrect forecast that predicts extreme heat that does not materialize could trigger unnecessary full activation, burning €5,000–10,000 in center-hours and staffing costs. Repeated false alarms could erode public trust and staff readiness. Estimated financial impact: €20,000–50,000 per incorrect trigger.

Likelihood: Low

Severity: Medium

Action: Establish a direct relationship with the national meteorological service (and local university weather station if available) by Month 1 (2026-11-08) to receive forecasts 5–7 days in advance and clarify confidence intervals. Define alert thresholds to include a 'marginal' advisory tier (for forecasts with lower confidence or borderline temperatures) that triggers phone check-ins and pre-positioned supplies only, not full center activation. Reserve full activation for forecasts with high confidence and clear threshold exceedance. Publish the alert forecast to partners and residents 24 hours in advance so centers can confirm staffing and residents can plan. Conduct post-event review of forecast accuracy and alert-trigger decisions monthly to refine thresholds and trust in the forecast.

Risk 15 - Integration & System

Health system coordination relies on daily aggregate counts of heat-related EMS calls and ED visits, but hospitals and EMS may lack standardized coding for 'heat-related' presentations or may not be able to produce daily counts without disrupting operations. If data is delayed, coded inconsistently or incomplete, the city cannot verify health impact or adjust operations mid-season.

Impact: Missing or late daily EMS/ED data could delay escalation decisions during a multi-day heat wave by 12–24 hours, reducing early intervention. Without reliable health data, the Month 4 (2027-02-08) gate evaluation of program impact will be unreliable, risking credibility of the scaling cost model. Estimated data-access delay: 2–4 weeks due to IT and reporting processes.

Likelihood: Medium

Severity: Medium

Action: Negotiate a data-sharing MOU with hospitals, EMS and primary care by end of Month 1 (2026-11-08), specifying (1) daily aggregate counts of ED visits and EMS calls coded as heat-related (to be agreed with clinical teams), (2) delivery of counts by 10 a.m. the next day via secure email or API, (3) a simple standardized form to ensure consistency. Conduct a 2-week data-validation pilot in April to test the reporting process and identify IT/coding gaps. Establish a fallback: if daily data cannot be produced, agree on weekly aggregate counts sufficient for trend analysis. Train hospital and EMS staff on the agreed coding and reporting process before May. Publish daily and weekly aggregate counts in a simple dashboard accessible to city operations staff (not the public, to protect privacy) so decisions can be made.

Risk 16 - Operational

The plan includes mandatory heat-protection clauses in municipal contracts (adjusted work schedules, breaks, water, shade). Enforcement requires site inspections and contractor compliance monitoring, which consume municipal public-works staff capacity. Private employers outside municipal contracts are only encouraged via guidance, not required; uptake and compliance are uncertain.

Impact: Without dedicated inspector capacity, contractor compliance with heat clauses will be spotty, and municipal outdoor workers may still suffer heat illness. Private employer adoption of heat guidance is likely to be <30% without regulatory incentive, leaving outdoor workers at private firms (construction, agriculture, delivery) at continued risk. Estimated reputational risk: if a municipal contractor or private-firm outdoor worker suffers preventable heat illness, media and unions will question the program's effectiveness.

Likelihood: Medium

Severity: Medium

Action: Designate one municipal public-works supervisor or contracted health-and-safety officer as heat-compliance monitor, with authority to conduct spot inspections of municipal and contracted outdoor work sites during alert days. Develop a simple heat-compliance checklist (schedule changes, water availability, shade areas, mandatory rest breaks, worker education) and conduct unannounced site visits to at least 50% of active contracts each summer. Document findings and issue corrective notices to contractors within 48 hours of non-compliance. For private employers, publish a heat-protection guidance pack (English and main languages in the city) by Month 1 (2026-11-08) and promote it via chambers of commerce, employer associations and local media. Offer free consultation to employers on heat-protection plans. Tie any municipal incentives (e.g., procurement bonus points) to certified heat-protection training for private firms, incentivizing voluntary adoption.

Risk 17 - Integration & Stakeholder

The plan requires partnerships with housing associations, social services, NGOs, pharmacies and faith organizations to conduct outreach and refer residents. If partner engagement is weak, partners lack capacity or priorities change mid-season, enrollment and contact rates will collapse.

Impact: Loss of a key partner (e.g., largest housing association serving 1000+ residents) could reduce outreach reach by 10–20%. If social services deprioritize heat outreach during a busy month, contact attempts could drop from planned 5000/month to 3000/month, failing the 60% contact-success gate. Estimated reach loss: 500–1000 residents per alert period.

Likelihood: Medium

Severity: Medium

Action: Sign formal partnership MOUs with housing associations, social services, NGOs and pharmacy chains by end of Month 1 (2026-11-08), including outreach commitments, data-sharing terms, liability and escalation contacts. Conduct joint quarterly planning meetings (Month 1, 4, 7, 10 = 2026-11-08, 2027-02-08, 2027-05-08, 2027-08-08) to review capacity, adjust targets and resolve conflicts. Establish a dedicated partner liaison officer (city-side) who maintains monthly contact, monitors capacity and escalates issues early. Provide partners with training, scripts and real-time feedback on performance (call counts, contact success) to maintain engagement. Build contingency: if a key partner drops out mid-season, identify a backup partner (second social service, NGO coalition) by Month 2 (2026-12-08) and brief them as standby.

Risk 18 - Operational

The plan aims for average transport time-to-pickup of <45 minutes during alert days. This depends on volunteer driver availability, taxi retainer response times, and geographic distribution of residents needing transport. During peak demand (early morning of a heat day), dispatcher may be overwhelmed and wait times could exceed 45 minutes.

Impact: If average transport time climbs to 50–60 minutes, the Month 4 (2027-02-08) gate (<45 minutes) will be failed, triggering a scale-back in funding and credibility. Residents waiting >1 hour for transport may decide not to travel to a cooling center, reducing utilization. Estimated impact on gate failure: 10–15% increase in wait times if dispatch is not well-coordinated.

Likelihood: Medium

Severity: Medium

Action: Hire or contract two dispatchers and one backup coordinator for the transport system (not one) to handle simultaneous requests during peak alert-day demand. Pre-position volunteer drivers and a taxi retainer fleet by 7 a.m. on each forecast alert day, so resources are standing by and not deployed elsewhere. Set dispatch software or spreadsheet to prioritize elderly and mobility-limited residents (shortest acceptable wait time 30 minutes), then others (target 45 minutes). Conduct a 'transport stress test' in May using a simulated alert scenario (5–10 transport requests in 2 hours) to measure actual dispatch performance and identify bottlenecks. If stress test shows average times >45 minutes, increase taxi retainer capacity or recruit additional volunteer drivers before June. Track average transport time daily during summer alerts and report to the city coordinator.

Risk 19 - Operational

Multilingual outreach and communications must reach recent migrants and residents with limited local-language skills, but translation and interpretation services are expensive and time-consuming. If communications are offered only in the city's main language(s) and English, significant populations may be excluded.

Impact: Recent migrants from non-European language groups (sub-Saharan, North African, Eastern European, Vietnamese, etc., depending on city demographics) may miss alerts or enrollment information, reducing reach by 10–20% in neighborhoods with high migrant density. Estimated reach loss: 500–1500 residents per city, depending on migrant population proportion. Reduced uptake could fail outreach-contact-success gates if migrant communities are under-counted.

Likelihood: Medium

Severity: Medium

Action: Identify the city's top 4–6 spoken languages by recent migrants (via municipal integration data, census or NGO networks) by Month 0 (2026-10-08). Procure interpretation services for the phone line (remote interpreter on standby during alert days) and translation of key materials (alert flyers, enrollment scripts, cooling-center welcome guides) by Month 1 (2026-11-08). Partner with migrant community associations to recruit community language ambassadors (paid part-time roles, 10–15 hours/week during summer) to deliver messages, accompany door-knocks and staff cooling-center welcome desks in their own languages. Test translated materials with focus groups of native speakers (Month 1 = 2026-11-08) to ensure accuracy and cultural appropriateness. Deploy translated door hangers, flyers and SMS in selected neighborhoods with high migrant density. Budget: €15,000–25,000 for translation, interpretation and ambassador stipends.

Risk 20 - Reputational & Social

A resident or visitor to a cooling center could suffer a preventable health event (heat stroke, cardiac event, fall) if the center is not staffed with first-aid capacity and there is no clear escalation to medical care. If such an incident occurs and media coverage ensues, the program could be blamed for inadequate safeguarding despite best efforts.

Impact: A serious incident at a cooling center could lead to litigation, regulatory complaint and loss of public trust. Even if the program is not legally liable, reputational damage could reduce center uptake by 10–20% and invite political scrutiny of the program's continuation. Estimated legal and reputation cost: €50,000–100,000.

Likelihood: Low

Severity: High

Action: Ensure every cooling center is staffed by at least one person with first-aid certification (refreshed annually) and a defibrillator (AED) on-site with staff trained in its use. Establish rapid escalation to 112 (emergency services) with pre-positioned phone line and clear incident-reporting protocols. Conduct center managers in basic heat-illness recognition and first-response (cold water, rest, elevation) by Month 2 (2026-12-08). Run quarterly first-aid refresher drills at each center (April, June, September) to keep skills sharp. Draft incident-response and incident-reporting templates so that any event is documented, reviewed by the city health officer and escalated if needed. Ensure liability insurance covers center operations and staff are aware of coverage limits. Communicate center first-aid and emergency procedures clearly to residents on entry (signage, staff introduction) to set expectations.

Risk 21 - Operational

The plan includes home installation of fans and shading by a handyperson service, which requires safety checks to ensure fans are used safely (directional airflow in extreme heat, not recirculating hot air) and shading installation does not create fire hazards or building-code violations. If safety checks are skipped or insufficient, residents could misuse fans and suffer harm, or insurance and liability issues could arise.

Impact: Resident misuse of installed fans (e.g., closed-room recirculation during extreme heat) could worsen heat illness rather than help, and if linked to a preventable death or hospital admission, litigation could follow. Installation of external shading that violates building codes or historic-preservation rules could trigger enforcement action and removal, undermining resident confidence. Estimated remediation or legal cost: €10,000–30,000.

Likelihood: Low

Severity: Medium

Action: Require all home-installation work (fans, shading) to be carried out by certified handypersons or contractors (not volunteers) who have completed a 2-hour heat-safety and installation-safety training by Month 2 (2026-12-08). Training must cover (1) proper fan use (directional airflow, outdoor-air intake, not closed-room recirculation), (2) safe installation on exterior surfaces (wind resistance, fire safety), (3) checking building-code compliance before work, (4) simple written guidance left with the resident on safe fan use and water intake. Conduct spot inspections of 10–20% of installations (selected randomly and by risk level) by a municipal building inspector or external quality auditor to verify workmanship and code compliance. Document inspection findings and any remediation work. Provide all residents receiving installations with written guidance (translated) on safe use; include troubleshooting and links to advice.

Risk 22 - Operational

The plan declares cooling centers and support services during heat alerts, then requires rapid stand-down when the alert ends. Staff, volunteers and partners may remain in alert mode longer than needed (treating borderline cases as emergencies, over-utilizing services), inflating costs and prolonging fatigue. Conversely, premature stand-down could leave residents vulnerable if heat returns within days.

Impact: Prolonged over-alert activation could increase operational costs by 15–25% (€75,000–125,000 over the summer if 2–3 alerts occur). Premature stand-down followed by rapid heat return could cause service gaps and trust erosion. Inconsistent stand-down decisions across partners could leave some services active and others closed, confusing residents.

Likelihood: Low

Severity: Low

Action: Define clear stand-down criteria in the alert protocol: cooling centers, transport dispatch and outreach phone line stand down when the forecast no longer meets alert thresholds and temperatures have been normal for 48 hours. Assign the city incident commander authority to issue stand-down orders and communicate them to all partners and the public within 2 hours. Include stand-down procedures in the Month 2 (2026-12-08) readiness gate training and drill (how staff clock out, centers close cleanly, volunteers are released). Check forecasts daily during summer and issue updates to partners each morning so everyone knows the current status. Conduct a mock stand-down drill in May to practice the process.

Risk 23 - Financial & Governance

The plan is a 12-month pilot with a requirement to produce a 'repeatable playbook and scaling cost model for other EU cities' by Month 12 (2027-10-08) (end of 2027). Documenting, costing and refining the model requires staff time and data analysis that may not be budgeted separately, and the playbook's transferability to very different EU cities (e.g., Baltic countries vs. Southern Europe) is uncertain.

Impact: If playbook documentation is not funded explicitly, it will be rushed or incomplete, limiting its value to other cities. Playbook reuse by cities with different housing stock, climates, demographics and legal frameworks may require substantial local adaptation, reducing the apparent transferability and cost model's credibility. Estimated effort: 300–500 staff-hours for playbook drafting, cost modeling and validation. If not budgeted: incomplete or late delivery.

Likelihood: Medium

Severity: Low

Action: Assign a dedicated playbook and evaluation officer (0.5 FTE for Months 9–12 = 2027-07-08 to 2027-10-08, or 1 FTE for Month 12 = 2027-10-08 post-season) within the budget to lead documentation work. Begin playbook drafting in Month 8 (2027-06-08) (not after the season ends) so lessons are captured while fresh. Include sections on: (1) decision rationale and trade-offs for each element (cooling centers, transport, outreach, etc.); (2) SOPs and checklists for each role; (3) budget breakdown by cost type and scaling assumptions; (4) city-specific adaptations (housing stock, climate, demographics); (5) replication checklist for other EU cities. Conduct playbook testing with a peer city (Month 11 = 2027-09-08) to identify gaps and refine guidance. Publish a draft playbook by Month 11 (2027-09-08) and final version by Month 12 (2027-10-08). Cost model must include both unit costs (€/person enrolled, €/center-hour, €/transport trip) and assumptions about how these scale to city size and climate.

Risk 24 - Operational

The plan's success hinges on achieving 80% of planned cooling-center hours, 60% outreach contact success and <45-minute transport time at the Month 4 (2027-02-08) gate. If any gate fails, €1.5M scale funding may not be released, forcing mid-season contraction. However, the gate measurement period (early summer, June–July) may not include sufficient heat events to test performance fairly.

Impact: If June–July are cooler than normal and no alert thresholds are crossed, gates cannot be measured against real heat events. Drill-based gate evidence may be weak if performed in cool conditions and not replicated during actual alerts. Scale funding delay could force closure of some centers or transport capacity by August, harming residents during the peak-risk period. Estimated impact: 2–4 week delay in scale funding release or non-release if gates are deemed unmeasurable.

Likelihood: Medium

Severity: Medium

Action: Revise gate criteria to allow measurement via formal drills and simulated alert scenarios if real heat events are insufficient. Pre-specify a 'drill protocol' by Month 3 (2027-01-08) that mirrors alert-day operations (all centers open, transport mobilized, phone line active for 4–6 hours) and is conducted in April or May (before the Month 4 = 2027-02-08 gate). Measure drill-based performance (center hours delivered, transport response time, outreach phone line wait time) and staff observations. Document drill results and use them to validate the Month 4 (2027-02-08) gates alongside any early real-event data. Include contingency decision: if insufficient heat events or drill results are available by Month 4 (2027-02-08), release 50% of the €1.5M to sustain operations through summer and defer full-release decision to Month 5 (2027-03-08) (based on June data).

Risk 25 - Strategic & Organizational

The plan requires a mayor's-office incident commander (or delegated authority) to declare alerts and coordinate cross-department action. If the mayor's office is distracted by other crises or transitions (staff turnover, election cycles), incident command may weaken or become politicized, leading to delayed or inconsistent alert decisions.

Impact: Delayed alert declarations could cost 12–24 hours of response time during a critical heat event. Politicized alerts (declaring or withholding based on political optics rather than forecasts) could erode scientific credibility and partner trust. Staff turnover in the mayor's office could orphan the heat program mid-summer if the new administration deprioritizes it. Estimated impact: 2–4 week operational disruption or alert-declaration delay.

Likelihood: Low

Severity: Medium

Action: Establish a written delegation of authority for heat-alert declaration, signed by the mayor and filed with the municipal legal department, specifying (1) the trigger criteria (forecast thresholds), (2) who can declare (incident commander, deputy, backup), (3) escalation chain if the primary commander is unavailable, (4) that alert declarations are evidence-based and not subject to political review. Ensure the deputy incident commander (from public health) has clear authority to declare if the mayor's office is unavailable. Conduct cross-training so the health department, civil protection and city council each understand the alert protocol independently. Include heat-program continuity in the mayor's transition briefing if elections or staff changes occur. Protect the heat-program officer role (1 FTE) from year-to-year budget cuts by framing it as ongoing business continuity, not a temporary project.

Risk summary

This 12-month municipal heatwave mortality-reduction program faces moderate-to-high operational, financial and reputational risks concentrated in the Month 2 (2026-12-08) and Month 4 (2027-02-08) readiness and scale gates. The three most critical risks are: (1) Supply-chain and procurement delays for cooling kits and transport contracts—if these do not arrive by February, the program cannot deploy home interventions or guarantee transport capacity in time for the first summer heat events, jeopardizing both the Month 2 (2026-12-08) and Month 4 (2027-02-08) gates and forcing budget reallocation. (2) Gate validation during cool season—the Month 4 (2027-02-08) gates (80% center hours, 60% outreach success, <45-minute transport) depend on real heat events or drills occurring by June; if June–July are cool, gates cannot be fairly measured, risking non-release of €1.5M scale funding and mid-summer operational collapse. (3) Staffing and volunteer availability—if street-contact, cooling-center and transport-dispatch teams are under-staffed or under-trained by June, they will fail to meet gates and leave residents at risk during peak summer heat. Mitigation priorities: (a) front-load procurement and contracting by end of Month 1 (2026-11-08) with contingency suppliers and price locks; (b) redefine gates to allow drill-based evidence alongside real events and include a contingency funding model if gates are delayed; (c) launch volunteer recruitment immediately and conduct staffing stress tests by May. Secondary risks include GDPR compliance uncertainty, partner capacity and engagement, technology integration failures, and reputational damage from operational failures or misinformation. The plan is viable if these gate and staffing risks are actively managed from Month 0 (2026-10-08) onward, with clear decision points at Months 1, 2, 3.5 and 4 (2026-11-08, 2026-12-08, 2027-01-23, 2027-02-08).

Make Assumptions

Question 1 - Which specific EU city (Castellón de la Plana, Poznań, or Modena) will serve as the pilot site, and what is the confirmed baseline heat-mortality or heat-related EMS-call rate for that city from the past three summers?

Assumptions: Assumption: Castellón de la Plana (Spain, ~170k population) is selected as the pilot, given Mediterranean climate, large elderly population (65+ ~20%) and existing municipal assets. Baseline heat-related EMS calls estimated at 80–120 calls per summer season (May–September), based on typical mid-sized Spanish coastal city profiles. Heat-attributable excess mortality estimated at 15–25 deaths per summer using temperature-mortality regression methods. These figures are provisional pending access to municipal EMS records and health department mortality data; local calibration is needed to confirm triggers and program targets.

Assessments: Title: Baseline Data Availability and Accuracy Assessment Description: Establishes the quantifiable baseline against which program impact will be measured, and confirms whether historical heat-mortality and heat-related EMS data are available and reliable for gate evaluation and attribution analysis. Details: Baseline data quality is critical for the Month 4 (2027-02-08) scale gate and for credibly evaluating harm reduction by Month 12 (2027-10-08). If EMS records lack consistent 'heat-related' coding, attribution will be weak and gates unmeasurable. Risks: (a) three-year historical data may not exist if the city has not previously tracked heat-related calls systematically, forcing baseline estimation from proxy data (ambient temperature + all-cause EMS); (b) coding inconsistency across EMS providers or summers could introduce 10–30% noise into baseline estimates; (c) mortality data requires manual chart review or cause-of-death coding that may take 4–8 weeks to obtain. Mitigation: request EMS and mortality data by Month 0 (2026-10-08); conduct rapid data-quality audit by Month 1 (2026-11-08); agree with health partners on heat-attribution coding before Month 2 (2026-12-08) readiness gate so drill and real-event data can be compared consistently. Opportunity: strong baseline enables robust attribution and strengthens playbook credibility for scaling to other cities.

Question 2 - How will the mayor's office–deputy public-health incident-command structure handle authority delegation during multi-day heat waves, rapid staff turnover or political transitions, and what written protocols will define alert-declaration criteria and escalation chains?

Assumptions: Assumption: A written delegation of authority will be signed by the mayor by Month 1 (2026-11-08), clearly stating trigger thresholds (e.g., forecast daytime high ≥35°C and night-time low ≥22°C for three consecutive days), who declares alerts (mayor or named deputy), and backup authority if the primary commander is unavailable (e.g., public health director auto-authorizes if mayor is unreachable). Delegation will be filed with municipal legal department and briefed to city council. Cross-training will ensure health, civil protection and public-works departments can operate independently of mayoral day-to-day involvement. Authority is presumed non-delegable to political advisors; only municipal officers have trigger authority.

Assessments: Title: Governance and Incident-Command Authority Clarity Assessment Description: Evaluates whether alert-declaration authority is clear, insulated from politicization, and robust against staff transitions or organizational disruptions. Details: Ambiguous authority or political oversight of alert declarations carries severe reputational risk: delayed alerts cost response time; politicized alerts (withholding alerts for political optics) undermine scientific credibility and invite media scrutiny if a preventable death occurs. Benefits of written delegation: unambiguous trigger criteria reduce decision delay to <1 hour and insulate the program from political optics. Risks: (a) mayor's office may resist formal constraint of authority; (b) if delegation is unsigned or vague, the city may face legal challenge if decisions are questioned; (c) staff turnover (e.g., new mayor after elections) may orphan the program unless the delegation is embedded in city ordinance or charter, not just a memo. Mitigation: embed delegation in municipal ordinance if possible (higher authority, survives staff change); brief all relevant departments jointly so everyone understands the protocol independently; frame delegation as routine emergency-management practice, not a constraint on mayoral authority. Opportunity: clear authority speeds decisions by hours during critical alerts and demonstrates professional governance to EU peer cities and auditors.

Question 3 - What is the composition (percentage urban/rural, socioeconomic deprivation, language distribution, proportion 65+, lone-dweller households, top-floor units) of the pilot city's population, and which neighborhoods have the highest concentration of vulnerability?

Assumptions: Assumption: Castellón de la Plana (or chosen city) has ~170k population, ~90% urban, with 20% aged 65+, ~5–8% recent migrants (North African, sub-Saharan, Eastern European; primary languages Spanish, Arabic, Portuguese), ~15% living alone (derived from household data), ~25% in top-floor flats or poorly insulated social housing (concentrated in peripheral blocks built 1960s–1980s). The most vulnerable neighborhoods are assumed to be the north and west peripheral blocks (built Soviet-era or 1970s, poor insulation, high concentrations of 65+, renters) and the central historic quarter (elderly homeowners, limited AC, narrow streets trapping heat). These figures are estimates pending municipal census and housing survey data; local validation is essential for targeting.

Assessments: Title: Geographic and Demographic Vulnerability Mapping Assessment Description: Validates the spatial distribution of high-risk residents to confirm that cooling centers and outreach are positioned to reach the most vulnerable, and that equity metrics can track coverage by deprivation and demographic bands. Details: Precise vulnerability data determines whether the network footprint (many small neighborhood refuges vs. few large sites) is adequate and where home kits should be concentrated. Risks: (a) if vulnerable populations are unmapped, the city may build a network that misses high-need areas (e.g., centers in wealthy downtown but not in peripheral blocks); (b) postcodes/neighborhoods may not align with administrative wards, complicating equity tracking; (c) language and migration data from municipal sources may be dated (census every 5–10 years) and under-count undocumented residents. Benefits: validated vulnerability map enables precise targeting of home kits and enables equity audits (e.g., ''center capacity per vulnerable resident in each neighborhood'') that prove fairness. Mitigation: combine census, GP-registered patient lists, housing-association data and NGO local knowledge (Months 0–1 = 2026-10-08 to 2026-11-08) to build a rapid vulnerability heat-map; use this to confirm cooling-center site selection and outreach-partner allocation; track coverage metrics by neighborhood throughout the summer. Opportunity: vulnerability map becomes a reusable tool for other years and for scaling to peer cities.

Question 4 - What is the realistic staffing plan (FTE count, roles, hiring timeline, skill requirements, retention strategy) for cooling-center staff, outreach coordinators, transport dispatch, phone line and street-contact teams to meet the Month 2 (2026-12-08) readiness gate?

Assumptions: Assumption: A mid-sized city pilot requires ~35–50 FTE total for May–September (5-month operational season): ~2–3 FTE coordination/command; ~12–18 FTE cooling-center staffing (split across 8–12 sites, ~1.5–2 per site per shift × 2–3 shifts/day on alert days); ~4–6 FTE outreach (door-knock, street contact, enrollment); ~2–3 FTE transport dispatch; ~2–3 FTE phone line (city or contracted call-center surge capacity); ~5–10 FTE handyperson or contracted installers (February–May for home kits). Most staff (centers, outreach, transport) are part-time or seasonal (alert-day only), not full-year. Volunteer drivers (~30–50) and center helpers (~20–30) supplement paid staff. Hiring begins Month 0 (2026-10-08); all staff in post by April 30 (Month 6.7 ≈ 2027-04-29). Retention strategy: clear role descriptions, fatigue management, peer support, pro-rata leave entitlements.

Assessments: Title: Staffing Availability, Readiness and Retention Assessment Description: Evaluates whether realistic staffing numbers can be recruited, trained and retained to meet operational gates and maintain morale during multi-day heat-wave surges. Details: Staffing is the most likely source of Month 2 (2026-12-08) and Month 4 (2027-02-08) gate failure. Risks: (a) seasonal hiring (Feb–April for May–Sept roles) competes with other municipal summer hiring; part-time and temporary roles may attract lower-quality candidates; (b) training 50+ people (staff + volunteers) in parallel to procurement and partner negotiations stretches coordination capacity; (c) volunteer recruitment may under-deliver if response is poor in autumn/winter when heat feels distant; safeguarding vetting (background checks, insurance) can take 4–8 weeks and bottleneck dispatch-driver start-dates; (d) staff fatigue during multi-day heat waves (7+ consecutive alert days in July–August) will drive absences and turnover mid-season; part-time staff may prioritize personal family needs over shifts. Benefits: explicit staffing plan with 20–30% reserve capacity reduces crisis-management and improves service continuity. Mitigation: designate a recruitment/HR coordinator (0.5 FTE, Months 0–4 = 2026-10-08 to 2027-02-08) by Month 0 (2026-10-08); launch volunteer recruitment in October–November (when heat safety is topical, before winter fatigue); stagger staff hiring in cohorts (40% in January, 40% in February, 20% in March) so training is incremental and retention can be evaluated early; establish fatigue-management protocols and cross-training by Month 2 (2026-12-08). Opportunity: rigorous staffing planning can serve as a model for other EU cities and reduce chaotic hiring and rework.

Question 5 - What is the detailed procurement and contracting timeline and approach for cooling kits, handyperson services, transport contracts, center fit-out and staffing, and what are the identified risks and backup suppliers if primary vendors cannot deliver?

Assumptions: Assumption: Procurement follows a staged approach: (a) fast frameworks or below-threshold purchasing for kits, handyperson services and initial transport by Month 1.5 (2026-11-23), releasing €500k–700k for immediate orders; (b) full competitive tenders for longer-lead items (transport standby retainers, multi-site security contracts) by Month 2 (2026-12-08); (c) delivery of 40–50% of kit stock by February (Month 4 = 2027-02-08), 80% by March (Month 5 = 2027-03-08), 100% by April (Month 6 = 2027-04-08). Transport contract is signed by January 31 (Month 3.7 ≈ 2027-01-29); handyperson and installer teams are in place by February. Procurement assumes a 4–6 week lead time for kits and 2–3 week notice for transport activation. Backup suppliers are identified for kits, handyperson services and transport before Month 1 (2026-11-08).

Assessments: Title: Procurement Speed, Risk and Budget Execution Assessment Description: Evaluates whether the procurement pathway can meet the Month 2 (2026-12-08) readiness gate without compromising quality, competition or audit compliance, and whether supply-chain risks are mitigated. Details: Procurement is the critical path to the Month 2 (2026-12-08) gate. If kits, transport or center fit-out are delayed beyond March (Month 5 = 2027-03-08), home interventions and transport capacity will miss the first summer heat events. Risks: (a) below-threshold and framework purchasing reduce competition and may yield higher unit costs; audit scrutiny may arise if sole-source or repeat use of the same vendors is challenged; (b) transport retainers lock in capacity but cost €50k–80k for standby (not used) unless a hot summer occurs; taxi suppliers may raise rates during peak summer demand; (c) kit suppliers (shading, fans, thermometers) may face production delays (Asian supply-chain disruptions) and miss February delivery; without backup suppliers, the program loses 2–4 weeks. Benefits: fast frameworks move orders within weeks and are audit-defensible if prior procurement is documented; early kit delivery allows handyperson work in low season (February–April) before center and outreach demands peak. Mitigation: issue specs for kits and services by October 31 (Month 0.8 ≈ 2026-11-01); contact suppliers immediately to confirm availability and lead times; place first call-off order for 30–40% of kit volume by November 15 (Month 1.2 ≈ 2026-11-14) to secure stock; identify 2–3 backup suppliers for each category (kits, handyperson, transport) by Month 1 (2026-11-08); lock in transport retainer rates by contract by end of Month 1 (2026-11-08) before summer demand spikes. Opportunity: transparent, benchmarked procurement builds playbook reusability across EU cities.

Question 6 - How will the program verify that the Month 4 (2027-02-08) gates (80% of planned cooling-center hours, ≥60% outreach contact success, <45-minute average transport time) can be measured fairly if June–July temperatures are below historical norms or alert thresholds are not crossed during real heat events?

Assumptions: Assumption: The Month 4 (2027-02-08) gate measurement window is defined to include both real heat events (if temperatures exceed thresholds May–July) and formal operational drills (if real events are insufficient). A 'drill protocol' will be pre-specified by Month 3 (2027-01-08), defining mock-alert scenarios (e.g., 4–6 hour activation, all centers open, transport and phone line mobilized, outreach calls attempted to sample enrolled residents). Drill performance data (center hours logged, transport response times, outreach contact attempts) will be compared against gate targets alongside any real-event data. If both drills and real events fall short of sufficient evidence by Month 4 (2027-02-08), the gate decision will be deferred to Month 5 (2027-03-08) with 50% of the €1.5M scale funding released contingently to sustain operations through summer.

Assessments: Title: Gate Measurement Validity and Contingency-Funding Assessment Description: Evaluates the fairness and feasibility of measuring operational gates during a cool season, and proposes contingency decision-rules to avoid non-release of funds due to weather chance. Details: The user constraint fixes the Month 4 (2027-02-08) gate, but early summer (June–July) weather is unpredictable. Risks: (a) if June–July are cooler than normal (25% probability in Mediterranean climates), alert thresholds will not be crossed, preventing real-world gate testing; (b) drill-based evidence may be viewed as weaker than real-event data by funders or auditors, and drills in cool weather may not reflect stress-tested performance under actual heat stress; (c) if gates are not released on schedule, the program will face a budget shortfall by August (estimated €200k–400k) and may be forced to close some centers mid-summer, harming residents during late-August peak heat. Benefits: pre-specified drill protocol allows gates to be tested regardless of weather, and contingency-funding rules provide decision clarity if evidence is ambiguous. Mitigation: draft drill protocol by Month 2.5 (2026-12-23), specifying date, duration, participant roles and target metrics; conduct a full-system drill by May (Month 7 = 2027-05-08) with all centers, transport, phone and outreach staff; document drill results rigorously (center-hours opened, transport requests and response times, phone-line call volume and wait time, outreach contact attempts) to use as gate evidence; redefine gate decision rule: release €1.5M on time if (real heat events + drill data) demonstrate ≥80% center hours, ≥60% outreach success and <45-min transport; if evidence is mixed, release 50% contingently by Month 4 (2027-02-08) and defer full release to Month 5 (2027-03-08) based on June real-world data. Opportunity: robust gate protocol demystifies funding decisions and builds stakeholder confidence in program management.

Question 7 - What specific protocols, translation capacity, and community-partner strategies will ensure that recent migrants and residents with limited local-language skills receive alerts, enrollment information and heat-illness escalation guidance in languages they understand, and how will multilingual reach be verified?

Assumptions: Assumption: The pilot city (Castellón, Poznań or Modena) has a top 4–6 spoken non-official languages (estimated from municipal registers): Spanish pilot—Arabic, Portuguese, Romanian; Polish pilot—Ukrainian, Vietnamese, Russian; Italian pilot—Romanian, Albanian, Arabic. These communities represent 5–15% of the population but may be concentrated in 2–3 neighborhoods. Translation and interpretation services will include: (a) professional translation of key materials (alert flyers, enrollment scripts, heat-illness recognition guides) into each language by Month 1 (2026-11-08); (b) telephone interpretation service for the heat-line and outreach staff (remote interpreter on standby during alert days); (c) recruitment of 8–12 paid community-language ambassadors (part-time, 10–15 hrs/week during alert season) to co-write messages, accompany door-knocks and staff cooling-center welcome desks; (d) pictogram-first designs for door hangers and center signage to reach non-literate residents. Reach verification: track language of enrollment contacts and verify that non-official-language speakers comprise ≥5% of outreach calls by alert day.

Assessments: Title: Multilingual Access and Equity Reach Assessment Description: Evaluates whether language access strategies will ensure recent migrants and non-native speakers can receive life-saving alerts and escalation guidance without delay, and whether coverage can be verified. Details: Excluded or delayed communication to non-native speakers could constitute health and equity harm, as these residents are often already isolated and have lower health-system access. Risks: (a) professional translation alone (without community ambassadors) is expensive (~€15k–25k for 4–6 languages) and does not build trust or address cultural barriers; ambassadors take 6–8 weeks to recruit, vet and brief (month 0–2 = 2026-10-08 to 2026-12-08), creating timeline pressure; (b) telephone interpretation services scale quickly but may be impersonal and ineffective for residents who avoid formal systems; (c) without pre-testing translated messages with native speakers, translations can be culturally inappropriate or medically inaccurate, undermining trust (e.g., heat-illness signs may have different cultural interpretations); (d) language reach tracking requires outreach staff to log the language used in each contact, adding administrative burden and potential privacy issues. Benefits: trusted community ambassadors dramatically improve enrollment and compliance among migrant residents and reduce misinformation. Mitigation: identify top languages and ambassador candidates by Month 0 (2026-10-08) through municipal integration offices and NGOs; commission professional translation of top 3–4 languages by Month 1 (2026-11-08); recruit ambassadors in parallel (month 0–2 = 2026-10-08 to 2026-12-08) and conduct focus-group testing of translated materials with native speakers before Month 2 (2026-12-08); budget for interpretation services (€200–300/day during alert days) in addition to ambassadors. Track language diversity in outreach calls via simple log form; audit 10% of calls by spot-check to verify language protocols are followed. Opportunity: multilingual messaging demonstrates inclusive governance and provides a reusable, transferable model for other EU cities with diverse migration profiles.

Question 8 - What are the explicit definitions, legal bases and data-handling protocols for the intermediary-held-list approach (housing associations, social services, NGOs, pharmacies holding and calling residents), and what is the GDPR risk assessment and mitigation for each partner?

Assumptions: Assumption: The intermediary-held-list model complies with GDPR by: (a) housing associations, social services and NGOs contact their own residents/clients using existing lawful bases (contractual, consent-based, public-task duties) and do not transfer personal data to the city; (b) only aggregate outreach results are reported to the city (e.g., ''100 residents contacted, 65 enrolled, average response time 2.5 days''), not names, addresses or health records; (c) opt-in consent forms (or partner-managed consent refresh) specify that contact is for heat-season welfare checks and can be declined; (d) data retention is limited to one season (October–September) and deleted thereafter; (e) a data-processing agreement (DPA) or MOU between each partner and the city clarifies data controller/processor roles, liability, breach notification and staff confidentiality. GDPR risk level: moderate, because contact is initiated by trusted intermediaries, not the city directly, and no personal data leaves the partner's systems. Residual risks include partner non-compliance, consent withdrawal mid-season, and breach of confidentiality by partner staff.

Assessments: Title: GDPR Compliance, Data Protection and Partner Accountability Assessment Description: Evaluates whether the intermediary-held-list model is legally sound under GDPR and whether partner accountability mechanisms can reduce data-protection risk and trust erosion if breaches occur. Details: GDPR compliance is a hard constraint for the plan's viability. The intermediary model is more protective than a city-held registry, but each partner's data-governance maturity varies, and unclear legal basis for contact could expose the city to regulatory challenge or resident complaint. Risks: (a) if a partner lacks a clear lawful basis for calling residents (e.g., social services contact only those already in active cases, excluding other vulnerable residents), the city cannot compel contact, limiting reach; (b) if a partner does not have explicit consent or a GDPR-compliant privacy notice on file, data regulator review could halt outreach mid-season; (c) if a partner breaches confidentiality (e.g., staff gossip about residents' heat illness or living alone), the city may face legal liability and trust erosion; (d) if a partner's systems are breached (ransomware, hacking), residents' data could be exposed; (e) Residents may withdraw consent mid-season (e.g., after a bad experience with staff), reducing contact base; (f) consent-refresh and data-retention mechanics are unclear—does consent expire at season end or annually? Are residents re-consented for Year 2?. Benefits: intermediary model avoids city holding personal health data, reduces GDPR audit scope and distributes liability. Mitigation: engage specialist GDPR legal counsel by Month 0.5 (2026-10-23) to draft template MOUs/DPAs for each partner type (housing association, social service, NGO, pharmacy); specify lawful basis (public-task/consent hybrid is typical for welfare), contact frequency, consent withdrawal mechanism and breach-notification procedures; obtain written legal sign-off by Month 1 (2026-11-08); brief all partners on GDPR obligations and staff confidentiality by Month 2 (2026-12-08); audit partner compliance mid-season (July, Month 9 = 2027-07-08) via spot-check review of consent records and staff training logs; establish a breach-reporting hotline so residents can report partner misconduct quickly. Opportunity: well-documented and audited GDPR compliance becomes a reusable, transferable safeguard for other EU cities and demonstrates municipal data ethics.

Distill Assumptions

• Castellón de la Plana (Spain, ~170k population) selected as pilot site with baseline 80–120 heat-related EMS calls per summer.
• Baseline heat-attributable excess mortality estimated at 15–25 deaths per summer using temperature-mortality regression methods.
• 20% population aged 65+; 5–8% recent migrants; ~15% living alone; ~25% in top-floor or poorly insulated units.
• Most vulnerable neighborhoods are peripheral north/west blocks (1960s–1980s, poor insulation) and central historic quarter.
• Written mayoral delegation of alert-declaration authority signed by Month 1 (2026-11-08) with clear trigger thresholds and backup authority chain.
• Low-cost advisory tier combines national warning with phone check-ins; full center activation reserved for upper tiers only.
• Network of 8–12 small neighborhood refuges in libraries, community centers, parish halls within walking distance.
• Intermediary-held contact lists (housing associations, social services, NGOs, pharmacies) with no personal data transferred to city.
• Vetted volunteer drivers (30–50) coordinated by dispatcher; taxi backup for transport-gate protection.
• 35–50 FTE seasonal staff (May–September) across coordination, centers, outreach, dispatch, phone line and installations.
• Hiring and training completed by April 30 to ready all staff before May summer season.
• Procurement of kits, transport contracts and center fit-out completed by Month 2 (2026-12-08) readiness gate.
• 40–50% of kit stock delivered by February; 80% by March; 100% by April.
• Month 4 (2027-02-08) gate measured via operational drills if June–July temperatures below historical norms and real events insufficient.
• Pre-specified drill protocol with mock-alert scenarios defined by Month 3 (2027-01-08) to test gates fairly.
• Contingency-funding rule: 50% of €1.5M released if evidence mixed; full release deferred to Month 5 (2027-03-08) if needed.
• Cooling-center 80% planned-hours gate measured via real events and operational drills.
• Outreach contact-success gate ≥60% for enrolled high-risk residents on alert days.
• Transport time-to-arrival gate <45 minutes average including wheelchair-accessible vehicles.
• Professional translation of key materials into 4–6 locally common non-official languages by Month 1 (2026-11-08).
• 8–12 paid community-language ambassadors (part-time, 10–15 hrs/week during alert season) recruited and briefed.
• Pictogram-first door hangers and center signage to reach non-literate residents.
• Telephone interpretation service for heat line and outreach staff during alert-day hours.
• GDPR-compliant data-processing agreements drafted with each partner type by Month 0.5 (2026-10-23).
• Partner-held contact data limited to one season (October–September); deleted thereafter.
• Consent forms specify heat-season welfare checks and allow mid-season withdrawal.
• Audit of partner GDPR compliance mid-season (July, Month 9 = 2027-07-08) via consent-record spot-checks.
• Home-intervention kit includes exterior shading, reflective blinds, window fans, thermometers, hygrometers, hydration supplies.
• Rubric-based household selection prioritizes top-floor units and social-housing blocks.
• Handyperson installation and fan-safety checks included; no major construction work.
• Lending scheme optional: kits installed May, collected September, cleaned and redeployed across seasons.
• Two-stage funding: €2.0M initial release; €1.5M released at Month 4 (2027-02-08) if gates met.
• Month 2 (2026-12-08) readiness gate: cooling centers contracted, staffed, transport signed, phone line operational, procurement orders placed, training completed.
• MOU signed with hospitals, EMS, primary care for daily aggregate counts (no identifiable patient records).
• Heat-protection clauses in municipal employment contracts requiring schedule changes, breaks, water, shade.
• Guidance package and recognition scheme offered to private employers (non-binding).
• Clinical nurse triage line for outreach staff to escalate suspected heat illness and prevent unnecessary EMS calls.
• Pre-season public campaign plus heat-event messaging templates via radio, flyers, pharmacy posters, door hangers, SMS.
• Trusted messengers (pharmacists, GPs, caretakers, faith leaders) briefed with consistent scripts and printed leave-behinds.
• Misinformation rebuttal channel to counter unsafe advice (alcohol, incorrect fan use in extreme heat).
• Street contact pathway for unhoused residents: daytime mobile rounds, drop-in cool points, referral transport triggers.
• Data from Consent-Light Identification Routes feeds home-kit targeting, outreach and enrollment.
• Governance incident-command structure: mayor's office incident commander with public-health deputy.
• Alert declarations issued within 1 hour of forecast trigger.
• Cross-training across health, civil protection and public works enables independent operation.
• Base comparison design: pilot districts vs. matched non-pilot districts and prior years, aggregate EMS and ED counts only.
• Temperature-adjusted attribution for heat-day outcomes; explicit confidence ranges and attribution limits stated plainly.
• Heat-related EMS calls, ED visits, excess mortality tracked as primary outcome proxies.
• Center utilization, transport requests served, outreach attempt/success rates tracked as operational KPIs.
• Coverage by neighborhood deprivation index, age bands and housing type tracked as equity metrics.
• Local calibration of alert thresholds from historical temperature and mortality data, reviewed after Year 1.
• Successive consecutive hot nights weighted more heavily than daytime peaks in threshold formula.
• Formal drill protocol pre-specified by Month 3 (2027-01-08); full-system drill executed by May.
• Heat Response Playbook with SOPs, checklists, scripts, procurement lists, partner MOUs delivered by Month 12 (2027-10-08).
• Cost model for city-wide scaling and replication to other EU cities delivered by Month 12 (2027-10-08).
• Data and evaluation report with limitations clearly stated delivered by Month 12 (2027-10-08).
• Year-2 roadmap identifying expansion priorities, elements to discontinue delivered by Month 12 (2027-10-08).
• 30% reserve staffing capacity built in to absorb multi-day surge and fatigue absences.
• Volunteer drivers subject to background checks, insurance, safeguarding vetting (4–8 week process).
• Fatigue-management protocols and staff cross-training established by Month 2 (2026-12-08).
• Below-threshold purchasing and frameworks used for fast kit and service procurement by Month 1.5 (2026-11-23).
• Transport standby retainer locked in by Month 1 (2026-11-08) before summer demand spike.
• 2–3 backup suppliers identified for kits, handyperson services, transport by Month 1 (2026-11-08).
• Specs for kits and services issued by October 31; first call-off order placed by November 15.
• Handyperson work scheduled February–April before center and outreach peak demand.
• After-action report completed with corrective actions closed before Month 4 (2027-02-08) gate decision.
• Reputational risk register includes politicization of alerts, failed response during media scrutiny, equity gaps.
• Volunteer-safety risk includes potential assault during street contact, safeguarding breaches, personal vehicle liability.

Review Assumptions

Domain of the expert reviewer

Public Health Emergency Management and Municipal Infrastructure Planning

Domain-specific considerations

• GDPR and data-protection compliance with intermediary-held contact lists and partner data-handling protocols
• Operational readiness and gate validation during cool season (Month 2–4 = 2026-12-08 to 2027-02-08) with fair measurement criteria if heat events are sparse
• Staffing capacity, volunteer vetting and fatigue management across 5-month alert season with multi-day surge demands
• Supply-chain and procurement timeline compression (8 weeks) for kits, transport contracts and center fit-out before summer season
• Equity reach and accessibility across neighborhoods and language groups, with verification mechanisms for coverage claims
• Reputational risk from operational failures (accessibility gaps, staffing gaps, misinformation) that harm vulnerable residents and undermine municipal credibility

Issue 1 - Gate Measurement Validity During Cool Season and €1.5M Release Contingency

The Month 4 (2027-02-08) gates (80% center hours, 60% outreach success, <45-minute transport) are scheduled for early summer, but June–July heat events are unpredictable. If temperatures fall below alert thresholds, gates cannot be measured against real events, risking non-release of €1.5M scale funding and mid-summer operational collapse. Drill-based evidence may be viewed as weaker than real-event data by funders or auditors. Without contingency-funding rules, the program faces €200k–400k budget shortfall by August, forcing closure of centers or transport during peak-risk late-summer heat.

Recommendation: Redefine the Month 4 (2027-02-08) gate to accept operational drills as valid evidence alongside real heat events. Pre-specify a 'drill protocol' by Month 3 (2027-01-08) that mirrors alert-day operations (all centers open, transport mobilized, phone line active for 4–6 hours). Conduct a full-system drill in May with rigorous documentation of center-hours delivered, transport response times and outreach contact attempts. Establish a contingency-funding rule: release €1.5M on time if combined real-event and drill data demonstrate gate targets; if evidence is ambiguous, release 50% contingently by Month 4 (2027-02-08) and defer full release to Month 5 (2027-03-08) based on June real data. Include €150k–200k contingency reserve within initial €2.0M to cover May–July operational costs if scale funding is delayed.

Sensitivity: If June–July are cooler than normal (25% probability), real heat events will not occur and gates cannot be tested fairly. Drill-based evidence alone may delay funding release by 3–6 weeks, forcing budget cuts to operations. Estimated financial impact: €200k–400k shortfall if scale release is deferred from Month 4 (2027-02-08) to Month 5–6 (2027-02-08 to 2027-03-08 to 2027-04-08). If gates are not released on schedule, cooling-center hours and transport capacity may contract by 25–40% by August, reducing mortality protection during peak-risk late summer. Probability of cool June–July: 20–25% in Mediterranean climates; impact severity on program viability: high.

Issue 2 - Supply-Chain and Procurement Timeline Compression for Cooling Kits and Transport Contracts

Procurement of cooling kits (exterior shading, reflective blinds, fans, thermometers), handyperson services, and transport contracts must be completed by Month 2 (2026-12-08) readiness gate to allow delivery by April and deployment in May–June. Lead times for kit suppliers are typically 4–6 weeks; transport retainer contracts require 2–3 week notice. Delays beyond February–March (Months 4–5 = 2027-02-08 to 2027-03-08) will push home-intervention rollout past the first summer heat events, missing peak-risk early season. Supply-chain disruptions (Asian production delays, supplier unavailability) or single-source dependency could force expensive expedited shipping (10–15% premium) or alternative supplier sourcing at higher cost.

Recommendation: Issue procurement specifications and contact suppliers by October 31 (Month 0.8 ≈ 2026-11-01) to confirm availability and lead times before Month 1 (2026-11-08). Place first call-off orders for 30–40% of total kit volume by November 15 (Month 1.2 ≈ 2026-11-14) to secure early stock. Negotiate expedited February delivery, accepting 10–15% price premium (€50k–100k) if needed. Identify 2–3 backup suppliers for each category (kits, handyperson, transport) by Month 1 (2026-11-08) and pre-qualify them. Lock in transport standby-retainer rates by contract by end of Month 1 (2026-11-08) before summer demand spikes. Arrange interim storage at municipal facility or partner warehouse. Keep 10–15% stock buffer pre-positioned by February for emergency deployment if heat events occur in March.

Sensitivity: If primary kit suppliers face production delays (4–8 week slip from Asian supply-chain issues), orders placed in October–November will not arrive until March–April, delaying home interventions by 4–8 weeks. Estimated cost impact: €50k–100k for expedited shipping and backup suppliers if delays occur. If transport retainer prices spike during peak summer demand (June–August), unbudgeted increases of €150k–250k could force cuts to home-kit installations (500–1000 fewer kits) or other services. Baseline assumption: 40–50% kit delivery by February (Month 4 = 2027-02-08), 80% by March (Month 5 = 2027-03-08). Variance: if 50% or fewer kits are delivered by February, home interventions begin 4–6 weeks late, missing peak-risk May–June period and reducing estimated mortality reduction by 15–25%.

Issue 3 - Staffing Recruitment, Vetting and Fatigue Management for Multi-Day Heat-Wave Surges

Operational readiness requires 35–50 FTE staff (cooling-center, outreach, dispatch, phone line, installers) recruited and trained by April 30 (Month 6.7 ≈ 2027-04-29). Volunteer driver vetting (background checks, insurance, safeguarding) takes 4–8 weeks and may bottleneck dispatch-driver start-dates if recruitment response is low. During multi-day heat waves (7+ consecutive alert days in July–August), fatigue and absences will stress service continuity; part-time and seasonal staff may prioritize personal family needs over shifts, reducing capacity by 10–25%. Without 20–30% reserve staffing capacity, service degradation is likely: cooling centers operate at reduced hours, transport dispatch slows (15–30 minute delays), phone line experiences long wait times (>10 minutes). Staff turnover mid-season due to burnout will add recruitment and training costs.

Recommendation: Designate a recruitment/HR coordinator (0.5 FTE, Months 0–4 = 2026-10-08 to 2027-02-08) by Month 0 (2026-10-08). Launch volunteer recruitment in October–November targeting retirees, charity staff and faith-group members through NGO networks in parallel with municipal advertising. Conduct vetting in fortnightly cohorts so early cohorts are trained and road-tested by Month 1 (2026-11-08). Stagger staff hiring in cohorts (40% January, 40% February, 20% March) so training is incremental. Establish a taxi-retainer backup contract by Month 1 (2026-11-08) with proportionally reduced guarantee; if volunteer numbers fall below 50% of target by Month 1.5 (2026-11-23), increase taxi retainer proportionally. Build 20–30% reserve staffing capacity (additional part-time center staff, backup dispatcher, on-call phone operators) to cover absences and multi-day surges. Establish rota limits: consecutive alert-day shifts max 3–4 days, mandatory 1–2 days rest between multi-day events. Cross-train staff across roles (center managers back up dispatch). Provide fatigue-management training and peer-support protocols by Month 3 (2027-01-08).

Sensitivity: If volunteer recruitment falls short by 30–50%, transport costs increase by €150k–250k to shift to taxi-only operation, forcing cuts to home-kit distribution (500–1000 fewer kits). Baseline: 30–50 volunteer drivers; variance: if only 15–25 volunteers recruited, average time-to-transport will slip from 45 minutes (target) to 55–70 minutes, failing the Month 4 (2027-02-08) gate. If vetting delays slip volunteers' start-dates by 3–6 weeks, dispatch capacity will be under-staffed until June, compromising early-May response capacity. During multi-day heat waves (7+ days), staff absence and fatigue-driven reduced hours could degrade center capacity by 15–25% and increase transport wait times by 20–40 minutes, further risking gate failure. Estimated cost of staff incident response, counseling and replacement hire if burnout occurs: €10k–20k per staff member; for 5–10 staff turnover: €50k–200k total.

Review conclusion

This 12-month municipal heatwave mortality-reduction program is viable but faces three critical interdependent risks: (1) gate measurement during cool season with contingency-funding uncertainty—the Month 4 (2027-02-08) gates depend on June–July heat events that may not occur, risking €1.5M non-release and mid-summer operational collapse; (2) supply-chain and procurement compression—kits and transport contracts must be ordered by November–December (Month 1–2 = 2026-11-08 to 2026-12-08) to arrive by February–April, or home interventions and transport capacity will miss the first summer events; (3) staffing recruitment and fatigue management—35–50 FTE staff must be hired, vetted and trained by April, with 20–30% reserve capacity to absorb multi-day surges, or operational gates will fail. Mitigation priorities: (a) redefine gates to accept drill-based evidence and establish contingency-funding rules by Month 2 (2026-12-08); (b) begin procurement and supplier vetting by October 2026 and place first orders by November to secure stock; (c) launch volunteer recruitment immediately and conduct staffing stress tests by May. Secondary risks include GDPR compliance uncertainty (mitigated via specialist legal review by Month 0.5 = 2026-10-23), partner capacity and engagement (mitigated via joint MOUs and performance monitoring), and equity reach across language groups (mitigated via community ambassadors and multilingual materials). With active management of these risks at Months 1, 2, 3.5 and 4 (2026-11-08, 2026-12-08, 2027-01-23, 2027-02-08), the program can meet gates, protect vulnerable residents and generate a reusable playbook for other EU cities.

Governance Audit

Audit - Corruption Risks

• Bribery or kickbacks from cooling-kit suppliers, transport contractors, or handyperson service providers in exchange for contract awards, sole-source purchasing, or expedited payment without competitive tender or quality verification.
• Nepotism in recruitment of cooling-center staff, outreach workers, dispatchers, or volunteer drivers through preferential hiring without transparent selection criteria or documented interviews.
• Conflicts of interest: incident commander, procurement officer, or partner-liaison staff steering contracts to family-owned suppliers, taxi operators, or translation firms, or accepting personal gifts or favors from vendors.
• Theft or misallocation of cooling kits, hydration supplies, or thermometer/hygrometer stock by handypersons, storage custodians, or center staff; sale of municipal equipment on the black market or for personal use.
• Information misuse: partner staff (housing associations, NGOs, social services) sharing enrolled residents' contact data with third parties (political campaigns, unsolicited marketing, creditors) beyond the agreed data-processing scope.
• Collusion between transport dispatchers and taxi-retainer operators to inflate trip counts, falsify response times, or double-bill for overlapping rides, or between outreach staff and intermediary partners to inflate contact-success metrics to meet the 60% gate.

Audit - Misallocation Risks

• Budget misuse: reallocation of cooling-center operational funds (staffing, utilities, supplies) to unbudgeted items (office furniture, personal equipment, meals) or deliberate overspending on low-priority items to deplete contingency reserves.
• Double spending: same kit component (e.g., fans) purchased twice through different procurement routes (framework call-off and competitive tender) without canceling the first order, resulting in duplicate stock and wasted funds.
• Inefficient allocation: concentration of cooling centers in affluent neighborhoods while high-risk peripheral and historic-quarter areas remain under-served; failure to track equity coverage by deprivation index.
• Unauthorized use of transport assets: volunteer drivers or dispatchers using taxi-retainer vehicles for personal errands outside alert-day mobilization, or dispatchers redirecting resources to non-heat-response municipal functions.
• Poor record-keeping: lack of documented procurement files, missing contracts, unsigned MOUs, or no audit trail for cash disbursements, preventing verification of compliance with procurement rules or budget allocations.
• Misreporting progress or results: inflated contact-success rates (claiming 70% when actual data shows 50%), falsified drill metrics, or overstated kit installation completion to meet Month 4 (2027-02-08) gates and trigger conditional funding release.

Audit - Procedures

• Quarterly external audit of procurement files and vendor contracts: review call-off orders, competitive tenders, sole-source justifications and supplier invoice-to-payment chains to verify compliance with municipal procurement thresholds and competitive requirements by Month 2, 5, 8, and 11 (2026-12-08, 2027-03-08, 2027-06-08, 2027-09-08).
• Monthly internal financial review: reconcile budget burn against planned spend by cost category (refuges, transport, kits, staffing, communications); flag overruns >10% and conduct drill-down reviews with cost-center owners within 5 working days.
• Biweekly data-integrity spot-checks of outreach contact logs and transport-dispatch records: audit 10% sample of recorded calls, contact outcomes and pickup times against actual partner records; validate drill metrics against real-time recordings or witness statements.
• Post-gate audit at Month 4 (2027-02-08): independent verification of all three gate metrics (80% center hours, 60% outreach success, <45-min transport) by external auditor; compare drill data against baseline assumptions and drill protocol to confirm fairness of measurement.
• Annual compliance audit of partner organizations (housing associations, NGOs, social services, pharmacies) against GDPR data-processing agreements: review consent records, staff confidentiality training logs, data-retention compliance and breach-notification procedures by Month 9 (2027-07-08).
• Post-season evaluation audit (Month 12 = 2027-10-08): verify heat-related EMS and ED data quality with hospitals/EMS, reconcile baseline estimates against final case counts, and validate any reported reductions in mortality with independent cause-of-death review.

Audit - Transparency Measures

• Monthly public dashboard (municipal website) reporting: planned vs. actual cooling-center hours delivered, outreach contact attempts and success rates by partner, transport requests and average response times, cumulative kit installations by neighborhood, and budget spend-rate against forecast by cost category; updated by 5th of each month.
• Published weekly meeting minutes from the incident-command team and monthly partner-coordination meetings: document alert declarations, trigger thresholds used, cross-department decisions on escalation, corrective actions closed, and budget reforecasts; accessible to council and stakeholders within 5 working days of meeting.
• Heat Response Playbook (draft by Month 11 = 2027-09-08, final at Month 12 = 2027-10-08): public document detailing all SOPs, decision logic, cost assumptions, staffing specifications, partner roles and lessons learned; identifies city-specific adaptations and replicability conditions for peer EU cities.
• Quarterly public stakeholder briefing (Months 1, 4, 7, 10 = 2026-11-08, 2027-02-08, 2027-05-08, 2027-08-08): open forum where vulnerable residents, NGO partners, faith leaders and media can ask questions about program progress, equity coverage and upcoming actions; minutes published within 10 days.
• Procurement transparency summary (published by Month 2 = 2026-12-08): list all contracts ≥€50k with vendor name, scope, value, procurement route and rationale for method (e.g., 'framework call-off for rapid kit delivery') to enable scrutiny and demonstrate competitive justification.
• Post-season evaluation report (Month 12 = 2027-10-08): independent university analysis of heat-related EMS calls, ED visits and excess mortality with explicit confidence intervals, comparison-group methodology, temperature adjustment and attribution caveats; published in plain-language summary and technical annex for public and peer-city use.

Internal Governance Bodies

1. Heat Response Steering Committee

Rationale for Inclusion: This is a high-complexity, multi-department municipal program with strategic dependencies on mayoral authority, cross-departmental coordination, and significant reputational risk. A strategic-oversight body is essential to ensure political alignment, secure timely budget decisions, resolve inter-departmental conflicts, and provide accountability to the funder and city council. The brief explicitly requires a mayor's-office incident commander; a Steering Committee crystallizes this authority and ensures continuity across staff transitions.

Responsibilities:

• Approve alert-trigger thresholds and incident-command delegation; escalate threshold changes to council if politically sensitive
• Release or withhold €1.5M tranche-2 funding at Month 4 (2027-02-08) based on gate-review evidence
• Resolve cross-department resource conflicts (e.g., public works, health, civil protection) and authorize budget reallocation
• Review monthly reforecasts and approve contingency-reserve drawdowns >€20k
• Oversee legal and GDPR compliance; approve data-processing agreements with partners
• Approve Year-2 roadmap and playbook before public release

Initial Setup Actions:

• Establish written delegation of incident-command authority signed by the mayor by Month 1 (2026-11-08)
• Set alert-trigger thresholds (Level 1: high ≥33°C or low ≥20°C on ≥2 consecutive days; Level 2: high ≥35°C and low ≥22°C for ≥2 consecutive days; Level 3: same as Level 2 for ≥3 consecutive days or national red warning) by Month 1 (2026-11-08)
• Approve incident-command and operations structure; name incident commander, operations lead and communications lead by Month 0.5 (2026-10-23)
• Engage GDPR counsel and approve legal-review scope by Month 0.5 (2026-10-23)
• Authorize procurement route and spending authorities by Month 0.8 (2026-11-01)

Membership:

• Mayor or delegated chief executive (Chair)
• Deputy Mayor or head of municipal health/public protection (Vice-Chair)
• Director of civil protection and emergency services
• Director of municipal communications
• Municipal finance director (observer for budget forecasts)
• External independent member: university or public-health institute evaluation partner (advisory, non-voting)

Decision Rights: Strategic decisions only: alert-threshold setting and modification; tranche-2 funding release/non-release; reallocation of >€20k from contingency; approval of GDPR and data-processing agreements; authorization of procurement routes and supplier sole-source justifications >€100k; approval of Year-2 roadmap and playbook before publication. All operational decisions remain with the incident commander and PMO. Escalation from operational level occurs for decisions impacting budget >€20k, legal exposure, or inter-departmental authority conflicts.

Decision Mechanism: Majority vote (4 of 6 members). Quorum = 4 members including Chair or Vice-Chair. Tie-breaker: Chair vote. In emergencies (e.g., mid-alert funding decision), incident commander may brief Chair and one other member by phone and recommend action; formalized in the next meeting (≤3 days). Legal and GDPR decisions require sign-off from legal counsel before vote.

Meeting Cadence: Monthly during Months 0–4 (2026-10-08 to 2027-02-08, project setup and gates) on the first Monday; bi-weekly during Months 5–7 (2027-03-08 to 2027-05-08, kit distribution and initial operations); monthly during Months 8–12 (2027-06-08 to 2027-10-08, season and playbook). Emergency meetings within 24 hours if: non-release of tranche-2 becomes likely, legal challenge emerges, major breach occurs, or incident commander escalates unresolved conflict.

Typical Agenda Items:

• Incident-command and operational status (via PMO briefing): alert declarations, response performance, gate-metric tracking
• Financial status: budget burn by cost category, reforecast and contingency drawdown justifications
• Legal and GDPR compliance: partner DPA progress, data-protection audit findings, breach-notification log
• Staffing and partner engagement: recruitment status, partner capacity and satisfaction, staff retention and fatigue incidents
• Gate metrics progress: cooling-center hours, outreach contact success, transport response time, drill results (if applicable)
• Risk register review: new risks, escalated mitigation actions, insurance and liability incidents
• Year-2 planning (Months 10–12 = 2027-08-08 to 2027-10-08): roadmap development, scaling cost model validation, funder and peer-city engagement

Escalation Path: Steering Committee decisions on budget release, threshold changes or legal interpretation escalate to the city council (or mayoral cabinet if council is not in session) if: (1) spending approval needed is above the mayor's delegated authority, (2) a legal opinion is contested, or (3) the decision affects public policy beyond heat response (e.g., new data-protection rules). Operational escalations to the Steering Committee come from the incident commander or PMO if: unresolved cross-department conflict, contingency drawdown >€20k needed, or legal exposure. If the Steering Committee cannot decide, the mayor casts the deciding vote; if still deadlocked, legal counsel issues a binding opinion (for GDPR/compliance) or the decision is tabled and deferred to the city council.

2. Heat Response Operations Team (Incident Command Structure)

Rationale for Inclusion: Operational delivery of cooling centers, transport, outreach, home kits and health coordination requires a unified command structure with clear ownership, rapid decision-making authority and incident-day responsiveness. The incident commander must declare alerts, mobilize resources, and coordinate cross-departmental actions within hours. This team executes the alert-trigger ladder, staffs refuges, dispatches transport and manages partner operations during alert periods. It also tracks gate metrics and prepares gate-review evidence for the Steering Committee.

Responsibilities:

• Declare heat alerts (Level 1, 2, 3) within 1 hour of forecast trigger; inform partners and public within 24 hours
• Mobilize cooling centers, transport dispatch, phone line and street contact on alert days; stand down when thresholds no longer met and temperatures normal for 48 hours
• Coordinate daily operations: SITREP at 08:30, partner briefing at 09:30, public update by 11:00 on Level 2-3 days
• Manage center staffing, volunteer dispatch, phone-line operations and outreach team deployment; authorize re-allocation of resources between sites if demand exceeds capacity at one location
• Escalate heat-illness or safety incidents to EMS; coordinate with health-system partners (hospitals, EMS) on aggregate data exchange and mutual-aid triggers
• Monitor and track gate-metric data daily: center-hours opened, outreach calls and success rates, transport requests and response times, kit installations
• Conduct monthly review of performance metrics, partner feedback and risk register; escalate budget or resource issues to Steering Committee; authorize corrective actions within operational scope (staffing adjustments, scheduling changes, local script updates)

Initial Setup Actions:

• Designate incident commander, public-health deputy, operations lead, communications lead and partner-liaison officer by Month 0.5 (2026-10-23)
• Establish written position descriptions, delegations of authority and role-specific escalation rules for each lead by Month 1 (2026-11-08)
• Establish daily SITREP and briefing schedule (09:30 start, 30-minute duration) and draft agenda templates by Month 1.2 (2026-11-14)
• Set up heat-response operations workspace (shared desks, phone line, email lists, shared drives, daily-log templates) by Month 1.5 (2026-11-23)
• Brief incident-command team on alert thresholds, decision criteria and escalation rules by Month 2 (2026-12-08); conduct tabletop scenario drill by Month 2.5 (2026-12-23)

Membership:

• Incident commander (mayor's office or delegated chief-of-staff equivalent)
• Public health deputy (municipal health department)
• Operations lead (civil protection or emergency management)
• Communications lead (municipal communications office)
• Partner-liaison officer (dedicated to this program, may be pooled from public health or social services)
• PMO/program coordinator (reports to incident commander, tracks budgets, gates and schedules)

Decision Rights: Operational decisions within delegated spending and personnel authority: alert declaration per thresholds set by Steering Committee; daily resource mobilization and staffing; re-allocation of resources between sites on alert days; partner communications and coordination; frontline incident management (first aid, escalation to EMS, de-escalation protocols). Cannot commit budget >€20k, alter strategic thresholds, or approve procurement without Steering Committee. Can authorize corrective actions <€5k (e.g., emergency supplies, local staff overtime). Decisions on gate-metric interpretation that affect the Month 4 (2027-02-08) release decision escalate to Steering Committee.

Decision Mechanism: Incident commander has final authority on daily operational decisions during alert periods. For non-alert decisions (e.g., monthly review, staffing adjustments, corrective actions), incident commander convenes the full Operations Team; consensus sought, but incident commander decides if consensus cannot be reached within 24 hours. Public-health deputy has veto on clinical safety decisions (e.g., escalation protocols, health-data access); if vetoed, incident commander escalates to Steering Committee. Communications lead has editorial control over public messaging; incident commander may override for urgent/sensitive statements, but communications lead may appeal to Steering Committee if override is systematic.

Meeting Cadence: Daily during alert days (Level 1, 2 or 3): SITREP 08:30 (15 min), partner briefing 09:30 (30 min), public update 11:00 (10 min). Weekly during non-alert periods (Months 1–5 = 2026-11-08 to 2027-03-08): Monday 14:00 (60 min) to review progress, staffing, procurement and risks. Bi-weekly during summer (Months 6–8 = 2027-04-08 to 2027-06-08) to monitor early heat and kit distribution. Daily during Months 9–11 (2027-07-08 to 2027-09-08, peak season): SITREP and briefing only if alert active; Friday debrief (60 min) for weekly review. Post-season: monthly closure/evaluation meetings.

Typical Agenda Items:

• Alert status and threshold interpretation: forecast review, trigger logic, alert-declaration timing and rationale
• Cooling-center operations: occupancy, staffing, supply availability, incident reports, accessibility issues, site-specific problems
• Transport and dispatch: request volume, response times, volunteer driver availability, taxi backup utilization, mobility-limited resident experience
• Outreach and enrollment: contact attempts by partner, success rates, language coverage, difficult-to-reach populations, escalation cases
• Health-system data: daily EMS/ED counts, trends, mutual-aid triggers, clinical escalation cases, hospital capacity alerts
• Staffing and fatigue: absences, incident reports, training gaps, peer support needs, retention issues
• Financial and procurement: spend tracking by category, reforecast, contingency-reserve status, supply-chain delays, vendor performance
• Risk and incident register: new incidents, safeguarding concerns, GDPR breaches, reputational issues, corrective actions status
• Gate-metric tracking: drilling progress, real-event data, readiness for Month 2, 4 (2026-12-08, 2027-02-08) gates

Escalation Path: Operational issues affecting gates or requiring >€20k spending escalate to the Steering Committee. During alert periods, critical incidents (serious injury, safety failure, reputational crisis) are reported immediately to the incident commander and chair of the Steering Committee; Steering Committee can convene within 24 hours if needed. If an alert threshold or interpretation is contested by a partner or the health system, the public-health deputy convenes a rapid review (24 hours) with relevant partners; if still unresolved, escalates to Steering Committee. Volunteer or staff safety incidents involving police or legal liability are reported immediately to the incident commander and municipal legal counsel; legal counsel advises on escalation to Steering Committee or council.

3. Cooling Center Operations & Accessibility Group

Rationale for Inclusion: Ten independent cooling-center sites require consistent staffing, safety, accessibility and service standards. This group ensures each site meets opening-day readiness, delivers planned hours, maintains accessibility, handles incident response and keeps supplies stocked. It is a specialized operational sub-unit reporting to the incident commander's Operations Team, responsible for the tangible 'refuge network' experience. The Month 4 (2027-02-08) gate (80% planned center hours) depends on this group's execution.

Responsibilities:

• Coordinate contracting and fit-out (water, first-aid kits, AEDs, signage, quiet rooms) at all 10 sites by Month 2 (2026-12-08)
• Conduct accessibility audit of all sites by Month 1.5 (2026-11-23); prioritize 5 fully accessible sites for May opening
• Hire and train cooling-center managers (1 per site) and support staff (1–2 per site) by Month 4 (2027-02-08); conduct health-and-safety orientation and first-aid training
• Operate centers per alert level: Level 1 = standby only; Level 2 = 10:00-20:00 daily; Level 3 = 3 sites extend to 24:00; stand down within 2 hours of end-alert declaration
• Track daily center-hours delivered, occupancy and supply usage; escalate accessibility or staffing gaps within 4 hours
• Respond to incidents at centers (injury, medical emergency, distressed resident): first-aid response, EMS notification if needed, incident log and debrief within 24 hours
• Manage supply chain (water, ice, first-aid kits, toiletries, printed materials) and inventory; order replacement supplies with 2-week lead time

Initial Setup Actions:

• Identify and secure facility-use agreements for all 10 sites by Month 1 (2026-11-08); confirm space, utilities and liability insurance
• Conduct accessibility audit and remediation planning for all sites by Month 1.5 (2026-11-23); prioritize 5 fully accessible sites (≥50% of planned capacity)
• Procure fit-out items (water dispensers, first-aid kits, AEDs, signage, quiet-room setup) and deliver to sites by Month 5 (2027-03-08)
• Recruit and vet cooling-center managers by Month 4 (2027-02-08); assign one manager per site with documented position description
• Conduct opening-day drill at all sites with full staffing, supply checks, accessibility verification and signage by Month 5.5 (2027-03-23)

Membership:

• Center Operations Lead (dedicates 1 FTE, reports to incident commander)
• Cooling-center manager representatives from 3–4 sites (rotates quarterly to ensure input from all 10 sites)
• Supply-chain and inventory coordinator (0.5 FTE, shared with other operations)
• Accessibility consultant or municipal disability-access officer (advisory, spot-check verification)

Decision Rights: Center Operations Lead approves: staffing adjustments within approved budget (hiring, scheduling changes, overtime up to 10% of budgeted hours); site-specific supply orders and emergency purchases <€2k; minor operational changes (e.g., water-distribution points, signage placement) and local accommodation of residents with disabilities. Cannot approve major remediation (>€10k per site), procurement of new equipment types, or changes to opening hours without incident commander approval. Accessibility decisions require review by the accessibility consultant before implementation. If a site is deemed unsafe or inaccessible beyond remediation, Center Operations Lead recommends closure to incident commander; incident commander decides in consultation with Steering Committee.

Decision Mechanism: Center Operations Lead makes routine staffing and supply decisions. Escalations to the incident commander occur if: accessibility or safety issues at a site threaten opening-day readiness, a site manager requests reassignment due to performance or safety concerns, or supply shortages threaten operations. For decisions affecting >3 sites, Center Operations Lead convenes site representatives (≥2 managers) and seeks consensus; if not reached within 24 hours, escalates to incident commander with both the managers' views and the lead's recommendation.

Meeting Cadence: Weekly during Months 1–5 (2026-11-08 to 2027-03-08, setup phase): Tuesdays 14:00 (60 min), covering fit-out, staffing, accessibility audit progress and procurement. Daily during alert days (Months 6–11 = 2027-04-08 to 2027-09-08): Morning briefing 08:00 (15 min) covering center readiness, staffing confirmation and supply status; afternoon debrief 18:00 (30 min) reviewing occupancy, incidents and corrective actions. Weekly on non-alert days during summer: Monday 14:00 (45 min) for supply planning, staffing review and accessibility checks.

Typical Agenda Items:

• Site readiness: facility-use agreement status, remediation progress, fit-out delivery, staffing assignments and training completion
• Accessibility: audit findings by site, remediation timeline and cost, prioritization of fully accessible sites, accessibility-check checklist completion
• Staffing: hiring progress, first-aid and orientation training, manager readiness, rostering for alert days, absence and leave planning
• Operations: center-hours delivered and occupancy by site, supply usage and inventory, incident reports and safety issues, resident feedback and accommodations
• Procurement and budgets: supply-chain status, lead-time risks, inventory turnover, cost tracking
• Equity: coverage of sites by neighborhood deprivation index, accessibility by disability type, language support availability at each site

Escalation Path: Site-specific safety or accessibility issues escalate to Center Operations Lead immediately; if remediation is not feasible within 4 weeks or costs >€10k, escalate to incident commander with options (defer opening, drop site, apply for supplementary funding). Staffing problems (manager unable to work, high absence rate, safety incident involving staff) escalate to incident commander. Supply-chain delays >2 weeks escalate to PMO/procurement coordinator to trigger backup suppliers. If a center fails the accessibility audit and remediation is not feasible, incident commander decides in consultation with Steering Committee whether to proceed with a non-fully-accessible site or defer its opening until remediation is complete. Accessibility consultant may appeal any decision to defer or proceed with non-accessible site to the disability-access ombudsman or local authority if consultation is inadequate.

4. Outreach, Enrollment and Intermediary-Partner Coordination Group

Rationale for Inclusion: High-risk residents are identified and contacted via intermediary partners (housing associations, social services, NGOs, pharmacies) who hold their own data. This group ensures partner readiness, coordinates outreach protocols and scripts, tracks contact-attempt and success-rate data (the Month 4 2027-02-08 gate requires ≥60% success), and manages the 'no wrong door' enrollment mechanism (phone line + in-person at refuges). It also ensures multilingual access, reaches unhoused people via street contact, and navigates the complex GDPR constraints of intermediary-held lists.

Responsibilities:

• Co-design and agree outreach scripts, call targets, escalation rules and feedback mechanisms with each partner by Month 1 (2026-11-08)
• Conduct joint training for all partner outreach staff (50–80 people across housing, social services, NGOs, pharmacies) by Month 2 (2026-12-08); refresher training before June alerts
• Monitor and track partner call volumes, contact attempts and success rates daily on alert days; provide real-time feedback to partners (call target vs. actual, success rate vs. gate threshold)
• Operate the heat-response phone line (08:00–22:00 daily; 24:00 at Level 3): answer enrollment inquiries, provide information on cooling centers and transport, log calls and escalations
• Coordinate street contact (NGO-led rounds for unhoused residents) and drop-in cool points at day centers; track outreach to unhoused cohort separately
• Manage 'no wrong door' intake: accept registrations at phone line and in-person at cooling centers; feed enrollment into transport and outreach dispatch systems
• Ensure multilingual access: coordinate interpretation services for phone line and outreach staff; brief community-language ambassadors; track language diversity in call logs

Initial Setup Actions:

• Identify and sign MOUs with ≥4 key intermediary partners (housing associations, social services, NGOs) by Month 1 (2026-11-08); specify outreach commitments, data terms and escalation contacts
• Draft outreach script (3–5 minute format with escalation rules) in collaboration with partners and nurse adviser by Month 1 (2026-11-08); test with focus groups of older residents by Month 1.5 (2026-11-23)
• Identify top 4–6 non-official languages spoken in the city and commission translation of core materials (flyer, enrollment script, escalation guidance) by Month 1 (2026-11-08)
• Recruit 8–12 community-language ambassadors from migrant associations by Month 1.5 (2026-11-23); brief them on heat illness, centers, transport and protocol by Month 2 (2026-12-08)
• Procure phone line infrastructure, call-tracking software (shared spreadsheet or secure platform) and first-aid/incident-escalation templates by Month 1.5 (2026-11-23); conduct mock-call drills with partners by Month 2 (2026-12-08)
• Agree street-contact protocol with homeless-service NGO partners and co-design referral cards and water/shade provision by Month 1 (2026-11-08)

Membership:

• Outreach and Enrollment Lead (1 FTE, reports to incident commander)
• Phone-line coordinator (1 FTE, reports to outreach lead)
• Partner-liaison officer (if separate from Command-Structure role; else liaison officer split between both groups)
• Representative or contact person from each of ≥4 key intermediary partners (housing association, social service, NGO, pharmacy chain)
• Community-language ambassador representative (rotating, 1 ambassador per month, advisory)

Decision Rights: Outreach Lead approves: script iterations and local language-specific adaptations within the agreed escalation framework; partner-specific call-target adjustments (up to ±20% of planned volume) based on partner feedback and capacity; local accommodation for residents (e.g., preferred language, preferred contact time) within the no-wrong-door protocol. Cannot approve changes to alert thresholds or escalation criteria without incident commander; cannot alter the 60% contact-success gate measurement without Steering Committee; cannot change phone-line hours or escalation path to health services. Partner representatives approve their own staffing decisions and call-volume commitment changes; if a partner proposes to reduce call volume by >20%, escalates to partner-liaison officer and incident commander.

Decision Mechanism: Outreach Lead makes routine enrollment, call-tracking and script decisions. Monthly partner-coordination meetings convene all partner representatives; consensus sought on call targets, script effectiveness and performance feedback; if consensus cannot be reached on a data-sharing or escalation issue, outreach lead proposes a resolution with documented partner input, and incident commander decides. Language and cultural-appropriateness decisions are made by outreach lead with input from community-language ambassadors and focus-group feedback; ambassadors have veto over messaging that is culturally insensitive or medically inaccurate, with escalation to incident commander if overridden.

Meeting Cadence: Weekly during Months 1–5 (2026-11-08 to 2027-03-08, setup and training): Wednesdays 14:00 (90 min) for script finalization, training delivery and materials translation. Bi-weekly during Months 6–8 (2027-04-08 to 2027-06-08, pre-season and early season): Mondays 10:00 (60 min) for phone-line readiness, partner briefing and early-season performance review. Daily during alert days (Months 9–11 = 2027-07-08 to 2027-09-08): Morning briefing 08:00 (10 min) confirming partner call staffing; afternoon debrief 17:00 (30 min) reviewing call volumes, success rates and incidents. Weekly on non-alert days during summer: Friday 14:00 (60 min) for performance tracking, troubleshooting and partner feedback.

Typical Agenda Items:

• Partner readiness: MOUs signed, staffing confirmed, training completed, data-tracking systems set up, access to call-list data from each partner confirmed
• Script and protocol: script effectiveness feedback from partners, escalation decision-making, language-specific adaptations, cultural appropriateness checks
• Phone-line operations: call volume, wait times, interpreter availability, incident escalations, staff fatigue and feedback
• Outreach performance: contact attempts and success rates by partner, comparisons to gate targets, language diversity in calls (≥5% non-official language target), difficult-to-reach populations
• Enrollment and no-wrong-door: in-person intake at cooling centers, phone-line registrations, duplicate prevention, data quality checks
• Street contact and unhoused: NGO round volumes, outreach to unhoused residents, referrals to centers and transport, incident reports
• Multilingual access: interpretation-service utilization and cost, translation quality feedback, ambassador recruitment and briefing progress, pictogram effectiveness
• GDPR and data protection: partner compliance audit schedule, consent-withdrawal log, data-retention timeline, breach-notification protocol

Escalation Path: Partner capacity issues or call-volume shortfalls escalate to partner-liaison officer; if a partner cannot meet ≥40% of target calls, incident commander evaluates remediation (additional support, reduced target, partner replacement). Phone-line staffing or infrastructure failures escalate to outreach lead immediately; if outages exceed 2 hours, incident commander is notified and backup protocols activated (e.g., SMS registration, in-person-only intake). Contact-success rate trending <60% triggers real-time adjustment: script review, partner debriefing, target reassessment and extra briefing by end of week. Language-access gaps (>5% of calls cannot be answered in the resident's language) escalate to outreach lead with 5-working-day remediation plan (additional interpreter, ambassador deployment). GDPR compliance concerns (e.g., partner data breach, unauthorized contact) escalate immediately to legal counsel and GDPR adviser; incident commander and Steering Committee notified if breach is serious or affects >100 residents.

5. Transport Coordination and Dispatch Group

Rationale for Inclusion: The transport system (volunteer drivers + taxi backup) determines whether the Month 4 (2027-02-08) gate of <45-minute average pickup time is met. This group recruits and manages volunteer drivers, coordinates with taxi operators, dispatches rides during alert days, and ensures wheelchair-accessible transport for mobility-limited residents. Transport is a critical bottleneck: if volunteer recruitment falls short or taxi retainers are insufficient, the entire gate fails, and home-kit budget gets cut. This group must operate with reliable metrics, clear prioritization and responsive escalation.

Responsibilities:

• Recruit, vet (background checks, insurance, safeguarding) and train volunteer drivers (target 40, range 30–50) by Month 2 (2026-12-08); conduct refresher training before June
• Manage volunteer-driver insurance and liability; conduct biannual safety reviews of volunteer fleet
• Sign standby-retainer contract with taxi/accessible-transport operator (capped €80k, ≥10 vehicles within 20 min, ≥3 wheelchair-capable) by Month 1.2 (2026-11-14); manage taxi-operator performance
• Operate dispatch center: answer transport requests, confirm destination (cooling center choice), prioritize elderly and mobility-limited residents (target 30-min pickup), general residents (target 45-min), log all requests and actual response times
• Ensure wheelchair-accessible vehicles are matched to wheelchair-user requests; track accessibility-accommodation success rate
• Track daily requests, response times, volunteer-vs-taxi utilization, failed requests and reasons; escalate gaps to incident commander
• Manage volunteer coordination: rostering, absence coverage, fuel/mileage reimbursement, incident reporting and debrief if volunteers encounter distressed residents

Initial Setup Actions:

• Identify and vet potential volunteer drivers from community networks (retirees, charity staff, faith groups) by Month 0.5 (2026-10-23); launch recruitment campaign by Month 0.8 (2026-11-01)
• Design volunteer vetting process (background check, driving-history review, safeguarding check, insurance verification) and conduct batch vetting (monthly cohorts) beginning Month 1 (2026-11-08)
• Procure taxi/accessible-transport standby retainer and sign contract by Month 1.2 (2026-11-14); include performance-measure clauses (response time <20 min, vehicle availability ≥80%, wheelchair-accessible vehicles ≥3)
• Establish dispatch infrastructure: phone line with call-logging, volunteer driver contact list, taxi operator hotline, shared real-time tracking spreadsheet or app, maps of cooling centers and travel times
• Recruit dispatch coordinator and backup dispatcher by Month 3 (2027-01-08); conduct dispatch training and mock-drill by Month 3.5 (2027-01-23)

Membership:

• Transport Lead / Dispatch Coordinator (1 FTE, reports to incident commander)
• Backup dispatcher (1 FTE)
• Volunteer driver representative (rotating, 1 volunteer per month, advisory)
• Taxi-operator contract manager (external, coordinated by transport lead)
• Accessibility advocate or disability-access officer (advisory, quarterly vehicle-access audits)

Decision Rights: Transport Lead approves: volunteer driver scheduling and roster adjustments; mileage/fuel reimbursement within budget; taxi-operator escalation (performance complaints, vehicle failures); local routing and destination changes per resident preference (e.g., preferred center). Cannot approve changes to response-time gates (30 min for priority, 45 min average), volunteer recruitment targets or taxi retainer terms without incident commander. Cannot commit >€5k for emergency transport or vehicle rental without incident commander approval. Volunteer representatives provide feedback on driver experience; taxi operator commits to service-level targets; both can escalate performance concerns to transport lead with 24-hour response required.

Decision Mechanism: Transport Lead makes routine dispatch and volunteer-management decisions. Volunteer-recruitment strategy and targets are set by transport lead with incident commander (Month 0.5 = 2026-10-23). Taxi-operator performance disputes are reviewed monthly by transport lead; if unresolved, escalate to incident commander. Priority-resident pickup (30-min target for mobility-limited) overrides general requests within dispatcher authority; if dispatch system cannot meet 30-min target >10% of the time, transport lead convenes emergency review with volunteers and taxi operator to identify and fix bottlenecks within 2 days.

Meeting Cadence: Weekly during Months 0–5 (2026-10-08 to 2027-03-08, recruitment and setup): Thursdays 14:00 (60 min) covering volunteer recruitment pipeline, vetting cohort schedule, taxi-contract negotiation and dispatch-infrastructure setup. Bi-weekly during Months 6–8 (2027-04-08 to 2027-06-08, pre-season): Thursdays 10:00 (45 min) for volunteer training, rosters, taxi-operator readiness and transport stress-test planning. Daily during alert days (Months 9–11 = 2027-07-08 to 2027-09-08): Dispatch briefing 07:30 (10 min) confirming volunteer and taxi availability; afternoon debrief 18:00 (30 min) reviewing request volumes, response times, accessibility matches and incidents. Weekly on non-alert days: Thursday 14:00 (60 min) for performance metrics, route optimization and volunteer feedback.

Typical Agenda Items:

• Volunteer recruitment and vetting: recruitment campaign results, vetting-cohort completion, signed agreements, insurance verification, training status
• Volunteer rostering and management: scheduling for alert days, absence coverage, fuel/mileage reimbursement tracking, incident reports and debriefings, retention feedback
• Taxi-operator performance: request fulfillment, response times, vehicle availability, wheelchair-accessible vehicle deployment, incident reports, contract compliance
• Dispatch operations: daily request volume and response times, volunteer vs. taxi utilization ratio, failed requests and reasons, priority-resident pickup success (30-min target)
• Accessibility: wheelchair-user request matching, vehicle-access audit results, accessibility-accommodation success rate, resident feedback
• Transport stress test (pre-season May drill): simulated request volume, dispatch load, response-time achievement, bottleneck identification and fixes
• Financial tracking: volunteer mileage/fuel reimbursement, taxi-operator invoice reconciliation, budget forecast

Escalation Path: Volunteer-recruitment shortfalls (pipeline <20 drivers by Month 1.5 = 2026-11-23) trigger taxi-retainer scale-up (capped €80k); transport lead proposes adjustment, incident commander approves. Volunteer safety incidents (assault, accident, safeguarding concern) escalate immediately to transport lead and incident commander; occupational health and legal counsel notified. Taxi-operator performance failures (response time >30 min >25% of the time, vehicle unavailability) are escalated to taxi operator with 48-hour remediation plan; if unresolved, incident commander considers contract termination or reduced reliance on volunteers. Accessibility failures (>1 wheelchair user cannot be transported within <45 min) trigger immediate review and extra wheelchair-capable taxi deployment. If average response time exceeds 45 minutes for >1 consecutive alert day, incident commander convenes emergency review with transport lead, volunteers and taxi operator within 24 hours to identify causes and corrective actions; failure to achieve <45 min within 3 days escalates to Steering Committee as gate risk.

6. Home Kit Distribution, Installation and Quality Assurance Group

Rationale for Inclusion: The home-kit program (shading, fans, thermometers, hydration supplies) reaches 2,000 high-risk homes (top-floor, poorly insulated, elderly, isolated). This group manages procurement, targeting, installation scheduling, handyperson vetting, and quality checks (particularly fan-safety). Installation must complete by Month 7.3 (2027-05-17) to benefit from the first heat events. The group also tracks equity metrics (coverage by neighborhood, housing type, age), manages supply logistics, and ensures GDPR compliance in the targeting process (no unauthorized access to vulnerability scores).

Responsibilities:

• Develop and maintain household-targeting rubric (score 0-100: top-floor 30 pts, age ≥75 25 pts, living alone 20 pts, pre-1980 15 pts, no AC 10 pts; ≥60 for kit eligibility) based on Consent-Light Identification Routes data
• Identify eligible households from enrolled high-risk residents and partner lists; verify consent before approaching; generate installation schedules by neighborhood and housing block
• Procure cooling kits (exterior shading, reflective blinds, fans, thermometers, hygrometers, hydration supplies) with 30–40% first call-off by Month 1.2 (2026-11-14); stagger deliveries to meet Feb, Mar, Apr, Jun targets
• Recruit, vet and train handypersons (target 10 FTE for Months 4–7 = 2027-02-08 to 2027-05-08) in installation safety, fan-use guidance and building-code compliance by Month 3 (2027-01-08)
• Schedule and execute home installations with consent, accessibility accommodation (no multi-floor climbs for elderly) and safety checks (fan testing, shading wind resistance, electrical safety); provide written guidance to residents on safe use (translated)
• Conduct quality-assurance inspections of 10–20% of installations (random sample + risk-based high-floor sites) by external QA auditor; log any issues and corrective actions within 5 days
• Track and report equity metrics: % installed by neighborhood deprivation index, housing type (social vs. private rental vs. owner-occupied), age band and language; identify and close coverage gaps by June

Initial Setup Actions:

• Obtain partner contact lists (housing associations, social services) and enrolled high-risk residents by Month 0.5 (2026-10-23)
• Finalize household-targeting rubric and validate against sample population by Month 1 (2026-11-08); check GDPR compliance of rubric (no sensitive data stored outside consent scope)
• Issue procurement specs for kits by Month 0.8 (2026-11-01); place first call-off order (30–40%) by Month 1.2 (2026-11-14); arrange storage by Month 3 (2027-01-08)
• Identify and vet handyperson service providers or recruit individual handypersons (employment vs. contract) by Month 2.5 (2026-12-23); conduct safety and installation training by Month 3 (2027-01-08)
• Design home-installation packet: consent form, scheduling letter, safety guidance, installation checklist and follow-up; translate into 4–6 languages by Month 2 (2026-12-08)

Membership:

• Home Kit Lead / Installation Coordinator (1 FTE, reports to incident commander)
• Procurement and logistics coordinator (0.5 FTE, shared with general procurement)
• Handyperson supervisor (1 FTE, manages 10-person team)
• Quality-assurance auditor (0.5 FTE external or internal, spot-check inspections)
• Equity analyst or data coordinator (0.5 FTE, tracks coverage metrics)
• Housing-sector representative from a key partner (advisory, site-access and landlord-cooperation facilitation)

Decision Rights: Home Kit Lead approves: household eligibility assessments per the agreed rubric; installation scheduling and route optimization; handyperson assignments and rescheduling; quality-assurance findings and corrective-action authorization (up to €500 per fix). Cannot alter the targeting rubric or equity metrics definitions without Steering Committee (data-governance and fairness decision). Cannot commit >€5k for emergency kit procurement or expedited delivery without incident commander. Handyperson supervisor approves: work scheduling, overtime, tool and supply management, and preliminary safety checks before formal QA. QA auditor has veto over any installation deemed unsafe (fan misuse, shading wind-resistance failure, electrical hazard); veto escalates immediately to Home Kit Lead and incident commander for remediation or re-do.

Decision Mechanism: Home Kit Lead makes routine targeting, scheduling and quality decisions. Eligibility disputes (e.g., a resident just below the 60-point rubric threshold but clearly vulnerable) are escalated to Home Kit Lead with partner input; lead decides with documented rationale (e.g., 'approved despite 58 points due to note from GP of severe cardiac disease'). Equity coverage gaps (e.g., <5% of kits in highest-deprivation neighborhoods by Month 6 = 2027-04-08) trigger review by home kit lead and equity analyst; if closure plan is inadequate, escalates to incident commander and outreach lead for outreach-targeted recruitment into the target neighborhoods. Handyperson safety or performance issues escalate to handyperson supervisor; if unresolved within 24 hours, escalate to home kit lead.

Meeting Cadence: Weekly during Months 0–3 (2026-10-08 to 2027-01-08, procurement and planning): Mondays 14:00 (60 min) for rubric finalization, procurement specs and handyperson recruitment. Weekly during Months 4–7 (2027-02-08 to 2027-05-08, installation): Mondays 10:00 (90 min) covering scheduling, supply delivery, handyperson deployment, quality-assurance findings and equity-coverage tracking. Bi-weekly during Months 8–11 (2027-06-08 to 2027-09-08, post-installation): Mondays 14:00 (45 min) for final coverage reports, lessons learned and follow-up surveys.

Typical Agenda Items:

• Targeting and eligibility: rubric validation, household-list generation, consent status by partner, enrollment growth vs. installation targets
• Procurement and logistics: kit delivery schedules, storage utilization, backup supplier status, lead-time risks, cost tracking
• Handyperson recruitment and training: hiring progress, training completion, safety protocols, incident reports, performance feedback
• Installation scheduling and execution: weekly installation targets, neighborhoods covered, appointment confirmations, accessibility accommodations (e.g., elderly mobility limits), resident feedback
• Quality assurance: inspection results, defect rates, corrective-action log, safety incidents, re-do or remediation completion
• Equity metrics: installations by neighborhood deprivation, housing type, age band, language; comparison to targets; coverage-gap analysis and closure plans
• Follow-up and resident satisfaction: post-installation surveys, safe-use guidance effectiveness, complaints or misuse reports

Escalation Path: Supply-chain delays (first call-off delivery >2 weeks late) escalate to procurement coordinator and incident commander; backup suppliers triggered if delay exceeds 3 weeks. Handyperson recruiting shortfalls (fewer than 7 of 10 FTE recruited by Month 3 = 2027-01-08) escalate to home kit lead; contingency: contract temporary labor or reduce installation targets. Installation-pace shortfalls (trajectory shows <80% completion by Month 7 = 2027-05-08) trigger schedule tightening and overtime authorization by home kit lead; if still on track to miss target, escalates to incident commander. Quality-assurance failures (>10% of inspected installations unsafe) trigger remedial training and re-work; if defect rate persists, handyperson supervisor and affected providers are reviewed for replacement. Equity-coverage gaps (highest-deprivation neighborhoods <30% of target by Month 6 = 2027-04-08) escalate to outreach lead for additional targeted enrollment; if closure plan unavailable within 1 week, escalates to incident commander and Steering Committee as equity risk.

7. Legal, GDPR Compliance and Data Protection Group

Rationale for Inclusion: This is a high-risk program handling personal data from intermediary partners, consent protocols, and partner data-processing agreements. GDPR compliance is a hard constraint; any significant breach or challenge could halt outreach mid-season. This group ensures pre-cleared data-processing agreements with each partner type, audits partner compliance mid-season, manages breach notification, and oversees data retention and deletion. It is a specialized assurance body reporting to the Steering Committee and supporting the incident commander's operations.

Responsibilities:

• Engage GDPR legal counsel by Month 0.5 (2026-10-23); obtain legal opinion on intermediary-held list model and consent basis by Month 1 (2026-11-08)
• Draft template data-processing agreements (DPAs) for housing associations, social services, NGOs and pharmacies specifying lawful basis (public task + consent hybrid typical), data scope (contact details and risk flags only, no health records), retention (one season, delete after), and breach notification (<48 hours)
• Obtain partner sign-off on DPAs by Month 1.5 (2026-11-23); brief partner staff on GDPR obligations and confidentiality by Month 2 (2026-12-08); document training attendance
• Conduct data-protection impact assessment (DPIA) screening for the program; if higher risk (unlikely given intermediary model), commission full DPIA by Month 1.5 (2026-11-23)
• Audit partner GDPR compliance at Month 9 (2027-07-08): spot-check consent records (≥20 files per partner), staff confidentiality training logs, data-retention status and any disclosed breaches; issue audit report with corrective-action requests
• Establish breach-reporting hotline and incident log; if breach reported, assess impact within 24 hours and notify data-protection authority within 48 hours if required (>100 individuals at high risk); notify affected residents within 5 days
• Oversee data deletion at season end (by October 31, Month 13 = 2027-11-08, unless re-consent obtained)

Initial Setup Actions:

• Retain GDPR specialist legal firm by Month 0.5 (2026-10-23) (estimated cost €20k–30k for advice + DPA drafting)
• Brief legal firm on intermediary-held list model, partner types, expected data types and retention needs by Month 0.7 (2026-10-29)
• Receive and review legal opinion on lawful basis and DPA template by Month 1 (2026-11-08); incorporate feedback and customize DPAs for each partner type
• Distribute DPA drafts to partners by Month 1.3 (2026-11-17) with 2-week sign-off target; resolve partner queries by Month 1.5 (2026-11-23)
• Conduct DPIA screening by Month 1 (2026-11-08); commission full DPIA if required by Month 1.3 (2026-11-17)

Membership:

• Legal and GDPR Lead (0.5–1 FTE, reports to Steering Committee and incident commander, likely shared with municipal legal department)
• GDPR specialist legal counsel (external retainer, available for advice on breaches, interpretation disputes)
• Data-protection officer (if the city has a DPO; else legal lead assumes this role)
• Partner representative from each partner type (advisory, DPA compliance and feedback)

Decision Rights: Legal lead approves: final versions of DPAs and partner briefing materials; DPIA screening and determination (full DPIA needed or not); breach-notification decisions (authority notification required or not); data-retention and deletion schedules; staff confidentiality training content and verification; audit findings and corrective-action requests to partners. Cannot approve operational decisions that have legal implications (e.g., change to data scope, alteration of lawful basis) without consulting GDPR legal counsel. Cannot override GDPR counsel's legal opinion; if counsel is consulted and gives advice, legal lead must follow unless Steering Committee overrides (documented with funder notification). Partners cannot opt out of DPA compliance; non-compliance is an enforcement matter handled by legal lead with incident commander escalation.

Decision Mechanism: Legal lead makes routine GDPR and data-protection decisions (training, audit scheduling, breach assessment). GDPR counsel and legal lead consult on novel or contentious issues (e.g., expanded data scope, new partner type); legal counsel advises, legal lead decides with incident commander. Partner DPA disputes (e.g., partner claims data scope is too broad) are addressed first by legal lead with partner; if unresolved, escalates to incident commander and then Steering Committee if necessary. Breach investigations are led by legal counsel with legal lead oversight; incident commander and Steering Committee kept informed.

Meeting Cadence: Weekly during Months 0–2 (2026-10-08 to 2026-12-08, setup phase): Thursdays 10:00 (60 min) for legal opinion development, DPA drafting and partner briefing preparation. Bi-weekly during Months 3–8 (2027-01-08 to 2027-06-08): Thursdays 14:00 (45 min) for compliance monitoring, staff training verification and incident log review. Monthly during Months 9–12 (2027-07-08 to 2027-10-08, audit and closure): Thursdays 14:00 (45 min) for audit findings, partner corrective actions and data-deletion planning.

Typical Agenda Items:

• GDPR counsel advice: interpretation of lawful basis, DPA compliance, partner questions, novel scenarios or disputes
• DPA status: partner sign-off progress, outstanding negotiations, execution deadlines
• Partner compliance: training attendance logs, data-access controls, file-security verification, incident-awareness surveys
• DPIA and risk assessment: screening results, full DPIA scope (if required), residual risks, mitigation actions
• Breach management: incident log review, breach reports received, assessment and authority-notification decisions, affected-resident notification
• Staff and partner training: confidentiality-briefing attendance, training content updates, re-training scheduling
• Data deletion and retention: end-of-season deletion schedule, resident opt-in renewals for Year 2 (if applicable), data-archival for evaluation (stripped of identifiers)

Escalation Path: Novel or contentious GDPR issues escalate to GDPR legal counsel; counsel's written advice is binding on legal lead unless overridden by Steering Committee (with funder and data-protection authority notification). Serious breaches (>100 residents, health data exposed, or deliberate misuse) escalate immediately to legal counsel, legal lead and incident commander; Steering Committee notified; data-protection authority notified within 48 hours if required by law. Partner non-compliance (e.g., unauthorized contact of residents, data breach, failure to train staff) is first addressed by legal lead with incident commander; if unresolved within 10 days, escalates to Steering Committee for enforcement (contract termination, remedial supervision, or referral to data-protection authority). Any request to expand data scope or alter consent basis escalates to legal counsel and Steering Committee for approval.

8. Evaluation, Data Quality and Playbook Documentation Group

Rationale for Inclusion: Month 12 (2027-10-08) deliverables include a repeatable Heat Response Playbook, a scaling cost model and a credible evaluation report on heat-related EMS calls, ED visits and mortality. This group ensures baseline data quality (Months 0–1 = 2026-10-08 to 2026-11-08), coordinates the evaluation design with a university partner, tracks outcome data throughout the season, produces the Month 4 (2027-02-08) gate-review evidence, and synthesizes lessons learned into the playbook. It is a specialized analytical group reporting to the Steering Committee and supporting the incident commander's after-action reviews.

Responsibilities:

• Obtain or estimate baseline heat-related EMS calls and ED visits and excess mortality data from hospitals/EMS; conduct data-quality audit by Month 1 (2026-11-08); agree on heat-attribution coding with clinical partners by Month 2 (2026-12-08)
• Negotiate a data-processing agreement with hospitals, EMS and primary care for daily aggregate heat-related counts (no identifiable records); establish a secure data-sharing method (email, SFTP, API) and a daily 10:00 a.m. delivery target by Month 1 (2026-11-08)
• Conduct a 2-week data-validation pilot in April (Month 6 = 2027-04-08) to test reporting process and identify IT/coding gaps before the season; agree on a fallback method (weekly if daily unavailable) by Month 1.5 (2026-11-23)
• Define evaluation design: baseline vs. pilot heat-days (post-stratified by temperature or matched district comparisons), aggregate EMS/ED counts, excess mortality estimation with temperature adjustment and confidence intervals; pre-specify analysis plan by Month 3 (2027-01-08)
• Convene a university evaluation partner under a data-processing agreement; partner conducts independent analysis and publishes findings regardless of direction by Month 12 (2027-10-08); provides a pre-registration of the analysis plan by Month 3 (2027-01-08)
• Compile all operational-performance data (gate metrics: center hours, outreach success, transport time; equity metrics: coverage by neighborhood and housing type; staffing and budget data) into a project database by Month 4 (2027-02-08) for gate review and later playbook costing
• Draft the Heat Response Playbook from Month 8 (2027-06-08) onward; include SOPs, decision trees, checklists, procurement specs, staffing plans, partner MOUs, cost breakdowns and lessons learned; conduct peer-city review by Month 11 (2027-09-08); finalize by Month 12 (2027-10-08)

Initial Setup Actions:

• Request baseline EMS and mortality data from hospitals and EMS by Month 0 (2026-10-08); establish data custodian role and request timelines
• Conduct rapid baseline data-quality audit (completeness, coding consistency, signal reliability) by Month 1 (2026-11-08); document any limitations
• Identify a university or public-health research partner (estimated cost €50k–80k for evaluation services); draft a research-collaboration agreement and data-processing agreement by Month 0.8 (2026-11-01)
• Design and agree evaluation plan with university partner and hospital/EMS clinical leads by Month 2.5 (2026-12-23); finalize by Month 3 (2027-01-08)
• Establish a secure data-sharing infrastructure (encrypted email or SFTP) with hospitals/EMS for daily aggregate counts; begin daily data collection by Month 1.8 (2026-12-02)
• Develop a playbook outline and assign sections by Month 7 (2027-05-08); begin drafting from Month 8 (2027-06-08) with lessons captured in real-time

Membership:

• Evaluation and Playbook Lead (0.5–1 FTE, reports to Steering Committee, may be shared with municipal public health or contracted to evaluation partner)
• University evaluation partner: epidemiologist or health-services researcher (lead analyst and publication lead)
• Data analyst (0.5–1 FTE municipal or partner staff, data extraction, quality assurance, database management)
• Health-system data custodian (hospital or EMS representative, provides baseline and ongoing outcome data)
• Incident commander and operations team (source of operational-performance data and lessons learned)

Decision Rights: Evaluation Lead approves: baseline data-quality assessments, coding-agreement decisions with clinical partners, evaluation-design specification and analysis-plan finalization with university partner. Cannot alter the fundamental comparison design or attribution methodology without Steering Committee and university partner approval (analytical integrity). Cannot release preliminary or final evaluation findings without university partner review and approval (to ensure scientific integrity). Operational groups approve what data gets extracted and shared for evaluation (performance metrics, program costs); cannot be forced to share data outside the agreed scope without legal/GDPR clearance. University partner has full editorial autonomy over the final evaluation report; findings cannot be suppressed or reframed by the municipality.

Decision Mechanism: Evaluation Lead and data analyst make routine data-quality and extraction decisions. Novel methodological questions (e.g., how to account for weather variation in heat-death attribution) are escalated to the university partner for expert advice. Data-collection failures or quality issues are escalated to health-system data custodian with 5-working-day remediation target; if unresolved, escalates to incident commander and Steering Committee for leverage. The university partner retains full autonomy over analytical decisions (statistical methods, interpretation of results); if the city disagrees with a finding, the disagreement is documented and published alongside the main report, but the finding is not suppressed.

Meeting Cadence: Monthly during Months 0–3 (2026-10-08 to 2027-01-08, design): Fridays 14:00 (60 min) for baseline-data review, partner agreement and evaluation-plan finalization. Bi-weekly during Months 4–7 (2027-02-08 to 2027-05-08, data collection): Fridays 10:00 (45 min) for data-quality checks, coding-process updates and gate-evidence compilation. Weekly during Months 8–11 (2027-06-08 to 2027-09-08, playbook drafting): Fridays 14:00 (60 min) for section drafting, lessons-capture, cost-model development and peer-city review. Monthly during Month 12 (2027-10-08): Final report, playbook and deliverable finalization.

Typical Agenda Items:

• Baseline data: completeness checks, coding agreement with clinical partners, historical patterns and seasonality, confidence-interval estimates for small areas
• Data-sharing infrastructure: hospital/EMS system testing, daily-count delivery confirmation, data-quality monitoring, holiday/staffing coverage for data delivery
• Evaluation design: comparison methodology, temperature adjustment, statistical power, sample-size sufficiency, pre-registered analysis plan, limitations and caveats
• Gate evidence: operationalization of the three gate metrics (center hours, outreach success, transport time), data-collection protocol, drill vs. real-event evidence weighting
• Ongoing outcome data: daily heat-related EMS and ED counts, weekly trend analysis, seasonal patterns, attribution to program activities (attribution challenges and caveats)
• Operational data compilation: center-hours tracking by site, outreach-attempt and success-rate log, transport-request and response-time log, kit-installation progress, staffing and budget by category
• Equity analysis: coverage by neighborhood deprivation, housing type, age band, language; comparison to target groups; outlier neighborhoods with low coverage
• Playbook development: section completion, lessons-learned capture from operations, cost-model development (unit costs per person, per center-hour, per kit), replicability guidance for peer cities
• University partner coordination: progress on analysis, preliminary findings, final-report timeline, data-archival and secondary-use agreements

Escalation Path: Baseline-data quality issues (e.g., <80% of heat-related cases are coded consistently) escalate to health-system data custodian and incident commander for remediation; if unresolved, data limitations are documented in the final report and caveats added to gate-review evidence. Data-sharing failures (e.g., hospital cannot provide daily counts due to IT constraints) escalate to Steering Committee for negotiation or fallback method (weekly aggregate). Evaluation-design disputes (e.g., comparison group selection methodology contested by partners) are resolved by the university partner's expert judgment; if the city disputes a decision, documented disagreement is published alongside the final report. Gate-evidence interpretation disputes (e.g., drill results vs. real-event data weighted differently) are decided by the Steering Committee with Evaluation Lead and university partner input. Playbook draft-section disputes (e.g., partners disagree with how their role is documented) are escalated to incident commander for facilitated resolution; final authority rests with Evaluation Lead and playbook editor, who may include dissenting partner commentary in an appendix.

Governance Implementation Plan

1. Senior municipal leadership (mayor's chief of staff or delegated executive) formally designates the incident commander, public-health deputy, operations lead, communications lead and partner-liaison officer. Issue written position descriptions, delegations of authority, and escalation rules specific to each role. Confirm each person's availability for Months 0–12 (2026-10-08 to 2027-10-08) and establish their direct reporting lines to the mayor's office.

Responsible Body/Role: Mayor's office or delegated chief executive (pre-project senior leadership), supported by municipal HR director.

Suggested Timeframe: By end of Month 0.5 (2026-10-23). Early designation ensures clarity and allows concurrent recruitment and legal setup.

Key Outputs/Deliverables:

• Written appointment letters or position confirmations for 5 lead roles
• Role-specific position descriptions and delegations of authority
• Escalation and decision-authority matrix signed by mayor or delegate
• Confirmed start dates and contact details for each lead

Dependencies:

• Project approval and budget release by city council or mayor
• Organizational readiness to assign FTE capacity to these roles

2. Project Manager or incident commander engages a GDPR specialist legal firm by written contract. Scope: review the intermediary-held list model, draft data-processing agreement templates for housing associations, social services, NGOs, and pharmacies, assess lawful basis for contact, and advise on risk mitigation. Set budget ceiling (≤€30k estimate) and delivery deadline (legal opinion by Month 1 = 2026-11-08).

Responsible Body/Role: Incident commander (newly designated), with support from municipal legal department and procurement.

Suggested Timeframe: Within 1 week of incident commander's appointment (Month 0.3–0.5 = 2026-10-15 to 2026-10-23).

Key Outputs/Deliverables:

• Signed GDPR counsel retainer agreement
• Documented scope and deliverables list
• Budget and timeline agreement
• Counsel contact and escalation protocol

Dependencies:

• Incident commander designated
• Budget authorization for legal services (€20k–30k estimate)

3. Incident commander convenes the Project Management Office (PMO) core team: project coordinator (FTE), HR/recruitment coordinator (0.5 FTE), procurement specialist (0.5 FTE), and partner-liaison officer. Establish shared workspace (desks, email lists, shared drives), daily standup schedule (09:00, 15 min), weekly planning meeting (Mondays 14:00, 60 min), and communication protocols (escalation hotline, incident log). Publish project charter and governance-body establishment roadmap to all team members.

Responsible Body/Role: Incident commander, supported by HR director for staff allocation.

Suggested Timeframe: Within 2 weeks of incident commander appointment (Month 0.5–0.7 = 2026-10-23 to 2026-11-05).

Key Outputs/Deliverables:

• PMO workspace established with shared digital infrastructure
• Core team roles confirmed and responsibilities documented
• Standup and planning meeting schedules published and confirmed
• Project charter and governance-body roadmap distributed to all stakeholders

Dependencies:

• Incident commander designated
• Budget availability for PMO staffing

4. Municipal legal department and GDPR counsel jointly draft template data-processing agreements (DPAs) and memoranda of understanding (MOUs) for each partner type: housing associations, social services, NGOs, and pharmacies. DPAs specify lawful basis (public-task/consent hybrid, to be confirmed by counsel), data scope (contact details and risk flags only, no health records), retention (one season, October–September), and breach notification (within 48 hours). Counsel issues written legal opinion on intermediary-held list model and consent basis by Month 1 (2026-11-08).

Responsible Body/Role: GDPR specialist legal counsel (external retainer) and municipal legal lead (internal, 0.5 FTE).

Suggested Timeframe: Drafts completed by Month 1 (2026-11-08); legal opinion delivered by same date.

Key Outputs/Deliverables:

• Template DPA for housing associations (draft)
• Template DPA for social services (draft)
• Template DPA for NGOs (draft)
• Template DPA for pharmacies (draft)
• Written legal opinion on lawful basis and GDPR compliance
• Recommended revisions and clarifications

Dependencies:

• GDPR counsel retainer signed
• Municipal legal department engaged

5. Project coordinator issues procurement specifications for cooling kits (exterior shading, reflective blinds, fans, thermometers, hygrometers), handyperson installation services, and transport infrastructure (phone line systems, call-tracking software, dispatch coordination tools). Specifications must include required delivery dates (first tranche February, second tranche by April), quality standards, and sustainability/reuse clauses. Contact leading 3–5 suppliers per category to confirm availability and lead times; document responses.

Responsible Body/Role: Project coordinator and procurement specialist, with input from Home Kit Lead (once designated; interim coordination via project manager).

Suggested Timeframe: Specifications issued by Month 0.8 (2026-11-01); supplier contact and lead-time confirmation by Month 1 (2026-11-08).

Key Outputs/Deliverables:

• Kit procurement specification document (v0.1)
• Handyperson service specification
• Transport/dispatch infrastructure specification
• Supplier lead-time and availability summary

Dependencies:

• Project PMO established
• Budget allocation for kits and services confirmed

6. Incident commander and public-health deputy jointly set and document heat-alert trigger thresholds per the strategic decision (Alert Trigger Ladder). Thresholds: Level 1 Advisory (forecast high ≥33°C or night low ≥20°C on ≥2 consecutive days), Level 2 Alert (high ≥35°C and low ≥22°C for ≥2 consecutive days), Level 3 Emergency (same as Level 2 for ≥3 days or national red warning). Publish thresholds to Steering Committee and all partners. Coordinate with national meteorological service (AEMET) to confirm forecast data access and delivery schedule.

Responsible Body/Role: Incident commander and public-health deputy (newly designated).

Suggested Timeframe: By end of Month 1 (2026-11-08).

Key Outputs/Deliverables:

• Documented alert-trigger thresholds (Level 1, 2, 3) with decision rationale
• Confirmation of forecast data access from AEMET
• Alert decision-tree flowchart and decision authority assignment
• Internal briefing memo for Steering Committee members

Dependencies:

• Incident commander and public-health deputy designated
• Strategic decision on Alert Trigger Ladder finalized

7. Incident commander prepares a formal agenda, membership list, and standing-meeting schedule for the Heat Response Steering Committee. Confirm availability and meeting commitment from mayor or chief executive (Chair), public-health deputy (Vice-Chair), civil protection director, communications director, municipal finance director and external evaluation partner (advisor). Send meeting invitations and confirm attendance for the first meeting (Month 1.3 = 2026-11-17).

Responsible Body/Role: Incident commander with support from municipal chief of staff or executive assistant.

Suggested Timeframe: By Month 1.2 (2026-11-14).

Key Outputs/Deliverables:

• Steering Committee charter and ToR (v0.1)
• Confirmed membership list with role titles and contact details
• Standing-meeting schedule (monthly, then bi-weekly, then monthly per project phases)
• Agenda template and decision-logging template
• Written calendar invitations sent and RSVPs confirmed

Dependencies:

• Incident commander designated
• Governance-body descriptions from governance-phase2-bodies.json available

8. HR coordinator launches formal recruitment for all governance-body roles and core staff: Cooling Center Operations Lead (1 FTE), Outreach and Enrollment Lead (1 FTE), Transport Lead / Dispatch Coordinator (1 FTE), Home Kit Lead / Installation Coordinator (1 FTE), Legal and GDPR Lead (0.5–1 FTE, may be municipal legal department role). Publish job descriptions, advertise via municipal channels and relevant professional networks, set application deadline (end of Month 1 = 2026-11-08), and plan interviews for Month 1.3–1.5 (2026-11-17 to 2026-11-30).

Responsible Body/Role: HR coordinator (0.5 FTE, designated by incident commander) and municipal HR director.

Suggested Timeframe: Recruitment launched by Month 0.8 (2026-11-01); interviews completed by Month 1.5 (2026-11-23).

Key Outputs/Deliverables:

• Job description documents for 5 lead roles
• Published recruitment announcements
• Interview panel composition and schedule
• Shortlist of candidates by role

Dependencies:

• Incident commander and HR coordinator appointed
• Budget allocation for lead roles confirmed

9. First meeting of the Heat Response Steering Committee: Incident commander briefs on project status, governance-structure setup, legal-review scope and timeline, and procurement plan. Steering Committee formally approves: (1) alert-trigger thresholds (Level 1, 2, 3); (2) alert-declaration delegation and backup authority; (3) GDPR legal-review scope and budget; (4) procurement route and spending authority (frameworks + below-threshold for tranche 1). Committee confirms monthly meeting cadence during setup (Months 0–4 = 2026-10-08 to 2027-02-08). Document all approvals and decisions.

Responsible Body/Role: Heat Response Steering Committee (majority vote, Chair has tie-breaker; quorum 4 of 6 members including Chair or Vice-Chair).

Suggested Timeframe: Month 1.3 (2026-11-17); allow 1 week for scheduling after membership confirmed.

Key Outputs/Deliverables:

• Steering Committee meeting minutes with formal approvals
• Signed alert-declaration delegation letter
• Approved GDPR legal-review scope and budget authorization
• Approved procurement route and authority matrix
• Distribution of decisions to all stakeholders and departments

Dependencies:

• Steering Committee membership confirmed and first meeting scheduled
• Alert thresholds and delegation drafted for approval
• GDPR legal review initiated

10. Partner-liaison officer identifies and initiates formal engagement with ≥4 key intermediary partners: housing associations, social services, NGOs and pharmacy chains. Send introductory letters explaining the program, data-protection model (intermediary-held lists, no personal data to city), expected roles (outreach via their existing contacts, daily call-logging, partner training) and timeline. Request designation of a partner contact person for each organization. Schedule individual scoping meetings to understand partner capacity, existing data systems, and any data-governance constraints.

Responsible Body/Role: Partner-liaison officer (incident commander until this role is hired; then designated Partner-liaison Officer within Heat Response Operations Team).

Suggested Timeframe: Introductory letters sent by Month 0.8 (2026-11-01); scoping meetings held by Month 1.2 (2026-11-14).

Key Outputs/Deliverables:

• Written introductory letters to ≥4 partners
• Scoping-meeting notes for each partner (capacity, data systems, constraints)
• Designated partner contact person and escalation contact for each organization
• Summary of preliminary partner feedback and risks

Dependencies:

• Partner-liaison officer designated or interim role assigned
• Program governance and data-protection model finalized

11. Cooling-center Operations Lead (or interim coordinator) identifies all potential refuge sites (target 10, range 8–12): libraries, community centers, parish halls, sports halls, malls. Confirm facility ownership/management, current heating/cooling systems, accessibility status, available space for people and supplies, liability insurance, and facility-manager contact. Request provisional facility-use agreements from each site for the 5-month season (June–October, Months 6.8–11.8 = 2027-04-23 to 2027-09-30). Conduct preliminary accessibility audit checklist at each site.

Responsible Body/Role: Cooling-center Operations Lead (external candidate or interim coordinator from civil protection or public works) with support from municipal facilities/real-estate office.

Suggested Timeframe: By Month 1.2 (2026-11-14); provisional agreements signed by Month 1.5 (2026-11-23).

Key Outputs/Deliverables:

• List of 10 proposed cooling-center sites with location maps
• Preliminary facility-use agreements (draft or signed) with each site
• Accessibility audit checklist results for each site
• Summary of required fit-out work and estimated costs per site

Dependencies:

• Cooling-center Operations Lead designated or interim role established
• Steering Committee approved governance and alert model

12. GDPR legal lead and counsel finalize all template data-processing agreements and MOUs based on counsel's legal opinion (Month 1 = 2026-11-08). Make revisions per counsel advice. Prepare separate versions if needed for different partner types (housing associations may have different data-handling capacity than NGOs). Include: data scope, lawful basis, contact frequency, escalation rules, breach notification (≤48 hours), data deletion schedule (season end), staff confidentiality and training requirements. Distribute finalized DPAs to all identified partners by end of Month 1.3 (2026-11-17) with 2-week review/sign-off target (deadline Month 1.5 = 2026-11-23).

Responsible Body/Role: GDPR specialist legal counsel (external) and municipal legal lead (0.5 FTE), with input from incident commander and partner-liaison officer.

Suggested Timeframe: Finalized DPAs ready for partner distribution by Month 1.3 (2026-11-17); sign-off deadline Month 1.5 (2026-11-23).

Key Outputs/Deliverables:

• Finalized template DPAs incorporating counsel's legal opinion
• Version control and change-log for each DPA
• Covering letter explaining DPA to each partner
• DPA sign-off checklist and tracking log

Dependencies:

• GDPR counsel's legal opinion received (Month 1 = 2026-11-08)
• Partners identified and contact persons confirmed

13. HR coordinator conducts second-round interviews and makes job offers to selected candidates for Cooling Center Operations Lead, Outreach and Enrollment Lead, Transport Lead / Dispatch Coordinator, Home Kit Lead / Installation Coordinator, and Legal and GDPR Lead. Obtain signed offer letters and employment contracts. Agree start dates (target 50% by Month 1.8 = 2026-12-02, remainder by Month 2 = 2026-12-08). Conduct background checks, occupational health clearance and compliance documentation as required.

Responsible Body/Role: HR coordinator (0.5 FTE) and municipal HR director.

Suggested Timeframe: Offers made and accepted by Month 1.5 (2026-11-23); contracts signed by Month 1.7 (2026-11-29); start dates confirmed.

Key Outputs/Deliverables:

• Signed employment contracts or service agreements (5 lead roles)
• Background-check clearance confirmations
• Occupational health clearance or pre-employment health assessments
• Confirmed start dates and onboarding schedule

Dependencies:

• Recruitment interviews completed (Month 1.3–1.5 = 2026-11-17 to 2026-11-30)
• Budget authorization for salaries confirmed

14. Incident commander and partner-liaison officer conduct individual scoping meetings with each of the ≥4 identified intermediary partners. Agenda: (1) review partner's existing resident/client contact database and data-protection practices; (2) explain heat-response program goals and the intermediary-held list model (no city access to personal data); (3) present the data-processing agreement template and explain lawful basis for contact (public task / consent hybrid); (4) confirm partner's capacity to conduct phone outreach (call-list, staff, availability); (5) discuss escalation rules and partner feedback mechanism; (6) agree on pilot call targets and schedule for Month 2 (2026-12-08) mock-drill testing. Document all partner commitments and concerns.

Responsible Body/Role: Partner-liaison officer (newly hired, or interim coordinator if not yet in post) with incident commander.

Suggested Timeframe: Meetings held by Month 1.5 (2026-11-23); documented summaries by Month 1.7 (2026-11-29).

Key Outputs/Deliverables:

• Partner-scoping meeting notes (1 per partner)
• Partner capacity assessment and call-target agreement
• Escalation protocol and feedback mechanism agreed
• Partner sign-off on data-processing agreement (or issues flagged for resolution)

Dependencies:

• Introductory partner engagement completed (Month 0.8–1.2 = 2026-11-01 to 2026-11-14)
• DPA templates finalized and ready for partner review

15. Procurement specialist issues formal procurement notices for kits, handyperson services, and transport infrastructure. For fast-track items (kits, installation, phone systems), use framework call-offs or below-threshold purchasing routes per the approved procurement plan. Issue specification documents, evaluation criteria, and submission deadlines (target: bids due by Month 1.5 = 2026-11-23 for Month 1.7 = 2026-11-29 decision). For taxi/accessible-transport retainer, issue a small competitive RFQ or invite negotiation from 2–3 pre-qualified operators; aim to sign contract by Month 1.2 (2026-11-14) to lock in standby rates before summer demand.

Responsible Body/Role: Procurement specialist (0.5 FTE) with incident commander and relevant lead roles.

Suggested Timeframe: Notices issued by Month 1.3 (2026-11-17); bids received by Month 1.5 (2026-11-23); awards by Month 1.7 (2026-11-29).

Key Outputs/Deliverables:

• Procurement notices for kits, handyperson and phone-system items
• RFQ or invitation for transport retainer contract
• Bid evaluation reports and selection rationale
• Purchase orders or contract awards (pending final signatures)

Dependencies:

• Procurement specifications finalized (Month 0.8 = 2026-11-01)
• Budget allocation confirmed
• Steering Committee approval of procurement route

16. First operational meeting of the Heat Response Operations Team: Incident commander convenes public-health deputy, operations lead (civil protection), communications lead and partner-liaison officer (interim or newly hired). Agenda: (1) review alert thresholds and incident-command delegation; (2) confirm SITREP and briefing schedule (08:30 and 09:30 on alert days); (3) review public-communications plan and messaging templates; (4) review partner and cooling-center status; (5) establish daily decision-log and escalation hotline; (6) plan for Month 2 (2026-12-08) readiness-gate drills (phone line, outreach mock-calls). Publish operations team charter and meeting schedule to all staff and partners.

Responsible Body/Role: Incident commander (chair), with public-health deputy, operations lead, communications lead and partner-liaison officer.

Suggested Timeframe: Month 1.5 (2026-11-23).

Key Outputs/Deliverables:

• Heat Response Operations Team charter and ToR
• Standing meeting schedule (daily SITREP and 09:30 briefing on alert days, weekly on non-alert)
• Decision-log template and escalation protocol
• Communications-cadence and messaging templates (draft)

Dependencies:

• Incident commander and operations leads designated
• Alert thresholds and delegation finalized
• Steering Committee's first meeting held and decisions documented

17. All governance bodies now formally established submit their initial meeting minutes and charter documents to the Steering Committee. Legal lead conducts a compliance check: confirm all roles are filled (or interim assignments documented), all DPAs are signed or in final review, all procurement orders are placed, and all operational teams have published charters and meeting schedules. Incident commander submits a project-status dashboard showing: (1) governance bodies operational; (2) staffing progress (% of positions filled); (3) procurement status; (4) partner engagement status; (5) risks and corrective actions. This consolidated status report is reviewed at the Steering Committee's Month 2 (2026-12-08) meeting as part of the readiness-gate assessment.

Responsible Body/Role: Legal and GDPR Lead (0.5–1 FTE) with incident commander and PMO coordinator.

Suggested Timeframe: Compliance check completed by Month 1.8 (2026-12-02); status dashboard finalized by Month 2 (2026-12-08) readiness-gate meeting.

Key Outputs/Deliverables:

• Consolidated governance-body charter and ToR document (all bodies, 1 summary)
• Governance compliance checklist (roles filled, DPAs signed, procurement placed, operational charters published)
• Project-status dashboard (staffing %, procurement %, partner % engaged, risks and corrective actions)
• Month 2 (2026-12-08) readiness-gate evidence summary (centers ready, transport signed, phone line live, training completed, procurement ≥90% ordered)

Dependencies:

• All governance-body leads hired and in post or interim-assigned
• DPAs signed with all partners
• All procurement orders placed
• All governance bodies' first meetings held and documented

18. Cooling-center Operations Lead finalizes facility-use agreements with all 10 sites. Conduct a detailed accessibility audit at each site using a standardized checklist (wheelchair access, toilet facilities, water points, quiet/low-stimulus rooms, parking, emergency exits, first-aid kit availability, AED locations). Categorize sites as 'fully accessible' (no remediation needed) or 'minor modifications required' (≤€10k, ≤4 weeks). Issue remediation cost estimates and timelines for each site. Prioritize 5–6 fully accessible sites to open by June 1 (Month 6.8 = 2027-05-02). For sites requiring remediation, develop a schedule and budget authorization for work to complete by May 31.

Responsible Body/Role: Cooling-center Operations Lead with an accessibility consultant or municipal disability-access officer (advisory role).

Suggested Timeframe: Accessibility audit completed by Month 1.5 (2026-11-23); remediation plans finalized by Month 2 (2026-12-08).

Key Outputs/Deliverables:

• Detailed accessibility audit report for each of 10 sites
• Categorization of sites (fully accessible, minor remediation, unsuitable)
• Remediation cost estimates and timelines per site
• Site prioritization: 5–6 priority sites for June opening with no or minor work
• Approved remediation budget and schedule

Dependencies:

• Cooling-center Operations Lead hired and in post
• Provisional facility-use agreements signed (Month 1.5 = 2026-11-23)
• Accessibility consultant or municipal accessibility office engaged

19. Transport Lead (Dispatch Coordinator) begins volunteer-driver recruitment campaign targeting retirees, charity staff, faith-group members and community volunteers. Partner with NGOs, faith organizations, municipal community centers and local media to advertise. Accept applications from October through January (Months 0–3 = 2026-10-08 to 2027-01-08). Conduct vetting in monthly cohorts (background check, driving history, safeguarding screening, insurance verification). Target: 40 volunteer drivers (range 30–50), with ≥20 fully vetted and trained by Month 2 (2026-12-08), remainder by Month 3 (2027-01-08). Provide each volunteer with orientation on heat response, center locations, transport-request protocols, passenger safety and incident reporting.

Responsible Body/Role: Transport Lead / Dispatch Coordinator (external hire or interim coordinator from civil protection) with occupational health and volunteer-coordinator support.

Suggested Timeframe: Recruitment launched Month 0 (2026-10-08); applications accepted through January; vetting in batches (monthly cohorts beginning Month 1 = 2026-11-08); ≥20 fully trained by Month 2 (2026-12-08), remainder by Month 3 (2027-01-08).

Key Outputs/Deliverables:

• Volunteer-recruitment campaign flyers and social-media posts
• Volunteer application form and vetting checklist
• Batch 1 vetting results (background checks passed/failed) by Month 1.8 (2026-12-02)
• Volunteer driver insurance certificates and agreements
• Volunteer orientation and training schedule
• Volunteer roster with contact details and vehicle information

Dependencies:

• Transport Lead hired or interim role assigned
• Budget for volunteer expenses (mileage, fuel) and insurance confirmed

20. Outreach and Enrollment Lead develops heat-response outreach scripts (3–5 minute call format with escalation rules). Scripts should include: greeting and program introduction; identification of the resident's heat risk; description of cooling centers and transport support; consent confirmation for future contact; escalation triggers (signs of heat illness, social crisis, homelessness). Draft scripts in Spanish and test with focus groups of older residents (target: 10–15 participants) by Month 1.5 (2026-11-23) to confirm clarity, cultural appropriateness and acceptability. Incorporate feedback and finalize scripts by Month 1.8 (2026-12-02). Translate core scripts into 4–6 identified non-official languages by Month 2 (2026-12-08) and conduct language-group focus testing.

Responsible Body/Role: Outreach and Enrollment Lead (external hire or interim coordinator) with partner-liaison officer, public-health nurse adviser and community language ambassadors (as they are recruited).

Suggested Timeframe: Draft scripts Month 1 (2026-11-08); focus-group testing Month 1.3–1.5 (2026-11-17 to 2026-11-30); revisions and translations Month 1.5–2 (2026-11-30 to 2026-12-08).

Key Outputs/Deliverables:

• Heat-response call script (Spanish, v1.0)
• Focus-group testing notes and feedback
• Revised script incorporating feedback (v1.1)
• Escalation decision-tree and escalation script (when to call EMS, when to refer to nurse line)
• Scripts translated into 4–6 languages (draft versions for partner review)

Dependencies:

• Outreach and Enrollment Lead hired or interim role assigned
• GDPR legal review completed so scripts comply with consent and data-handling rules
• Community partners (focus groups) identified

21. Home Kit Lead develops a household-targeting rubric to identify homes eligible for the 2,000-kit program. Rubric scoring (0–100 points): top-floor or poor insulation = 30 points; age ≥75 (or 65+ with self-declared chronic condition) = 25 points; living alone = 20 points; built before 1980 = 15 points; no air-conditioning = 10 points. Eligibility threshold = ≥60 points. Validate rubric against a sample of 50–100 enrolled high-risk residents from partner contact lists to confirm sensitivity and specificity. Assess GDPR compliance (ensure rubric does not infer protected health data beyond what residents have consented to share). Finalize rubric by Month 1.8 (2026-12-02) and pilot the targeting process on a sample of 200 households by Month 2 (2026-12-08).

Responsible Body/Role: Home Kit Lead / Installation Coordinator (external hire or interim coordinator) with Outreach and Enrollment Lead and an equity analyst or data coordinator.

Suggested Timeframe: Draft rubric Month 1 (2026-11-08); validation and GDPR check Month 1.3–1.5 (2026-11-17 to 2026-11-30); finalized rubric Month 1.8 (2026-12-02); pilot targeting Month 2 (2026-12-08).

Key Outputs/Deliverables:

• Household-targeting rubric (scoring methodology, point weights, threshold)
• GDPR compliance assessment for rubric
• Validation-test results (sample of 50–100 households)
• Pilot-targeting report (200 households scored and prioritized)

Dependencies:

• Home Kit Lead hired or interim role assigned
• Enrolled high-risk resident data from outreach partners available
• GDPR legal review confirms data-handling scope

22. Incident commander and public-health deputy finalize the emergency-management operational structure in writing. Document: (1) alert-declaration process (forecast data receipt, threshold evaluation, decision authority, notification sequence); (2) daily SITREP and briefing schedule on alert days; (3) stand-down criteria and procedures (alert ends when forecast no longer meets thresholds and actual temperatures normal for 48 hours); (4) escalation hotline and incident-log procedures; (5) mutual-aid triggers with hospitals and EMS (e.g., notify at ≥1.5× historical average heat-related call volume); (6) handover coverage for multi-day events (backup incident commander, rotation of SITREP leads). Publish this as an operational playbook chapter. Conduct a tabletop scenario drill with the Operations Team (2 hours, Month 2 = 2026-12-08) to validate the process and identify gaps.

Responsible Body/Role: Incident commander with public-health deputy and operations lead (civil protection), supported by PMO coordinator.

Suggested Timeframe: Operational procedures documented by Month 1.8 (2026-12-02); tabletop drill conducted Month 2 (2026-12-08).

Key Outputs/Deliverables:

• Alert-declaration and operational procedures document (SOP, flowchart, decision tree)
• SITREP and briefing templates with sample data
• Stand-down criteria and notification procedure
• Mutual-aid trigger matrix (EMS/hospital notification thresholds)
• Tabletop scenario drill after-action report with lessons and corrective actions

Dependencies:

• Incident commander and operations leads designated
• Alert thresholds set and approved by Steering Committee
• Operations Team established and first meeting held

23. Procurement specialist places the first batch of purchase orders (30–40% of total kit volume, ≈600–800 kits) for cooling supplies (shading, fans, thermometers, hygrometers). Negotiate expedited delivery for February (Month 4 = 2027-02-08) to allow ≥6 weeks for installations before the first summer heat days (target June 1 = Month 6.8 = 2027-05-02). Lock in transport standby-retainer contract terms with taxi/accessible-transport operator if not already signed. Identify 2–3 backup suppliers for each kit category to mitigate supply-chain risk. Arrange secure interim storage (municipal facility or supply partner warehouse) for kits arriving in February–March.

Responsible Body/Role: Procurement specialist (0.5 FTE) with Home Kit Lead (once hired) and project coordinator.

Suggested Timeframe: First call-off orders placed by Month 1.2 (2026-11-14); transport contract signed by Month 1.2 (2026-11-14); backup suppliers identified by Month 1 (2026-11-08); storage arrangement confirmed by Month 1.5 (2026-11-23).

Key Outputs/Deliverables:

• Purchase orders for first kit batch (30–40% of 2,000 kits)
• Signed transport/taxi standby-retainer contract with pricing and performance terms
• Backup supplier contact list and pre-qualification documentation
• Storage facility agreement and inventory-management protocol

Dependencies:

• Procurement specs finalized and RFQs issued (Month 0.8–1 = 2026-11-01 to 2026-11-08)
• Supplier bids evaluated and awards recommended (Month 1.5 = 2026-11-23)
• Budget authorization for purchase orders confirmed

24. Conduct a formal, comprehensive Steering Committee meeting (Month 2 = 2026-12-08) to review and make a go/no-go decision on the Month 2 (2026-12-08) readiness gate. Gate criteria: (1) ≥8 of 10 cooling-center sites signed with named managers; (2) ≥50% of places in fully accessible sites; (3) transport retainer contract signed; (4) ≥20 volunteer drivers vetted; (5) heat helpline live (08:00–22:00 daily, 24-hour at Level 3) with a successful mock drill (5–8 simulated calls, ≥3 escalations handled correctly); (6) outreach training delivered to 50–80 partner and street-contact staff with ≥80% attendance and pass score; (7) 100% of tranche-1 procurement orders placed. Incident commander presents evidence for each criterion. Committee votes to pass, pass-with-conditions or fail, and approves any corrective actions if gate is not fully passed. Document decision.

Responsible Body/Role: Heat Response Steering Committee (majority vote, quorum 4 of 6 including Chair or Vice-Chair), with incident commander and lead-role representatives presenting evidence.

Suggested Timeframe: Month 2 (2026-12-08), scheduled 1 week in advance.

Key Outputs/Deliverables:

• Readiness-gate evidence summary (1-pager per criterion with supporting data)
• Heat helpline mock-drill after-action report
• Outreach training attendance and assessment results
• Procurement status and order-confirmation list
• Steering Committee decision minutes with formal vote
• Go/no-go approval for proceeding to Month 4 (2027-02-08) scale gate and full operations

Dependencies:

• All governance bodies operational and reporting metrics
• Cooling centers, transport, phone line and outreach staff in place
• Mock drills and training completed
• Procurement ≥90% ordered

25. Immediately after Month 2 (2026-12-08) readiness gate (whether passed or conditional), Evaluation Lead and university evaluation partner finalize the evaluation design and pre-register the analysis plan. Specify: baseline heat-related EMS and ED counts (obtained from hospitals by Month 1 = 2026-11-08, quality audited by Month 1.5 = 2026-11-23); comparison methodology (pilot vs. matched districts and prior years, aggregate counts only, no identifiable records); temperature-adjustment method; confidence-interval reporting; and plain-language statement of attribution limits. Data-processing agreement with hospitals, EMS and primary care is finalized; daily aggregate-count delivery test (validation pilot) scheduled for April (Month 6 = 2027-04-08). University partner publishes the pre-registered protocol on a registry (e.g., OSF) by Month 3 (2027-01-08).

Responsible Body/Role: Evaluation Lead (0.5–1 FTE, municipal or partner) and university evaluation partner (external, ≈€50k–80k contract).

Suggested Timeframe: Evaluation design finalized by Month 2.5 (2026-12-23); pre-registered protocol published by Month 3 (2027-01-08).

Key Outputs/Deliverables:

• Finalized evaluation design document (comparison groups, statistical methods, attribution approach)
• Data-processing agreement with hospitals/EMS/primary care
• Pre-registered analysis plan (published on OSF or registry)
• Baseline data-quality report and any limitations or caveats
• Data-sharing infrastructure test plan (validation pilot for April)

Dependencies:

• Baseline EMS and ED data obtained and quality-audited (Months 0–1 = 2026-10-08 to 2026-11-08)
• University evaluation partner contracted and data-processing agreement signed
• Steering Committee approved the evaluation scope

26. Recruit, vet and begin training 8–12 community-language ambassadors from identified migrant associations and communities. Ambassadors will be paid part-time staff (≈10–15 hours/week during alert season) responsible for: translating and culturally adapting materials; co-delivering phone-line interpretation support; accompanying door-knock teams in their own languages; staffing cooling-center welcome desks; and conducting focus-group testing of heat messages. Launch recruitment by Month 1 (2026-11-08) with a target start date of Month 1.8 (2026-12-02). Conduct vetting (background check, reference checks) and onboarding by Month 2 (2026-12-08). Provide ambassadors with a 2-day orientation on heat illness, program goals, escalation rules and confidentiality by Month 2.5 (2026-12-23).

Responsible Body/Role: Outreach and Enrollment Lead with partner-liaison officer and community association representatives.

Suggested Timeframe: Recruitment launched Month 1 (2026-11-08); ambassadors hired and onboarded by Month 2 (2026-12-08); orientation and training Month 2–2.5 (2026-12-08 to 2026-12-23).

Key Outputs/Deliverables:

• Ambassador recruitment flyers in community languages and via partner channels
• Ambassador job descriptions and role expectations
• Selected ambassador list with language coverage and community affiliations
• Background-check and reference-check documentation
• Ambassador orientation and training materials (translated)
• Signed ambassador agreements and NDA/confidentiality documents

Dependencies:

• Outreach and Enrollment Lead hired
• Target language groups identified (4–6 languages by Month 0 = 2026-10-08)
• Migrant community associations or NGO partners engaged
• Budget for ambassador stipends and training confirmed

27. Legal lead convenes a partner compliance-and-briefing session with representatives from all ≥4 key intermediary partners (housing associations, social services, NGOs, pharmacies). Agenda: (1) present the finalized data-processing agreements and obtain signatures if not yet signed; (2) brief all partner staff on GDPR obligations, data-protection rules, confidentiality and incident-reporting procedures; (3) distribute outreach scripts, escalation protocols and call-logging templates; (4) confirm partner call-target commitments for the remainder of the season; (5) establish weekly/bi-weekly partner-liaison contact schedule; (6) answer partner questions on consent, data-handling and liability. Document attendance and sign-off from each partner. Provide partners with training materials (slide deck, handout) and digital resources (template call logs, escalation guides).

Responsible Body/Role: Legal lead (0.5–1 FTE) with Outreach and Enrollment Lead, partner-liaison officer and GDPR counsel (advisors).

Suggested Timeframe: Briefing session conducted by Month 2 (2026-12-08); attendance confirmation and sign-off by Month 2.5 (2026-12-23).

Key Outputs/Deliverables:

• Signed data-processing agreements from all partners (or documented timeline for final signature)
• GDPR and confidentiality briefing slides and handout materials
• Outreach script and escalation protocol distributed to all partner staff (attendance log)
• Call-logging template and incident-reporting form provided to partners
• Partner commitment letter (call targets, data-handling, escalation)
• Weekly liaison contact schedule published

Dependencies:

• DPA templates finalized and customized per partner type (Month 1.3 = 2026-11-17)
• Partners have reviewed DPAs and provided feedback
• Outreach scripts and escalation protocols finalized (Month 1.8 = 2026-12-02)
• Legal lead and GDPR counsel available for briefing

28. Heating-systems and procurement coordinator confirms the delivery schedule and logistics for the first batch of cooling kits (30–40% of 2,000, ≈600–800 kits ordered at Month 1.2 = 2026-11-14). Negotiate expedited shipping for February arrival. Arrange intake inspection and inventory verification upon delivery. Set up secure interim storage with climate control (to prevent fan degradation) and an inventory-management system (tracking kit location, condition, hand-off to installers). Prepare a kit-distribution protocol: priority allocation to highest-scoring households (from Home Kit Lead's targeting rubric), geographic batching by neighborhood for installer efficiency, and consent verification before each household's installation is scheduled.

Responsible Body/Role: Procurement specialist (0.5 FTE), Home Kit Lead and logistics coordinator (may be shared with general municipal logistics).

Suggested Timeframe: Delivery logistics finalized by Month 2 (2026-12-08); storage facility prepared by Month 3 (2027-01-08); first kits received ≈Month 4 (2027-02-08).

Key Outputs/Deliverables:

• Kit delivery schedule and shipment confirmations
• Storage facility access and inventory-management protocol
• Kit-distribution sequencing and neighborhood/household priority list
• Installation-scheduling process (consent verification, scheduling letters to residents)
• Inventory-tracking system and daily intake log

Dependencies:

• Purchase order for first kit batch placed (Month 1.2 = 2026-11-14)
• Storage facility identified and contracted (Month 1.5 = 2026-11-23)
• Home Kit Lead hired and targeting rubric finalized (Month 1.8 = 2026-12-02)

29. Establish the heat-response phone line and dispatch-coordination system. Procure or configure telephony infrastructure (dedicated phone line, call queuing, call recording if permitted by Spanish law, call transfer to interpretation services). Set up call-tracking software (shared spreadsheet with partner-liaison officer, or a secure cloud platform) to log all incoming calls, resident details, requests, responses and escalations. Recruit 2–3 FTE phone-line operators (1 permanent + 1–2 surge/part-time) by Month 1.8 (2026-12-02). Conduct training (call scripts, escalation triggers, de-escalation, interpreter coordination, incident reporting) by Month 2.5 (2026-12-23). Conduct a 4–6 hour mock-call drill with 5–8 simulated calls including escalation cases (heat illness, social crisis) by Month 2.5 (2026-12-23) and document results.

Responsible Body/Role: Outreach and Enrollment Lead (phone-line owner) with transport lead (for dispatch coordination), PMO coordinator and occupational health.

Suggested Timeframe: Telephony infrastructure procured and installed by Month 1.8 (2026-12-02); operators hired by Month 1.8 (2026-12-02); training and mock drill completed by Month 2.5 (2026-12-23); system live and operational by Month 2 (2026-12-08) readiness gate.

Key Outputs/Deliverables:

• Phone-line setup with call-queuing and escalation features (tested)
• Call-tracking system (spreadsheet template or platform)
• Trained phone-line operators (employment contracts, training certificates)
• Call-handling and escalation SOP
• Mock-call drill report (5–8 simulated calls, ≥3 escalations, success rate ≥80%)
• Go-live checklist and 24-hour on-call support plan

Dependencies:

• Budget for phone-line setup and operators confirmed
• Outreach scripts and escalation protocols finalized
• Interpretation services contract signed (external provider or municipal arrangement)

30. Recruit, vet and begin training handypersons (target 10 FTE for Months 4–7 = 2027-02-08 to 2027-05-17) responsible for installing cooling kits (exterior shading, fans, thermometers). Vet candidates for occupational health and safety certification (or willingness to obtain it), relevant trade experience, background check and occupational-health clearance. Provide each handyperson with a 1-day safety-and-installation training covering: (1) electrical safety and fan-installation safety; (2) fan-use guidance for residents (directional airflow, outdoor-air intake); (3) shading and wind-resistance assessment; (4) building-code compliance checks; (5) customer communication and consent; (6) incident reporting and feedback. Training conducted by Month 3.5 (2027-01-23). Arrange tools, equipment and safety gear by Month 3 (2027-01-08). Finalize handyperson employment or contract terms by Month 3 (2027-01-08) with start date ≥Month 4 (2027-02-08).

Responsible Body/Role: Home Kit Lead / Installation Coordinator with occupational health and a qualified trades supervisor or external training provider.

Suggested Timeframe: Recruitment launched Month 2 (2026-12-08); hiring completed by Month 2.8 (2027-01-01); training conducted Month 3–3.5 (2027-01-08 to 2027-01-23).

Key Outputs/Deliverables:

• Handyperson job description and qualification criteria
• Recruitment announcements and applications (target 10 FTE)
• Vetting documentation (background checks, trade certifications, occupational-health clearance)
• Handyperson employment or service contracts (10)
• 1-day safety-and-installation training curriculum and materials
• Training attendance and assessment results (target ≥80% pass)
• Handyperson roster, contact details and insurance information

Dependencies:

• Home Kit Lead hired
• Budget for handyperson wages/contracts confirmed
• Kit components and installation specifications finalized
• Occupational health and safety requirements confirmed

31. PMO coordinator drafts the full-system operational drill protocol for Month 3.2 (2027-01-14). Drill will simulate a Level 2 or Level 3 alert lasting 4–6 hours, activating all systems: cooling centers open to full capacity, transport dispatch handles ≥30 simulated requests (including ≥5 wheelchair-user priority cases targeting 30-min pickup), outreach phone line receives ≥20 calls (mixture of enrollment inquiries, requests for transport, escalation cases), and all partner outreach staff place sample calls (≥300 attempts across all partners). Drill will test: center staffing and operations readiness, accessibility compliance, transport dispatch speed and volunteer/taxi coordination, phone-line call handling and escalation, heat-illness recognition and EMS escalation, and inter-organizational communication. Draft evaluation checklist and success criteria (80% center hours, 60% outreach success, <45 min transport time). Publish protocol to all participants by Month 2.5 (2026-12-23).

Responsible Body/Role: PMO coordinator (project manager) with incident commander, Cooling-center Operations Lead, Transport Lead, Outreach Lead and all governance-body leads.

Suggested Timeframe: Draft protocol completed by Month 2.5 (2026-12-23); drill conducted Month 3.2 (2027-01-14); after-action report completed by Month 3.5 (2027-01-23).

Key Outputs/Deliverables:

• Detailed drill protocol (scenario, timeline, participant roles, success criteria)
• Drill evaluation checklist and gate-metric data-collection forms
• Participant briefing and instructions (distributed to all staff and partners)
• Drill execution log (timeline of events, decisions, issues noted)
• Drill after-action report (center-hours delivered, outreach contact success rate, transport response times, escalation cases handled correctly)
• Corrective-action list with owners and completion deadlines

Dependencies:

• All governance bodies operational and reporting metrics
• Alert thresholds, operational procedures and escalation protocols finalized
• Cooling centers, transport, phone line and outreach staff in place or nearly in place

32. Conduct the full-system operational drill on a specified date (Month 3.2 = 2027-01-14) with all governance bodies and operational teams activated. Incident commander declares a simulated Level 2 alert (forecast high ≥35°C and low ≥22°C for 2 consecutive days). Operations Team convenes at 07:00, SITREP at 08:30, partner briefing at 09:30. Cooling centers open their doors at 10:00 with full staffing; transport dispatch stands by with volunteer drivers and taxi operator on standby; phone line opens at 08:00 with operators and (if possible) live interpretation services. Outreach partners place sample calls (target ≥300 attempts across all partners, ≥60% connection success rate). Transport requests are generated (target ≥30 requests, ≥5 wheelchair-user priority cases). After 4–6 hours of continuous operation, incident commander declares stand-down at 16:00. All teams complete incident logs and action-item forms. A debrief is held the same day (17:00–18:30) with all lead roles present.

Responsible Body/Role: Incident commander (exercise controller) with Heat Response Operations Team, all governance-body leads and operational staff (Cooling-center managers, transport dispatchers, phone-line operators, outreach partners).

Suggested Timeframe: Drill conducted Month 3.2 (2027-01-14); debrief completed same day; after-action report drafted within 3 days (by Month 3.3 = 2027-01-17).

Key Outputs/Deliverables:

• Drill execution log with timeline and decision record
• Center-hours delivered by site (target ≥80% of planned hours)
• Outreach contact attempts and success rates by partner (target ≥60%)
• Transport requests received, response times and wheelchair-user accommodation (target <45 min average, <30 min for priority cases)
• Heat-illness and escalation cases handled (number and outcome)
• Debrief notes and participant feedback
• Incident log of issues, gaps and corrective actions

Dependencies:

• Drill protocol finalized and distributed to all participants
• All operational systems (phone line, cooling centers, transport dispatch) live and tested
• Cooling-center staff, transport dispatchers and operators trained and on-call

33. Incident commander and key leads review drill after-action report (completed Month 3.5 = 2027-01-23) and identify all corrective actions needed before the Month 4 (2027-02-08) scale gate. Corrective actions fall into categories: (1) staffing gaps (additional operators, volunteers, center support staff); (2) procedural improvements (revised escalation rules, faster transport routing); (3) technology fixes (phone-line call queuing, dispatch software); (4) training needs (repeat training for staff who did not meet standards). Assign owner and completion deadline (target ≤Month 3.8 = 2027-02-01, within 2 weeks of drill debrief) for each action. Close-out checklist confirms all actions are verified complete by Month 3.9 (2027-02-04). Document closure with evidence (training records, system logs, staffing confirmations).

Responsible Body/Role: PMO coordinator (action-tracking owner) with incident commander and all governance-body leads who own specific corrective actions.

Suggested Timeframe: After-action report completed Month 3.5 (2027-01-23); corrective-action plan finalized Month 3.6 (2027-01-26); actions executed and closed by Month 3.9 (2027-02-04).

Key Outputs/Deliverables:

• Corrective-action list with owners, deadlines and completion evidence
• Staffing adjustments (additional hires or schedule changes) documented
• Revised procedures or escalation rules published to all staff
• Technology fixes or system improvements validated
• Repeat training or skill assessments completed and documented
• Closure checklist signed off by each action owner

Dependencies:

• Drill after-action report completed and shared with all leads
• Sufficient budget and staffing flexibility to execute corrective actions
• Steering Committee monitoring of closure status

34. Conduct the Steering Committee's Month 4 (2027-02-08) scale-gate review and funding-release decision. Incident commander presents comprehensive evidence for the four scale-gate criteria: (1) ≥80% of planned cooling-center hours delivered in the drill; (2) ≥60% contact success from ≥300 outreach attempts; (3) mean transport time <45 min over ≥30 requests (including ≥5 wheelchair users); (4) 100% of after-action corrective actions from the drill closed and verified. Additionally present: status of kit procurement and delivery (target ≥40% by Month 4 = 2027-02-08), handyperson training completion (all 10 trained and on-contract), partner compliance audit (GDPR, call-logging, data protection). If all criteria are met, Committee formally approves the release of the full €1.5M tranche-2 funding. If 1 criterion fails but evidence is incomplete (e.g., insufficient natural heat events by Month 4 = 2027-02-08 to validate gates in real conditions), Committee approves conditional release: €750k (50%) immediately, remainder after a re-test in Month 5 (2027-03-08) using real-world heat data. If 2+ criteria fail, Committee does not release tranche-2; corrective actions and re-test planned for Month 5 (2027-03-08) at the earliest. Document formal vote and decision.

Responsible Body/Role: Heat Response Steering Committee (majority vote, quorum 4 of 6 including Chair or Vice-Chair), with incident commander and governance-body leads presenting evidence.

Suggested Timeframe: Month 4 (2027-02-08), scheduled at least 1 week in advance; decision documented same day.

Key Outputs/Deliverables:

• Scale-gate evidence package (center hours, outreach success rate, transport response times, corrective-action closure, kit procurement status)
• Steering Committee meeting minutes with formal vote on each criterion
• Formal funding-release decision letter or memo (full release, conditional release, or no release)
• Communiqué to all staff and partners confirming gate decision and next steps

Dependencies:

• Drill completed and after-action report finalized (Month 3.5 = 2027-01-23)
• All corrective actions closed and verified (Month 3.9 = 2027-02-04)
• Kit procurement on track (≥40% delivered or in-transit by Month 4 = 2027-02-08)
• Handyperson recruitment and training completed

35. Following the Month 4 (2027-02-08) scale-gate decision (whether full, conditional or no release), the Steering Committee formally approves and the incident commander confirms the operational readiness of all governance bodies to enter the live operational season (Months 6.8–11.8 = 2027-04-23 to 2027-09-30). Each governance body lead submits a readiness certification covering: (1) staffing (all roles filled, trained, on-call rosters confirmed); (2) systems (phone line, dispatch, cooling centers, partner call-tracking operational and tested); (3) supplies (kits in storage or arriving, handyperson ready to deploy, shelter supplies stocked); (4) protocols (escalation, GDPR, incident reporting, stand-down all documented and drilled); (5) partner commitment (all intermediaries' MOUs signed, staff trained, call targets confirmed). Incident commander and Steering Committee Chair sign off on the overall go-live. A public announcement and pre-season communications campaign (flyers, radio, pharmacy posters, community briefings) launch by Month 6.5 (2027-04-23).

Responsible Body/Role: Incident commander and all governance-body leads, with Steering Committee Chair oversight.

Suggested Timeframe: Readiness certifications submitted by Month 4.5 (2027-02-23); Steering Committee review and go-live approval by Month 5 (2027-03-08).

Key Outputs/Deliverables:

• Readiness certification from each governance body (staffing, systems, supplies, protocols, partner commitment)
• Consolidated operational-readiness checklist
• Steering Committee formal approval and go-live authorization
• Public announcement of program launch (press release, municipal website, social media)
• Pre-season campaign materials (flyers, radio spots, pharmacy posters, community briefings)

Dependencies:

• Month 4 (2027-02-08) scale-gate decision made and communicated
• All staffing hired and trained
• All systems tested and operational
• Cooling-center accessibility audit and remediation completed
• Kit procurement and handyperson training on schedule

36. From Month 5 onward (2027-03-08), governance bodies transition from setup and gate-preparation mode to regular operational reporting and rhythm. Monthly Steering Committee meetings (standing: first Monday of each month 14 = 2027-12-08:00, Months 5–12 = 2027-03-08 to 2027-10-08) review: (1) financial forecasts and budget burn; (2) staffing and fatigue status; (3) partner engagement and capacity; (4) procurement delivery status; (5) risk register; (6) preparation for summer season (June–September). Operations Team maintains weekly meetings on non-alert days (Mondays 14:00, Months 5–8 = 2027-03-08 to 2027-06-08) and daily standups with SITREP (08:30) and partner briefing (09:30) during any alert periods. Sub-groups (Cooling Centers, Outreach, Transport, Home Kits) establish their own meeting cadences: Cooling Centers weekly (Tuesdays 14:00 during setup, transitioning to ad-hoc during season); Outreach weekly (Wednesdays 14:00, then daily during alert days); Transport weekly (Thursdays 14:00, then daily during alerts); Home Kits weekly (Mondays 10:00 during installation phase = Months 4–7 = 2027-02-08 to 2027-05-17). Data and evaluation group meets monthly (Fridays 14:00).

Responsible Body/Role: Incident commander (chair of Operations Team), Steering Committee members, and all governance-body leads.

Suggested Timeframe: Governance transition to regular rhythm by Month 5 (2027-03-08); sustained through end of project Month 12 (2027-10-08).

Key Outputs/Deliverables:

• Monthly Steering Committee meeting calendar and standing agendas published
• Weekly Operations Team and sub-group meeting schedules published
• Meeting-cadence documentation in the operational playbook
• Monthly financial and risk-management dashboards prepared by PMO for Steering Committee review
• Weekly operations summaries (for non-alert weeks) shared with stakeholders

Dependencies:

• All governance bodies established and leads in post
• Operational systems live and stable
• Financial and staffing tracking systems operational

37. From Month 8 onward (2027-06-08), the Evaluation Lead, data analyst and university evaluation partner begin drafting the final Heat Response Playbook, cost model, and evaluation report. Playbook chapters include: (1) strategic decisions and rationale (Alert Trigger Ladder, Refuge Network, Intermediary-Held Lists, Mobility Support, Command Structure, Home Kits, Health Integration, Worker Protection, Communications, Language Access, Evaluation); (2) SOPs and checklists (alert declaration, cooling-center operations, transport dispatch, phone-line handling, escalation, de-escalation, incident reporting, stand-down); (3) procurement and staffing templates (job descriptions, supplier specs, contract terms, partner MOUs); (4) lessons learned and adaptations (what worked, what was hard, what to change for Year 2); (5) unit costs and scaling assumptions (€ per person enrolled, per center-hour, per kit, per transport trip, per staff FTE). University partner analyzes operational and outcome data (EMS, ED, mortality proxies) against the pre-registered protocol. Playbook draft shared with peer EU cities for comment by Month 11 (2027-09-08); final version and evaluation report delivered by Month 12 (2027-10-08).

Responsible Body/Role: Evaluation Lead (0.5–1 FTE) with Playbook Editor (may be Evaluation Lead or separate role), university evaluation partner, and incident commander/governance leads (content contributors).

Suggested Timeframe: Playbook drafting begins Month 8 (2027-06-08); section drafts submitted by Month 10 (2027-08-08); peer-city review Month 11 (2027-09-08); final version Month 12 (2027-10-08).

Key Outputs/Deliverables:

• Heat Response Playbook (draft Months 8–10 = 2027-06-08 to 2027-08-08, final Month 12 = 2027-10-08)
• Scaling cost model with unit costs and assumptions
• Data and evaluation report (preliminary by Month 11 = 2027-09-08, final Month 12 = 2027-10-08)
• Year-2 roadmap (expansion priorities, elements to discontinue, estimated budget for Year 2)
• Lessons-learned and adaptation summary

Dependencies:

• Operational data collected throughout Months 6–11 (2027-04-08 to 2027-09-08) (center hours, outreach attempts/success, transport times, kit installations)
• Health-system outcome data (EMS, ED, mortality) collected and analyzed
• University evaluation partner data analysis complete
• All governance bodies document their decision-making and challenges for playbook lessons-learned section

38. Conduct a final Steering Committee meeting (Month 12 = 2027-10-08) to review and formally approve the Heat Response Playbook, scaling cost model, evaluation report and Year-2 roadmap for public release. Committee considers: (1) Are the lessons learned and adaptations clearly documented? (2) Is the cost model transparent and defensible for other EU cities? (3) Are attribution caveats and limitations honestly stated? (4) Is the Year-2 roadmap realistic and funded? Committee votes to approve for publication. Incident commander prepares a final project close-out report (budget reconciliation, staffing outcomes, partner feedback, next-steps). A final debrief meeting is held with all governance-body leads and key partners to capture verbal feedback and recognize contributions. Public launch event (press conference, municipal briefing, dissemination to peer cities and EU networks) scheduled for Month 12 (2027-10-08) or soon after.

Responsible Body/Role: Heat Response Steering Committee (majority vote), with incident commander, Evaluation Lead and playbook editor presenting final deliverables.

Suggested Timeframe: Final Steering Committee meeting Month 12 (2027-10-08); public launch by end of Month 12 (2027-10-08) or early Month 13 (2027-11-08).

Key Outputs/Deliverables:

• Steering Committee formal approval of Playbook, cost model, evaluation report and Year-2 roadmap (meeting minutes with vote)
• Final project close-out report (budget reconciliation, staffing, partner feedback, lessons learned)
• Public-release press release and communications pack
• Heat Response Playbook published (PDF and possibly online portal)
• Scaling cost model published with replicability guidance for other EU cities
• Evaluation report published with peer-reviewed or audited findings
• Year-2 roadmap and funding proposal (if applicable)
• Final debrief meeting minutes and participant feedback

Dependencies:

• All draft deliverables (Playbook, cost model, evaluation report, roadmap) completed and reviewed by Steering Committee by Month 11 (2027-09-08)
• Peer-city feedback incorporated (Month 11 = 2027-09-08)
• University evaluation partner's final report submitted
• Budget reconciliation and staffing outcomes documented

Decision Escalation Matrix

Month 4 (2027-02-08) Scale-Gate Failure or Unmeasurable Evidence Escalation Level: Heat Response Steering Committee Approval Process: Majority vote (4 of 6 members including Chair or Vice-Chair). Steering Committee reviews gate-measurement evidence (drill data, real-world heat events, corrective-action closure). If gates are failed, the Committee votes on: (1) no release of €1.5M tranche-2 and mandatory corrective re-test by Month 5 (2027-03-08), or (2) conditional 50% release (€750k) if evidence is incomplete due to cool season, with final decision after Month 5 (2027-03-08) re-test. If gates are passed, full €1.5M is approved for immediate release. Rationale: The Month 4 (2027-02-08) gate decision gates control €1.5M funding release (43% of total budget) and determines operational scale for the critical May–September heat season. A failed gate triggers a budget crisis (€200–400k cash gap) and potential service reductions mid-summer. The decision affects public safety, partner continuity, and program credibility. Only the Steering Committee has authority to approve or withhold conditional funding and escalate unmet gates to corrective re-planning. Negative Consequences: Non-release or delayed release of €1.5M by 4–8 weeks would force closure of 25–40% of planned cooling-center hours and transport capacity by August, coinciding with peak summer heat risk. Estimated harm: 500–1,500 fewer high-risk residents reached, 15–25% reduction in outreach contact success, loss of volunteer driver confidence and partner engagement. Reputational damage: audit and funder scrutiny if gates are failed; media coverage if residents are turned away from overcrowded centers during a heat wave.

Budget Overrun or Contingency-Reserve Drawdown Exceeding €20k Escalation Level: Heat Response Steering Committee Approval Process: Incident commander submits a budget-reforecast report documenting: (1) spending by category to date, (2) variance from budget, (3) root cause, (4) corrective action (reduce scope, reallocate budget, draw contingency). Steering Committee reviews and votes to approve the reforecast and contingency drawdown (if >€20k requested). Large drawdowns (>€50k) require documented justification (e.g., supplier price spike, staff absence surge, emergency remediation) and may trigger supplier or scope review. Rationale: The total €3.5M budget is hard-capped with limited contingency (€280k = 8%). Overruns threaten both gates and final deliverables. Overruns may stem from procurement delays requiring expedited shipping, staffing gaps forcing extended taxi retainers, or facility remediation cost growth. Steering Committee authority ensures spending decisions are visible, documented and aligned with strategic priorities (gates > playbook > home kits, in case trade-offs are needed). Negative Consequences: Uncontrolled spending exhausts contingency by Month 6 (2027-04-08), leaving no buffer for summer emergencies (staff illness surge, supplier failure, facility damage). If €280k is drawn and overruns continue, tranche-2 release is at risk. Cumulative overrun of 15% (€525k) creates a funding shortfall of €245k that cannot be covered, forcing either mid-season service cuts or funder request for supplementary funds (likely denied if funder is a municipal council with fixed budgets). Reputational cost: audit finding of budget mismanagement, loss of funder confidence for Year-2 proposal.

GDPR Compliance Breach or Partner Data-Handling Violation Escalation Level: Heat Response Steering Committee Approval Process: Legal and GDPR Lead (with external GDPR legal counsel) investigates any reported or discovered breach. Assessment includes: data scope affected, number of residents, confidentiality risk, partner culpability. Legal team determines if breach must be reported to the Spanish Data Protection Authority (AEPD) within 48 hours (if >100 residents at high risk or health data exposed). Steering Committee is briefed within 24 hours of discovery. If breach is serious (100+ residents, deliberate misuse, regulator notification required), Committee may authorize: (1) contract suspension of breaching partner, (2) resident notification campaign, (3) enhanced oversight, (4) corrective-action plan with funder notification. Decision is documented and, if required, escalated to municipal legal counsel and city council. Rationale: The program relies on intermediary-held contact lists and partner compliance with GDPR and data-protection obligations. A breach (e.g., partner leaks resident contact details or health flags to a third party, or unauthorized contact outside the agreed scope) undermines resident trust, violates the legal basis for the program, and exposes the city to regulatory fines and litigation. GDPR compliance is a hard constraint: failure to resolve a breach promptly risks program suspension or funder withdrawal. Negative Consequences: Serious breach (100+ residents, health data exposed) triggers 48-hour AEPD notification requirement and potential regulatory investigation. Estimated fine under GDPR Article 83: €10k–€50k (minor breach) to €100k–€500k+ (serious breach involving health data). Resident notification and credit-monitoring costs: €5k–€20k. Partner contract termination reduces outreach reach by 10–20% (500–1,000 residents). Loss of public trust and media coverage of 'data leak' damages program credibility and Year-2 funding prospects. Estimated total reputational and financial cost: €100k–€750k.

Critical Incident at a Cooling Center (Serious Injury, Death, Major Safety Failure) Escalation Level: Heat Response Steering Committee (if serious or reputational impact); immediate notification to incident commander and chair within hours Approval Process: Cooling-Center Operations Lead reports incident to incident commander immediately. Incident commander convenes an emergency review (within 24 hours) with operations lead, legal counsel and occupational health to assess: (1) cause (staffing gap, equipment failure, medical emergency, accessibility failure); (2) liability and insurance coverage; (3) immediate corrective action (site closure, additional staffing, equipment repair); (4) public communication and incident disclosure; (5) regulatory reporting (to occupational safety authority if staff injury, to municipal health authority if resident harm). Steering Committee is notified same day if incident involves death, serious injury, or reputational crisis (media attention likely). Committee may authorize: (a) site temporary closure and remediation, (b) external incident investigation, (c) public statement and transparency, (d) enhanced insurance or legal defense. If fatality occurs and program is blamed, funder and city council are notified immediately and Steering Committee meets within 48 hours to decide continuation. Rationale: A serious incident (death, heat-stroke hospitalization, fall, assault) at a cooling center creates immediate liability, regulatory exposure and reputational crisis. The center is municipally managed and staffed; the city is liable for duty of care. Rapid escalation ensures legal protection, incident documentation, corrective action and transparent communication. Transparency and swift action reduce legal and reputational risk; cover-up or delay amplifies damage. Negative Consequences: Serious injury or death at a center followed by delayed or poor response triggers: (1) litigation by resident/family for negligence, seeking €50k–€500k+ damages; (2) media coverage ('municipal heat program fails to protect resident') damaging public trust; (3) occupational safety regulator investigation if staff injured; (4) funder loss of confidence and Year-2 funding denial; (5) city council political pressure to defund or restructure the program; (6) partner and volunteer recruitment collapse due to reputational damage. Estimated cost: €200k–€1M (legal defense, settlement, lost funding, staff replacement).

Volunteer Driver or Outreach Staff Safety Incident (Assault, Abuse, Safeguarding Concern) Escalation Level: Heat Response Steering Committee; immediate escalation to incident commander and occupational health Approval Process: Transport Lead or Outreach Lead reports incident to incident commander and occupational health within 2 hours. Occupational health conducts immediate welfare check and offers counseling/support. HR coordinator and legal counsel assess: (1) whether police/authorities should be notified (assault, threat); (2) incident documentation and log; (3) staff/volunteer leave entitlements and duty-of-care obligations; (4) insurance coverage; (5) safeguarding and volunteer-management protocol review. If incident indicates systemic safeguarding failure (multiple incidents, inadequate training, poor vetting), incident commander escalates to Steering Committee within 24 hours for governance-level decision on: (a) safeguarding protocol audit and retraining, (b) volunteer recruitment pause and re-vetting, (c) additional supervision and insurance requirements, (d) external safeguarding review if serious or repeated incidents. Rationale: Volunteers and staff are municipal program representatives and are exposed to vulnerable residents (elderly, isolated, potentially hostile). Assaults, abuse or safeguarding breaches create duty-of-care obligations, legal liability, and staff safety risks. Swift incident response protects staff welfare, fulfills legal obligations and identifies systemic issues (poor training, insufficient vetting, inadequate supervision) before they recur. Negative Consequences: Unaddressed staff safety incident leads to: (1) volunteer or staff resignation, reducing dispatch and outreach capacity by 5–15%; (2) retained trauma and reduced effectiveness of affected staff; (3) reputation damage affecting future volunteer recruitment; (4) litigation if staff/volunteer claims negligence or inadequate safeguarding; (5) occupational health regulator finding if incident indicates systematic risk. Cumulative impact of 2–3 incidents without remediation could force program pause or external safeguarding takeover. Estimated cost per serious incident: €10k–€50k (legal, counseling, recruitment replacement).

Procurement or Supply-Chain Failure Threatening Month 2 (2026-12-08) Readiness Gate or Home-Kit Deployment Deadline Escalation Level: Heat Response Steering Committee (if delay exceeds 4 weeks or forces budget contingency drawdown >€50k) Approval Process: Procurement specialist and Home Kit Lead (or Cooling-Center Operations Lead) report supply-chain risk to incident commander within 5 working days of discovery. Incident commander convenes emergency review with PMO coordinator, lead role and legal counsel to assess: (1) root cause (supplier bankruptcy, production delay, shipping disruption, quality issue); (2) impact (which gate is at risk, delay duration, cost of expedite/backup supplier); (3) corrective action options (accelerate delivery, use backup supplier, reduce scope); (4) budget impact (does contingency or scope cut avoidable). If delay exceeds 3 weeks or remediation requires >€50k contingency drawdown, incident commander escalates to Steering Committee within 24 hours with: (a) delay timeline and gate-impact assessment, (b) corrective-action options ranked by cost and speed, (c) recommendation (e.g., pay 15% premium for expedite, or defer non-critical items to Month 5 = 2027-03-08). Committee votes on approval and any scope trade-offs (e.g., reduce home-kit count to prioritize cooling centers). Rationale: Cooling kits, transport contracts and center fit-out are on the critical path to the Month 2 (2026-12-08) readiness gate and the May–June summer season. Delays >4 weeks push kit installation or transport readiness into June or July, missing the peak early-summer heat risk and failing gates. Escalation ensures visibility of supply-chain risks, timely use of contingency funds for expedited delivery, and if necessary, scope trade-offs approved by leadership rather than ad-hoc cuts. Negative Consequences: Supply-chain failure causing >6-week delay in kits or transport (e.g., supplier bankruptcy, shipping port disruption) means home interventions cannot be installed before June heat events, reducing estimated mortality reduction by 15–25%. Transport readiness slip forces reliance on taxi-only model (+€150–250k), cutting home-kit budget by €150–250k (500–1,000 fewer kits). Cascading impacts: Month 2 (2026-12-08) readiness gate fails due to incomplete procurement; Month 4 (2027-02-08) scale gate fails due to low home-kit installation numbers; €1.5M tranche-2 is not released on schedule; program enters summer under-resourced. Estimated total cost of 6-week delay: €150–250k contingency drawdown + 15–25% reduced mortality protection + reputational damage (gates failed despite advance planning).

Monitoring Progress

1. Gate-Metric and Operational-KPI Tracking (Month 2 = 2026-12-08 Readiness, Month 4 = 2027-02-08 Scale, Seasonal Performance)

Monitoring Tools/Platforms:

• Gate-Measurement Checklist (Excel/shared spreadsheet)
• Cooling-Center Hours and Occupancy Log (daily site-by-site tracking)
• Transport Dispatch Log (request-by-request response-time tracking)
• Outreach Contact-Attempt and Success-Rate Spreadsheet (by partner, daily)
• PMO Operations Dashboard (consolidated weekly summary)

Frequency: Daily during alert days (Months 6.8-11.8 = 2027-04-23 to 2027-09-30); weekly on non-alert days during setup (Months 1-5 = 2026-11-08 to 2027-03-08); consolidated monthly for steering committee review.

Responsible Role: PMO Coordinator and Incident Commander, with daily data collection from Cooling-Center Operations Lead, Transport Lead and Outreach Lead.

Adaptation Process: Weekly Operations Team review (Mondays 14:00, non-alert Months 1-5 = 2026-11-08 to 2027-03-08) identifies metric shortfalls (center hours <80%, outreach success <60%, transport time >45 min); incident commander authorizes corrective actions: additional staffing, script revision, route re-optimization, escalation support. Monthly reports to Steering Committee flag trends requiring budget reallocation or scope adjustment. At Month 2 (2026-12-08) and Month 4 (2027-02-08), consolidated gate-evidence package is prepared for formal go/no-go decision.

Adaptation Trigger: Month 2 (2026-12-08) Readiness Gate: if any of the 7 readiness criteria unmet, incident commander convenes 24-hour corrective-action meeting and reports to Steering Committee; if criteria cannot be closed by Month 2.5 (2026-12-23), gate is flagged as fail-at-risk. Month 4 (2027-02-08) Scale Gate: if center-hours or outreach-success or transport-time fail the thresholds, no release of tranche-2 €1.5M (triggering €200-400k cash gap); if evidence is insufficient due to cool season, conditional 50% release (€750k) and re-test at Month 5 (2027-03-08). Real-time during season: if transport time rises above 45 min for >1 consecutive alert day, transport lead escalates to incident commander within 2 hours; if persistence >3 days, escalates to Steering Committee as gate-failure risk.

2. Critical Success Factor Tracking: Cooling-Refuge Network Reach and Accessibility (Equity and Access)

Monitoring Tools/Platforms:

• Site-Coverage Map and Equity-Reach Analysis (GIS if available, or spreadsheet with neighborhood postcode data)
• Cooling-Center Occupancy and Demographics Spreadsheet (age, gender, neighborhood, language, disability accommodation)
• Accessibility Audit Checklist and Remediation-Tracking Log (per site)
• Equity Metrics Dashboard (% of target 65+ reached, % from top-deprivation neighborhoods, % in fully accessible sites, % with language support)

Frequency: Monthly during setup (Months 1-5 = 2026-11-08 to 2027-03-08) to confirm site readiness and accessibility; weekly during season (Months 6.8-11.8 = 2027-04-23 to 2027-09-30) to track occupancy by neighborhood and demographic; final equity-coverage summary at Month 12 (2027-10-08).

Responsible Role: Cooling-Center Operations Lead and an Equity Analyst or Data Coordinator (0.5 FTE), reporting to incident commander.

Adaptation Process: Monthly Operations Team review compares actual occupancy and demographics against targets (≥70% of enrolled residents within 800 m; ≥50% of places in fully accessible sites; ≥5% of users identified as non-official-language speaker or wheelchair user). If a site shows low utilization (<20% occupancy on alert days) or if a neighborhood is under-represented (≤20% of expected enrollees), Cooling-Center Operations Lead recommends: (1) extended hours or special programming at underused sites, (2) targeted outreach to under-represented neighborhoods, (3) transport-priority deployment to sites serving highest-need areas. Accessibility shortfalls (e.g., wheelchair users turned away) trigger immediate site remediation or closure; inaccessible sites are closed until remediation is complete (≤4 weeks, ≤€10k).

Adaptation Trigger: Site occupancy <20% over 2 consecutive alert days → Operations Lead meets with site manager within 24 hours to identify barriers (location, hours, comfort, marketing); adjust hours, transport routing, or outreach targeting within 1 week. Site accessibility failure (wheelchair user cannot access toilet, quiet room unavailable, stairs block entry) → reported by center staff or observed in accessibility spot-check; if not immediately remediable, site is closed to new entrants and referrals diverted to accessible sites within 4 hours. Geographic equity gap (highest-deprivation neighborhoods contribute <30% of enrollees by Month 6 = 2027-04-08) → Outreach Lead and partner-liaison officer launch targeted street-team and partner recruitment in those neighborhoods by Month 6.5 (2027-04-23); if coverage gap persists to Month 7 (2027-05-08), incident commander re-allocates outreach resources or requests additional partner commitments.

3. Critical Success Factor Tracking: Outreach Enrollment and Contact Success (60% Gate and Equity Reach)

Monitoring Tools/Platforms:

• Partner Call-Logging Spreadsheet (calls attempted, calls connected, consent obtained, reasons for no-contact, language of contact)
• Enrollment Registry by Partner and Neighborhood (tracked in intermediary systems; city receives aggregate counts only, GDPR-compliant)
• Outreach-Success Rate Calculation (success = call connected + information provided or referral accepted; gate = ≥60%)
• No-Wrong-Door Tracking (phone-line and in-person intake at centers; separate count from partner-based outreach)

Frequency: Daily during alert days to track active outreach; weekly during setup (Months 1-5 = 2026-11-08 to 2027-03-08) to validate scripts and partner readiness; real-time dashboard (rolling 7-day average) during season (Months 6.8-11.8 = 2027-04-23 to 2027-09-30) to identify contact-rate shortfalls before they compound.

Responsible Role: Outreach and Enrollment Lead and phone-line coordinator, with daily data aggregation from all intermediary partners (housing associations, social services, NGOs, pharmacies).

Adaptation Process: Real-time partner feedback loop: if a partner reports call-completion rates <50% on any alert day, Outreach Lead convenes emergency 24-hour review with that partner to diagnose (staff absence, script confusion, technical issue with phone systems, resident unavailability) and implement corrective action (additional staff surge, script simplification, extended calling window). Weekly review (Fridays 14:00, Months 1-5 = 2026-11-08 to 2027-03-08) compares actual script-test results (do residents understand the message and accept referral?) against baseline expectations; if acceptance is <60%, script is revised with partner input and focus-group tested by end of week. During season, if rolling 7-day average contact success falls <60%, Outreach Lead escalates to incident commander within 24 hours with proposed remediation (e.g., additional interpretation support, ambassador pairing with partners, extension of calling hours).

Adaptation Trigger: Individual partner monthly success rate <60% (measured as calls connected / attempts) for 2 consecutive weeks → Outreach Lead and partner representative meet within 48 hours; if partner lacks capacity, assess whether call targets should be reduced (triggering lower total enrollment) or supplemented by a backup partner or city-funded surge staff. If >2 partners fail the 60% threshold simultaneously, incident commander escalates to Steering Committee as a gate-failure risk by Day 7 of the alert week. Non-official-language contact rates <5% of total attempts (city-wide, month-on-month) → Language-access coordinator (Outreach Lead with community ambassadors) increases interpreter deployment or ambassador pairing with partners within 1 week; if gap persists to Month 8 (2027-06-08), escalates to incident commander and Steering Committee as equity-goal failure.

4. Critical Success Factor Tracking: Transport Capacity and Response Time (45-Minute Gate and Wheelchair-User Access)

Monitoring Tools/Platforms:

• Transport Dispatch Log (request timestamp, caller ID, destination choice, volunteer/taxi assignment, pickup time, actual arrival time, user feedback)
• Volunteer Driver Availability and Utilization Report (daily count of available drivers, requests served, average pickup time by priority level)
• Taxi-Operator Performance Report (requests assigned to taxi, response times, vehicle type deployed, accessibility match)
• Transport Stress-Test Results (pre-season May drill and simulated peak-demand scenarios)

Frequency: Real-time logging during alert days; daily summary at end of each alert day; weekly aggregate report on non-alert days during setup (Months 1-5 = 2026-11-08 to 2027-03-08); monthly Steering Committee dashboard during season (Months 6.8-11.8 = 2027-04-23 to 2027-09-30).

Responsible Role: Transport Lead / Dispatch Coordinator (1 FTE) and backup dispatcher (1 FTE), with data aggregation by PMO coordinator.

Adaptation Process: Daily alert-day debrief (18:00, Cooling-Center Operations Lead, Transport Lead, Outreach Lead, incident commander) reviews transport requests, response times, failed requests and reasons (volunteer unavailable, taxi delayed, resident refused transport). If average response time for any alert day is >45 min, Transport Lead convenes same-day remediation meeting with volunteer representative and taxi operator to identify bottleneck (e.g., volunteer geographic clustering, taxi dispatch lag, mismatched destinations). Corrective actions authorized same-day: re-position volunteers, alert taxi operator of high-demand geography, cascade requests to backup volunteers or additional taxi surge. Weekly review (Thursdays 14:00, Months 1-5 = 2026-11-08 to 2027-03-08) compares volunteer recruitment pipeline against targets (target 40, range 30-50; if <20 by Month 1.5 = 2026-11-23, proportionally increase taxi retainer by €10-30k). Wheelchair-user requests are flagged separately; if any wheelchair user waits >45 min or is assigned a non-wheelchair-accessible vehicle, incident commander is notified within 2 hours and Transport Lead submits same-day corrective-action memo.

Adaptation Trigger: Single alert-day average response time >45 min → Transport Lead escalates to incident commander within 4 hours with root-cause summary and corrective action. Sustained average >45 min over 2+ consecutive alert days → incident commander convenes Steering Committee emergency session within 24 hours; gate failure for Month 4 (2027-02-08) is flagged and remediation plan (additional taxi surge, volunteer recruitment acceleration, route optimization, standby expansion) is approved or budget reallocation authorized. Volunteer recruitment <20 by Month 1.5 (2026-11-23) → taxi retainer is scaled up by €10-30k (proportional offset) within 48 hours; if volunteer target remains unmet by Month 2 (2026-12-08), Month 2 (2026-12-08) readiness gate is conditional on taxi-retainer adequacy confirmation. Wheelchair-user wait >45 min or non-accessible vehicle assignment → incident commander is notified within 2 hours; if this occurs >1 time per week during season, Transport Lead meets with taxi operator to enforce wheelchair-accessible vehicle availability; if operator cannot comply, backup taxi provider is activated or volunteer recruitment for accessible vehicles accelerates.

5. Major Risk Tracking: Procurement and Supply-Chain Delivery (Cooling Kits and Transport Contracts)

Monitoring Tools/Platforms:

• Procurement Status Dashboard (order-placement dates, supplier lead times, delivery-date forecasts, expedite-cost exposure)
• Kit-Delivery Tracking Log (units ordered, units received, units in storage, units deployed, inventory aging)
• Taxi-Retainer Contract Performance Scorecard (standby fee, request volume, response times, vehicle availability, wheelchair-accessible units)

Frequency: Weekly during setup (Months 0-3 = 2026-10-08 to 2027-01-08) to confirm supplier timelines and place orders on schedule; bi-weekly during Months 4-7 (2027-02-08 to 2027-05-17) to track kit delivery, acceptance and handoff to handypersons; monthly thereafter.

Responsible Role: Procurement Specialist (0.5 FTE) and Home Kit Lead, with backup supplier coordination and expedite-authorization by incident commander.

Adaptation Process: Weekly procurement review (Thursdays 10:00, Months 0-3 = 2026-10-08 to 2027-01-08) confirms supplier lead times and confirms first call-off order (30-40% kit volume) is placed by Month 1.2 (2026-11-14); if supplier lead time exceeds 6 weeks, backup suppliers are activated immediately or expedite premium (estimated 10-15% cost increase, €50-100k) is approved by incident commander. Bi-weekly kit-delivery review (Mondays 10:00, Months 4-7 = 2027-02-08 to 2027-05-17) tracks: (1) kits received and passed quality inspection, (2) inventory turnover rate (kits deployed faster than plan indicates under-budgeting or slower indicates lagging installations), (3) handyperson installation pace (target 100% installed by Month 7.3 = 2027-05-17). If 40% of kits are not received by Month 4 (2027-02-08), gap is flagged as Month 4 (2027-02-08) gate-evidence risk; Home Kit Lead requests expedite at supplier or activates backup within 24 hours. Taxi-retainer scorecard (monthly, Mondays 14:00 Transport Lead review) tracks whether operator meets response-time commitment (<20 min), vehicle availability (≥10 vehicles ≥80% of alert days), wheelchair-accessible units (≥3, always available); if operator is underperforming on 2+ metrics 2 consecutive months, contract amendment or termination is escalated to incident commander.

Adaptation Trigger: Supplier delay of >3 weeks detected (e.g., unit does not ship by forecast date) → Procurement Specialist contacts supplier for expedite commit within 24 hours; if manufacturer cannot accelerate, backup supplier is contacted same day for alternative sourcing. Approval for expedite cost ≤€50k is granted by incident commander; cost >€50k requires Steering Committee approval. Kit delivery 2+ weeks late (would miss planned installation before June 1 = Month 6.8 = 2027-05-02 heat events) → Home Kit Lead escalates to incident commander with cost/timeline trade-offs (pay 15% premium for air-freight, or defer installations to July, or reduce kit count from 2,000 to 1,500). Decision is made within 48 hours and escalated to Steering Committee if contingency drawdown >€20k or scope reduction is needed. Taxi-operator performance failure (response time >25 min average, vehicle unavailability >2 alert days per week) detected in monthly scorecard → Transport Lead meets with operator within 48 hours to issue corrective-action notice (cure within 2 weeks or contract amendment/termination considered); if operator cannot cure, incident commander activates backup taxi provider or redirect requests to volunteer-only model if volunteer capacity permits.

6. Major Risk Tracking: GDPR Compliance and Partner Data-Protection (Legal Constraint and Operational Continuity)

Monitoring Tools/Platforms:

• Data-Processing Agreement (DPA) Sign-Off Tracker (status with each of 4+ partners, sign-off deadline Month 1.5 = 2026-11-23)
• Partner GDPR Compliance Audit Checklist (consent-record spot-check, staff-training attendance, data-handling practices, incident reporting)
• Breach-Incident Log (any reported or discovered data-handling violation; contact with data-protection authority if required)

Frequency: Monthly during setup (Months 0-2 = 2026-10-08 to 2026-12-08) to track DPA negotiation and sign-off; quarterly spot-check audit of partner compliance (Month 3 = 2027-01-08, Month 6 = 2027-04-08, Month 9 = 2027-07-08); real-time breach-incident log during entire project.

Responsible Role: Legal and GDPR Lead (0.5-1 FTE, may be municipal legal department or external GDPR counsel), with partner-liaison officer for audit coordination.

Adaptation Process: Monthly DPA sign-off check (Thursdays 10:00, Months 0-2 = 2026-10-08 to 2026-12-08) monitors each partner's review and approval of the template DPA; if a partner flags GDPR concerns (e.g., questions the lawful basis for contact), legal lead convenes immediate clarification call with GDPR counsel; legal response is provided within 48 hours and incorporated into revised DPA. Quarterly partner-compliance audit (Months 3, 6, 9 = 2027-01-08, 2027-04-08, 2027-07-08) spot-checks (per partner): 10-20 resident-contact consent records to verify explicit consent is documented; staff-training attendance logs to confirm all personnel have received GDPR and confidentiality briefing; data-handling practice observations (e.g., phone calls are logged correctly, personal data is not shared with unauthorized recipients); any-incident disclosure (e.g., 'we misdirected a call to a resident's adult child instead of the resident'). Audit findings are summarized in a report issued to the partner within 5 days, with corrective-action timeline (target: cure within 10 days). Real-time breach log: any partner or staff member can report a suspected data breach via a confidential hotline; legal lead investigates within 24 hours, assesses whether breach meets AEPD notification threshold (>100 residents at high risk, or health data exposed), and decides within 48 hours whether to notify the data-protection authority (mandatory within 48 hours if threshold met).

Adaptation Trigger: Partner DPA not signed by Month 1.5 (2026-11-23) deadline → legal lead meets with partner within 48 hours to identify blocking issue and issue a revised DPA with clarifications or remove partner from program if they cannot agree with lawful basis. >25% of partner staff audited are unable to articulate GDPR confidentiality rules (fail 'quiz' or cannot cite their confidentiality agreement) → partner is issued corrective-action notice requiring re-training within 2 weeks; legal lead may audit again post-re-training; if re-audit fails, partner is placed on enhanced oversight (weekly instead of quarterly compliance checks). Breach involving ≥10 residents (e.g., partner confirms it contacted 10 residents who had withdrawn consent) → legal lead and GDPR counsel assess severity and authority-notification requirement within 24 hours; if >100 residents potentially affected, AEPD notification is issued within 48 hours and incident commander notifies Steering Committee and funder immediately; corrective action (enhanced vetting, contract amendment, partner suspension) is authorized within 5 days. Serious breach involving health data (e.g., partner leaks resident's cardiac-disease flag to unauthorized third party) → immediate partner contract suspension pending investigation; legal lead escalates to incident commander and Steering Committee within 24 hours; funder is notified; AEPD notification issued within 48 hours; estimated GDPR fine exposure €10k-500k+ depending on negligence; program operational continuity assessed (can other partners absorb outreach load if breaching partner is terminated?).

7. Major Risk Tracking: Staffing Availability and Fatigue During Multi-Day Heat Waves (Operational Continuity and Service Degradation)

Monitoring Tools/Platforms:

• Staffing Roster and Absence Log (by role: cooling-center managers, support staff, dispatchers, phone operators, handypersons, outreach teams; daily headcount and sickness/leave record during alert days)
• Fatigue-Incident Report (any safety incident, staff complaint, or performance issue potentially related to overwork or fatigue)
• Service-Degradation Tracker (any reduction in center hours, transport dispatch delays, phone-line wait times, escalation failures correlated with staffing gaps)

Frequency: Daily during alert days to confirm available staff and escalate absences immediately; weekly review (Mondays 14:00) during non-alert periods to forecast staffing risk for next alert period; monthly fatigue-management audit (1st Friday of each month, Months 3-12 = 2027-01-08 to 2027-10-08).

Responsible Role: HR Coordinator (0.5 FTE, Months 0-4 = 2026-10-08 to 2027-02-08) and then PMO Coordinator (0.5 FTE, Months 5-12 = 2027-03-08 to 2027-10-08), with incident commander escalation authority.

Adaptation Process: Daily absence check: on each forecast alert day (by 06:30), all operational leads (Cooling-Center Operations, Transport, Outreach) confirm available staff numbers to incident commander and PMO coordinator; if any role is <80% staffed, incident commander convenes immediate 30-minute conference call to authorize: (1) cancellation or consolidation of lower-priority centers, (2) mutual-aid across departments (e.g., PMO staff back up phone line), (3) call-back of off-duty staff or authorization of overtime premium pay, (4) early stand-down criteria if alert is low-risk. Weekly forecast review (Mondays 14:00) compares staffing roster against planned alert-day scenarios and identifies upcoming gaps (e.g., 'July 15-17 alert forecast but 3 center managers on leave'); if gap cannot be filled with internal cross-training or scheduled overtime, incident commander approves emergency hire or temporary staffing agency contract within 48 hours. Monthly fatigue audit (Fridays 14:00): HR coordinator reviews incident logs, staff-sick-leave patterns, and performs anonymous staff surveys (5-question pulse check on workload, safety concerns, intent-to-stay); if fatigue-related absences are >10% in a given week or multiple staff report safety concerns, HR coordinator convenes immediate fatigue-management meeting with affected department lead and proposes: (a) shift-limit enforcement (no staff works >4 consecutive alert days), (b) peer-support or counseling access, (c) temporary reduction in service scope (e.g., close 1 lower-utilization center) to reduce demand, (d) staffing surge authorization.

Adaptation Trigger: Any alert-day staffing level <80% for a critical role (cooling-center manager, dispatcher, phone-line operator) → incident commander is notified by 06:00 on alert day; within 2 hours, contingency staffing is deployed (cross-training, mutual aid, emergency hire) and if not achievable, service reduction is announced to the public and partners (e.g., 'Due to staffing constraints, 2 of 10 cooling centers will close today; transport may experience 60+ minute delays'). Fatigue-related absence rate >15% in a given week (e.g., 3 of 18 cooling-center FTE out sick during a 3-day alert) → incident commander escalates to Steering Committee within 24 hours with assessment of service-degradation risk; if degradation >25% (fewer center-hours, longer transport times), Steering Committee may authorize temporary service reduction, additional staffing budget or alert-scope narrowing until staffing recovers. Staff-injury incident related to fatigue (e.g., transport dispatcher collision while driving during 6th consecutive alert day) or safeguarding breach due to fatigue (e.g., outreach worker mishandles heat-illness escalation) → immediate escalation to legal counsel, occupational health and Steering Committee; post-incident review and remedial training/rest is mandatory before staff returns to duty; incident commander re-evaluates fatigue-management protocols and may enforce stricter shift limits or surge-staffing thresholds.

Governance Extra

Governance Validation Checks

1. Completeness Confirmation: All core requested components are generated across five phases: Phase 1 audit procedures document corruption and misallocation risks; Phase 2 internal bodies establish 6 primary governance structures (Steering Committee, Operations Team, Cooling Centers, Outreach, Transport, Home Kits, Legal/GDPR, Evaluation); Phase 3 implementation plan sequences 47 detailed setup and operational steps (Months 0–12 = 2026-10-08 to 2027-10-08); Phase 4 decision-escalation matrix covers 5 major issue types with approval authority (gates, budget, GDPR, critical incidents, procurement); Phase 5 monitoring plan specifies tracking frequency, tools, and adaptation triggers for 7 critical success factors (gate metrics, equity reach, outreach success, transport time, procurement, GDPR compliance, staffing fatigue). Deliverables (playbook, cost model, evaluation report, Year-2 roadmap) are assigned by Month 12 (2027-10-08). Framework is comprehensive.
2. Internal Consistency Check: Logical alignment between stages is largely sound. Implementation plan sequences governance-body establishment and role recruitment appropriately (Months 0–2 = 2026-10-08 to 2026-12-08 setup, Month 3 = 2027-01-08 full-system drill, Month 4 = 2027-02-08 gate decision, Month 5+ sustained operations). Decision-escalation matrix correctly assigns budget/gate/GDPR escalations to Steering Committee with incident commander as escalation initiator; Operations Team has clear delegated authority for <€5k spend and operational decisions. Monitoring plan links gate-metric tracking to Operations Team weekly reviews and Steering Committee monthly dashboards, creating feedback loops. However, one consistency gap exists: the ultimate Project Sponsor's role and veto authority over Steering Committee decisions is not explicitly defined. If mayor is Chair but holds other portfolio responsibilities, who decides if mayoral-office capacity for incident command becomes unavailable mid-season? Delegation letter (Phase 3, Step 6) addresses backup authority only for alert declaration, not for strategic Steering Committee decisions (budget reallocation, gate interpretation, year-2 planning).
3. Process Depth and Clarity Gaps – Volunteer Safeguarding and Duty-of-Care Boundaries: Transport and Outreach sections mandate teams ≥2 (never solo) and reference 'safeguarding checks' and 'incident reporting,' but the actual duty-of-care protocols for encounters with heat-distressed residents are underdeveloped. Transport phase3 specifies vetting (background check, insurance, safeguarding screening) and Phase 5 includes fatigue-incident tracking, yet specific guidance on when staff should call EMS vs. provide water/shade, consent models for acute distress (e.g., disoriented elderly resident unwilling to go to center), and de-escalation scripts are missing. Street-contact pathway (risk register item) acknowledges 'consent and enforcement ambiguities' but governance bodies do not formally own protocols for contact with unhoused people; Street Contact Pathway group is listed in assumptions but not in Phase 2 internal bodies, creating a coordination gap if field incidents occur. Mitigation: Phase 3 should add a detailed step (Month 1.5 or 2 = 2026-11-23, 2026-12-08) for co-designing heat-illness escalation checklists with a municipal nurse adviser or occupational health partner, then validate in drills (Phase 5, monitoring).
4. Conflict-of-Interest Management and Independent Oversight – Limited Detail: Phase 1 audit mentions nepotism, kickbacks, and sole-source purchasing risks but does not specify how the Steering Committee or external evaluation partner (described as advisory, non-voting member) will oversee procurement integrity. No rotation of procurement authority, no competitive bid review by an independent panel, no post-award audit oversight are documented. External evaluation partner has full editorial autonomy over evaluation report (Phase 4, decision-escalation), which is good for independence, but no formal conflict-of-interest disclosure or independence certification from the university partner is specified. If the university is in Castellón or Valencia and has existing municipal relationships, potential bias is unaddressed. Mitigation: Phase 3 should add a month-0 step requiring: (1) procurement governance policy (lowest-price, best-value, or other criteria; bid review thresholds); (2) university partner independence declaration; (3) post-award audit schedule (quarterly, external auditor).
5. Escalation Path Endpoints and Authority Ambiguity: Several escalation paths terminate at vague endpoints. Phase 4 specifies that operational escalations reach 'incident commander' or 'Steering Committee,' but many decisions (e.g., GDPR policy change, contract termination of a major partner, major scope reduction) could exceed incident commander authority and Steering Committee voting authority. The phrase 'if still deadlocked, legal counsel issues binding opinion' (Phase 2, Steering Committee rationale) creates a de facto fourth authority (legal counsel) whose mandate and scope are not written. If legal counsel and the Steering Committee disagree on whether a gate failure is remediable or whether tranche-2 should be released on contingent terms, who breaks the tie? Phase 4 specifies 'city council' as an escalation destination for policy changes, but no decision-escalation matrix entry addresses city-council involvement in gate decisions or major budget reforecasts. Mitigation: Phase 3 should explicitly define: (1) which decisions require city-council notification vs. approval (gate release likely requires approval; staffing adjustment likely requires notice only); (2) define incident commander's upper spending and scope-change authority (current: <€5k); (3) clarify legal counsel's advisory vs. binding role; (4) establish a three-way tie-break rule (incident commander + Steering Committee Chair + legal counsel unanimous or defer to funder).
6. Processes for Thresholds, Triggers and Contingencies – Underspecified in Places: Alert-trigger thresholds (Level 1, 2, 3 by temperature and consecutive-day counts) are specified in Phase 3, Step 6, but stand-down criteria ('thresholds no longer met + 48 hours normal temperature') lack precision: does 'normal' mean <30°C, <25°C, <20°C? Historical baselines are not defined until Month 1 (2026-11-08) baseline audit (Phase 5), so the 48-hour stand-down rule cannot be operationalized until summer. Adaptation triggers in Phase 5 specify numeric thresholds for escalation (e.g., center occupancy <20% → review within 24 hours; contact-success rate <60% for 2 weeks → escalate) but do not define the decision rule for whether to modify the trigger itself after Month 7 (2027-05-08) if evidence accumulates that a threshold is wrong. Will thresholds be re-calibrated post-season for Year 2? Who owns that decision? Transport-time gate specifies <45 minutes average but internal priority target 30 minutes for mobility-limited; if average is 42 minutes but 70% of mobility-limited users wait >30 minutes, does the gate pass or fail? Mitigation: Phase 1 (audit procedures) should add a quarterly 'threshold validation review' (Months 2, 5, 8, 11 = 2026-12-08, 2027-03-08, 2027-06-08, 2027-09-08) where Operations Team compares gate thresholds against real data and recommends adjustments; Steering Committee approves threshold changes with documented rationale.

Tough Questions

1. **What is the current probability-weighted forecast for June–September 2027 heat-event frequency, multi-day-wave frequency, and night-temperature extremes in Castellón de la Plana, and how does this compare to the threshold assumptions (Level 2: high ≥35°C and low ≥22°C for ≥2 days; Level 3 for ≥3 days)? Will June–July likely produce sufficient real-world heat events to validate the Month 4 (2027-02-08) gates fairly, or should the contingency-funding rule for 50% conditional release be pre-approved now to reduce gate-decision risk in February?
2. Show documented evidence that the intermediary-held list model (housing associations, social services, NGOs, pharmacies making calls on behalf of the city) will achieve ≥60% contact success with ≥300 enrolled high-risk residents during the full-system drill (Month 3.2 = 2027-01-14). What are the partner's historical call-completion rates for similar populations, and what de-escalation or follow-up protocols will be used if a partner's contact rate falls below 50%?
3. **Produce a detailed volunteer-recruitment pipeline forecast: as of today (Month 0 = 2026-10-08), how many confirmed volunteer-driver prospects exist in the recruitment target (retirees, charity staff, faith-group members)? What are the monthly recruitment and vetting-completion rates from comparable municipal volunteer programs in Spain or EU cities? If recruitment reaches only 20–25 volunteers by Month 2 (2026-12-08) instead of the target 40, how will the taxi-retainer contract (currently capped €80k) be scaled to fill the gap, and does this fit in the €3.5M budget without cutting home kits?
4. **Verify baseline heat-related EMS and ED-visit counts: provide 3-year historical data (2024–2026) from Castellón de la Plana EMS and hospitals on calls/visits coded as heat-related, with data-quality audit (% complete, coding consistency, seasonal patterns). If such data does not exist, how will the city establish a defensible baseline by Month 1 (2026-11-08) for the evaluation protocol, and what are the assumptions about baseline uncertainty?
5. **Clarify the ultimate project sponsor's role and veto authority: if the mayor's office is the incident commander's seat and the mayor holds other portfolio responsibilities, who ensures continuity and strategic oversight if the mayor is unavailable (illness, leave, election transition) for >2 weeks during the critical Months 4–9 (2027-02-08 to 2027-07-08) period? Is the Steering Committee Vice-Chair (head of public health) authorized to make gate-release decisions unilaterally, or does Steering Committee require the mayor's attendance?
6. **Produce an operational plan for the Months 5–6 (2027-03-08 to 2027-04-08) contingency-funding scenario in which the Month 4 (2027-02-08) scale gate is not fully passed due to insufficient June heat events. If only 50% of €1.5M (€750k) is released contingently, which services are deferred or cut (e.g., are home kits paused, are backup volunteers stood down, are outreach targets reduced)? What is the staffing plan during May–June if the contingency release occurs, and are there specific escalation triggers to suspend or stand down services?
7. **Document the street-contact protocol for unhoused residents during alert days: who formally owns the outreach to this group (NGO partner or municipal team), what is the explicit duty-of-care boundary when staff encounter someone in acute heat distress or with mental-health crisis, at what point is emergency medical services (EMS) called vs. water/shade/transport offered, and what are the safeguarding and consent rules when a person cannot provide informed consent? Provide draft scripts and incident-escalation checklist for the drill (Month 3.2 = 2027-01-14).

Summary

This 12-month municipal heatwave mortality-reduction program in Castellón de la Plana, Spain (€3.5M, 43 FTE peak) uses a tiered-alert governance model with mayoral-level incident command, intermediary-held outreach lists (housing associations, social services, NGOs, pharmacies), 10 neighborhood cooling refuges, volunteer+taxi transport, and 2,000 home-kit installations. The framework balances equity reach (targeting 65+, isolated, poorly housed, migrants) with GDPR constraints and operational speed. Two hard gates (Month 2 = 2026-12-08 readiness: centers/transport/phone/training in place; Month 4 = 2027-02-08 scale: ≥80% center hours, ≥60% outreach contact, <45 min transport time) condition €1.5M tranche-2 release. Governance consists of a strategic Steering Committee (mayor, health, civil protection, communications, finance, external evaluation partner), an Operations Team (incident commander, deputies, communications), and six operational sub-bodies (cooling centers, outreach/enrollment, transport, home kits, legal/GDPR, evaluation/playbook). Key strengths: clear incident-command authority, intermediary model preserves privacy, drill-based gate evidence allows measurement even during cool seasons, equity tracking by neighborhood and demographic. Key gaps: insufficient detail on volunteer safeguarding and street-contact duty-of-care boundaries; escalation endpoints sometimes vague ("Senior Management"); limited contingency for staffing surge during extreme events; adaptation thresholds for standby reductions post-alert are undefined; role clarity for the ultimate Project Sponsor is not explicit within the hierarchies.

Suggestion 1 - Barcelona Climate Shelters Network (Xarxa de Refugis Climàtics)

Barcelona City Council's network of air-conditioned or cool public spaces (libraries, civic centers, schools, parks), launched in 2019 and expanded in later summers. Each site has set opening hours and a public map. The network works alongside the city's heat-wave plan and social-services outreach to older residents. Sites are municipal assets rather than new builds.

Success Metrics

Number of shelters in the network (the city reports a figure, not verified here) Share of residents within a short walk of a shelter (city-reported, not verified) Visits per season, reported by the city or the Barcelona public health agency

Risks and Challenges Faced

Uneven site quality and accessibility: the city published site information and expanded the network gradually. Low awareness among vulnerable residents: communication moved through social services and neighborhood networks. Staffing and opening hours at municipal sites: the network used existing site staff, with extended hours set by alert level.

Where to Find More Information

https://www.barcelona.cat (search 'refugis climàtics') Barcelona Climate Plan documents on the Ajuntament de Barcelona website Agència de Salut Pública de Barcelona (ASPB) publications

Actionable Steps

Contact the Barcelona City Council climate shelters programme team through the Ajuntament's official contact form or press office. Ask the Agència de Salut Pública de Barcelona for its heat-plan evaluation lead, to discuss refuge utilization and alert triggers. Request a call with the programme coordinator to review site-selection criteria and the accessibility checklist.

Rationale for Suggestion

Closest Mediterranean, Spanish-language match for the 'many small walkable refuges' design. It shows how to use libraries and community centers without construction, publish accessibility information and link refuges to social services. Barcelona is far larger than Castellón, so the scale does not transfer directly. Its siting logic does.

Suggestion 2 - Paris Plan Canicule and Registre Canicule (Ville de Paris / CCAS)

Paris runs a heat-wave plan with a voluntary registry of vulnerable residents (older, disabled or isolated people). The city's social-action agency (CCAS) phones registered people during alerts. The city also opens cooled rooms and 'cool paths' and runs a volunteer scheme (Paris Entraide / Registre Canicule). Alert levels follow Météo-France's national heat warnings.

Success Metrics

Number of people registered (published periodically by the city; not verified here) Share of registered people reached by phone during alerts (reported in post-event reviews) National post-2003 mortality reductions in later heatwaves (Santé publique France analyses)

Risks and Challenges Faced

Registry under-enrolls isolated people: enrolment was promoted through health professionals, social services and neighbours. Call-capacity peaks during alerts: CCAS staff and volunteers were mobilised, and calls were prioritised by vulnerability. Data-protection rules: registration is voluntary and consent-based with defined retention.

Where to Find More Information

https://www.paris.fr (search 'plan canicule') Santé publique France heat-health publications: https://www.santepubliquefrance.fr Météo-France vigilance canicule documentation

Actionable Steps

Contact the CCAS de Paris / Ville de Paris social-action department through the official website contact form to ask for the registry call protocol. Contact Santé publique France's environmental-health unit for the evaluation methods behind heat-mortality estimates. Ask for the consent form template and data-retention terms to compare with the Spanish AEPD requirements.

Rationale for Suggestion

Provides a documented consent-based registry, a phone-tree protocol and a tiered response keyed to national warnings, all within normal municipal powers and GDPR. This is what the 'no wrong door' enrollment and phone-tree design needs. Paris is a capital with far more resources, so the scale differs. The protocols are reusable. The plan's intermediary-list model differs from Paris's city-held registry, so the legal basis needs separate review in Spain.

Suggestion 3 - Ahmedabad Heat Action Plan (with NRDC and Indian Institute of Public Health Gandhinagar)

South Asia's first city-level heat action plan, launched in 2013 by the Ahmedabad Municipal Corporation with the NRDC and the Indian Institute of Public Health Gandhinagar. It uses colour-coded forecast-based alerts, trained health workers, outdoor-worker guidance, public education and cool-roof pilots. Ahmedabad has several million residents. Later evaluations and updates are available.

Success Metrics

Published analysis estimating avoided deaths per year after implementation (figure from the peer-reviewed study; not verified here) Expansion of the model to other Indian cities

Risks and Challenges Faced

Alert fatigue and threshold calibration: thresholds were revised using local mortality data over successive years. Reaching informal and outdoor workers: the plan used worker guidance, community health workers and media. Attribution of mortality change: published analyses state their limits.

Where to Find More Information

NRDC Ahmedabad Heat Action Plan reports: https://www.nrdc.org Peer-reviewed evaluation of the plan (search Ahmedabad Heat Action Plan evaluation, e.g. in Environmental Health Perspectives or PLOS)

Actionable Steps

Contact the NRDC India climate resilience team through the NRDC website to ask about alert-threshold calibration. Contact the Indian Institute of Public Health Gandhinagar's climate-health researchers for the evaluation protocol.

Rationale for Suggestion

Secondary suggestion, geographically distant. It is the best-documented example of a tiered alert ladder with pre-agreed actions and a published evaluation, which matches the plan's trigger design. Climate, housing and governance differ substantially from Spain, so only the alert, communication and evaluation structure transfer.

Summary

Reference projects for a Castellón de la Plana heatwave pilot (~170k residents, €3.5M, tiered alerts, small refuges, intermediary-held outreach, volunteer drivers with taxi backup). Mediterranean examples come first. Barcelona's climate shelter network and Paris's registry-based heat plan are close matches in climate and policy. Ahmedabad's Heat Action Plan is distant but is the best evidence for tiered alerts. Figures are approximate unless stated. Contacts are organisational roles, not named individuals. Verify all links and contacts before use.

1. Cool-Season Gate Measurement & Funder Evidence Acceptance

The Month 2 (2026-12-08) and Month 4 (2027-02-08) gates fall in the cool season with no real heat events. Funder acceptance of drill-based evidence is undocumented and is the single highest-risk assumption. If the funder rejects drills at Month 4 (2027-02-08), a €200–400k cash gap emerges, forcing mid-season cuts that harm residents during peak summer. This must be validated immediately before any other work proceeds.

Data to Collect

• Written funder confirmation that drill-based evidence is acceptable for Month 2 (2026-12-08) and Month 4 (2027-02-08) gates
• Funder's written acceptance of the partial-release rule (€750k at Month 4 = 2027-02-08 if gates are unmeasurable, remainder after Month 5 = 2027-03-08 re-test)
• Funder's definition of 'sufficient evidence' (e.g., minimum drill scale: transport requests, outreach attempts, center-hour activations)
• Contingency funding or credit-line commitment (€200–400k) if tranche-2 release is delayed
• Funder's policy on real-event validation: when would gates be re-tested if cool June–July occurs?

Simulation Steps

• Create a written 'Funder Communication Protocol' document specifying drill criteria, partial-release thresholds and contingency triggers; share with funder by email with 5-day response deadline (Month 0.2 = 2026-10-14)
• Schedule a synchronous video call (or in-person meeting if funder is local) by Month 0.3 (2026-10-17) to walk through the cool-season timing, drill protocol draft, and €200–400k cash-gap scenario; record funder's verbal position and follow up with written summary within 24 hours
• Use a simple decision-tree flowchart (drill evidence accepted? → proceed to Month 1 = 2026-11-08. Evidence rejected? → escalate to mayor's office, negotiate alternative funding) to clarify contingencies and distribute to all stakeholders

Expert Validation Steps

• Engage the funding organization's program officer (or their supervisor if the officer is hesitant) to confirm in writing that drill evidence meets their evidence standards; require explicit sign-off from someone with budget-authorization authority, not just program staff
• If the funder is a national or EU fund, consult the funder's published guidance on 'proof of concept' and 'pilot gate evidence' to identify any precedent for drill-based validation in other similar programs
• If the funder remains resistant, request an in-principle decision letter that allows the program to proceed with operational preparedness (Month 2 = 2026-12-08 gate) while deferring the scale-gate financial decision to Month 5 (2027-03-08) based on real-event data; this trades some timeline risk for certainty

Responsible Parties

• Project Manager/PMO Lead: draft and circulate funder-communication protocol
• Incident Commander: participate in funder discussion and confirm political/operational feasibility of partial-release scenario
• Funder's program officer: provide written responses and approve alternative funding pathways if needed
• Finance/CFO liaison: quantify the €200–400k cash-gap scenario and confirm municipal credit-line availability

Assumptions

• High: Funder will accept drill-based evidence for cool-season gates because operational readiness is measurable and real-event validation is unavoidable given the seasonal timing. Funder views this as a replicable risk for other pilot cities and has precedent (e.g., EU disaster-response pilots, climate-adaptation programs) for evidence-light early gates.
• High: A partial-release rule (€750k at Month 4 = 2027-02-08, remainder after May re-test) is financially and politically acceptable because it de-risks the program: the city delivers operationally, and the funder retains funding leverage to ensure quality. Both parties have aligned interest in scaling only if gates are truly met.
• Medium: Municipal credit-line or EU contingency funding of €200–400k is accessible within 48 hours if a tranche-2 release is withheld, allowing the city to bridge operations through June without immediate cuts. Historical precedent: municipalities can draw credit lines for cash-flow timing gaps.
• Medium: Funder defines 'sufficient drill evidence' as: ≥100 simulated transport requests, ≥200 outreach contact attempts, ≥2,000 center-hour activations, and all after-action items closed. These thresholds are achievable in a month-long drill protocol.

SMART Validation Objective

By Month 1 (2026-11-08), obtain written funder confirmation that: (1) drill-based evidence satisfies Month 2 (2026-12-08) and Month 4 (2027-02-08) gates if gates are measurable; (2) unmeasurable evidence triggers the €750k partial release at Month 4 (2027-02-08) and re-test at Month 5 (2027-03-08); (3) a contingency funding mechanism (credit line, clawback, or EU grant) is in place to cover any cash gap >€160k if tranche-2 is delayed beyond Month 4 (2027-02-08). Document in a signed amendment to the funding agreement.

Notes

• This is the single gate-release risk. All other risks (procurement, staffing, partner engagement) are operationally manageable; but if the funder withholds €1.5M at Month 4 (2027-02-08) due to evidence rejection, the program has no recourse within the current budget.
• Schedule this conversation for Month 0.2 (2026-10-14), before procurement and hiring begin. A 'no' from the funder at Month 4 (2027-02-08) means 4 months of wasted setup costs and broken promises to residents and partners.
• Document everything in writing. Verbal assent from the funder is not sufficient; a signed amendment to the funding agreement is required.

2. Procurement Lead-Time Validation & Supplier Backup Activation Triggers

Cooling kits (shading, fans, thermometers) must be ordered by Month 1.2 (2026-11-14) and delivered 40–50% by Month 4 (2027-02-08) to enable installation by Month 6 (2027-04-08) before the first heat events in May–June. EU suppliers typically require 6–8 weeks for mass-produced items. If the primary supplier slips by 4 weeks, kits arrive in June, missing the peak-risk May period and breaking the enrollment promise. No supplier relationships exist yet; this is a blind spot. Validation must occur by Month 0.8 (2026-11-01) to allow replan.

Data to Collect

• Detailed supplier quotes and firm lead-time commitments for kits (shading, fans, reflective blinds, thermometers, hydration supplies) from ≥3 primary vendors and ≥2 backup vendors
• Expedited-delivery cost premiums (% above standard price for 2–4 week acceleration) and minimum-order quantities per supplier
• Supplier capacity (available stock vs. custom-build timeline) and production constraints during Q4–Q1 (holiday season, Chinese New Year for Asian suppliers)
• Warehouse/interim-storage options and costs for 600–800 units staging area by Month 1.5 (2026-11-23)
• Logistics and duty/tariff information if kits are imported; border delays during Q4 are common

Simulation Steps

• Issue a detailed RFQ (Request for Quotation) to 5–8 regional and national suppliers by email by Month 0.3 (2026-10-17), specifying exact quantities (600–800 units for first tranche), quality specs, delivery address, and deadline for quote (5 business days). Use a standardized RFQ template with columns for supplier name, lead time (days), price, expedite-cost %, and available stock.
• Create a supplier-scoring spreadsheet (price, lead time, backup availability, geographic risk) and rank vendors; select top primary and 2 backups by Month 0.8 (2026-11-01). Model supply-chain scenarios: (a) primary supplier on-time, (b) primary slips 2 weeks, (c) primary slips 4+ weeks. For each scenario, calculate backup-activation cost and delivery date shift.
• Run a delivery-timeline simulation: if first order placed Month 1.2 (2026-11-14), when do kits arrive under each scenario? Create a Gantt chart showing planned vs. stress-test timelines; identify the 'point of no return' date (by which backup must be activated to retain May delivery).

Expert Validation Steps

• Contact 2–3 municipal procurement officers from comparable EU cities (Valencia, Barcelona, Italian cities) who have run home-kit distribution programs; ask for their supplier lead-time experience and any single-source-failure incidents they encountered. Document lessons learned and apply to Castellón's vendor selection.
• Engage a procurement specialist (€5–8k contract, 2–3 week engagement) to pre-qualify all identified suppliers, verify business registration and financial stability, and confirm that they can support emergency activation (48-hour order acceptance). Specialist delivers a 'supplier risk scorecard' rating each vendor on reliability, capacity-surge capability, and communication responsiveness.
• Request written commitment letters from primary and backup suppliers (by Month 1 = 2026-11-08) specifying: (a) firm price quote, (b) committed delivery date for ≥600 units, (c) 'emergency activation' trigger (city can order additional 200–300 units at 7-day notice with expedite fee capped at X%), and (d) penalty clauses if supplier misses committed date.

Responsible Parties

• Procurement lead: issue RFQs, track responses, score suppliers, negotiate backup agreements, maintain weekly delivery dashboard
• Finance/budget officer: confirm expedite-cost authorization (up to €200k premium) and interim-storage budget allocation
• Facilities/public works: identify and contract interim storage (500–800 m², lockable, climate-controlled, accessible for unloading)
• Primary and backup suppliers: provide firm quotes, delivery schedules, and emergency-activation agreements signed

Assumptions

• High: At least 2–3 credible suppliers exist in Spain or Portugal that can provide shading, fans, and thermometers at the required volume (600–800 units) within 6–8 weeks. Suppliers are willing to offer emergency-acceleration options for a 10–15% cost premium.
• Medium: Interim storage of 600–800 units (≈60–80 m² footprint, 2–3 pallets) is available within the municipal facility network at minimal cost (≤€500/month). Storage is secure, climate-controlled to prevent mold/humidity damage, and accessible for staged delivery to installation sites.
• High: Expedite-cost premiums for accelerated delivery are ≤15% (estimate: 10–15% above standard price). If actual expedite costs exceed 20%, the €200k budget buffer may be insufficient and cost-sharing with home-kit scope reduction becomes necessary.
• Medium: First-tranche orders can be placed by Month 1.2 (2026-11-14) without full specification approval from the city council or other governance bodies. Municipal procurement authority can issue orders directly for items <€100k per supplier or via existing framework agreements.

SMART Validation Objective

By Month 1.2 (2026-11-14), confirm in writing that: (1) primary supplier can deliver 600–800 units by February 2027 at a fixed price with penalty clauses; (2) 2 backup suppliers are pre-qualified and will activate within 7 days of notice if primary supplier slips >2 weeks; (3) interim storage (≥200 units) is secured at a municipal facility by Month 1.5 (2026-11-23); (4) all tranche-1 kit orders are placed by Month 2 (2026-12-08) with delivery confirmations locked in. Track against timeline weekly; trigger backup activation immediately if primary supplier misses any intermediate milestone by >7 days.

Notes

• This data collection must complete by Month 1 (2026-11-08) to allow a 2-week replan cycle before orders are placed at Month 1.2 (2026-11-14). Any discovery of supply-chain risk later will force immediate contingency spending or scope cuts.
• The €150–250k 'taxi-only fallback' is unavailable if kits also slip, because both are competing for budget: if transport costs rise by €150k AND kits are delayed (forcing expedite premium of €80–120k), the combined hit is €230–370k, exceeding the €160k available tranche-1 contingency by €70–210k.
• Build in a 10–15% buffer stock (100–200 extra units) in the first tranche to account for damage in transit, installation errors, or emergency replacement needs.

3. Volunteer Driver Recruitment, Vetting & Retention Pipeline Validation

The 45-minute transport-time gate depends on 40 volunteer drivers being vetted and operationally ready by Month 2–3 (2026-12-08 to 2027-01-08). Vetting includes background checks (10–14 days via police), insurance verification (7–10 days), and safeguarding training (3 hours per person). No recruitment partnership, no intake method, and no retention strategy are documented. If recruitment falls short of 20 by Month 1.5 (2026-11-23), the taxi retainer must be scaled up immediately (+€40–80k), forcing home-kit scope cuts from 2,000 to 1,500. This is a second-order risk with high financial impact; validation is critical by Month 1 (2026-11-08).

Data to Collect

• Recruitment partnership confirmations from ≥3 organizations (job centers, faith communities, NGO networks, retired-professional associations, universities) specifying intake procedures and expected volunteer yield (e.g., 'job center expects 15 applications/week for volunteer transport roles')
• Police background-check turnaround time and cost (per person); clarify holiday season delays (Q4 typically slower)
• Insurance requirements and available products (volunteer vehicle liability insurance, cost per driver, coverage limits)
• Baseline volunteer attrition rate from comparable municipal programs in Spain or EU (expected 15–25% by mid-season)
• Completed vetting pipeline as of Month 1.5 (2026-11-23): number of recruits in intake, vetting, training and fully-operational status

Simulation Steps

• Launch volunteer recruitment immediately (Month 0.1 = 2026-10-11) with a public call via job centers, faith organizations, municipal website and social media, specifying: role (flexible alert-day driver), time commitment (10–30 h/month average), pay (€12–15/h), and training provided. Set initial intake deadline Month 1.5 (2026-11-23) targeting 50–60 applications.
• Model the vetting pipeline as a flowchart with weekly cohorts (5–8 recruits per cohort starting Month 0.5 = 2026-10-23): background check (2 weeks turnaround), insurance verification (1 week), 2-hour safeguarding training (1 week), written test, and operational sign-off. Calculate expected yield: 60 recruits → ≈50 pass vetting → ≈40 active (20% early attrition) by Month 2 (2026-12-08).
• Track pipeline weekly on a public dashboard (numbers in intake, in vetting, in training, fully-approved) and flag any cohort that falls >1 week behind. Establish a decision rule: if <15 are fully vetted by Month 1.5 (2026-11-23), immediately activate the taxi-retainer scale-up trigger (increase capped offer from €80k to €100–120k and re-negotiate with operator for confirmed ≥15 vehicles).

Expert Validation Steps

• Contact 2–3 municipal volunteer-coordinator leads from Valencia, Barcelona, or other Spanish cities with active volunteer-driver programs; ask about: (a) typical recruitment yield (applications-to-vetted ratio), (b) vetting timeline and bottlenecks, (c) mid-season attrition patterns, (d) safeguarding incidents encountered. Document lessons and apply to Castellón's planning.
• Engage a specialist HR/recruitment consultant (€8–12k contract, 2–3 weeks) to design the recruitment campaign, identify partnership contacts, and provide a vetted list of 5+ recruitment organizations with confirmed capacity to support the volume target. Consultant delivers a 'recruitment risk scorecard' assessing each partner's ability to deliver on intake promises.
• Request written commitments from recruitment partners (job centers, faith organizations) specifying monthly intake target and current volunteer-driver candidate pipeline (e.g., 'job center has 10 active volunteer-driver candidates available immediately'). Verify they have capacity to promote the program and conduct intake screening.

Responsible Parties

• HR/Recruitment Coordinator: manage recruitment campaign, partner relationships, intake coordination, vetting tracking
• Volunteer Safeguarding Lead: conduct vetting reviews, training delivery, incident tracking, retention outreach
• Police/background-check liaison: communicate vetting turnaround times and manage batch submissions
• Insurance broker: verify coverage options and cost per driver
• Recruitment partner organizations: deliver intake candidates and conduct preliminary screening

Assumptions

• High: Recruitment partners (job centers, faith organizations, NGOs) can supply 50–60 volunteer-driver candidates by Month 1.5 (2026-11-23) from existing networks and media promotion. Yield from applicants-to-vetted is ≈70% (42 approved from 60 applicants), and early attrition by Month 2 (2026-12-08) is ≈20% (leaving 33 operationally available).
• Medium: Police background checks complete within 10–14 days per person under normal circumstances; Q4 delays (holidays, staffing) add 1–2 weeks. Batch submissions (weekly cohorts of 5–8) are more efficient than individual submissions.
• Medium: Volunteer vehicle insurance is available at ≤€500/year per driver, covering liability and personal injury. Municipal insurance policy may cover volunteers under an endorsement (cost TBD with broker).
• High: Mid-season volunteer attrition is 15–25%, with peak loss during July–August (multi-day heat waves, fatigue). A 40-volunteer target requires 50–52 recruits at Month 0 (2026-10-08) to sustain 40 active through Month 11 (2027-09-08).

SMART Validation Objective

By Month 1.5 (2026-11-23), confirm that: (1) ≥15–20 volunteer drivers are fully vetted and trained, in a pilot-ready cohort; (2) ≥30–35 recruits are in the vetting/training pipeline with confirmed completion dates by Month 2.5 (2026-12-23); (3) recruitment partners have signed commitments to continue intake and are on track to deliver ≥40 recruits by Month 3 (2027-01-08); (4) if <15 are fully vetted by this date, a written contingency decision is made to scale the taxi retainer and reduce home-kit scope. Conduct a 'recruitment stress test' (simulate dispatch demand with only 20 volunteers) at Month 2 (2026-12-08) and measure mean pickup time under fatigue.

Notes

• If recruitment falls short, the consequences are immediate and costly: <15 volunteers by Month 1.5 (2026-11-23) → trigger taxi-retainer scale-up (+€40–80k) → reduce home kits from 2,000 to 1,000–1,500 → lower equity reach and visible program credibility. This is a 'canary in the coal mine' for the whole program.
• Safeguarding vetting (criminal-record check, interview, references) is non-negotiable. Street-contact roles and transport for mobility-limited residents require high trust. Any corner-cutting on vetting exposes the city to liability and reputational damage.
• Build in a 20–30% reserve pool of vetted-but-inactive volunteers (15–20 people on a standby roster) activated only on Level 3 alerts or if active roster falls <25. This requires recruiting 60–70 total candidates to secure 40–50 active + 15–20 reserve.

4. GDPR Compliance & Data-Processing Agreement Validation

The intermediary-held-list model (housing associations, social services, NGOs, pharmacies) is central to GDPR safety but lacks explicit legal validation. Without written GDPR counsel opinion and signed data-processing agreements (DPAs) by Month 1.5 (2026-11-23), partner engagement will stall, and the city faces regulatory risk (AEPD investigation, €100k+ fines). If a partner withdraws mid-season citing GDPR concerns, outreach reach drops by 10–20%, failing the 60% contact-success gate. Legal clarity must be obtained by Month 1 (2026-11-08) to unlock partner recruitment and training.

Data to Collect

• Written GDPR legal opinion from a specialist law firm confirming that the intermediary-held-list model complies with GDPR Article 6 (lawful basis: consent or public task) and Spanish LOPDGDD Article 9
• Determination of whether the city is a joint data controller (Article 26 joint-controller agreement required) or data subject; clarity on processor relationships for each partner type
• Template data-processing agreements (DPAs) for housing associations, social services, NGOs, and pharmacies, specifying: data types, lawful basis, retention period, breach notification, audit rights
• Data Protection Impact Assessment (DPIA) screening or full DPIA for the health-data loop (hospital/EMS aggregate counts), assessing re-identification risk and controls
• Partner GDPR compliance readiness (do partners have existing data-governance policies, staff training, incident-reporting procedures?) assessed via a brief survey

Simulation Steps

• Engage a GDPR specialist law firm (€20–30k contract, 4–6 weeks engagement) by Month 0.5 (2026-10-23) with a detailed brief on the intermediary model, partner organizations, and data types. Request delivery of: (1) legal opinion memo (2–3 pages) on lawful basis and controller status, (2) template DPA for each partner type, (3) consent form (if consent-based) or ordinance (if public-task-based) translated into Spanish and Valencian, (4) DPIA template or summary for the health-data loop.
• Create a GDPR compliance checklist (partner data-handling practices, staff confidentiality, access logs, breach-reporting procedures) and distribute to all 4–6 main partners (housing associations, social services, NGOs, pharmacies) by Month 1 (2026-11-08), asking them to complete by Month 1.3 (2026-11-17) to identify gaps. Use a simple online form (Google Forms or equivalent) to collect responses.
• Prepare a Data Protection Impact Assessment (DPIA) for the health-data loop: document data flow (hospital → city), controls (aggregation, 12-month deletion), and residual risks (re-identification via postal code + age + sex); conclude with a recommendation (proceed with safeguards, or reject) by Month 1.5 (2026-11-23).

Expert Validation Steps

• Request written guidance from the Spanish Data Protection Agency (AEPD) (or consult published AEPD criteria/rulings on heat-alert contact) on whether intermediary-held lists and daily contact calls to enrolled residents constitute a lawful basis under Article 6 and LOPDGDD. AEPD formal guidance is not always available, but published opinions can clarify precedent. Allocate 2–4 weeks for AEPD response if a formal request is made.
• Have the GDPR counsel review each partner organization's existing data-governance policies and provide a 'compliance readiness rating' (green: ready, yellow: needs training, red: major gaps). Partners rated 'red' must remediate before enrolling in the program (e.g., adopt a privacy notice, document consent, implement access logs).
• Engage a municipal legal department representative (or city attorney) to review the signed DPAs before execution to confirm alignment with municipal liability and insurance policies. Confirm that joint-controller agreements do not create unexpected shared liability for the city if a partner breaches confidentiality.

Responsible Parties

• GDPR/Legal Officer: coordinate with counsel, draft consent forms/ordinances, oversee DPIA, manage partner compliance audits
• Specialist GDPR Law Firm: deliver legal opinions, template DPAs, DPIA template
• Partner organizations (4–6): complete GDPR readiness survey, execute DPAs, train staff on confidentiality and consent protocols
• Municipal legal department: review DPAs for liability implications, confirm alignment with municipal insurance

Assumptions

• High: The intermediary-held-list model (personal data never transferred to the city, only aggregates reported) complies with GDPR and Spanish law, because data controllers (housing associations, social services, NGOs) independently determine contact frequency and methods, and the city only specifies alert triggers. Joint-controller agreements (Article 26) clarify roles and liability.
• Medium: Partner organizations have (or can quickly adopt) basic data-governance practices: written privacy notices, documented consent, incident-reporting procedures, and staff confidentiality training. No partner will be unable to meet baseline GDPR compliance due to resource constraints.
• High: A lawful basis for heat-alert contact can be established under GDPR Article 6(1)(e) (public task) via a municipal ordinance, avoiding the need for explicit consent from every enrolled resident. If consent is required (Article 6(1)(a)), the consent form and withdrawal procedures are simple enough to implement at scale.
• Medium: The Spanish Data Protection Agency (AEPD) will provide timely guidance (within 2–4 weeks) on heat-alert contact lawfulness if a formal request is submitted; published AEPD criteria and precedent cases are available to inform the legal opinion if AEPD cannot respond.

SMART Validation Objective

By Month 1.5 (2026-11-23), obtain: (1) signed GDPR legal opinion confirming lawful basis (specify Article 6 basis: consent 6(1)(a), public task 6(1)(e), or hybrid) and controller/processor roles for each partner; (2) executed data-processing agreements signed by each of the 4–6 main partners, incorporating the legal opinion and DPA template; (3) written GDPR compliance readiness assessment for each partner, with remediation plan for any 'red-rated' gaps; (4) DPIA screening for the health-data loop completed and approved. Train 50–80 partner staff on GDPR, confidentiality and consent by Month 2 (2026-12-08). Conduct partner GDPR audit (spot-check consent records, access logs) at Month 9 (2027-07-08).

Notes

• GDPR compliance is a hard blocker: if the legal opinion is unfavorable or partners withdraw due to perceived GDPR risk, outreach enrollment collapses and the program is unviable. This must be validated by Month 1 (2026-11-08) before any partner recruitment or data-processing begins.
• The intermediary model is chosen to avoid personal data transfer to the city, but this also reduces the city's control over contact and audit rights. Joint-controller agreements must carefully define each party's role and liability so no party can claim the other is responsible for a breach.
• Data deletion is mandatory: all personal data (names, addresses, phone numbers) held by partners must be deleted within 30 days after Month 12 (2027-10-08) unless residents re-consent for Year 2. Ensure all partners understand and can execute this deletion.

5. Intermediary Outreach Network Capacity & Reach Validation

The 60% outreach-contact-success gate (Month 4 = 2027-02-08) depends on 4–6 intermediary organizations (housing associations, social services, NGOs, pharmacies) having adequate call-center capacity to contact enrolled residents on alert days. The plan assumes ≥3,000 enrolled, targeting 5,000 contact attempts per month in season, with 60% success (3,000 reached). However, no baseline capacity has been documented: How many staff do housing associations actually have available? What are their summer turnover rates? How many calls can they attempt per person per day? If partner capacity is <50% of assumptions, the contact-success gate will fail immediately, and the program has no contingency (the intermediary model does not allow the city to directly make calls). Capacity validation is critical by Month 1 (2026-11-08).

Data to Collect

• Current call-center staffing (FTE) per partner organization available for outreach during alert season (May–September)
• Typical call volume per staff member per day (calls/person/day) and average call duration (minutes/call)
• Summer turnover or availability constraints (staff take leave, competing priorities) with estimated capacity loss (%)
• Historical maximum call volume each partner has sustained (to establish baseline peak capacity)
• Infrastructure: do partners have telephone systems, call-logging tools, and real-time reporting capabilities to support daily tracking and escalation?

Simulation Steps

• Conduct a brief telephone survey (15–20 minutes per organization) of the 4–6 identified intermediary organizations by Month 0.8 (2026-11-01), asking their operations leads: current social-work/outreach staff count, average calls-per-day they handle, call duration, summer staffing constraints, and available data-tracking systems. Record responses in a standardized form.
• Create a capacity simulation: assume 3,000 enrolled residents, 5,000 contact attempts/month in season, ≥60% success. Distribute target across partners based on their size (e.g., social services 40%, housing associations 30%, NGOs 20%, pharmacies 10%). Calculate implied call attempts per staff member per day per partner. Identify any partner falling significantly short of required capacity.
• Model stress scenarios: if one partner drops out mid-season (capacity loss >30% due to staff illness or competing priorities), can remaining partners absorb the shortfall? Create a contingency-routing plan specifying which partners would take additional load.
• Prepare a mock-call simulation (5–10 sample calls per partner) at Month 1.5 (2026-11-23) to test their systems and measure actual call-taking speed and logging accuracy; use results to adjust capacity estimates and call scripts.

Expert Validation Steps

• Request written capacity commitments from each of the 4–6 partner organizations (by Month 1 = 2026-11-08) specifying: (a) baseline staff available for heat outreach during May–September, (b) committed contact-attempt target per alert day (e.g., 'social services will attempt 800 calls per alert day'), (c) escalation procedures if they fall short (e.g., 'if we cannot reach 60% by 12:00, city can activate backup partners'), and (d) confirmation that call-logging and real-time reporting are available.
• Consult with 2–3 municipal social services or NGO leads from comparable EU cities (Valencia, Barcelona, or other mid-sized cities) about their experience with intermediary-call programs: typical capacity utilization, seasonal constraints, and common failures. Identify patterns and red flags.
• Engage a call-center operations expert (€3–5k contract, brief review) to audit partner call-handling infrastructure and estimate realistic capacity under high-volume conditions (alert-day surge). Expert provides a capacity scorecard and recommendations for process improvements (e.g., batch-calling, shift rotation) to meet targets.

Responsible Parties

• Partner Liaison Officer: conduct capacity survey, obtain written commitments, monitor partner performance against targets
• Outreach Lead: design and run mock-call simulation, train partners on call scripts, provide real-time feedback during drills
• Each intermediary partner: supply capacity data, participate in mock drills, commit to contact-attempt targets in writing
• Call-center operations expert (contract): audit partner infrastructure and provide capacity recommendations

Assumptions

• High: The 4–6 identified intermediary organizations (housing associations, social services, NGOs, pharmacies) collectively have ≥30–40 FTE of social-work/outreach staff available for heat-alert contact work during May–September. Each organization can sustain ≥20–30 calls per day per staff member, yielding ≥600–1,200 combined attempts per alert day.
• Medium: Summer staffing loss (leave, competing crises) is ≤15% from baseline, so net available capacity remains ≥85% of normal staffing levels. No partner will experience >25% staffing loss in any single month.
• Medium: All 4–6 partners have access to telephone systems, basic call-logging (spreadsheet or minimal CRM), and the ability to report daily or weekly contact counts to the city. None require custom IT integration or data-pipeline setup beyond a shared secure spreadsheet.
• Medium: Partner staff are motivated to participate in heat outreach (alignment with their missions of supporting vulnerable residents) and will prioritize heat calls over competing work during Level 2–3 alerts. Intrinsic motivation is sufficient; no additional incentive payments are required.

SMART Validation Objective

By Month 1 (2026-11-08), confirm that: (1) each partner has provided a written capacity commitment (baseline staff, contact-attempt targets, data-tracking capability); (2) the combined capacity of all 4–6 partners equals or exceeds 5,000 contact attempts/month in season, with ≥60% expected success (≥3,000 reached); (3) a contingency routing plan exists: if any partner falls <50% of committed capacity by Month 2.5 (2026-12-23), city can reallocate that partner's target to backup partners or activate emergency outreach staff. Measure actual capacity in the full-system drill (Month 3.2 = 2027-01-14) with ≥300 simulated enrollment calls, and validate ≥60% success rate. If drill shows <55% success, adjust gate to 55–58% or activate escalation protocols.

Notes

• This is the second most critical operational gate after volunteer recruitment. If partners lack call capacity, the 60% contact-success gate will fail at Month 4 (2027-02-08), and there is no fallback: the city cannot directly call 3,000+ people without violating the GDPR intermediary model. The only recourse is to reduce the enrollment target (to 2,000 or fewer), which reduces the program's reach.
• Partner capacity is likely to degrade under multi-day heat events (July–August, Months 9–10 = 2027-07-08 to 2027-08-08) due to staff fatigue and competing demands. Capacity should be measured at realistic peak stress (not just average), and a 20% reserve should be built into staffing targets.
• If the mock-call simulation (Month 1.5 = 2026-11-23) reveals that partners can only sustain ≤40% contact success, escalate immediately to the outreach lead and incident commander. Options: (a) reduce enrollment target to 2,000, (b) activate city outreach staff directly (trade GDPR risk for reach), or (c) scale the taxi retainer (use transport drivers to hand-deliver alerts). Each option has budget or legal implications that must be resolved by Month 2 (2026-12-08).

6. Baseline Heat-Health Data Quality & Coding Validation

The Month 4 (2027-02-08) evaluation baseline depends on verified heat-related EMS calls (estimated 80–120 per summer) and excess mortality (estimated 15–25 deaths). These figures are provisional and unverified. If the actual baseline is 2–3× smaller (20–40 EMS calls, 5–10 deaths), the evaluation may lack statistical power to detect a real 10–15% reduction. Conversely, if baseline is larger (200+ EMS calls), the evaluation needs a larger sample and different comparison design. Coding practice also varies: some hospitals code heat explicitly (ICD-10 T67.0–T67.9), others code symptoms (dehydration, syncope) without flagging heat attribution. Without baseline clarity by Month 1 (2026-11-08), the evaluation design will be built on sand, and the month-12 report will reveal the analysis is underpowered or uninterpretable.

Data to Collect

• Three years (2023–2025) of heat-related EMS calls by date and location (postcode if available), coded as explicit heat-related or coded as symptoms (dehydration, syncope, collapse) that may be heat-attributable
• Three years of ED visits to the main hospital coded as heat-related or as heat-attributable symptoms; determine which ICD-10 codes are used
• Excess mortality estimates (per municipality or regional health authority) for hot-season months (June–September) for the past 3 years, with temperature-adjusted attribution if available
• Confirmation of which organization (EMS service, hospital, regional public health authority) maintains the authoritative baseline; who is the data custodian and what are access restrictions?
• Coding practice documentation: does the EMS use explicit 'heat-related' coding? Does the hospital? If not, how are heat-attributable cases identified (retrospective chart review, symptom pattern)?
• Data quality metrics: completeness (% of records with required fields), consistency across services, temporal patterns (do peaks match known heat events?)

Simulation Steps

• Request 3-year historical data (2023–2025) from the municipal EMS service, hospital ED, and regional public-health authority by email with a specific data-request form (identify variables: date, time, location, ICD-10 code, chief complaint, age, outcome). Request delivery by Month 0.8 (2026-11-01) to allow analysis time.
• Create a data-quality audit spreadsheet: calculate completeness (% of records with each variable), identify missing or inconsistent date ranges, flag any zero-count months (which may indicate data entry issues). Analyze temporal pattern: do high-count days or weeks align with known heat events from meteorological data (AEMET archives)?
• Conduct a manual coding review: sample 30–50 EMS call records and 30–50 ED visits coded as 'heat-related' and verify against clinical documentation (chief complaint, vital signs, treatment) that they are plausibly heat-attributable. Identify any false positives or false negatives.
• Compare the three-year average to the plan's provisional estimate (80–120 EMS calls, 15–25 deaths per summer). Calculate the magnitude of difference and assess power: if actual baseline is 30 EMS calls (vs. 100 estimated), a 20% reduction is only 6 cases/season, requiring a much larger comparison group or longer time series to detect statistically.

Expert Validation Steps

• Engage a heat-health epidemiologist (€10–15k contract, 4–6 weeks) to audit the baseline data, assess coding practice, and recommend a temperature-adjusted baseline model (e.g., regress EMS calls on daily mean temperature and prior-day maximum to estimate expected calls at different heat levels). Epidemiologist delivers a 'baseline validation report' with confidence intervals and recommendations for the evaluation design.
• Contact the director of the municipal EMS service and hospital ED to confirm: (a) whether they code heat-related cases explicitly, (b) if not, whether a retrospective review is feasible to identify heat-attributable cases from clinical notes, and (c) whether they can provide daily aggregate counts by 10:00 a.m. next day during the season.
• Request written confirmation from the regional public-health authority (or Ministry of Health) regarding heat-attributable excess-mortality estimates for the city for prior years (2023–2025). This is typically published post-hoc (3–6 months after summer) and uses temperature-adjusted regression; use published estimates as a benchmark for the program's year-one evaluation.

Responsible Parties

• Data/Evaluation Coordinator: request and receive historical data, conduct quality audit, manage epidemiologist contract, deliver baseline report
• Heat-health epidemiologist (contract): validate coding, build temperature-adjusted model, assess power, provide evaluation-design recommendations
• EMS service director: confirm coding practice, commit to daily-count reporting during season, clarify access restrictions
• Hospital ED director: same as EMS
• Regional public-health authority: provide excess-mortality estimates and temperature-adjustment methodology

Assumptions

• High: Heat-related EMS calls and ED visits are coded or documented in a way that can be identified from administrative data (ICD-10 codes, chief complaint text, or retrospective chart review). Baseline data for 2023–2025 is available and accurate.
• Medium: The actual baseline (80–120 EMS calls, 15–25 deaths per summer) is accurate within ±50% (i.e., actual range is 40–180 EMS, 8–38 deaths). The provisional estimate was based on published literature or peer-city benchmarks, not uninformed guessing.
• Medium: EMS and hospital data systems can produce daily aggregate counts (no identifiable patient data) by 10:00 a.m. each day during May–September. Neither service requires >1 hour of manual compilation per day; automated or semi-automated reports are feasible.
• High: Statistical power to detect a 10–15% reduction in EMS calls or ED visits is adequate given the baseline size. If the actual baseline is much smaller than estimated (e.g., 30 calls/season vs. 100 estimated), power calculations must be redone and the evaluation may be under-powered to detect effects smaller than 30–40%.

SMART Validation Objective

By Month 4 (2027-02-08), deliver: (1) a 'baseline validation report' confirming the 3-year average of heat-related EMS calls, ED visits and excess mortality with confidence intervals and coding-quality assessment; (2) a temperature-adjusted baseline model showing expected EMS/ED calls at different heat levels (for comparison during evaluation); (3) confirmation of data-custodian roles and real-time reporting procedures (hospital and EMS will provide daily aggregates by 10:00 a.m. during alerts); (4) statistical power calculation for the evaluation: given the actual baseline size, what reduction (%) can be detected with 95% confidence using a comparison-group design? If power is insufficient (e.g., actual baseline is 30 EMS calls and expected detection limit is >30% reduction), document the limitation explicitly in the evaluation plan and the final report.

Notes

• Baseline data quality is foundational. A poorly documented or inconsistently coded baseline will undermine the credibility of the final evaluation, even if the program was operationally successful. Time spent validating the baseline now (Month 1 = 2026-11-08) pays dividends at Month 12 (2027-10-08).
• If the actual baseline is much smaller than estimated (e.g., Castellón de la Plana has typically only 30–40 heat-related EMS calls per summer, not 80–120), the program should not increase the annual target to artificially inflate effect size. Instead, the evaluation design should be revised to focus on secondary outcomes (cooling-center utilization, transport equity, partner engagement) or to extend the evaluation timeline to Year 2 to accumulate larger sample sizes.
• Heat-attribution is inherently uncertain: not all ED visits coded as 'heat exhaustion' are caused by heat (some are concurrent conditions), and not all heat-related deaths are coded as such (some are coded as cardiac, stroke, or unspecified). The evaluation should state these limitations explicitly and use confidence intervals rather than point estimates.

7. Cooling-Center Accessibility & Facility Readiness Audit

The Month 2 (2026-12-08) readiness gate requires ≥50% of cooling-center places (≥200 of ≈400) to be fully accessible (wheelchair ramps, accessible toilets, quiet rooms, water, signage). The plan identifies 10 sites (libraries, community centers, parish halls, sports facilities) but has not audited them. Accessibility remediation can cost €10k–40k per site and take 2–4 weeks; any site failing accessibility by Month 2 (2026-12-08) will be deferred to July or dropped, reducing planned capacity and forcing more residents to depend on transport. This gate is hard to achieve without early action; validation must occur by Month 1 (2026-11-08).

Data to Collect

• Physical accessibility audit results (from a certified accessibility auditor or municipal building inspector) for each of the 10 proposed cooling-center sites: wheelchair ramps, elevator/lift access, accessible toilet facilities (grab bars, height, door width), water fountains or stations, signage (large print, pictograms), quiet/low-stimulus rooms, emergency exit routes
• Remediation cost estimates and timelines per site (who will do work, how long, cost cap for the site to remain eligible)
• Site capacity (number of places available for residents, parking, water and toilet ratios relative to occupancy)
• Facility-use agreements (MOU or lease) confirmation: can the city open the site during alert hours (10:00–20:00 at Level 2, potentially 24-hour at Level 3)?
• Staffing and security arrangements per site: who manages the site, are there existing staff, do they need training on heat-illness first aid or escalation procedures?

Simulation Steps

• Schedule accessibility audits for all 10 proposed sites by Month 0.8 (2026-11-01), with audit completion by Month 1 (2026-11-08). Use a standardized accessibility checklist (e.g., following Spanish accessibility standards or EU accessibility guidelines): wheelchair access, toilet accessibility, quiet room presence, water availability, signage, emergency routes. For each site, generate a 'green/yellow/red' rating (green = fully accessible now, yellow = minor remediation <€5k and <2 weeks, red = major work or unsuitable).
• Create a remediation scorecard: list all sites, their accessibility rating, estimated cost and timeline for remediation. Prioritize the 8 'greenest' sites for opening at Month 2 (2026-12-08). For any 'yellow' sites, confirm remediation can be completed by Month 2 (2026-12-08) (4 weeks away from Month 0.8 = 2026-11-01) and commit budget. For any 'red' sites, recommend deferral to July or dropping from the network.
• Prepare a site-opening readiness checklist per site: facility MOU signed, manager named, staff identified, first-aid and heat-illness training scheduled, water/toilets operational, signage installed, quiet room designated, accessible entrance clear, emergency procedures posted. Use this checklist for the Month 2 (2026-12-08) gate audit.

Expert Validation Steps

• Engage a certified accessibility auditor (or municipal building inspector with accessibility expertise) (€8–12k for 10 sites, 2–3 weeks) to conduct professional accessibility audits. Auditor delivers a detailed report per site with photographs, remediation recommendations and cost estimates.
• For any site rated 'yellow' (remediable), obtain quotes from 2–3 contractors for the specified remediation work. Confirm timelines fit within the 4-week window (Month 0.8 = 2026-11-01 to Month 1.3 = 2026-11-17 to 2026-11-17) and budget (≤€10k per site cap is specified in the plan; anything higher requires exception approval).
• Consult with representatives from disability-advocate organizations or wheelchair-user groups in Castellón de la Plana (if such groups exist) to validate the accessibility audit findings and ensure that the audit captures real usability barriers, not just regulatory compliance (e.g., the presence of a ramp is not enough if the slope is too steep for a wheelchair user to navigate alone).

Responsible Parties

• Cooling-Center Network Manager: coordinate accessibility audits, collect site responses, manage remediation timeline and budget, ensure MOUs are signed
• Certified accessibility auditor (contract): conduct 10-site audits, deliver detailed findings and cost estimates per site
• Facilities/public works: approve remediation work, hire contractors, oversee completion, confirm timeline
• Site managers/facilities partners: participate in audit, confirm capacity for staffing and alerts, sign MOUs

Assumptions

• High: At least 8 of the 10 proposed sites (libraries, community centers, parish halls, sports facilities) in Castellón de la Plana are already reasonably accessible (wheelchair ramps, accessible toilets) or can be made accessible with minor remediation (≤€10k, ≤4 weeks). No site requires major construction work (e.g., elevator installation, structural modifications) which would be prohibitively costly.
• Medium: The 8 accessible sites collectively provide ≥200 places (50% of 400 planned) and are distributed geographically to serve most neighborhoods within walking distance. The distribution is equitable: no single site dominates, and high-need neighborhoods (high deprivation, many 65+ residents) are within 800 m of at least one site.
• Medium: All 10 proposed facility partners (libraries, community centers, churches, sports clubs) are willing to open during alert hours (10:00–20:00 at minimum, potentially 24-hour at Level 3) and to sign facility-use MOUs. No partner will withdraw or impose unreasonable conditions (e.g., extreme costs, unavailability on weekends).
• Low: Existing facility staff can be trained on heat-illness recognition and escalation within 1 day (4 hours), and no additional safety equipment (AED, first-aid supplies) is missing or unavailable. Minimal capital investment beyond training is required.

SMART Validation Objective

By Month 1.5 (2026-11-23), confirm that: (1) all 10 proposed sites have been audited for accessibility, with results documented in a standardized format; (2) at least 8 of 10 sites are rated 'green' (fully accessible) or 'yellow-remediable' (minor work <€10k, <4 weeks); (3) remediation for all 'yellow' sites is scheduled and funded by Month 2 (2026-12-08); (4) the cumulative places available in all 'green' and remediated 'yellow' sites equals or exceeds 200 (50% of 400 planned); (5) facility-use MOUs are signed for at least 8 sites, specifying hours, staffing, liability and accessibility requirements; (6) each site has a named manager, identified staff, and scheduled training dates. Any 'red'-rated site is either dropped or deferred to July; do not include it in Month 2 (2026-12-08) gate calculation.

Notes

• Accessibility audit is a gating item: if 6 of 10 sites are rated 'red' (unsuitable), the program loses 60% of planned capacity, forcing a network redesign and potentially a delay to the Month 2 (2026-12-08) gate. Early audit (Month 0.8 = 2026-11-01) provides time to pivot if needed.
• Accessibility includes not just wheelchair access but also quiet rooms for residents with sensory sensitivities, accessible water fountains (not just toilets), and legible signage for people with low vision. A site may have a wheelchair ramp but be otherwise noisy or overwhelming for an older person with anxiety.
• If a key site (e.g., a central sports hall with 80+ places) fails accessibility, the fallback is to reduce the planned network size and increase focus on the 8 accessible sites, which may mean fewer places within walking distance for some neighborhoods. This trade-off should be decided by the incident commander and funder before Month 2 (2026-12-08).

Summary

Immediate Actionable Tasks

Critical path (complete by Month 1 = 2026-11-08):

1. Funder Evidence Acceptance (Item 1): Obtain written funder confirmation that drill-based gates are acceptable and that the €750k partial-release rule applies if evidence is insufficient. This is the highest-risk assumption; proceed with confidence only after written sign-off. If the funder refuses, immediately escalate and renegotiate funding structure or identify contingency credit line.

2. Procurement Lead-Time Validation (Item 2): Issue detailed RFQs to 5+ kit suppliers, obtain firm quotes and delivery commitments, and pre-qualify 2–3 backup suppliers with emergency-activation agreements by Month 1 (2026-11-08). Lock in first-tranche orders by Month 1.2 (2026-11-14) with February delivery confirmation. Any slippage >2 weeks triggers backup activation immediately.

3. Volunteer Recruitment Launch (Item 3): Begin volunteer driver recruitment immediately (Month 0.1 = 2026-10-11) targeting 50–60 candidates, establish a rolling vetting pipeline with fortnightly cohorts, and track pipeline status weekly. If <15 are fully vetted by Month 1.5 (2026-11-23), immediately activate the taxi-retainer scale-up trigger to €100–120k and accept reduced home-kit scope.

4. GDPR Compliance Kickoff (Item 4): Engage GDPR specialist law firm by Month 0.5 (2026-10-23) (€20–30k, 4–6 weeks). Obtain written legal opinion on lawful basis and controller/processor roles by Month 1 (2026-11-08). Finalize and execute all partner data-processing agreements by Month 1.5 (2026-11-23). No partner recruitment or outreach training can proceed without signed DPAs.

5. Intermediary Capacity Survey (Item 5): Conduct brief capacity survey of all 4–6 intermediary partners (housing associations, social services, NGOs, pharmacies) by Month 0.8 (2026-11-01). Obtain written capacity commitments (staff, contact-attempt targets) by Month 1 (2026-11-08). If combined capacity is <4,000 contact attempts/month or if expected contact-success rate is <55%, escalate to outreach lead and incident commander immediately for contingency planning.

6. Baseline Data Request (Item 6): Request 3-year historical heat-related EMS calls, ED visits and mortality data from EMS, hospital and regional public-health authority by email (Month 0.3 = 2026-10-17). Commission a heat-health epidemiologist (€10–15k, 4–6 weeks) to validate baseline by Month 1 (2026-11-08). If actual baseline is <50 EMS calls per summer (vs. 80–120 estimated), flag power limitation for the evaluation design immediately.

7. Cooling-Center Accessibility Audits (Item 7): Engage certified accessibility auditor (€8–12k, 2–3 weeks) to audit all 10 proposed sites by Month 1 (2026-11-08). If >3 sites are rated 'red' (major remediation), escalate site-selection decisions to the cooling-center network manager and incident commander immediately. Confirm ≥8 accessible sites by Month 1.5 (2026-11-23).

High-impact decision points:

• Month 0.5 (2026-10-23): Funder response to drill-based gates and partial-release rule must be written. If funder refuses, activate contingency funding or re-scope gates.
• Month 1 (2026-11-08): Incident commander, GDPR counsel, epidemiologist, and accessibility auditor all deliver key findings. Major decision point: if any single item fails (funder refusal, GDPR blocker, baseline underpowered, accessibility gap), escalate to mayor's office and steering committee for re-scope options.
• Month 1.5 (2026-11-23): Volunteer recruitment, partner capacity, and DPA execution all converge. If any are short of target, trigger immediate contingency (taxi scale-up, reduced kit scope, GDPR re-negotiation with partners).
• Month 2 (2026-12-08): Readiness gate passed or failed based on procurement orders placed, volunteer vetting progress, partner DPAs signed, and site accessibility confirmed. Any failed gate criterion requires immediate corrective action or program re-scope.

Validation sequence: Start with Items 1 and 4 (funder + GDPR) in parallel immediately, as they are legal/governance blockers. Simultaneously, launch Items 2, 3, 5 and 7 (operational work). Complete Item 6 (baseline) by Month 1 (2026-11-08) to inform evaluation design. All seven items should be substantially complete by Month 1.5 (2026-11-23) to de-risk the Month 2 (2026-12-08) readiness gate.

Documents to Create

Create Document 1: Heat Response Program Charter

ID: 0bcf463d-731c-446f-9d67-733e1f376c31

Description: Project charter defining goals, scope, constraints, stakeholders, and governance structure for the 12-month municipal heatwave-response pilot in Castellón de la Plana. Establishes authority, budget, timeline, and decision-making framework. Audience: city leadership, funder, partners, operational team.

Responsible Role Type: Project Manager / PMO Lead

Primary Template: PMI Project Charter Template

Secondary Template: EU Public Health Program Charter

Steps to Create:

• Synthesize project brief and SMART criteria into a one-page executive summary.
• Define scope: 10 cooling refuges, 40 volunteer drivers + taxi retainer, 5,000 outreach contact attempts, 2,000 home kits, health-data loop, worker protection, communications.
• Specify hard constraints: €3.5M cap, 12-month duration, no new legislation, GDPR limits, no major construction.
• List four scale gates (Month 4 = 2027-02-08): 80% center hours, 60% outreach success, <45-min transport, after-action closure.
• Name incident commander (mayor's office), public-health deputy, operations lead, communications lead, partner-liaison officer.
• Obtain signatures from mayor, funder representative, and incident commander by Month 0.5 (2026-10-23).

Approval Authorities: Mayor's office, funder, incident commander, public-health department director

Essential Information:

• Define the 12-month pilot scope in Castellón de la Plana: ~10 cooling refuges, 40 volunteer drivers + taxi backup, 5,000 outreach contact attempts, 2,000 home kits, health-data coordination, worker protection and multilingual communications.
• Establish hard constraints: €3.5M total cap (€2.0M initial, €1.5M conditional at Month 4 = 2027-02-08), no new legislation, GDPR compliance limits, no major construction, realistic hireable staffing.
• Specify the four scale gates (Month 4 = 2027-02-08): (1) ≥80% of planned cooling-center hours delivered; (2) ≥60% outreach contact success from ≥300 attempts; (3) mean pickup time <45 minutes over ≥30 requests including wheelchair users; (4) after-action report completed with 100% of corrective actions closed.
• Name the incident-command structure: mayor's office incident commander with public-health deputy, civil-protection operations lead, municipal communications lead, partner-liaison officer. Obtain written mayoral delegation of authority by Month 1 (2026-11-08) specifying trigger thresholds and backup authority.
• List critical dependencies: GDPR counsel opinion and partner data-processing agreements by Month 1.5 (2026-11-23); all procurement orders (kits, transport retainer, refuge fit-out, handyperson services) by Month 2 (2026-12-08); staff and volunteer vetting completed by Month 2 (2026-12-08); hospital/EMS aggregate-data MOU by Month 1 (2026-11-08).
• Define the readiness gate criteria (Month 2 = 2026-12-08): ≥8 of 10 sites contracted and staffed; ≥50% places fully accessible; transport retainer and ≥20 volunteer drivers vetted; heat helpline live and tested; all staff and partner training ≥80% complete; all tranche-1 procurement orders placed.
• Specify budget allocation across categories: Refuge network €850k; Transport €380k; Outreach/phone/street €450k; Home kits €800k; Health coordination €120k; Worker protection €50k; Communications/language €170k; Governance/PMO/legal/evaluation/playbook €400k; Contingency €280k (8% reserve).
• Set contingency-funding rules for gate failure or measurement uncertainty: failed gate = no release; unmeasurable/insufficient evidence (e.g. cool-season heat events absent) = €750k (50%) released at Month 4 (2027-02-08) with remainder after Month 5 (2027-03-08) re-test.
• Identify funding gaps and Year-2 sustainability: Year-2 recurring cost ≈€2.3M estimated for same footprint; funding source not identified. Taxi-only fallback scenario (+€150-250k) requires €40-240k above the €160k tranche-1 contingency if also paired with delayed-release cash gap.
• Establish the drill-and-rehearsal schedule: full-system drill Month 3.2 (2027-01-14); after-action corrective actions closed by Month 3.9 (2027-02-04); gate decision Month 4 (2027-02-08); second drill, transport stress test and stand-down drill by Month 7 (2027-05-08) before peak summer.

Risks of Poor Quality:

• Ambiguous or missing incident-command authority delays alert declarations by 6-12 hours during critical heat events, losing response time. Politicized or unsigned delegation invites legal challenge to alert decisions, undermining credibility with partners and the public.
• Incomplete or vague scope definition (unclear refuge footprint, transport capacity or outreach target groups) causes rework in procurement, hiring and partner contracting. Estimated delay: 2-4 weeks into the operational period; cost impact: €50-150k in expedited hiring or procurement.
• Unspecified gate criteria or measurement rules (e.g., unclear what constitutes ≥80% center hours or how to measure during a cool season) create disputes over funding release and erode funder and stakeholder confidence. Exposure: €1.5M release withheld or delayed by 4-8 weeks.
• Missing or incomplete budget allocation across workstreams creates mid-project conflicts over resource prioritization. If transport retainers or kit procurement are under-resourced, the program will fail gates (45-minute transport target, home-intervention coverage) and revert to lower-cost but less effective alternatives.
• Unclear staffing plan (FTE numbers, hiring timeline, role responsibilities, fatigue protocols) causes operational gaps during multi-day heat-wave surges. Centers close early or operate at reduced hours, phone line experiences long waits, transport dispatch slows. Estimated reach loss: 10-25% reduction in service capacity; staff turnover and burnout cost €10-20k per person.
• Weak or missing contingency-funding rules expose the program to €200-400k cash-flow gap if the Month 4 (2027-02-08) gates cannot be measured fairly (e.g., cool-season heat events absent) or are failed. Forced mid-summer contraction or project suspension damages equity, media credibility and partner trust.
• Unspecified GDPR and data-protection milestones or oversight mechanisms allow partners to proceed without clear lawful basis for outreach contact. Data regulator challenge or partner breach mid-season could halt outreach operations and reduce enrollment reach by 10-20%, failing the 60% contact-success gate.
• Absent or incomplete critical-path dependencies (e.g., procurement timelines, volunteer-vetting processes, facility-fit-out schedules) mean Month 2 (2026-12-08) readiness gate may be missed. Kit delivery slips beyond April, home interventions begin 4-8 weeks late, missing early-May heat events. Estimated mortality-impact loss: 15-25%.

Worst Case Scenario: The Heat Response Program Charter is not created, or is created with significant gaps and ambiguity. Result: At Month 1 (2026-11-08), the team lacks a written reference point for scope, authority and decision rules. Incident-command authority is unclear, GDPR compliance strategy is unsigned, and procurement does not proceed on time. The Month 2 (2026-12-08) readiness gate is missed by 3-4 weeks due to delayed contracting and staffing. By Month 4 (2027-02-08), facilities are not fully operational, volunteer drivers are under-vetted, and kits have not arrived. June heat events occur (or a drill is conducted), and gates are failed or unmeasurable due to incomplete preparation. The funder withholds the €1.5M release pending a re-test. By August (peak-risk period), the program is underfunded and contracted back to 3-4 refuges and minimal transport capacity. Vulnerable residents dependent on cooling centers and transport find services unavailable or degraded. Media reports elderly deaths during a heat wave, blaming failed program response. Political accountability questions undermine the playbook's credibility and scaling prospects. Year-2 funding is not approved, and the pilot closes. Estimated financial impact: €300-600k wasted; estimated excess mortality unpreventd: 5-15 additional heat-related deaths; reputational cost: program cited as cautionary example in EU heat-response discussions.

Best Case Scenario: The Heat Response Program Charter is completed by Month 0.5 (2026-10-23) with clear, authoritative definitions of scope, constraints, governance, gates and contingencies. The charter is signed by the mayor, funder and incident commander, establishing binding commitment and decision-making authority. Result: By Month 1 (2026-11-08), mayoral delegation is in place, GDPR counsel opinion is obtained and partner MOUs are drafted. Procurement proceeds on time; kits and transport contracts are ordered by Month 1.5-2 (2026-11-23 to 2026-12-08). Staff hiring follows the staggered schedule; volunteer recruitment yields 35+ drivers by Month 2 (2026-12-08). The Month 2 (2026-12-08) readiness gate is passed on schedule with all refuges contracted, staffed and accessible, phone line live and tested, and all procurement orders placed. A full-system drill in January (Month 3.2 = 2027-01-14) demonstrates operational readiness; after-action corrective actions are closed by Month 3.9 (2027-02-04). At Month 4 (2027-02-08), gates are measured via combined drill data and early summer heat events (or contingency re-test rule if cool-season). The €1.5M scale release is approved and flows on schedule by March (Month 5 = 2027-03-08), funding peak-summer operations (June-August) without cash-flow gaps. The program delivers ≥80% center hours, ≥60% outreach success and <45-minute transport times. Cooler-season evaluation shows modest reductions in heat-related EMS calls and ED visits (or null result with honest uncertainty reported). The playbook, cost model and equity-outcome summary are completed by Month 12 (2027-10-08), providing a reusable, auditable template for other EU cities. Year-2 funding discussions begin with evidence-based cost and outcomes data. Estimated mortality reduction (first year): 2-5 preventable deaths; estimated reputational and scaling value: €2-5M in follow-on programs across 3-5 EU cities.

Fallback Alternative Approaches:

• If a full, formal charter cannot be completed by Month 0.5 (2026-10-23) due to resource or approval delays, produce a Minimum Viable Charter by Month 0.8 (2026-11-01) covering: (1) one-page scope summary; (2) hard constraints and gates; (3) incident-command names and delegated authority; (4) procurement critical path; (5) Month 2 (2026-12-08) readiness gate checklist. Circulate to incident commander, funder and legal counsel for 48-hour rapid sign-off. This abbreviated version avoids project delay while deferring detailed SOPs to Month 1 (2026-11-08).
• If mayoral delegation cannot be obtained as a formal document by Month 1 (2026-11-08), use an interim verbal confirmation recorded in meeting minutes with attendees (mayor, health director, civil protection lead, funder representative), stating trigger thresholds and authorized persons. Obtain formal written delegation within 2 weeks thereafter. This preserves operational continuity if formal bureaucracy is slow.
• If all procurement cannot complete by Month 2 (2026-12-08) due to market delays, implement a two-wave strategy: fast-track 40-50% of kit volume and the transport retainer through below-threshold or framework purchasing by Month 1.5 (2026-11-23); defer the remaining 50-60% of kits to a competitive tender that concludes by Month 3 (2027-01-08). This splits procurement risk and still allows 80% kit delivery by April. Accept a 10-15% price premium on expedited first wave.
• If GDPR counsel cannot produce a full opinion by Month 1 (2026-11-08) due to regulatory uncertainty, obtain an interim legal letter by Month 0.8 (2026-11-01) stating that the intermediary-held-list model is provisionally compliant under GDPR Article 6(1)(e) (public task) pending finalized MOUs. Proceed with partner engagement on this interim basis; obtain full opinion by Month 1.5 (2026-11-23). This reduces legal bottleneck without exposing the program to unmitigated GDPR risk.
• If staff and volunteer recruitment falls behind (fewer than 20 volunteer drivers by Month 1.5 = 2026-11-23), scale the taxi-retainer contract proportionally to ensure transport-gate protection (≤45 min). Simultaneously extend volunteer recruitment deadlines to Month 2.5 (2026-12-23) and accelerate vetting (weekly cohorts instead of fortnightly). Accept that peak volunteer numbers may be lower and taxi costs higher (€50-100k overrun estimate), but avoid gate failure.
• If the Month 2 (2026-12-08) readiness gate is missed and corrective actions cannot close by Month 2.5 (2026-12-23), trigger a funder restart/re-scope conversation at Month 3 (2027-01-08). Options: (a) defer the Month 4 (2027-02-08) gate to Month 5 (2027-03-08) and adjust funding drawdown schedule; (b) reduce scope (e.g., 7-8 refuges instead of 10) to meet a revised readiness target by Month 3.5 (2027-01-23); (c) extend the pilot by 2-3 months into Month 15 (2028-01-08) if required. Charter should include explicit language authorizing this escalation path to avoid project paralysis.

Create Document 2: Alert Trigger Ladder & Activation Thresholds

ID: 66c144d3-201d-4804-89ea-dd946e738907

Description: Defines three alert levels (Advisory, Alert, Emergency) with forecast trigger criteria, mandatory actions per tier, spending authority, and stand-down procedures. Links national meteorological-service forecasts to pre-agreed operational response. Audience: incident command, operations, partners, public.

Responsible Role Type: Incident Commander / Operations Lead

Primary Template: Heat Action Plan Alert Protocol (Barcelona/Paris model)

Secondary Template: National Meteorological Service Guidance (AEMET)

Steps to Create:

• Confirm temperature thresholds with national meteorological service (AEMET) and local climate context: Level 1 ≥33°C daytime or ≥20°C night for ≥2 days; Level 2 ≥35°C daytime and ≥22°C night for ≥2 days; Level 3 same for ≥3 days.
• Specify actions per level: advisory = phone checks + pre-positioned supplies; alert = centers 10:00-20:00; emergency = 24-hour operation + surge staffing.
• Define spending authorization per tier (e.g., Level 1 ≤€2k, Level 2 ≤€10k, Level 3 open).
• Establish stand-down criteria: forecast <35°C and prior 48 hours normal temperature; stand-down order ≤2 hours after criteria met.
• Include historical summer temperature data (2015–2025) for Castellón to validate thresholds post-hoc after first season.
• Finalize by Month 1 (2026-11-08); validate with AEMET; publish to partners and public by Month 6 (2027-04-08).

Approval Authorities: Incident commander, AEMET representative, operations lead, public-health deputy

Essential Information:

• Define three tiered alert levels (Advisory/Level 1, Alert/Level 2, Emergency/Level 3) with precise forecast-based trigger criteria (daytime highs and nighttime lows) and consecutive-day thresholds that convert national meteorological service (AEMET) forecasts into operational actions.
• Specify mandatory operational actions per tier: Level 1 → phone check-ins and pre-positioned supplies only; Level 2 → cooling centers 10:00–20:00 hours; Level 3 → 24-hour center operation plus surge staffing.
• Establish clear spending authorization limits for each alert tier (e.g., Level 1 ≤€2k, Level 2 ≤€10k, Level 3 open) to clarify which municipal officials can approve expenditures without escalation.
• Document stand-down criteria and procedures: alert ends when forecast falls below threshold temperatures AND prior 48 hours of actual temperatures remain normal; stand-down order issued and communicated to all partners and public ≤2 hours after criteria met.
• Include or reference historical summer temperature data (2015–2025) for Castellón de la Plana to validate that proposed thresholds correspond to observed heat events and heat-mortality risk in prior years; note any data gaps or limitations.
• Define escalation rules: when commander observes conditions (e.g., actual temperatures approaching threshold or meteorological-service confidence changes), procedures for upgrading or downgrading alert level mid-event.
• Specify forecast-access procedures: direct relationship with AEMET, forecast delivery timeline (5–7 days advance preferred; minimum 24 hours), confidence intervals, and how forecast uncertainty is handled (e.g., marginal advisory tier for borderline forecasts).
• Establish post-season review protocol: track false-alarm rate (full activations that did not result in widespread heat illness), missed-event rate (heat events that occurred below declared thresholds), and use metrics to refine thresholds after Year 1.

Risks of Poor Quality:

• Vague trigger thresholds or absent consecutive-day criteria lead to inconsistent alert declarations across years, eroding partner and public trust in the system and reducing operational readiness.
• Spending-authority ambiguity causes delayed approvals during critical hours, preventing timely activation of centers and transport when populations need help most.
• Absence of stand-down procedures prolongs unnecessary center operations, burning €5k–10k per false-alarm day and exhausting staff fatigue reserves needed for real events.
• Missing historical-data context allows thresholds to be set without grounding in local heat-mortality patterns, risking either over-activation (alert fatigue) or under-activation (missed dangerous nights).
• Incomplete escalation rules and forecast-access procedures leave command-seat occupant guessing about when and how to upgrade/downgrade, introducing politicization or clinical error.
• Absent post-season review discipline means the first season's learned adjustments are lost; thresholds cannot be refined based on observed false-alarm and missed-event rates, perpetuating suboptimal triggers.
• Lack of KPI tracking (false-alarm rate, missed-event rate, command response time) prevents data-driven improvement and credible reporting to funders and peer cities.

Worst Case Scenario: A poorly defined alert ladder causes cascading failures: thresholds set too high miss the dangerous hot-night events that drive mortality in vulnerable groups (elderly, isolated, homeless); command delays alert declaration by 12–24 hours because spending and escalation authority are unclear, leaving cooling centers closed when they are needed most. Alternatively, thresholds set too low trigger frequent false alarms that exhaust the €850k refuge budget on marginal days, leaving insufficient funds for real events in August. Partners and the public lose confidence after repeated false alerts, reducing enrollment and center uptake during the critical Month 4 (2027-02-08) scale gate evaluation, causing the gate to fail and the €1.5M release to be withheld. A preventable heat death occurs during a missed-event gap, triggering media scrutiny, political blame and program cancellation before Year 2 can be funded or evaluated.

Best Case Scenario: A clear, data-grounded alert ladder with specific forecast thresholds and spending authority enables incident commanders to declare alerts within 1 hour of forecast triggers, activating centers and transport reliably and predictably. Post-season review of false-alarm and missed-event rates (tracked as KPIs) allows thresholds to be refined after Year 1, reducing wasteful over-activation while ensuring dangerous nights are caught. Partners and the public understand alert criteria transparently, build trust in the system's fairness, and respond promptly to enrollment and center utilization. The ladder's clarity also speeds cross-department approvals by removing ambiguity about who can commit funds at each tier, enabling rapid procurement and redeployment decisions during multi-day heat waves. The documented thresholds and post-hoc refinement process become a reusable, transferable model for other EU cities with similar climates.

Fallback Alternative Approaches:

• If historical Castellón temperature and mortality data are unavailable or too sparse to calibrate local thresholds by Month 1 (2026-11-08), adopt the national AEMET alert framework directly (yellow, orange, red warnings) without local customization, accepting that sensitivity may be suboptimal but avoiding the analysis burden and timeline risk.
• If command-seat incident-commander availability or decision-making speed is unreliable, delegate alert declaration authority to the public-health director or a standing heat-desk duty officer with a written, pre-signed delegation letter specifying triggers, so declaration does not require mayoral sign-off in real time.
• If post-season threshold refinement requires analyst capacity not available internally by Month 8 (2027-06-08), commission a university or external consultant to conduct the false-alarm and missed-event analysis (cost estimate €8k–15k) and recommend Year-2 threshold adjustments.
• If AEMET forecast-delivery timing is unreliable or confidence intervals are wide, supplement with outputs from a local weather-station or university model (e.g., Universitat Jaume I, Castellón) that may provide higher-frequency or higher-confidence local forecasts; establish a dual-source protocol where alerts are declared only if both sources agree.
• If spending-authority clarity cannot be embedded in a single document due to municipal bureaucratic constraints, produce a parallel decision-matrix or flowchart that incident commanders can reference in real time, mapping alert level → spending limit → approver, with pre-signed blank purchase orders or standing delegations.
• If a full 10-year historical baseline is not available by Month 1.5 (2026-11-23), conduct a rapid mini-baseline using 3–5 recent summers and hospital/EMS records, acknowledged as provisional; commit to a retrospective full-baseline by Month 11 (2027-09-08) for Year-2 threshold refinement.

Create Document 3: GDPR Compliance & Data-Processing Framework

ID: 7fbc7480-96b7-4a91-9f60-d6d2f8a92a4e

Description: Specifies lawful basis for heat-alert contact (public task + consent hybrid), defines controller/processor roles (housing associations, social services, NGOs as joint controllers or processors; city as recipient only), outlines data-protection-impact assessment (DPIA) scope, partner audit procedures, breach-notification escalation, and data-retention/deletion timeline (one season only, delete ≤30 days after Month 12 = 2027-10-08). Includes template data-processing agreements (DPAs), consent forms, privacy notices (translated), and audit checklists.

Responsible Role Type: GDPR Compliance Officer / Legal Counsel

Primary Template: EU GDPR Article 26 Joint Controller Agreement

Secondary Template: Data Processing Agreement (DPA) Template (Standard Contractual Clauses)

Steps to Create:

• Commission GDPR specialist law firm (€15-30k, Month 0.5 = 2026-10-23) to: (1) advise on lawful basis (public task + consent? consent-only? public-task-only?), (2) draft joint-controller agreement and processor DPA templates, (3) assess DPIA scope.
• Obtain written legal opinion by Month 1 (2026-11-08) confirming GDPR compliance path; if public-task basis is used, draft or identify municipal ordinance authorizing heat-alert contact.
• If consent-based: co-design affirmative-consent form (2 pages max, translated into 4-6 languages) specifying: purpose (heat-season welfare checks), data types, retention (one season), withdrawal method, and non-consensual alternative (street outreach if refuses contact calls).
• DPIA scope: If health-data loop (EMS/ED counts) is joint-controlled, complete formal DPIA (€8-12k, 4-6 weeks) addressing re-identification risk, access controls, retention security; submit to health-system legal teams by Month 1.3 (2026-11-17).
• Partner DPAs: Finalize joint-controller or processor agreements with each of 4-6 partner organizations (housing associations, social services, NGOs, pharmacies, hospitals, EMS) by Month 1.5 (2026-11-23). Agreements must specify: lawful basis, data types, retention, audit rights, breach notification (48-hour reporting to DPO and AEPD if applicable), and liability.
• Partner staff briefing: Conduct 1-hour session for 50-80 partner staff (housing caretakers, social workers, NGO field staff, pharmacists, EMS dispatch) on GDPR obligations, consent procedures, and incident reporting; distribute one-page checklist and maintain attendance roster; repeat annually.
• Designate a Data Protection Officer (DPO) or data-protection contact (0.3-0.5 FTE municipal staff or external consultant); publish DPO contact details in all resident-facing materials (flyers, posters, heat-line scripts, center signage).
• Establish breach-incident log (accessible only to DPO and incident commander): log suspected unauthorized access, disclosure, or data loss; notify AEPD within 48 hours if breach confirmed (Article 33); notify affected residents within 72 hours (Article 34).
• Partner audit: Month 9 (2027-07-08), spot-check 2-3 partner organizations for GDPR compliance (consent records, privacy-notice logs, staff training attendance, any breach reports). Document findings and corrective actions.
• Data deletion: ≤30 days after Month 12 (2027-10-08), delete all personal data from partner records and city systems unless re-consented for Year 2. Retain only aggregated outcome data (EMS counts, ED visits, participation numbers, anonymized).
• Finalize framework by Month 1.5 (2026-11-23); audit partner compliance by Month 9 (2027-07-08).

Approval Authorities: GDPR Counsel, Data Protection Officer, partner organizations' legal representatives, Spanish Data Protection Agency (AEPD) if consultation needed

Essential Information:

• Define the lawful basis for heat-alert contact (public task, consent, or hybrid model) under Spanish data-protection law and GDPR Article 6, with legal opinion by Month 1 (2026-11-08)
• Clarify data-controller and data-processor roles for each intermediary partner type (housing associations, social services, NGOs, pharmacies) and specify whether the city is a joint controller, separate controller, or recipient-only
• Design and draft affirmative-consent forms (translated into 4–6 non-official languages identified by Month 0 = 2026-10-08) specifying: purpose, data types, retention period (one season only), withdrawal method, and non-consensual alternative routes
• Scope and complete a Data Protection Impact Assessment (DPIA) if health-system data (EMS/ED aggregate counts) involves re-identification risk or cross-linking with city systems; address access controls, security and breach procedures
• Draft template data-processing agreements (DPAs) and joint-controller agreements conforming to GDPR Articles 26–28 and Spanish Organic Law 3/2018 (LOPDGDD); include provisions for sub-processors, audit rights, breach notification (48-hour escalation), liability allocation and international data transfers if applicable
• Establish a Data Protection Officer (DPO) role or designate a data-protection contact (municipal staff or external consultant, 0.3–0.5 FTE); publish DPO contact details in all resident-facing materials (flyers, heat-line scripts, refuge signage) and partner briefing materials
• Design and implement a breach-incident log (access-controlled, DPO + incident commander only) and escalation procedure: suspected breaches logged immediately, AEPD notification within 48 hours if breach confirmed (Article 33), resident notification within 72 hours (Article 34)
• Create partner-staff briefing package: 1-hour training session covering GDPR obligations, consent procedures, incident reporting, and confidentiality; conduct for 50–80 staff across all partner organizations by Month 2 (2026-12-08); maintain attendance roster and provide one-page checklist
• Define audit procedures for partner GDPR compliance: spot-check 2–3 partner organizations at Month 9 (2027-07-08) for consent records, privacy-notice logs, staff-training attendance, and any breach incidents; document findings and corrective-action timelines
• Specify data-retention and deletion procedures: all personal data retained only for the one-season period (October–September); deletion of all personal data from partner systems and city records within 30 days after Month 12 (2027-10-08) unless re-consented for Year 2; retain only aggregated outcome data (EMS counts, ED visits, anonymized participation numbers)

Risks of Poor Quality:

• Ambiguous or missing lawful-basis definition leads to legal challenge from data subjects or AEPD, halting outreach mid-season and forcing partner withdrawal; estimated delay 2–4 weeks and reputational harm
• Unclear controller/processor roles create liability confusion if a breach occurs, delaying incident response and violating GDPR Article 33 notification timelines (48-hour escalation)
• Consent forms that are unclear, untranslated, or legally insufficient for non-native speakers reduce enrollment validity and increase AEPD audit risk; estimated reach loss 10–20% if migrant communities distrust the process
• Incomplete DPIA or failure to assess re-identification risk leaves the program exposed to regulatory finding of inadequate safeguards; combined with cost and time to remediate: €10–20k and 4–8 weeks
• Weak or missing DPA templates result in partner non-compliance with GDPR obligations, exposing the city to joint-liability claims if data is mishandled; estimated exposure €50–100k in legal costs
• Absent DPO or unclear data-protection contact creates confusion over breach reporting and harms public trust; AEPD may levy administrative fines (Article 83–84, up to 4% of global revenue or €20M for public bodies)
• No breach-incident log or delayed escalation violates GDPR Article 33 and 34, incurring AEPD findings and potential fines for non-notification; estimated reputational and financial damage €20–100k
• Inadequate or untranslated partner briefing results in inconsistent GDPR compliance across organizations, increasing breach likelihood and audit findings; estimated cost to remediate €5–15k per partner
• Missing partner audit procedures prevent detection of consent violations or data misuse until after the season or after an AEPD complaint; remediation and fines retroactively applied
• Unclear or delayed data-deletion procedures leave personal data in systems beyond the retention period, violating GDPR Article 5(1)(e); residents or AEPD may demand deletion and impose fines for prolonged storage

Worst Case Scenario: A GDPR data-protection framework that is legally ambiguous, incomplete or inadequately translated results in a partner organization or data subject filing a complaint with Spain's AEPD. The AEPD investigation finds that the city lacked a clear lawful basis for contact, inadequate consent procedures for non-native speakers, or incomplete DPAs with unclear liability. While the investigation is ongoing (4–8 weeks), public media coverage of "unlawful heat-alert data collection" erodes resident trust and partner confidence, causing partner withdrawal and enrollment collapse. If the AEPD issues an administrative finding, the city faces reputational damage, mandatory corrective actions and a potential fine (EUR 10,000–100,000 range for public bodies). Outreach operations are halted mid-season pending legal remediation, costing estimated 2–4 weeks of lost contact time during peak heat risk and reducing the 60% outreach-contact gate achievement.

Best Case Scenario: A legally sound, pre-specified GDPR framework with clear lawful-basis opinion, translated consent forms, template DPAs and a designated DPO enables rapid partner sign-up by Month 1.5 (2026-11-23) and confident outreach from Month 2 (2026-12-08). Partner organizations operate with explicit guidance, attend staff briefings and maintain audit-ready consent records. Breaches (if any) are detected and escalated within 48 hours to the AEPD per Article 33. The program meets the 60% outreach-contact gate with high partner confidence and no legal challenges. The framework becomes a reusable, transferable model for other EU cities, demonstrating municipal data ethics and reducing adoption barriers for scaling.

Fallback Alternative Approaches:

• Engage a specialized GDPR law firm at Month 0.5 (2026-10-23) to provide a rapid legal opinion (€15–30k) on the most conservative lawful basis (consent-only) and provide template DPAs and consent forms ready for signature by Month 1 (2026-11-08); accept shorter retention windows or explicit opt-in if needed to simplify compliance and reduce partner friction
• If full DPIA is too resource-intensive, conduct a GDPR screening assessment (€3–5k, 1–2 weeks) to assess re-identification risk; if risk is low (aggregate counts only, no linking to health records), defer full DPIA and proceed with streamlined DPAs
• If recruiting a full-time DPO is unaffordable (0.5 FTE = €20–30k/year), designate a municipal legal officer or external consultant as part-time data-protection contact (0.3 FTE = €12–15k) with escalation authority to the incident commander; this reduces cost while maintaining breach-response accountability
• If partner capacity for consent and GDPR training is low, deliver briefings via recorded video (15 min) with accompanying one-page checklist and Q&A email support rather than live sessions; reduces scheduling friction and allows partners to train staff on their timeline by Month 2 (2026-12-08)
• If comprehensive partner audit (2–3 organizations) is resource-constrained at Month 9 (2027-07-08), conduct a desk-based audit using partner-submitted copies of consent records and staff-training logs rather than on-site inspections; reduces cost and time while maintaining accountability
• If data-deletion at Month 12 (2027-10-08) is operationally complex (distributed partner systems), establish a data-deletion task force 2 weeks before (Month 11.4 = 2027-09-20) to coordinate with all partners; provide a deletion checklist and certified deletion confirmation from each partner by deadline
• If translation into 4–6 languages exceeds budget, prioritize the 2–3 highest-volume language groups (identified by NGO/census data) and deliver translation by professional service; use pictograms and simplified Spanish for lower-volume groups; reduces cost from €15–25k to €8–12k

Create Document 4: Full-System Drill Protocol & Exercise Script

ID: e27579ab-3489-45fb-a924-5c0b466d9fe3

Description: Detailed drill procedures for testing all operational elements (alert declaration, center activation, transport dispatch, outreach calls, EMS escalation, center stand-down) under realistic stress conditions. Specifies simulation scenarios (3+ consecutive hot-night events, 40+ simultaneous transport requests, 80%+ center occupancy, multi-day staff fatigue, misinformation reports), observer roles, timing, success criteria (80% center hours, 60% contact success, <45-min transport), and after-action reporting template.

Responsible Role Type: Operational Resilience & Surge Planning Lead / Project Manager

Primary Template: FEMA Full-Scale Exercise Protocol

Secondary Template: Incident-Command System (ICS) Exercise Evaluation Guide

Steps to Create:

• Drill scope (finalized Month 2.5 = 2026-12-23): Simulate 3+ consecutive hot-night alert events; activate all 10 cooling centers; dispatch 40+ simultaneous transport requests (including ≥5 wheelchair users); conduct 200+ outreach contact attempts via partners; manage center surge to 80%+ occupancy; simulate 2-3 EMS escalations and 1-2 misinformation reports; run continuously for 48-72 hours to test staff fatigue.
• Scenario vignettes: (1) Alert declared at 12:00 Day 1; centers open 10:00-20:00; 15 transport requests 12:00-18:00; (2) Second day: two requests at 06:00 (before official hours); centers extend to 06:00-22:00; 20 transport requests 10:00-20:00; (3) Multi-day transition: staff absences (2 call-outs per site), dispatch queue backs up, center occupancy peaks at 85%; misinformation (radio rumor: 'alcohol cools faster') circulates; messenger team and comms lead must respond ≤4 hours.
• Participant roles: Incident commander (declares alerts, authorizes spending); operations lead (manages centers, transport, EMS coordination); communications lead (public updates, misinformation response); dispatch coordinator (assigns drivers, tracks wait times); center managers and staff (log occupancy, manage residents, escalate incidents); outreach leads (log contact attempts); observer team (independent, track metrics, flag issues, document decisions).
• Success criteria (Month 4 gates = 2027-02-08): ≥80% of planned center-hours delivered (target 2,620 hours planned; pass ≥2,096 hours actual); ≥60% contact success (≥180 of 300 attempts reached, enrolled, or escalated); mean transport pickup <45 min over ≥30 requests (including wheelchair users); all after-action items identified and assigned by end of drill day 3.
• Measurement & data collection: Observer team logs in real-time: alert decision time (vs. forecast trigger + 1 h); center openings/closings (vs. plan); occupancy by hour (photos, tally); transport request count, assignment time, pickup time, destination; outreach contact attempts and outcomes (log form per partner); escalations and EMS interactions; any incidents (assault, injury, system failure); staff fatigue indicators (post-shift surveys); misinformation reports and response time.
• After-action process: Drill concludes 17:00 Day 3; draft after-action report within 48 hours (Day 4-5) documenting: actual vs. planned performance, root causes of any deviations, identified corrective actions, and assigned owners. Corrective-action meeting Week 1 post-drill (Month 3.4 = 2027-01-20) to review draft, assign owners, and set completion dates. All actions must be closed by Month 3.9 (2027-02-04) before Month 4 (2027-02-08) gate decision.
• Finalize drill protocol (including maps, contact lists, scripts, observer checklist) by Month 2.5 (2026-12-23); conduct drill Month 3.2 (2027-01-14); after-action draft Month 3.5 (2027-01-23); actions closed Month 3.9 (2027-02-04); gate decision Month 4 (2027-02-08).

Approval Authorities: Incident commander, operations lead, observer team (independent or external evaluator), funder representative

Essential Information:

• Define realistic multi-day simulation scenarios that mirror actual alert conditions: 3+ consecutive hot-night events triggering Level 2/3 alerts, with specific forecast trigger values (high ≥35°C, low ≥22°C) that activate the full center, transport and outreach network.
• Specify quantified success criteria aligned to the Month 4 (2027-02-08) gates: ≥80% of planned 2,620 center-hours delivered (pass ≥2,096 hours); ≥60% contact success from ≥300 outreach attempts (≥180 reached/enrolled); mean transport pickup <45 minutes over ≥30 requests including ≥5 wheelchair users; all corrective actions closed by Month 3.9 (2027-02-04).
• Detail stress-test scenarios simulating real operational failures: 40+ simultaneous transport requests at peak hours, centers reaching 80–85% occupancy, 2–3 staff absences per site due to fatigue, dispatch queue backlog, misinformation circulating (e.g., 'alcohol cools faster'), EMS escalations for heat-illness suspicion, and a late-arriving transport request (after-hours demand).
• Map participant roles with clear responsibilities: incident commander (declares drill start/end, authorizes escalations), operations lead (manages center and transport activations, logs occupancy), dispatch coordinators (assigns drivers, tracks time-to-pickup), center managers (staff the sites, document incidents), outreach leads (log contact attempts per partner), communications lead (responds to misinformation ≤4 hours), independent observer team (measures metrics, identifies root causes).
• Establish measurement protocol with real-time data collection: observer checklist capturing alert decision time (vs. forecast+1h target), center opening/closing times (vs. plan), hourly occupancy with photographic evidence, transport request count/assignment/pickup times, outreach contact outcomes (reached, enrolled, escalated, failed), EMS interactions, any incidents (assault, system failure, injury), staff fatigue survey post-drill.
• Prescribe after-action reporting and corrective-action closure: draft report within 48 hours (Month 3.5 = 2027-01-23); identify root causes for any performance gaps (e.g., 'dispatcher overwhelmed at 14:00 due to only 1 operator scheduled'); assign corrective owners and target dates; mandatory closure of all actions by Month 3.9 (2027-02-04) before gate decision.
• Define drill timing and scheduling: finalize protocol and maps by Month 2.5 (2026-12-23); execute full-system drill Month 3.2 (2027-01-14) for 48–72 consecutive hours; after-action meeting with funder and key partners Week 1 post-drill (Month 3.4 = 2027-01-20); corrective actions closed by Month 3.9 (2027-02-04); gate decision at Month 4 (2027-02-08).
• Include contingency measurement rule: if the drill provides insufficient evidence (e.g., poor participation, data gaps), document why; clarify that real heat events in June–July can supplement drill data for gate measurement; specify the fallback: 50% release at Month 4 (2027-02-08) if evidence mixed, full release deferred to Month 5 (2027-03-08).

Risks of Poor Quality:

• Unrealistic or vague stress-test scenarios fail to expose actual operational bottlenecks (e.g., dispatch overwhelmed, centers at capacity), allowing gaps to persist into the real summer season and causing preventable service failures during early-May heat events.
• Success criteria not anchored to the Month 4 (2027-02-08) gates allow subjective pass/fail decisions and diffuse accountability; unclear thresholds (e.g., 'most center hours delivered') invite disputes with the funder about whether gates are met, risking non-release of €1.5M funding.
• Incomplete participant-role definitions leave ambiguity about who decides to escalate to EMS, who authorizes stand-down, or who manages misinformation response; confusion during the drill leads to delayed decisions and eroded confidence in command structure.
• Poor data-collection protocols (missing observer assignments, no real-time logging, photos not taken) result in incomplete after-action evidence; without documented metrics, the funder cannot assess whether 80% center hours or 60% contact success were actually achieved, jeopardizing funding release.
• Weak after-action process (report written weeks later, corrective owners unclear, actions not tracked) allows identified problems to remain unfixed when the real summer season begins; staff may not know which fixes were implemented, reducing readiness and morale.
• Absence of a contingency-measurement rule leaves the city unprepared if June–July are cooler than normal and real heat events do not occur; the drill becomes the sole evidence, but if its quality is questioned, the Month 4 (2027-02-08) gate decision hangs unresolved, delaying the €1.5M release.
• Failure to test multilingual communications, volunteer-driver fatigue, or partner capacity during the drill means equity gaps and staffing weaknesses are discovered in real heat events instead, harming vulnerable residents and eroding public trust in the program.

Worst Case Scenario: The drill is poorly designed or executed: scenarios are abstract (e.g., 'simulate a hot day' without specific forecasts or request volumes), success criteria are subjective ('most centers operated well'), participant roles are unclear, and data collection is incomplete (occupancy estimates instead of counts, no transport time-logs). The after-action report identifies major gaps (e.g., 'dispatcher could not handle 40 requests'; 'outreach teams made only 150 of 300 planned calls due to partner staff absences'; 'average transport time was 62 minutes, not 45'). However, corrective actions are vague ('improve communications'), accountability is diffuse ('the team will do better'), and closure is incomplete by Month 3.9 (2027-02-04). The funder questions whether drill results are credible evidence for the Month 4 (2027-02-08) gate. No real heat events occur in June–July. The city cannot demonstrate that the 80% center-hours, 60% contact-success, and <45-minute transport gates have been met. The €1.5M scale release is withheld pending a re-test. By August, without confirmed funding, the program cuts center hours and transport capacity by 30%, leaving vulnerable residents at peak summer risk. A preventable heat death in late August triggers media investigation, finding the drill protocol had inadequate quality-assurance and the gates were never validly measured.

Best Case Scenario: The drill protocol is detailed and realistic: specific stress-test vignettes (e.g., 'alert declared 12:00; 40 transport requests 12:00–18:00; occupancy peaks 85% at 14:00; dispatch queue at 8 vehicles waiting; two staff call-outs; misinformation report 14:30') are scripted with expected outcomes. Success criteria are quantified and tied directly to the Month 4 (2027-02-08) gates: ≥2,096 center-hours observed, ≥180 outreach contacts logged, mean 43-minute transport time over 32 requests. Participant roles are explicit with decision authorities (commander declares stand-down ≤2 hours; comms lead responds to misinformation ≤4 hours). Real-time observer teams log data (timestamps, occupancy photos, transport assignment logs, contact forms per partner). The drill runs 48–72 hours with high-fidelity stress (concurrent fatigue, late calls, competing priorities). The after-action report (Month 3.5 = 2027-01-23) documents: drill ≥80% center-hours (2,150 of 2,620 planned); ≥60% contact success (195 of 300); mean 42-minute transport time; identifies 4 corrective actions (e.g., 'hire second dispatcher by Month 3 = 2027-01-08'; 'partner A needs call-center training by Month 3.5 = 2027-01-23'; 'signage installation at 2 sites by Month 3.8 = 2027-02-01'). All actions close by Month 3.9 (2027-02-04). The funder receives validated evidence. The €1.5M is released on schedule at Month 4 (2027-02-08). Staff confidence in the system increases. When real heat events occur in June–July, operations execute smoothly, meeting gates and demonstrating credible harm reduction that supports Year-2 funding and scaling to other EU cities.

Fallback Alternative Approaches:

• If designing a full 48–72 hour drill is too resource-intensive or risks coordinator burnout before the real season, conduct a tiered-exercise approach instead: tabletop exercise at Month 2.9 (2027-01-04) to walk through decision logic and role clarity (4–6 hours, in-person, command team + observer); functional exercise at Month 3.2 (2027-01-14) to test specific operational elements in sequence (dispatch response, center activation, partner call-out) with 2–3 hour runs, not full 72 hours; full-scale drill deferred to Month 7 (2027-05-08) after staffing is complete, allowing time for fixes identified in tabletop and functional exercises. Consolidate Month 4 (2027-02-08) gate evidence: 50% weight to functional exercise results, 50% to real heat events in May–June if available.
• If independent observer capacity is limited, assign one internal observer (e.g., PMO staff or evaluation partner) to each operational area (dispatch, outreach, centers) with pre-printed observer checklists and simple tally forms; conduct spot-check validation by an external evaluator (university partner) post-drill (review logs, interview participants, audit data) within 1 week. Accept lower real-time data quality in exchange for faster post-hoc validation and reduced coordination burden.
• If stress-testing 40+ simultaneous transport requests is infeasible with volunteer drivers or dispatch capacity, reduce the drill to 20–25 requests (realistic for a single-day Level 2 alert) and run the drill twice (transport stress test as separate functional exercise); measure average time-to-pickup in both runs and average the results. Document that the drill underestimates peak-capacity testing; use real June–July events (if any) to validate 40+ request performance.
• If partner outreach teams cannot commit to 200+ mock calls during a 48–72 hour drill (low capacity or competing summer work), reduce the mock-call target to 100 calls spread over 3 days (e.g., 30 calls Day 1, 35 Day 2, 35 Day 3) and measure contact success on a pro-rata basis; document that the drill uses a lower stress level and that real heat-event contact data will supplement the gates measurement. Ensure the 100 calls exercise the same partner network (all 5–6 intermediaries) to test each partner's process.
• If the drill cannot measure all four gates simultaneously due to scheduling or data constraints, conduct the drill focused on transport and center operations (quantifiable, high-risk), defer outreach-contact and after-action-closure validation to a second, lighter functional exercise or to real-event measurement in June–July. Gate decision rule: if drill passes ≥3 of 4 gates plus real events (if any) show contact success ≥60%, release the full €1.5M; if drill fails 2+ gates, release 50% contingently and re-test at Month 5 (2027-03-08).
• If the drill reveals major unfixable gaps (e.g., staffing shortage means dispatch cannot handle >20 requests), defer the Month 4 (2027-02-08) gate decision by agreement with the funder: release €750k (50%) immediately to sustain operations and hire additional dispatch staff; schedule a second drill or validated real-event test at Month 5 (2027-03-08) to measure all gates with corrected staffing; full release contingent on Month 5 (2027-03-08) results. Document the rationale and timeline in the gate-decision letter.

Create Document 5: Procurement & Contracting Strategy

ID: f6efa0b2-0d45-432c-88ef-6bd643d1bbb1

Description: Specifies procurement routes (framework call-offs, below-threshold purchasing, simplified tenders) for four product categories: cooling kits (€800k), transport retainer (€80k), handyperson services (€150k), and refuge fit-out (€100k). Includes specifications, supplier-qualification criteria, delivery timelines, backup-supplier agreements, price-lock and expedite-fee authorization, and audit-trail documentation procedures.

Responsible Role Type: Municipal Procurement Officer / Contract Law Specialist

Primary Template: EU Public Procurement Directive Guidance (2014/24/EU)

Secondary Template: Spanish Public Procurement Regulations (LCSP)

Steps to Create:

• Procurement planning (Month 0 = 2026-10-08): Define €3.5M budget by category; identify existing municipal framework agreements (utilities, services, maintenance) suitable for call-offs; confirm legal thresholds (Spain: €50k EU below-threshold, varying by region for services/supplies).
• Specifications (by Month 0.8 = 2026-11-01): Issue detailed RFQs for (1) cooling kits: shading, reflective blinds, fans, thermometers, specs; (2) transport: vehicle type, capacity, response-time SLA, insurance; (3) handyperson: electrician/installer qualifications, training requirements; (4) fit-out: accessibility remediation, fit-out standards.
• Supplier identification & pre-qualification (Month 1 = 2026-11-08): Request quotes from ≥3 primary suppliers and ≥2 backup suppliers per category; evaluate on price, lead time, quality, and experience; pre-qualify backups with written 'emergency activation' agreements specifying ≤7-day mobilization and expedite premium (≤10% price increase).
• Procurement route decision (Month 1 = 2026-11-08): For each category, determine lowest-risk legal route: (1) kits ≤€100k/call-off = framework call-off if framework exists (audit-safe); (2) kits >€100k per batch = simplified below-threshold tender (€50-200k threshold band, written documentation, 2-3 quotes); (3) transport retainer ≤€80k = framework or simplified tender; (4) handyperson ≤€150k total = framework or simplified tender. Document route choice and legal justification.
• Order placement (Month 1.2-2 = 2026-11-14 to 2026-12-08): Place first-tranche kit orders (30-40%) by Month 1.2 (2026-11-14) with primary supplier; include SLA for February 2027 delivery. Place transport retainer contract by Month 1.2 (2026-11-14) with 48-hour cancellation clause. Confirm all tranche-1 orders placed by Month 2 (2026-12-08) readiness gate.
• Contract management: (1) Delivery tracking (log actual receipt date vs. planned); (2) quality assurance (inspect first 5% of kit shipment for defects); (3) invoice & payment (audit invoice against SLA, delivery confirmation, quality check); (4) change orders (scope/timeline changes require written approval and amendment; document reason, cost, and incident commander sign-off).
• Audit readiness: Maintain complete procurement file per order including: RFQ and responses, evaluation criteria and scoring, selected-supplier justification, contract document (signed), delivery record, quality-assurance checklist, payment authorization, and any change orders. File must be defense-able to municipal audit and EU auditors.
• Backup activation trigger: If any supplier misses committed delivery date by >1 week, immediately (≤24 hours) notify backup supplier, confirm mobilization, and place emergency order. Authorize expedite-fee payment (up to 10% premium, approximately €80-120k for kits; €8-12k for transport/services) without additional approval.
• Finalize procurement strategy by Month 0.8 (2026-11-01); execute first orders by Month 1.2 (2026-11-14); confirm all orders by Month 2 (2026-12-08).

Approval Authorities: Municipal Procurement Officer, CFO/Budget Director, incident commander (for budget authority), legal counsel (for contract terms)

Essential Information:

• Define procurement routes (framework call-offs vs. below-threshold purchasing vs. simplified tenders) for four product categories: cooling kits (€800k), transport retainer (€80k), handyperson services (€150k), and refuge fit-out (€100k), with rationale for each choice and audit defensibility.
• Specify detailed RFQ and specification documents for each category by Month 0.8 (2026-11-01), including product standards (cooling kit specifications: exterior shading, reflective blinds, fan type/wattage, thermometer/hygrometer accuracy, hydration supplies packaging), transport SLA (response time ≤20 min for ≥10 vehicles including ≥3 wheelchair-capable), handyperson qualifications (electrician certification, heat-safety training completion), and refuge fit-out accessibility standards (wheelchair access, AED placement, water/toilet facilities).
• Identify and pre-qualify ≥3 primary suppliers and ≥2 backup suppliers per category by Month 1 (2026-11-08), with written emergency-activation agreements specifying ≤7-day mobilization and expedite-fee caps (≤10% price premium authorized without additional approval).
• Document the order placement timeline and triggers: first-tranche kit call-off for 30–40% volume (600–800 units) by Month 1.2 (2026-11-14); transport retainer contract signed by Month 1.2 (2026-11-14) with 48-hour cancellation clause; all tranche-1 orders confirmed by Month 2 (2026-12-08) readiness gate.
• Establish backup-supplier activation rules: if primary supplier misses committed delivery date by >1 week, notify backup within 24 hours, confirm mobilization, and place emergency order; authorize expedite-fee payment (€80–120k for kits, €8–12k for services) without escalation if within the authorized cap.
• Create complete procurement-file audit trail per order including: RFQ and responses, evaluation criteria/scoring, selected-supplier justification, signed contract, delivery record, quality-assurance inspection checklist (first 5% of shipment), invoice vs. SLA verification, payment authorization, and any change orders with incident-commander sign-off.
• Define delivery-tracking and quality-assurance processes: log actual receipt vs. planned date; inspect first 5% of each kit shipment for defects and correct or replace within 5 business days; accept/reject invoice based on SLA, delivery confirmation and QA sign-off; escalate defects or delays to backup supplier immediately.
• Specify procurement governance: approval authorities (Municipal Procurement Officer, CFO/Budget Director, incident commander for budget, legal counsel for contract terms) and documentation standards (all files defense-ready for municipal and EU audit, with legal justification for each route choice).
• Calculate and authorize contingency spending: identify expedite-fee authorization threshold (€10–15k per procurement event without additional approval; cumulative ≤€120k from tranche-1 contingency); trigger condition: primary supplier delay >1 week; document business case (date, reason, cost, signed authorization).
• Quantify pricing risk and lock-in strategy: obtain fixed-price quotes and benchmark against market by Month 1 (2026-11-08); lock in transport-retainer rates by contract by Month 1.2 (2026-11-14) before summer demand spike; for kits, negotiate volume-discount terms and agree on expedite-fee caps before first order.

Risks of Poor Quality:

• If procurement routes are not legally justified or documented, audit may find non-compliance with EU Public Procurement Directive (2014/24/EU) and Spanish LCSP regulations, triggering mandatory re-procurement, project delay of 6–8 weeks, and reputational damage; estimated legal cost: €20–30k.
• Inadequate specifications (vague product standards, missing SLAs for transport, unclear installer qualifications) will result in quality mismatches, supplier disputes, contract claims and potential rework; examples: fans ordered without proper airflow specification causing resident harm, transport vehicles lacking wheelchair lifts failing accessibility gate, handyperson work failing electrical code inspection.
• If backup suppliers are not pre-qualified or emergency-activation procedures are unclear, primary supplier delay will cascade: kits will not arrive until March–April, delaying home installations past the first May–June heat events by 4–8 weeks; estimated reach loss: 15–25% of target homes untreated during peak-risk season.
• Missing or incomplete procurement-file documentation (RFQs, evaluation notes, contract copies, delivery records) will fail audit and undermine program credibility; funder, auditors and EU partners will question financial controls and procurement integrity, risking project pause or phase-out.
• Inadequate quality-assurance processes (no inspection of kit shipments, no verification of transport-vehicle specifications) will result in defective or unsuitable equipment reaching the field: fans that malfunction, reflective blinds that fail installation, wheelchair-access vehicles lacking proper lifts; remediation cost: €20–50k and operational disruption during alert days.
• If delivery tracking is not rigorously maintained, shortages or delivery mismatches will go undetected until late in the supply chain, causing sudden gaps in kit availability or transport capacity during early heat events; estimated operational impact: 2–3 week delay in full deployment.
• Budget and cost-control failures: if expedite fees are not pre-authorized or caps are exceeded, procurement coordinator will delay decisions or exceed budget, causing both order delays and overspend; estimated cost exposure: €150–250k if taxi-only fallback is triggered without pre-planning.
• Reputational damage if sole-source or repeat-vendor patterns emerge without documented justification; media, unions, auditors or political opponents may claim favoritism or inflated pricing, damaging public trust in the program.

Worst Case Scenario: Procurement delays exceed the Month 2 (2026-12-08) readiness gate, with no kits or transport contracts in place by the deadline. Primary suppliers confirm 10–14 week lead times, and backup suppliers are unavailable or unaffordable. Cooling kits do not arrive until April–May, home installations slip by 6–8 weeks, and no handypersons are contracted to install. Transport retainer is not signed, leaving only volunteer drivers (if recruitment succeeds, which is uncertain). The Month 2 (2026-12-08) readiness gate fails, and the program enters the cooling season (June–August) with no pre-positioned home kits and inadequate transport capacity. Early heat events in May–June find refuges open but transport severely constrained, home-level interventions absent, and the Month 4 (2027-02-08) gates unachievable. Scale funding (€1.5M) is not released, forcing budget cuts and mid-summer operational contraction. Vulnerability in homes and transport pathways during peak-risk summer months leads to preventable heat illness and death in untreated top-floor and mobility-limited residents; media coverage blames failed procurement planning and municipal incompetence. Estimated financial impact: €350–650k unbudgeted draw on contingency and operating costs, plus reputational damage affecting Year-2 funding and future EU partner interest.

Best Case Scenario: Procurement is completed on schedule with all orders placed by Month 2 (2026-12-08), kits arriving by April (Month 6.7 = 2027-04-29), and transport contract operational by Month 1.2 (2026-11-14). Cooling-center fit-out, refuge staffing and handyperson deployment are all in place by May 1 (Month 6.8 = 2027-05-02). First-tranche budget (€2.0M) is fully committed without cost overruns, contingency is preserved for operational needs, and backup suppliers are not needed. Home installations of 2,000 kits proceed smoothly February–May with zero defects and fast handyperson completion. Transport retainer delivers reliable response times (mean <40 min), volunteer driver vetting yields 40+ recruits, and dispatch coordination is rehearsed in May drills. Month 4 (2027-02-08) gates are passed on the strength of drill results, enabling full release of €1.5M scale funding on schedule. Summer heat events find the entire system operational and responsive: refuges reach 80%+ planned hours, outreach achieves 60%+ contact success, transport meets the 45-minute threshold, and staff morale is high. Procurement planning becomes a reusable playbook section that other EU cities can adapt, demonstrating transparent, auditable financial controls and schedule discipline.

Fallback Alternative Approaches:

• If primary supplier lead times exceed 6 weeks by Month 0.8 (2026-11-01), immediately activate backup suppliers and place a small first call-off (10–15% of volume, ~200 kits) with an expedite-fee premium (≤10%, ~€8–12k) at Month 1 (2026-11-08), then conduct a full competitive tender for the second tranche (70–80% of volume) with a longer delivery window (April–May) to obtain better pricing and avoid single-source dependency.
• If municipal framework agreements are unavailable or unsuitable for kits and transport, conduct a rapid simplified below-threshold tender (€50–200k band in Spain) for each category by Month 1 (2026-11-08), with a 2-week RFQ process and ≥3 quotes required; document evaluation and selected-supplier justification to maintain audit compliance.
• If legal counsel is unavailable or EU Procurement Directive interpretation is unclear, engage a specialized procurement law firm for focused advisory support (€5–10k scope) rather than full-scope representation; this accelerates route decisions without committing to extended legal retainer.
• If backup-supplier pre-qualification is not complete by Month 1 (2026-11-08), establish a contingency sourcing pool by Month 1.5 (2026-11-23) via rapid RFQs to secondary regional/national suppliers; confirm availability and expedite-fee caps in writing, then hold this pool on standby pending primary delivery.
• If refrigeration, storage or transportation logistics bottleneck kit distribution by February, arrange interim warehousing with the selected supplier or a third-party logistics provider (€3–5k monthly cost) rather than forcing delayed delivery; confirm cold-chain management (for certain kit materials, if applicable) in the storage contract.
• If handyperson vetting or certification cannot be completed by Month 3 (2027-01-08), contract an external installation firm (social enterprise, NGO or contractor group) that already holds certified electrician staff and can be mobilized at short notice with training only on the heat-safety checklist (2-hour briefing); this reduces hiring bottleneck but slightly increases unit cost (~€50/install).
• If the transport retainer bid process yields only one qualified respondent or quoted rates are unexpectedly high (>€80k), exercise a contingency procurement route: (a) extend the volunteer-driver target to 50–60 (recruiting urgently in November–December) and retain only a scaled-down taxi fallback (€30–40k, emergency-only, not standby retainer); or (b) negotiate a shorter retainer term (May–July only, not May–September) to stay within budget; or (c) broker a non-profit taxi or community-transport partnership that accepts lower rates in exchange for municipal promotion or procurement preference.
• If tranche-1 budget pressure forces cuts before Month 3 (2027-01-08), prioritize in order: (1) maintain full refuge fit-out and transport retainer (gates depend on them); (2) reduce kit volume to 1,500 (75% of 2,000 target) and cut lower-priority social housing; defer remaining 500 kits to tranche-2 (Month 4 = 2027-02-08 budget); or (3) negotiate volume discounts or phased payment terms with suppliers to defer cost to Month 4 (2027-02-08).

Documents to Find

Find Document 1: Castellón de la Plana Demographic & Census Data

ID: 616f23d3-774e-4db6-9946-6528ff41bced

Description: Official municipal census and demographic data (2020 or most recent) specifying: age distribution (65+ population count and percentage), housing types (owner-occupied, rented, social housing, top-floor prevalence), education and literacy levels, migrant and recent-arrival populations by origin country/language, employment rates, and health-insurance coverage. Identifies vulnerable populations and geographic concentrations for targeting cooling refuges and outreach. Primary input for vulnerability mapping and equity metrics.

Recency Requirement: Most recent available (2020 Census or municipal 2024-2025 update preferred); supplement with 2015-2020 trend data if needed.

Responsible Role Type: Project Manager / Data Analyst

Steps to Find:

• Contact Castellón de la Plana municipal statistics office or Valencian regional statistics agency (Institut Valencià d'Estadística, IVE).
• Request: age distribution (5-year bands, especially 65+), housing type by neighborhood, migrant/foreign-born population by country of origin, language spoken at home.
• Search national Spanish statistics portal (Instituto Nacional de Estadística, INE) for Castellón municipality-level data.
• Request municipal housing authority data on social-housing locations, building age, and insulation quality of stock.

Access Difficulty: Easy. Spanish census data are freely available via INE portal; municipal statistics are public unless privacy-restricted. Contact municipal social services or urban planning department for neighborhood-level housing stock detail.

Essential Information:

• Confirm whether Castellón de la Plana municipal census and demographic data (2020 or most recent) are accessible and contain: age distribution with 65+ count and percentage, housing types (owner-occupied, rented, social housing, top-floor prevalence), education and literacy levels, migrant and recent-arrival populations by origin country and language, employment rates, health-insurance coverage.
• Identify geographic concentration of vulnerable populations (65+, living alone, top-floor/poorly insulated units) by neighborhood or postcode to validate cooling-refuge site selection and outreach targeting.
• Quantify baseline heat-related EMS calls (current estimate 80–120 per summer) and heat-attributable excess mortality (current estimate 15–25 per summer) using municipal EMS records and health-department mortality data with consistent coding definitions.
• List all candidate cooling-refuge sites (libraries, community centers, parish halls, churches, sports halls, malls) with current use, operating hours, wheelchair access status, water/toilet/first-aid facilities, parking and signage.
• Confirm migrant and linguistic diversity: identify top 4–6 non-official languages spoken by residents and concentration in neighborhoods to guide interpretation and ambassador recruitment.

Risks of Poor Quality:

• Incomplete or outdated census data (older than 2020) will misidentify vulnerable-population concentrations, causing cooling refuges to be sited in low-need areas and home kits to reach the wrong households, reducing equity coverage and mortality protection.
• Missing baseline EMS and mortality counts will prevent credible attribution of harm reduction by Month 4 (2027-02-08), undermining the Month 4 (2027-02-08) gate evaluation and playbook credibility for other EU cities.
• Incomplete site inventory (missing wheelchair-access data or operating-hours constraints) will force remediation or site substitution mid-season, delaying refuge opening and delaying the Month 2 (2026-12-08) readiness gate.
• Inaccurate language-community identification will leave migrant residents unable to receive alerts or escalation guidance, reducing enrollment and contact-success rates below the 60% Month 4 (2027-02-08) gate and creating health and equity harm.
• Unverified population estimates will cause staffing and budget allocations to be misaligned with actual demand, leading to undersized or oversized operations and gate failure.

Worst Case Scenario: If demographic and census data are unavailable or inaccessible, the program cannot validate the pilot's geographic footprint or measure equity coverage. Cooling refuges may be sited in low-need areas and home kits directed to low-risk households, leaving the most vulnerable unprotected. Baseline EMS and mortality data missing or unreliable prevents credible Month 4 (2027-02-08) gate evaluation, risking non-release of the €1.5M scale funding and loss of funder confidence in the playbook. Unconfirmed migrant-language profiles delay ambassador recruitment and translation by 4–6 weeks, causing non-official-language residents to miss enrollment and alert contact entirely, resulting in preventable heat illness or death in those communities. Combined, these gaps could cause a 2–4 week delay to the Month 2 (2026-12-08) readiness gate and gate failure at Month 4 (2027-02-08), forcing the program to scale back or cease operation mid-summer.

Best Case Scenario: Accessible, recent census and administrative data (2020 or newer) with neighborhood-level granularity enable rapid, precise vulnerability mapping by Month 0.5 (2026-10-23), confirming cooling-refuge siting and outreach targeting. Baseline EMS and mortality data obtained by Month 1 (2026-11-08) with consistent heat-attribution coding in place by Month 2 (2026-12-08) provide a robust foundation for Month 4 (2027-02-08) gate evaluation and credible attribution analysis. Confirmed migrant-language communities and concentration data by Month 0 (2026-10-08) allow immediate ambassador recruitment and translation procurement, ensuring enrolled non-official-language residents receive alerts and escalation guidance in their preferred language. With these inputs, staffing and budget allocations align with actual demand, enabling the program to meet Month 2 (2026-12-08) readiness and Month 4 (2027-02-08) scale gates on schedule, deliver a credible playbook, and build funder confidence in scaling to other EU cities.

Fallback Alternative Approaches:

• If municipal census or housing data are unavailable, request aggregated data from municipal social services, housing authority and utility companies (gas/electricity distribution) to infer housing condition and age distribution by neighborhood; cross-reference with GIS mapping of buildings by age and energy-efficiency labels if available.
• If baseline EMS and mortality data are absent or historically uncoded for heat attribution, conduct a rapid retrospective audit of a sample of prior-summer ED and EMS records (n=100–200 cases) using clinical criteria (core temperature, heat-related ICD codes, clinical judgment) to establish a pilot baseline; estimate confidence intervals and caveats clearly in the Month 4 (2027-02-08) gate report.
• If current demographic data are outdated (pre-2015), supplement with the most recent municipal planning or health equity assessments, NGO local-knowledge interviews (housing associations, social services, faith leaders) and a rapid survey sample (n=200–300 residents in high-need neighborhoods) conducted by Month 1 (2026-11-08) to triangulate vulnerable populations.
• If migrant-language data are not recorded in municipal sources, contact NGO partners (immigrant associations, refugee services, faith communities) and conduct 5–10 key-informant interviews by Month 0.5 (2026-10-23) to identify top languages and neighborhood concentrations; cross-check against census 'country of birth' fields if available.
• If cooling-center site inventory is incomplete, conduct a 1-week rapid canvass (Month 0.5 = 2026-10-23) of all candidate facilities (libraries, community centers, etc.) via phone and in-person visit checklist covering wheelchair access, water/toilets/first-aid, parking, signage and current operating hours; document findings in a simple spreadsheet and use to prioritize remediation or substitution before site-selection decision at Month 1 (2026-11-08).

Find Document 2: Castellón de la Plana Historical Heat Data & Temperature Records

ID: 1f879ea9-02e6-450a-bb45-247ffa4dff2e

Description: Daily maximum and minimum temperature records (2010-2025) from national meteorological service (AEMET) or local weather station, with date and location. Used to validate alert thresholds historically (how often does forecast ≥35°C daytime and ≥22°C night occur? how many are actual heat events vs. false alarms?), and to establish the baseline relationship between temperature and heat-related EMS/ED calls for temperature-adjusted evaluation.

Recency Requirement: 15-year historical record preferred (2010-2025); minimum 5-year baseline (2020-2025).

Responsible Role Type: Data and Evaluation Coordinator

Steps to Find:

• Contact Spanish national meteorological service (Agencia Estatal de Meteorología, AEMET) and request historical temperature data for Castellón de la Plana station (daily high/low, date).
• Download from AEMET public portal (https://www.aemet.es) or request via open-data API.
• Cross-check with local university or research institute weather data if available (e.g., Universitat Jaume I, Castelló, may have local station data).
• Obtain additional context: known major heat events in Castellón (2003, 2010, 2015, 2018, etc.) and their reported temperature and impact.

Access Difficulty: Easy. AEMET historical weather data are publicly available via portal and downloadable. Local university data may require a research-partnership request but are typically shared for public-health context.

Essential Information:

• Obtain 15-year daily maximum and minimum temperature records (2010–2025) from AEMET for Castellón de la Plana weather station, with date stamps for every record.
• Cross-validate alert-threshold frequency: how many days per year historically meet or exceed ≥35°C daytime AND ≥22°C night-time conditions for ≥2 consecutive days (Level 2 Alert trigger)?
• Quantify false-alarm rate: of those days meeting forecast thresholds, what percentage resulted in actual heat-related EMS/ED call spikes or mortality excess?
• Document known major heat events in Castellón (2003, 2010, 2015, 2018, and others): date, observed temperature, reported EMS calls, deaths, media coverage.
• Establish baseline temperature-mortality relationship: regression coefficient (deaths or EMS calls per 1°C above threshold) if data exist, with confidence intervals.
• Confirm data quality: missing days, measurement gaps, station relocations, or method changes over 15 years that could bias threshold calibration.
• Obtain parallel data from local university weather station (Universitat Jaume I) if available to validate AEMET record and assess local microclimate variation by neighborhood (e.g., heat-island effects in central vs. peripheral zones).

Risks of Poor Quality:

• Incomplete or missing data (>10% gaps) invalidates threshold calibration and forces reliance on national proxies, losing city-specific sensitivity and risking either over-alert (fatigue, budget burn) or under-alert (missed hot nights and preventable deaths).
• Inconsistent temperature measurement method or station relocation (e.g., different sensor, elevation, urban-ization change) introduces systematic bias; thresholds calibrated on 2010–2015 data may not apply 2025–2027.
• False-alarm rate unquantified: thresholds set without validation against actual EMS/ED load leave City uncertain whether forecast ≥35°C reliably predicts health impact; poor thresholds fail both gates and erode stakeholder trust.
• Baseline relationship (temperature vs. EMS/ED/mortality) absent or weak: evaluation at Month 4 (2027-02-08) cannot attribute observed changes to program vs. natural temperature variation, making scaling cost model non-credible.
• Neighborhood-level heat variation unmapped: peripheral and central Castellón may have 2–4°C difference due to density and materials; single city-wide threshold misses high-risk microclimates, leaving hot-spot residents under-protected.
• Historical data not accessible by Month 1 (2026-11-08): threshold calibration cannot be completed, forcing default (national thresholds) which may be misaligned to local climate, jeopardizing Month 2 (2026-12-08) readiness and drill validity.

Worst Case Scenario: If 15-year temperature records are incomplete, inaccessible, or of poor quality by Month 1 (2026-11-08), alert thresholds cannot be locally calibrated and must default to national forecast criteria. A defaulted, un-validated threshold may be misaligned to Castellón's actual heat-mortality risk: if too loose (low threshold), the program over-activates centers on marginal days, burning €10k–15k per false alarm and exhausting center-hours budget by July (€1.2M budget, 25 planned activation days, each ~€52k—three unnecessary activations consume €156k and reduce reserves for real peaks). If too tight (high threshold), the program misses hot-night events that drive elderly mortality, potentially leaving 5–10 heat-vulnerable residents unprotected during critical July–August surges. Either scenario—budget collapse or preventable mortality during observed heat event—triggers media scrutiny, funder loss of confidence, and non-release of €1.5M scale funding at Month 4 (2027-02-08). Estimated financial and reputational impact: €200k–400k cash shortfall plus credibility loss for playbook scaling to other EU cities.

Best Case Scenario: By Month 1 (2026-11-08), a complete 15-year AEMET record and validated local university data establish precise city-specific alert thresholds: ≥35°C daytime AND ≥22°C night-time occurs 18–25 days per season historically, and 80%+ of those days correlate with ≥1.3× baseline EMS call load. Threshold-calibrated forecasts reduce false alarms to <15% and ensure real heat events are caught. Baseline temperature-mortality regression (e.g., 2.1 deaths/°C above 32°C threshold) quantifies expected harm without intervention, enabling credible Month 4 (2027-02-08) attribution and scaling cost model ($X per prevented death). Neighborhood heat-mapping reveals that central Castellón reaches 2–3°C hotter than periphery; this directs home-kit and transport resources to highest-risk zones, improving equity and impact. Drill thresholds set using this data are realistic and validate operational readiness. Month 4 (2027-02-08) gate measurement against calibrated, evidence-grounded thresholds is defensible and builds stakeholder and funder confidence in the program's precision, supporting Year-2 continuation and replication to peer EU cities.

Fallback Alternative Approaches:

• If AEMET 15-year record is incomplete or inaccessible, request 5-year minimum baseline (2020–2025) by Month 1 (2026-11-08) and supplement with proxy: published Spanish national summer heat events (AEMET heat warnings, red-alert days) and Castellón newspaper archives (El Periódico de Castellón, La Ronda) documenting observed temperatures and health impacts in 2010–2019; cross-reference with hospital administrative data (admission logs by date, not patient names) to infer EMS call spikes.
• Contact Universitat Jaume I (Climate and Environmental Sciences group) at Month 0.5 (2026-10-23) to request access to local weather-station records or to conduct a 3–6 month pilot microclimate monitoring (April–September 2027) alongside AEMET data, establishing local calibration for future years.
• If baseline temperature-mortality relationship cannot be derived from local data (small samples, incomplete coding), use published regression coefficients from peer Spanish cities (Madrid, Barcelona, Valencia) adjusted for Castellón's climate and housing stock, documented in literature (e.g., Spanish National Health Institute reports on heat mortality). Disclose this limitation transparently in the evaluation report and playbook.
• Conduct a rapid expert-elicitation workshop at Month 1 (2026-11-08) with local public-health physician, EMS medical director and meteorologist: ask them to propose alert thresholds based on professional judgment and prior experience with Castellón heat events. Use their input to validate or adjust quantitative thresholds and document the rationale.
• If neighborhood-level heat mapping is not available, use proxy: map top-floor flats and poor-insulation social housing (available from municipal building registry) as proxy for heat vulnerability; concentrate home kits and mobile cool-points there, and measure neighborhood coverage equity in the evaluation report.
• For Month 2 (2026-12-08) readiness gate, use national meteorological forecast thresholds (AEMET red/orange/yellow warnings) as interim alert criteria, documented as provisional; commit to local calibration by Month 4 (2027-02-08) and threshold review by Month 6 (2027-04-08) once real summer 2027 data arrive. This allows gates to proceed on schedule while preserving the option to adjust thresholds for Year 2.

Find Document 3: Castellón de la Plana Municipal Cooling-Center Asset Inventory

ID: f99bad9d-b417-474d-8a99-6239257d50ca

Description: Official list of municipal or accessible public facilities (libraries, community centers, parish halls, sports facilities, schools, government offices) with: location (address, postal code), floor area, occupancy capacity, current opening hours, accessibility features (wheelchair access, toilets, water, parking), utilities (air-conditioning, heating, water supply), and insurance/liability status. Used to identify and audit the 10 proposed cooling-center sites.

Recency Requirement: Current (2024-2025); update if facilities have undergone recent renovation or closure.

Responsible Role Type: Cooling Center Network Manager

Steps to Find:

• Contact Castellón de la Plana municipal facilities or asset-management department; request comprehensive facility inventory with accessibility audit data.
• Request municipal facility-use agreements or insurance documentation for liability assessment.
• Contact library system, municipal sports/recreation department, and social services to cross-check facility capacity and opening-hour availability.
• Visit or photograph proposed sites to verify accessibility; document any gaps (missing ramps, inadequate toilets, no quiet room).

Access Difficulty: Medium. Municipal facilities data are typically held internally; access requires formal request to facilities management or city procurement office. Some data may be classified (insurance, security). Accessibility audit reports may be incomplete; physical verification required.

Essential Information:

• Identify and list all municipal and publicly accessible facilities (libraries, community centers, parish halls, sports facilities, schools, government offices) in Castellón de la Plana with complete addresses and postal codes.
• Document floor area (m²) and current functional occupancy capacity for each site under normal and heat-alert conditions.
• Map accessibility features for each facility: wheelchair ramps/level entry, accessible toilets (≥1 per 50 occupants), water fountains or supply, parking (general and disabled), quiet/low-stimulus rooms.
• Record utilities availability: air-conditioning system type and capacity (kW or equivalent); backup power; water supply capacity (liters/hour); heating (not required for summer, note for completeness).
• Verify current opening hours and flexibility for extended hours (10:00–20:00 standard, 24:00 capability for ≥3 sites at alert Level 3).
• Confirm liability insurance coverage and facility-use agreement status for each proposed site; identify gaps requiring legal action before Month 2 (2026-12-08) readiness gate.
• Audit which sites meet accessibility standards (ramps, toilets, water, quiet space) to confirm ≥50% of planned refuge places are in fully accessible facilities, per the refuge-site standard.
• Identify remediation needs (cost, timeline) for each inaccessible site; confirm remediation cost ≤€10k and timeline ≤4 weeks, else deprioritize or defer the site.
• Verify capacity of water supply and sanitation under continuous occupancy (10:00–20:00, potentially 200–400 residents per day at Level 2–3 across all sites).
• Cross-reference each site's location (address, postal code) against the vulnerability heat map to confirm ≥70% of enrolled residents are within 800 m (10-minute walk) of ≥1 refuge.

Risks of Poor Quality:

• Incomplete or outdated facility list: if closed, relocated, or newly renovated sites are not flagged, the city may commit to sites that are unavailable, reducing actual refuge capacity below the planned 400 places and forcing transport-only access for residents who cannot travel.
• Missing or inaccurate accessibility audit: if ramps, toilets, water or quiet rooms are not documented, the city may open a site that excludes wheelchair users, deaf/hard-of-hearing, or sensory-sensitive residents, violating disability access law and failing the equity gate.
• Underestimated occupancy capacity: if a site's functional capacity is overstated (e.g., assuming 50 places when furniture/layout allows only 30), the city will overcommit refuge hours and overcrowd sites, increasing heat-illness risk and breaching occupancy fire codes.
• Insurance and liability gaps: if a facility lacks public-liability insurance or a formal use agreement is not signed by Month 2 (2026-12-08), the city faces litigation exposure if an incident occurs at an unstaffed or inadequately protected site.
• Utility underestimation: if water supply or sanitation capacity is not verified for continuous 10-hour occupancy, sites may run out of water or face toilet failures during peak alert days, forcing premature closures and resident evacuation.
• Spatial mismatch to vulnerable populations: if the 10 sites are located in affluent or central districts only, isolated and mobility-limited residents in peripheral neighborhoods will exceed the 800 m walking distance threshold, reducing actual reach by 20–30% and failing the equity intent.
• Remediation scope creep: if accessibility barriers are discovered after commitment (e.g., structural ramp required), remediation costs and timelines could exceed the €10k and 4-week thresholds, forcing site abandonment mid-setup and destabilizing the network footprint.
• Misalignment with refuge-hours assumption: if water, sanitation or utilities cannot support extended hours (24:00 at Level 3), the city cannot deliver the promised overnight cooling, reducing protection of hot-night mortality risk among elderly residents.

Worst Case Scenario: The city commits to 10 refuge sites without completing a full accessibility and capacity audit. Two sites (due to be large, central facilities) lack disability ramps and adequate sanitation and require €15k–20k and 6–8 week remediation. The audit is completed only in March (Month 5 = 2027-03-08), past the Month 2 (2026-12-08) readiness gate, leaving no time to fix the sites or find replacements. The city opens the refuges at 70% capacity (280 instead of 400 places) and cannot accommodate wheelchair users at three sites. During the first Level 3 alert in June, water supply fails at one site due to inadequate pressure, forcing evacuation of 80 residents mid-day. Media coverage frames the program as "inaccessible and unsafe." Enrollment collapses by 40%, outreach contact attempts drop to 3,000/month (from 5,000 planned), and the 60% contact-success gate fails. Reputational damage affects the scale decision and Year-2 funding is denied. Estimated reach loss: 900 residents; estimated legal cost: €50k–100k.

Best Case Scenario: A comprehensive, verified asset inventory is completed by Month 1 (2026-11-08), identifying 12 sites (8–12 planned), 450+ places, all with confirmed accessibility and utility capacity. Eight sites meet the fully accessible standard; two require <€8k remediation (ramping, toilet upgrade) on 2-week schedules; two are deferred or dropped. All sites are mapped against the vulnerability heat map, confirming ≥75% of enrolled residents within 800 m. Insurance, facility-use agreements and liability coverage are confirmed and signed by Month 2 (2026-12-08). Water-supply testing at each site confirms capacity for 10–24 hour continuous operation. Staffing and accessibility briefings occur without gaps. The first Level 3 alert in June opens all refuges at full capacity, water and sanitation function flawlessly, wheelchair and sensory-access accommodations are validated, and residents report feeling safe. Enrollment and contact rates hit 80% of target by Month 4 (2027-02-08). The scale gate is met. Documented accessibility and contingency infrastructure become a reusable model for other EU cities, strengthening the scaling playbook.

Fallback Alternative Approaches:

• If a comprehensive municipal inventory cannot be obtained by Month 0.5 (2026-10-23), engage a facility-assessment consultant (estimated cost €8k–12k, timeline 2–3 weeks) to conduct rapid site surveys and accessibility audits of the top 15 candidate facilities, prioritizing those already contracted or in frequent public use.
• If a single municipal facilities department cannot provide complete data, create a cross-departmental working group (libraries, sports/recreation, social services, public works) at Month 0 (2026-10-08) to pool facility ownership and operational information; designate one lead coordinator to compile a unified inventory by Month 1 (2026-11-08).
• If insurance or liability documentation is incomplete or outdated, require each site to obtain a renewal certificate of public-liability insurance (covering the heat-response activity) and a formal facility-use agreement signed by the facility owner/manager and the city legal department by Month 1.5 (2026-11-23); estimated cost €500–1,500 per site.
• If water-supply or sanitation capacity cannot be verified through existing utility records, conduct on-site water-pressure and flow tests (5–10 minutes per site) and a sanitation load assessment (occupancy × toilet ratio) in Month 1 (2026-11-08); estimated cost €1,500–2,500 for all sites; engage a municipal water/sanitation engineer.
• If accessibility audit findings exceed the €10k or 4-week remediation threshold for a site, immediately (by Month 1.5 = 2026-11-23) identify a backup facility (10–15 candidate replacements identified at Month 0 = 2026-10-08) and shift the refuge allocation; estimate 1–2 backup sites will be needed.
• If the spatial distribution of sites does not meet the 800 m walking-distance target for ≥70% of enrolled residents, augment the network with informal cool points (pharmacies, parish halls, shopping centers, sheltered housing) that are already air-conditioned and trusted by residents, requiring no new infrastructure investment but adding staffing coordination cost (estimated €50k–80k).
• If full 24-hour capability at three sites cannot be confirmed by Month 2 (2026-12-08), scale back to 10:00–22:00 hours at Level 2–3 and offer 24-hour transport-and-phone triage instead; this extends the transport model but keeps the refuge footprint viable.

Find Document 4: Castellón de la Plana Baseline Heat-Related Mortality & Excess-Death Estimates

ID: 0bf77087-1fd6-46b3-ac5c-2546b74f0704

Description: Three-year historical data on deaths attributed to heat (ICD-10 code T67 or documentation of 'heat-related' in death certificate) or excess mortality during summer months (May-September) compared to expected seasonal baseline (e.g., via statistical/demographic methods). Used to establish baseline harm and to assess program attribution post-hoc. May be obtained from regional health authority, national health statistics office, or municipal vital statistics.

Recency Requirement: Most recent 3-5 years of data (2020-2025); supplement with 2010-2019 trend if available to establish longer-term patterns.

Responsible Role Type: Data and Evaluation Coordinator / Health Epidemiologist

Steps to Find:

• Contact regional health authority (SSVS) or Valencian public-health institute (Agencia de Salut Pública) for mortality data by cause of death, including heat-related codes (T67.0-T67.9).
• Request municipal vital statistics (registro civil) for death certificates with heat or heat-related condition notation.
• Search Spanish national health statistics portal (Instituto de Salud Carlos III) for Castellón excess-mortality or heat-attributable-death estimates.
• Contact university epidemiology department or research institute in Valencia region; they may have conducted prior heat-mortality studies with Castellón data.
• Request from national statistical office (INE) if mortality data by cause and municipality are published.

Access Difficulty: Hard. Mortality data are sensitive and privacy-protected. Individual death certificates are restricted-access. Aggregated mortality counts (by heat-code ICD-10 or monthly excess-death estimates) are more accessible via health authorities. University researchers may have already analyzed this data; a research partnership may accelerate access.

Essential Information:

• Confirm 3–5 years of historical heat-related mortality data (2020–2025) by ICD-10 heat codes (T67.0–T67.9) or death-certificate notation; provide annual counts, seasonal distribution (May–September focus), and geographic breakdowns by district or neighborhood within Castellón de la Plana.
• Establish baseline excess mortality during summer months using temperature-adjusted statistical methods (e.g., expected deaths minus observed deaths, or regression of deaths on temperature lagged 0–3 days); quantify 95% confidence intervals around baseline estimates to anchor uncertainty for Year-1 attribution analysis.
• Document data quality and coding consistency across years and providers (municipal vital records, regional health authority, EMS): identify gaps, coding rule changes, or incomplete records that may inflate or deflate baseline estimates by >10%.
• Provide demographic and geographic breakdowns of baseline by age bands (65–74, 75–84, 85+), living situation (alone vs. household), housing type (top-floor vs. ground, social vs. private), and neighborhood deprivation index or postal code to confirm vulnerability mapping used in the program design.
• List data custodians, access agreements, and confidentiality constraints; confirm whether aggregate counts (deaths by heat code) are openly available or require a data-processing agreement; specify retention period and deletion protocols post-evaluation.

Risks of Poor Quality:

• Incomplete or under-coded baseline (e.g., heat-related deaths coded as 'cardiovascular' rather than T67) will systematically underestimate true baseline, making any Year-1 program impact appear artificially large and undermining credibility of the scaling cost model when presented to peer EU cities.
• Inconsistent coding across years (e.g., 2020 excluded heat codes but 2021–2025 included them) introduces trend noise that cannot be distinguished from program effect, causing Month 4 (2027-02-08) attribution gates to fail or produce uninterpretable results.
• Missing or delayed access to data by Month 1 (2026-11-08) will delay coding-agreement meetings with EMS and health partners, pushing the MOU sign-off past the Month 2 (2026-12-08) readiness gate and preventing drill-based validation of daily aggregate reporting protocols.
• Baseline estimates with wide confidence intervals (e.g., ±30–50% around point estimate) or small cell counts in demographic subgroups will make it impossible to detect plausible program effects (15–25% reduction in heat deaths, estimate) with statistical power, weakening evaluation credibility and funder confidence in Year-2 funding decisions.
• Lack of geographic granularity (e.g., only city-wide totals, not by neighborhood) prevents the program from validating whether targeted intervention in high-risk districts achieved equity gains or merely reproduced prior patterns.

Worst Case Scenario: The program operates for 12 months, implements cooling centers, transport, outreach and home kits, and measures outcomes at Month 12 (2027-10-08). However, the baseline data are either unavailable, incomplete (coding gaps, missing years), or inconsistently defined. At evaluation, the team cannot distinguish program-driven mortality reduction from year-to-year noise or seasonal variation, and any claimed reduction (e.g., 20% fewer heat deaths) is challenged as unverifiable. The playbook is published with a caveat that attribution was not possible, undermining its credibility for other EU cities. Peer-city adoption is delayed or abandoned, and Year-2 funding (€2.3M, estimate) is withheld pending a stronger evaluation design, leaving the program unable to scale. Reputational damage: municipal government loses confidence in evidence-based health interventions.

Best Case Scenario: Baseline data are obtained by Month 1 (2026-11-08), coded consistently across years, with demographic and geographic breakdowns and 95% confidence intervals. The team validates the baseline via a partner audit at Month 1.5 (2026-11-23), achieves full coding agreement with EMS and hospitals by Month 2 (2026-12-08), and uses this to pre-specify the attribution analysis protocol. Daily aggregate reporting from health partners is validated during drills. At Month 12 (2027-10-08), evaluation shows plausible 12–18% reduction in heat-related EMS calls and 10–15% reduction in excess deaths with narrow confidence intervals. The playbook and scaling cost model are published with high credibility, attracting peer-city interest and securing Year-2 funding commitment from funder or new source. Program expands to city-wide by Month 15 (2028-01-08).

Fallback Alternative Approaches:

• If municipal vital-statistics records are unavailable or restricted-access, request aggregated excess-mortality estimates (observed minus expected deaths by month and age band) from the regional health authority (SSVS) or Valencian public-health institute (Agencia de Salut Pública), which may already have published this analysis for policy purposes.
• If historical EMS data by heat-code are not routinely extracted, commission a rapid retrospective review of EMS call records for Months 5–9 (2027-03-08 to 2027-07-08) of 2023–2025 using a simple triage form (call chief complaint, location, outcome, temperature that day); use the sample to estimate annual heat-call volume and seasonal pattern, accepting wider confidence intervals.
• If individual-level data access is blocked by privacy regulation, partner with a university epidemiology department or regional research institute (e.g., University of Valencia) that holds a data-use agreement with the health authority; they can compute baseline statistics under their institutional oversight and provide aggregate results to the city under a data-processing agreement.
• If baseline data collection will take >6 weeks and delay the Month 1 (2026-11-08) legal-review milestone, adopt a provisional baseline from published national or regional heat-mortality statistics (e.g., Spanish National Statistics Institute mortality tables) as a placeholder for drill planning and procurement; commit to replacing it with local data by Month 3 (2027-01-08).
• If demographic and neighborhood-level breakdowns of baseline cannot be linked to individual death records due to privacy constraints, use census and housing data to construct a vulnerability-weighted proxy baseline (e.g., age-stratified mortality rates applied to census age distribution in each neighborhood), which can be validated against aggregate totals and refined after Year 1.

Find Document 5: Spanish & Valencian GDPR & Health-Data Protection Guidance

ID: 88109013-c68c-4514-9aae-15c88b189001

Description: Official regulatory guidance from Spanish Data Protection Agency (AEPD) and regional health authorities on: lawful basis for processing health data for public-health emergencies (Article 6 GDPR), consent requirements and withdrawal procedures (Article 7), data-processing agreements (Article 28), and special-category data rules (Article 9). Clarifies whether heat-alert contact is a 'public task' (Article 6(1)(e)) or requires explicit consent, and how intermediary-held health data (housing associations, social services) is governed.

Recency Requirement: Current GDPR guidance (2021 or later); AEPD published criteria or decisions preferred.

Responsible Role Type: GDPR Compliance Officer / Legal Counsel

Steps to Find:

• Visit Spanish Data Protection Agency (AEPD) website (aepd.es) and search for guidance on health data, public-health emergencies, and intermediary data sharing; download published documents and criteria.
• Request AEPD published decisions or opinions on heat-alert contact lawful basis (may be available as case studies or FAQ).
• Contact AEPD directly via email or phone for guidance on whether the intermediary-held-list model complies with Spanish law (they may issue formal written guidance).
• Search Valencian regional law (Generalitat Valenciana) for any regional data-protection guidance or health-privacy guidance (beyond national GDPR).
• Review Catalan Data Protection Authority (APDCAT) or other Spanish regional authority guidance for heat or emergency health contexts; may be transferable precedent.
• Consult with municipal legal department or GDPR counsel for case law or AEPD decisions on public-health and emergency-context data processing.

Access Difficulty: Easy to Medium. AEPD website has public guidance in Spanish; English translation may be needed. AEPD accepts guidance requests but response time varies (2-8 weeks). Regional authorities may have fewer published resources. Legal counsel familiar with Spanish GDPR practice is helpful.

Essential Information:

• Clarify whether heat-alert contact to intermediary-held residents (housing associations, social services, NGOs, pharmacies) qualifies as a 'public task' under GDPR Article 6(1)(e) or requires explicit consent under Article 7, and under which Spanish/Valencian legal authority.
• Define the lawful basis and data-processing chain for aggregate heat-related EMS and ED counts shared daily from hospitals and EMS to the city incident commander (Article 6 GDPR and Spanish health-privacy law equivalents).
• Specify retention periods, deletion procedures and conditions for re-consent if heat-alert operations continue into Year 2 beyond the initial 12-month pilot.
• Confirm whether data-processing agreements (Article 28 GDPR) with intermediary partners are mandatory or whether a simpler MOU suffices if no personal data is transferred to the city.
• Identify AEPD published decisions, guidance documents or case studies on heat emergencies, public-health alerts or intermediary-held health data to support the legal interpretation.
• State the procedure and timeline for notifying AEPD (or regional equivalent) if a data breach occurs during outreach (e.g., partner staff misconduct, accidental disclosure).

Risks of Poor Quality:

• Inaccurate or outdated GDPR guidance could lead to a legal challenge from data subjects or AEPD, delaying partner sign-off by 2–4 weeks and forcing redesign of the outreach model mid-implementation (Month 1–2 = 2026-11-08 to 2026-12-08 readiness gate risk).
• If the lawful basis is unclear, housing associations, social services or NGOs may withdraw from partnerships, reducing outreach reach by 10–25% and failing the Month 4 (2027-02-08) 60% contact-success gate.
• Guidance that incorrectly interprets Spanish data-protection law (beyond GDPR) could expose the city to additional liability under regional regulations, incurring unexpected legal fees (€15,000–30,000) and reputational damage.
• Missing guidance on breach notification timelines could cause the city to miss AEPD reporting deadlines (48 hours), triggering regulatory penalties and media scrutiny.
• Absence of precedent or case studies on heat emergencies could force reliance on generic GDPR guidance, leaving ambiguities about risk allocation between city and intermediary partners unresolved, leading to disputes during the season.

Worst Case Scenario: The city proceeds with the intermediary-held-list model without legal clearance, believing the 'public task' basis is solid. In June–July, a partner (e.g., housing association) faces AEPD scrutiny or a resident complaint about data handling. AEPD issues a provisional halt to data sharing pending investigation (typical 2–8 weeks). Outreach contact attempts drop from 5,000/month to 500–1,000/month, failing the 60% contact-success gate. The €1.5M scale funding is withheld at Month 4 (2027-02-08). The city must halt or drastically reduce operations by August during peak summer heat risk, leaving 1,500–2,000 enrolled residents without check-in support. Estimated harm: 5–15 preventable excess deaths in the unprotected population; legal remediation and potential fines €50,000–100,000; program credibility destroyed for Year 2 and EU scaling.

Best Case Scenario: AEPD or regional authority issues clear, published guidance by Month 1 (2026-11-08) confirming the intermediary-held-list model complies with Spanish law under the 'public task' basis, with specific language on retention and deletion. Template data-processing agreements are provided or confirmed as unnecessary. Partners (housing associations, social services, NGOs) sign MOUs by Month 1.5 (2026-11-23) with confidence. Outreach proceeds uninterrupted through the season, achieving ≥60% contact success and meeting the Month 4 (2027-02-08) gate. The €1.5M scale funding is released on schedule. The playbook documents this legal pathway as a reusable precedent for other EU cities, reducing their legal-review timeline and cost by 50% and accelerating pan-European adoption of the heat-response model.

Fallback Alternative Approaches:

• Obtain a formal written GDPR legal opinion from a specialist Spanish data-protection counsel by Month 0.5 (2026-10-23) if AEPD guidance is unavailable or delayed. Budget €15,000–30,000 and use the opinion as the basis for partner MOUs; this is slower than published guidance but provides contractual liability protection.
• Shift to a consent-based registry model (opt-in enrollment through GPs, pharmacies and cooling centers) if the public-task interpretation is rejected. This reduces legal risk but lowers reach to isolated, offline residents by an estimated 15–25%; combine with building-level canvassing via local sentinels to recover reach (adds €100,000–150,000 in outreach staffing and 4–6 weeks of timeline).
• Request a formal AEPD guidance opinion via the agency's guidance-request process (typically 4–8 weeks); parallel this with legal counsel drafting interim MOUs so that no delay occurs if AEPD response is slow.
• Engage a regional university law school or public-health research center as a partner to co-author a position paper on heat-emergency data sharing and submit it to AEPD as a reference; this builds precedent and may accelerate clarity (timeline 6–10 weeks, cost €5,000–10,000 co-funding).
• Pilot the intermediary-held-list model with one trusted partner (e.g., the largest housing association or social service) in Month 1–2 (2026-11-08 to 2026-12-08) under informal data-sharing practices, gather 2–4 weeks of operational data on partner capacity and resident response, then formally obtain legal clearance and scale to all partners by Month 3 (2027-01-08). This de-risks the model with evidence but delays full-scale outreach by 3–4 weeks.

Find Document 6: EU & Spanish Public Procurement Rules & Thresholds (2024-2025)

ID: 27dfc82c-e0be-46ce-a7c8-90f12cae8251

Description: Current EU public-procurement directives (2014/24/EU, 2014/25/EU) and Spanish national transposition (LCSP - Ley de Contratos del Sector Público) specifying procurement thresholds (below-threshold vs. tender-required amounts), simplified procedures for emergency or low-value purchases, framework-agreement rules, and audit requirements. Used to determine legal procurement route for cooling kits, transport, and handyperson services within the €3.5M budget.

Recency Requirement: Current (2024-2025); Spanish LCSP as amended 2023-2024; EU Directive 2014/24/EU.

Responsible Role Type: Municipal Procurement Officer / Contract Law Specialist

Steps to Find:

• Download Spanish public-procurement law (LCSP, Ley 9/2017) from official government source (boe.es).
• Search Spanish Public Sector Contracts Board (Junta de Contratación del Sector Público) website for current thresholds, guidance, and case studies.
• Download EU Directive 2014/24/EU (Procurement Directive) and its preamble from EUR-Lex.
• Contact Spanish municipal association (FEMP) or local municipal procurement office for practical guidance on below-threshold purchasing and framework-agreement procedures in Spain.
• Search for OECD or EU publications on emergency procurement procedures (may be relevant if heat response is framed as emergency/public-health urgency).

Access Difficulty: Easy. Spanish law is public and available via boe.es; EU directives are on EUR-Lex. Municipal associations provide practical templates and training. Complexity is moderate; a municipal procurement officer or external legal counsel familiar with Spanish rules is helpful.

Essential Information:

• Identify the current EU and Spanish public-procurement regulatory framework (Directives 2014/24/EU, 2014/25/EU and LCSP transposition) applicable to the city of Castellón de la Plana in 2024–2025.
• Quantify the euro thresholds that trigger mandatory competitive tender vs. simplified/below-threshold procurement for each purchase category (cooling kits, transport retainer, handyperson services, refuge fit-out, security contracts).
• Determine which procurement pathways (framework call-offs, below-threshold direct award, simplified emergency procedures, competitive tender) are available to meet the Month 2 (2026-12-08) readiness gate without violating audit requirements.
• Document the audit-readiness requirements for each pathway: file documentation, competitive justification, price benchmarking, single-source authorization, and record retention.
• Clarify whether heat-response can be framed as an emergency or public-health urgency under Spanish law to justify expedited or non-competitive procedures.
• Specify template contract language required under LCSP for framework agreements and standby retainers (e.g., minimum capacity guarantees, call-off procedures, price escalation caps).
• Identify any Spanish municipal-association (FEMP) or regional government guidance on procurement templates or pre-vetted supplier lists for kits, transport, or security services.
• Define the liability and audit exposure if the city uses below-threshold purchasing repeatedly to avoid transparency or competitive bidding, and what documentation mitigates this risk.

Risks of Poor Quality:

• If thresholds are misunderstood or applied inconsistently, orders may be challenged as non-compliant, forcing re-tendering mid-season and delaying delivery by 4–8 weeks past the Month 2 (2026-12-08) gate.
• Lack of audit-ready documentation (e.g., missing competitive justification for sole-source awards, price benchmarking, or call-off records) exposes the city to regulatory audit findings, reputational damage and potential contract invalidation.
• Ambiguity on whether heat-response qualifies for emergency-procurement exemptions could lead to legal challenge by excluded bidders, tying up resources in dispute resolution.
• If handyperson, kit or transport contracts lack proper LCSP-compliant escalation-cap clauses, summer demand spikes could trigger cost increases of €50k–150k, forcing mid-season service cuts.
• Repeated use of below-threshold purchasing without transparent competitive process invites scrutiny from auditors, EU funder reviews and political opponents, undermining the program's credibility.
• Template contract language that fails to align with LCSP requirements (e.g., standby-retainer guarantees, call-off procedures, payment terms) could result in supplier disputes, non-performance claims or cost disputes during alert days.

Worst Case Scenario: The city misapplies procurement thresholds or uses expedited procedures without proper legal basis, triggering an audit finding or legal challenge by an excluded bidder. Contracts are invalidated mid-season; retenders delay kit delivery and transport contracting past March, preventing home interventions and forcing the transport model to taxi-only at +€150k–250k cost. Schedule slip of 4–8 weeks forces closure of Month 2 (2026-12-08) readiness gate. €1.5M scale funding is withheld. Program credibility erodes; playbook reuse by other EU cities is compromised. Estimated financial and reputational cost: €50k–100k legal remediation + €150k–250k operational overrun + loss of scaling opportunity.

Best Case Scenario: Clear, auditable procurement pathways are documented by Month 0.8 (2026-11-01), thresholds and justifications are pre-vetted by legal counsel, and a hybrid strategy (frameworks for speed, competitive tenders for tranche 2) meets the Month 2 (2026-12-08) gate without audit exposure. All kit and transport orders are placed by Month 2 (2026-12-08), delivery milestones are met by April, and home interventions and transport are operational by May. Procurement is transparent and replicable; other EU cities adopt the same templates and procedures, reducing their procurement time and risk. Public trust in municipal governance is strengthened. Program meets all gates and scales successfully.

Fallback Alternative Approaches:

• Engage a specialized Spanish public-procurement law firm by Month 0 (2026-10-08) (cost ≈€15k–30k) to provide written legal opinion on thresholds, eligible procedures, audit requirements and template contracts. Use the opinion to justify procurement decisions in writing and build audit-ready files.
• Contact the Spanish municipal association (FEMP) and request template procurement files, supplier pre-qualification lists, and guidance on heat-response emergencies. FEMP may have published case studies or model tenders for similar services.
• Consult the regional government (Generalitat Valenciana) procurement office to clarify whether regional or national frameworks for emergency public health exist, and whether they offer pre-qualified supplier lists or expedited procedures.
• Identify whether Castellón de la Plana has an existing municipal procurement framework (e.g., for energy, transport, or facilities management) that can be leveraged via call-off orders rather than new tenders.
• If competitive tendering cannot be completed by Month 2 (2026-12-08), split procurement into two phases: place 30–40% of kits and transport via below-threshold or framework by Month 1.2 (2026-11-14), then conduct a full competitive tender for the remainder starting Month 2 (2026-12-08), with delivery expected by Month 5 (2027-03-08). Document the split as a staged delivery strategy, not as avoidance of competition.
• Request a waiver or confirmation letter from the local EU funder (likely a national or regional ministry) clarifying whether the heat-response program qualifies for public-health emergency treatment under procurement rules, and in writing.

Find Document 7: Castellón de la Plana NGO & Social Services Directory (Housing Associations, Social Care, Homeless Services, Migrant Organizations)

ID: b501f078-895b-4278-b459-d0b4227342d4

Description: Comprehensive list of local non-governmental and community organizations, including: housing associations/cooperatives (vivienda social), social services (servicios sociales), homeless or rough-sleeping services, migrant integration organizations, faith-based groups, and language/cultural associations. Includes contact names, phone, email, service scope, and current client base. Used to identify and engage partners for intermediary-held outreach, street contact, language access, and community trust-building.

Recency Requirement: Current (2024-2025); update annually; some turnover in staff/leadership expected.

Responsible Role Type: Partner Liaison Officer / Community Engagement Lead

Steps to Find:

• Contact Castellón municipal social services department for official registry of partner organizations and referral networks.
• Request municipal integration or migration office directory of migrant associations and support organizations.
• Search online directories: Plataforma del Voluntariado de España (Spanish volunteer directory), Guía del Tercer Sector (Spanish NGO directory), and regional Valencian NGO networks.
• Contact Castellón archdiocese or religious affairs office for list of faith-based organizations (mosques, churches, synagogues) active in social care.
• Inquire with municipal housing authority about housing associations and their outreach/welfare roles.
• Request homeless-service NGO directory from Castellón social services or regional authorities.

Access Difficulty: Easy to Medium. Municipal social services maintain partner registries (usually shared readily). Online directories and faith organizations are publicly listed. Contact details may be incomplete; direct phone verification needed.

Essential Information:

• Identify and list all active housing associations, social cooperatives (vivienda social) and social-housing managers operating in Castellón de la Plana with current contact names, phone numbers, email addresses, service areas and estimated client bases (target: 5-10 organizations).
• Obtain complete registry of municipal and regional social services offices (servicios sociales) with department heads, phone, email and service scope (elderly care, disability support, family services); confirm which offices manage outreach capacity for heat-alert campaigns.
• Compile comprehensive directory of homeless-services NGOs, rough-sleeping outreach teams and emergency shelter operators active in Castellón, including overnight shelter capacity, day-center locations, current client counts and outreach staff rosters.
• Locate and verify 4-6 migrant-integration organizations, language associations and cultural centers serving non-Spanish speaking communities (Arabic, Romanian, Portuguese speakers confirmed; others TBD at Month 0 = 2026-10-08), including staff, current client populations and existing community-trust relationships.
• Obtain contact details and social-mission descriptions for all active faith-based organizations (Christian churches, mosques, synagogues, other faiths) engaged in social outreach or welfare services in Castellón.
• Identify public libraries, community centers, parish halls and other existing assets (owners, facility managers, opening hours, accessibility status, water and toilet provision, security arrangements) suitable for conversion to cooling refuges.
• Document any existing data-sharing or welfare-referral partnerships between organizations (e.g., housing association → social services → NGO → pharmacy chains) to understand formal consent and data-handling agreements already in place.
• Confirm which organizations hold lawful bases (contractual duty, existing consent frameworks or public-task authority) for contacting their own clients or residents, and which would need new consent or data-processing agreements under GDPR.
• Quantify total potential reach: sum of enrolled clients, residents and service users across all identified partner organizations to validate whether 3,000 enrolled high-risk residents by Month 7 (2027-05-08) is achievable.
• Identify any known gaps in geographic coverage (neighborhoods or populations underserved by existing organizations) to inform recruitment of additional partners or direct municipal outreach.

Risks of Poor Quality:

• Incomplete or outdated partner directory means some high-risk residents will not be identified or contacted, reducing outreach reach below the 60% contact-success gate (Month 4 = 2027-02-08) and equity coverage by neighborhood.
• Inaccurate contact details (wrong phone, departed staff) lead to failed enrollment calls, wasting outreach capacity and delaying partner engagement, compressing the hiring and training timeline before Month 2 (2026-12-08).
• Missing or incorrect data on partner organization lawful bases and consent frameworks forces redundant GDPR vetting and delays MOU signature, potentially pushing data-processing agreements past the Month 1.5 (2026-11-23) deadline.
• Underestimating partner capacity (e.g., not knowing a housing association manages 8,000 residents) leads to unrealistic outreach targets and partner fatigue, causing mid-season partner dropout and loss of 10-20% of planned contacts.
• Failure to map existing data-sharing agreements and trust relationships causes duplicate consent requests or partner confusion about consent scope, eroding community trust and NGO cooperation.
• Unverified accessibility or facility information for proposed cooling-refuge sites (e.g., library lacking wheelchair access, parish hall lacking water) forces late-stage site remediation or substitution, jeopardizing the Month 2 (2026-12-08) readiness gate.
• Missing information on migrant-community organizations and language capabilities means language-access targets (≥5% of outreach in non-official languages, Month 4 = 2027-02-08) are unachievable, failing equity metrics.
• Lack of clarity on faith-leader involvement and trust relationships slows recruitment of trusted messengers, reducing uptake of communications and enrollment among faith-affiliated residents.

Worst Case Scenario: If the directory is incomplete, inaccurate or outdated, the outreach model collapses. Partner organizations cannot be contacted reliably, delaying engagement by 2-4 weeks and compressing MOU negotiation into a 2-week window before Month 2 (2026-12-08). Critical partners (social services, housing associations) may withdraw if GDPR concerns are not pre-cleared, reducing reach by 15-25% and invalidating the 3,000-enrollment target. Geographic gaps mean entire neighborhoods of vulnerable residents (e.g., migrant enclaves, homeless populations) are missed. A failed refresh of the directory mid-season (staff turnover in partner organizations) could orphan the outreach operation by July, collapsing the 60% contact-success gate and forcing the program to rely solely on self-enrollment at refuges, reducing demonstrated harm reduction and jeopardizing the Month 4 (2027-02-08) scale release of €1.5M.

Best Case Scenario: A current, verified directory with 50+ confirmed partner contacts enables rapid, parallel partner engagement from Month 0 (2026-10-08). GDPR compliance is pre-cleared via legal review of existing consent frameworks, accelerating MOU signature by Month 1 (2026-11-08). Outreach targets and partner capacity are realistic, lowering mid-season fatigue and dropout. Mapping of existing data-sharing agreements avoids consent redundancy and builds on established trust. Cooling-refuge sites are pre-verified for accessibility and facility readiness, eliminating remediation delays. Migrant organizations are identified and briefed early, enabling 8-12 community ambassadors to be recruited, vetted and trained by Month 2 (2026-12-08), supporting language-access targets. Faith-leader networks accelerate trusted-messenger recruitment. By Month 4 (2027-02-08), 3,000+ high-risk residents are enrolled and 60%+ are contacted, gates are met, and the program scales with credibility across EU peer cities.

Fallback Alternative Approaches:

• If municipal registry is outdated or incomplete, conduct rapid community canvas by Month 0.5 (2026-10-23): partner liaison officer and 2-3 community volunteers visit neighborhoods, query libraries, pharmacies, post offices, markets and faith centers by phone and in-person to build a current contact list. Budget: €3k-5k; timeline: 2-3 weeks.
• If formal social-services registry is unavailable, request the municipal integration officer or health department to provide names and phone numbers of known social organizations and programs; cross-check against online directories (Plataforma del Voluntariado de España, regional NGO databases, Linkedin searches for organization staff).
• If housing-association data is fragmented across municipal housing authority and regional cooperatives, issue a formal information request (solicitud de acceso) by Month 0 (2026-10-08) to municipal housing authority and regional government housing office, with 10-day statutory response time.
• If faith-organization contacts are weak, contact the Castellón archdiocese, the regional Islamic Federation (FEERI), and municipal religious affairs office for list of registered congregations and their social-outreach leaders; follow with phone verification of active programs.
• If migrant-community organizations are sparse in the directory, engage the municipal integration office (oficina de inmigración) or regional integration authority to request names and contacts of established migrant associations; cross-check census data on non-Spanish speakers by neighborhood to identify likely locations for targeting outreach.
• If partner data-governance frameworks are unclear, conduct a rapid 30-minute legal screening call with GDPR counsel (Month 0.5 = 2026-10-23) to identify which partners likely have lawful bases (public-task welfare duties, existing client consent) and which require new consent; use findings to prioritize GDPR vetting.
• If partner outreach capacity is reported as uncertain or minimal, propose a small pilot engagement with 2-3 partners (e.g., one housing association, one NGO, one pharmacy chain) in Month 1 (2026-11-08) to test call volumes and success rates before scaling to all partners; adjust targets and recruitment based on pilot results.
• If accessibility or facility readiness data for proposed refuge sites is missing, conduct a rapid site survey by municipal facilities/accessibility officer and partner liaison officer in Month 1 (2026-11-08): checklist inspection (ramps, toilets, water, AED, parking) of each proposed site, documented with photos and remediation cost estimates; drop or defer sites requiring >€10k remediation or >4 weeks work (per threshold).
• If cooling-refuge sites prove inadequate after survey, activate contingency site list (e.g., larger malls with seasonal tenants, municipal sports halls with off-season availability, temporary modular cooling units if budget allows); re-plan network footprint by Month 1.5 (2026-11-23).
• If the directory cannot be completed by Month 0.5 (2026-10-23), proceed with identified partners (50-70% of initial target) by Month 1 (2026-11-08) and backfill additional partners by Month 2 (2026-12-08); accept a 5-10% reduction in enrolled-resident target and geo-coverage to avoid delaying GDPR vetting and partner engagement.

Find Document 8: Cooling Kit Suppliers & Availability (Exterior Shading, Reflective Blinds, Fans, Thermometers)

ID: 5e244756-36a0-4a28-a693-3aeede639bd9

Description: Supplier market survey for home-kit components: manufacturers or distributors of exterior shading/blinds, window fans, digital thermometers, and hygrometers available in Spain or Europe; unit costs, minimum order quantities, lead times (weeks to delivery), expedite options, and product specifications (quality, durability, safety standards for fans). Used to finalize kit procurement specifications and budget, and to validate whether €800k is sufficient for 2,000 homes.

Recency Requirement: Current pricing & availability (2024-2025); valid for 2-3 months lead time.

Responsible Role Type: Home Interventions and Handyperson Coordinator

Steps to Find:

• Conduct online search for EU/Spanish suppliers of: exterior aluminum blinds/shading (e.g., Bandalux, Gradus, Hunter Douglas, or local Spanish brands), reflective window treatments, directional window fans (6-8 inch, safe for elderly use), and digital thermometer/hygrometer kits.
• Request quotes from ≥3 suppliers per component (shading, blinds, fans, thermometers) for bulk orders (600-2,000 units); specify quality standards (safety, durability), lead time, and per-unit cost.
• Check if municipal procurement framework agreements already exist for energy-efficiency or home-improvement kits; may allow faster ordering.
• Request lead-time and expedite-cost information for Q1-Q2 2027 (Feb-May 2027) delivery to align with project schedule.
• Inquire about bulk discounts, payment terms, and product warranties.

Access Difficulty: Medium. Supplier information is available online or via direct contact; competition is moderate. Pricing varies by supplier, quality, and order size; multiple quotes are essential for cost validation.

Essential Information:

• Identify supplier options for exterior aluminum shading/blinds (e.g., Bandalux, Gradus, Hunter Douglas, local Spanish brands) with unit costs, minimum order quantities and lead times (weeks to delivery) for bulk orders (600–2,000 units).
• Confirm availability and lead times for 6–8 inch directional window fans safe for elderly use, with safety certifications (CE, UL or equivalent) and durability specifications.
• List digital thermometer/hygrometer kits suitable for distributed placement; specify accuracy, display readability for vision-impaired users and battery life.
• Obtain quotes from ≥3 suppliers per component (shading, blinds, fans, thermometers); compare per-unit cost, bulk discounts, payment terms and product warranties.
• Verify whether municipal procurement framework agreements already exist for energy-efficiency or home-improvement kits that could accelerate ordering.
• Confirm expedite-cost premium (% markup) and feasibility of Q1–Q2 2027 delivery (February–May 2027) to align with project home-installation schedule.
• Validate whether €300 per-home cost assumption (€250 hardware + €50 installation labour) is achievable under current market conditions or requires adjustment.
• Identify backup suppliers (2–3 per category) to mitigate single-source delay risk, with lead times and alternative product specifications.

Risks of Poor Quality:

• Supplier quotes not obtained by Month 0.8 (2026-11-01) delay first call-off order to after Month 1.5 (2026-11-23), pushing 40–50% kit delivery past Month 4 (2027-02-08) and home installations beyond May–June peak-risk season; estimated delay 4–8 weeks and lost mortality protection.
• Inaccurate cost data (e.g., suppliers quoting higher per-unit prices than budget assumed) reveals a shortfall in the €800k home-kit allocation mid-procurement, forcing cuts to kit quantity (500–1,000 fewer homes) or quality, or triggering budget reallocation that defunds transport or outreach.
• Supplier lead times longer than 4–6 weeks (e.g., 8–10 weeks from Asian supply-chain issues) make February delivery impossible without expensive expedite premiums (10–15%, €50k–100k estimate), exhausting contingency reserve.
• Fan products lacking proper safety certifications or durability for Mediterranean climate (e.g., corrosion in salt air) lead to resident safety incidents, liability claims or equipment failures mid-season requiring replacement.
• No identified backup suppliers means a single-source production delay or supplier bankruptcy forces abandonment of that component or sourcing at emergency premium costs.
• Missing framework agreement research causes re-procurement from scratch using slower competitive tendering, delaying orders by 3–4 weeks and missing the Month 2 (2026-12-08) readiness gate.

Worst Case Scenario: Supplier availability survey is delayed or returns inadequate data (no confirmed quotes, lead times >8 weeks, per-unit costs 20–30% higher than budgeted). The project cannot place first call-off orders by Month 1.2 (2026-11-14) and misses the Month 2 (2026-12-08) readiness gate procurement deadline. Home kits do not arrive until May–June at earliest, leaving no time for installation before summer peak-heat season (Months 6.8–11.8 = 2027-05-08 to 2027-10-08). Project is forced to cut kit scope from 2,000 homes to <1,000 or abandon home interventions entirely, reducing estimated mortality protection by 15–25% and failing to meet equity targets for top-floor and social-housing priority units. Budget shortfall of €100k–200k forces cuts to transport retainer or outreach staffing, jeopardizing the Month 4 (2027-02-08) gates and credibility of the pilot.

Best Case Scenario: Supplier survey identifies 3–4 competitive suppliers per component by Month 0.8 (2026-11-01) with per-unit costs within or below budget (€250 hardware), lead times 4–6 weeks, and established frameworks or bulk-discount terms. First call-off order for 600–800 kits (30–40% of 2,000) placed by Month 1.2 (2026-11-14) with expedite delivery to February; 40–50% stock in place by Month 4 (2027-02-08) allows installation pipeline to reach 80% completion by Month 7.3 (2027-05-17), covering 1,600 homes before and during peak summer heat. Backup suppliers identified and pre-qualified reduce single-source risk. Full-scale home-intervention coverage meets equity targets for top-floor and social-housing priority units. Cost savings from early competitive bidding preserve €50k–100k of contingency for other risks.

Fallback Alternative Approaches:

• If lead times >6 weeks: negotiate expedite fees (10–15% premium, €50k–100k estimate) with top 2–3 suppliers for February delivery to maintain timeline; absorb cost within the €800k home-kit budget or draw from contingency.
• If per-unit costs 15–20% above budget: reduce target kit quantity from 2,000 to 1,500–1,700 homes, prioritizing top-floor and social-housing units; scale lower without proportionally reducing installation quality.
• If preferred suppliers unavailable or backlogged: activate 2–3 pre-identified backup suppliers by Month 0.8 (2026-11-01) and conduct parallel procurement (split order across suppliers) to diversify risk and ensure volume.
• If municipal frameworks do not exist: conduct a fast competitive tender in two lots (shading/blinds in one lot, fans/thermometers in another) by Month 1 (2026-11-08), with 2-week turnaround to place orders by Month 1.5 (2026-11-23).
• If installation costs higher than €50/unit: negotiate fixed-price handyperson contracts by Month 1.5 (2026-11-23) or train municipal or volunteer installers (2–3 week ramp) to reduce labour cost.
• If no home kits available by April: defer non-priority (lower-scoring rubric) installations to Year 2 or shift to a seasonal lending scheme (May install, September collection) to stretch existing stock across multiple summers and reduce upfront procurement burden.

Strengths

• Established practice: heat action plans, refuges and welfare checks are proven, giving low novelty risk.
• Existing municipal assets (libraries, community centers, parish halls) allow about 10 refuge sites (~400 places) without construction.
• Intermediary-held lists keep personal data with trusted partners, lowering GDPR exposure and reaching offline residents.
• Mayoral-level command with a public-health deputy speeds cross-department approvals and procurement.
• Disciplined design: a tiered alert ladder (Level 1 advisory) limits alert fatigue, explicit gates and a €280k contingency (8%).
• Strong NGO networks and a nearby university (Valencia) support outreach, language access and evaluation.

Weaknesses

• KILLER APPLICATION MISSING: no single compelling flagship use-case yet exists that makes residents, partners and other cities adopt the model. The plan is a bundle of seven workstreams, so the value proposition is diffuse and hard to communicate or scale.
• Month 2 (2026-12-08) and Month 4 (2027-02-08) gates fall in the cool season, so evidence rests on drills, which funders may see as weaker.
• Hard critical path: procurement, hiring (43 peak FTE) and vetting of ≥20 volunteers all compress into Months 0-2 (2026-10-08 to 2026-12-08).
• Baseline data (80-120 EMS calls, 15-25 excess deaths, provisional estimates) is unverified, and small-area counts are noisy.
• Contingency (€280k) cannot cover both the taxi-only fallback and a delayed release (exposure €350-650k, estimate).
• No identified funding for Year 2 (≈€2.3M/year, estimate).
• Opt-in/intermediary reach: 3,000 enrolled residents is ≈9% of 65+ (estimate), leaving most at-risk people unreached.

Opportunities

• Develop a killer application: a 'Hot Night Guarantee' for enrolled high-risk residents. Any Level 2-3 alert triggers a trusted-person call within a set time, a ride to a refuge within 45 minutes, and a fitted cool home. One simple promise could drive enrollment, trust and funder interest. Obstacles: it depends on volunteer and taxi capacity, partner call capacity, GDPR-limited reach, a cool-season launch, and a promise that must be kept at surge.
• Use the 2,000 home kits (rubric-scored) as a visible, tangible benefit that supports enrollment.
• Learn from Barcelona's refuge network and Paris's registry protocols, and from Ahmedabad's tiered alerts and evaluation.
• Publish a reusable playbook and cost model (€/center-hour, €/trip, €/enrollee) to attract EU funding for scaling.
• Use trusted messengers (pharmacists, GPs, caretakers, faith leaders) and ambassadors to build trust and referrals.
• Local data from the first season can calibrate alert thresholds for Year 2.

Threats

• Cool June-July weather could leave the gates untestable, delaying the €1.5M and causing a €200-400k cash gap (estimate).
• Supply-chain slippage of 4-8 weeks could push kit installation past the first heat events.
• Volunteer shortfall could push pickup times above 45 minutes or force taxi-only operation (+€150-250k).
• GDPR challenge or partner withdrawal could cut outreach reach by 10-25%.
• Reputational damage from an incident at a refuge, an outreach assault or a failed response under media attention.
• Staff fatigue and surge in multi-day heat waves could cut service 10-25%.
• Misinformation (alcohol, fan misuse) and weak trust among migrants.
• Political turnover or competing crises could weaken incident command.

Recommendations

• Month 0-1 (2026-10-08 to 2026-11-08): Incident commander and communications lead define the 'Hot Night Guarantee' (call, ride, cool home) as the flagship offer. Test its wording with focus groups by Month 1 (2026-11-08).
• Month 1 (2026-11-08): Procurement lead issues specs by Month 0.8 (2026-11-01), places the first 30-40% kit call-off at Month 1.2 (2026-11-14) and signs the taxi retainer (cap €80k), with 2-3 backup suppliers per category.
• Month 0.5-1.5: Legal counsel and partner liaison officer obtain the GDPR opinion (Month 1 = 2026-11-08) and sign partner DPAs (Month 1.5 = 2026-11-23).
• Month 0-3 (2026-10-08 to 2027-01-08): HR coordinator and volunteer lead recruit in fortnightly cohorts, with ≥20 vetted by Month 2 (2026-12-08). If fewer than 20 are in the pipeline at Month 1.5 (2026-11-23), scale the retainer.
• Month 2.5-4: Operations lead finalizes the drill protocol (Month 2.5 = 2026-12-23), runs the full-system drill (Month 3.2 = 2027-01-14) and closes after-action items by Month 3.9 (2027-02-04). The funder is briefed on the 50% partial-release rule.
• Month 2-7 (2026-12-08 to 2027-05-08): Health deputy and university partner agree EMS/ED coding and a pre-specified evaluation protocol. They also identify a Year-2 funding source by Month 9 (2027-07-08).

Strategic Objectives

• Pass the Month 2 (2026-12-08) readiness gate: ≥8 of 10 refuge sites signed, ≥50% of places accessible, retainer signed, ≥20 volunteers vetted, and 100% of tranche-1 orders placed.
• Pass the Month 4 (2027-02-08) scale gate: ≥80% of planned refuge hours delivered in the drill, ≥60% contact success from ≥300 attempts, mean pickup <45 min over ≥30 requests, and all after-action items closed.
• Enroll 3,000 high-risk residents by Month 7 (2027-05-08), with ≥5% of outreach calls in non-official languages.
• Install kits in 2,000 homes (rubric score ≥60) by Month 7.3 (2027-05-17), with 10-20% of installs inspected.
• By Month 12 (2027-10-08), deliver the playbook, cost model, evaluation report and a Year-2 roadmap with an identified funding source.

Assumptions

• Castellón de la Plana (~170k residents) is the pilot site; population estimates (65+ ≈34,000) are unverified.
• Baseline of 80-120 EMS calls and 15-25 excess deaths per summer is provisional.
• Alert thresholds (≥33°C/20°C advisory; ≥35°C/22°C alert) are proposed and will be reviewed after the first season.
• The funder accepts drill evidence for the Month 4 (2027-02-08) gate and the 50% partial-release rule.
• No new legislation is needed, and the mayor signs the delegation of authority by Month 1 (2026-11-08).
• The budget is 100% grant-financed, with no revenue.

Missing Information

• Verified local EMS, ED and mortality history, and heat coding practice.
• Recruitment evidence for volunteer drivers and taxi retainer quotes.
• Partner call-center capacity and lawful basis confirmed by counsel (AEPD view).
• Resident research on what offer would drive enrollment (killer-app validation).
• Accessibility audit results for candidate sites.
• Funder's written position on drill-based gates.
• Year-2 funding source.
• Local migrant language mix, to be confirmed Month 0 (2026-10-08).

Questions

• Which single promise to residents would make an isolated 75-year-old enroll, and can the city keep it on its worst day?
• Is the 45-minute pickup target realistic for wheelchair users with 40 volunteers and a capped €80k retainer?
• What happens if the funder rejects drill evidence at Month 4 (2027-02-08), and can the €160k tranche-1 contingency cover the gap?
• Does the intermediary-list model reach the most isolated residents, or does it mainly reach people already known to services?
• Who funds Year 2, and which components would be cut if funding is only partial?

Roles Needed & Example People

Roles

1. Heat Response Incident Commander

Contract Type: full_time_employee

Contract Type Justification: Incident Commander must maintain continuous authority and institutional knowledge across a 12-month program with critical decision points at Months 2 and 4 (2026-12-08, 2027-02-08). This role drives daily governance, procurement approvals, and cross-department coordination throughout setup and operational phases. Political accountability and delegation-of-authority requirements demand a stable, authorized municipal officer, not a contractor or temporary arrangement.

Explanation: Serves as the single point of authority for all alert declarations, operational decisions and cross-department coordination. Resides in or is delegated from the mayor's office, with a public-health deputy. Declares alerts, authorizes spending per tier, chairs daily SITREPs, and is accountable to the city for all response actions. Essential for speed, clarity and political legitimacy during real or simulated heat events.

Consequences: Without clear, single-authority incident command, alert declarations will be delayed or contested across departments. Cross-department orders may conflict. Procurement approvals will stall. Political accountability will blur, inviting media scrutiny if a response fails. The city will fail to meet the Month 2 (2026-12-08) readiness gate (incident command authority signed and operational).

People Count: 1 primary incident commander (mayor's office or delegated) + 1 deputy (public health) = 2 total. The deputy must be capable of full authority if the primary is unavailable.

Typical Activities: Declares heat alerts based on forecast thresholds within 1 hour of trigger; chairs daily SITREPs at 08:30 during alerts; authorizes spending per alert tier and resolves disputes between departments (e.g., cooling-center hours vs. budget); signs incident-command delegation letters and updates authorities if unavailable; reviews daily aggregate EMS/ED counts and escalates if volume exceeds thresholds; signs off on after-action reports and gate assessments; maintains continuity briefings with successor if political transitions occur.

Background Story: María José García Ribera, 58, from Valencia, is a seasoned municipal administrator with 22 years in city government, including 8 years managing civil-protection responses to flooding and industrial incidents. She holds a degree in public administration and an executive qualification in emergency management. For the past 3 years, she has advised the mayor's office on resilience and sustainability. Her familiarity with heat-response protocols is limited but her authority to coordinate cross-department action is established; the mayor has explicitly delegated heat-alert declaration to her with written authority. She is known for decisive, evidence-based decision-making under time pressure.

Equipment Needs: Computer with dual monitors and secure municipal network access; secure phone line and encrypted mobile device; incident-command software or shared access to alert tracking spreadsheet; audio-video conferencing system for daily SITREPs (08:30 briefings across departments); municipal authorization letter and delegation documentation (signed, filed); weather alert feed direct from national meteorological service (AEMET); real-time EMS/ED aggregate data dashboard (view-only secure access); alert-declaration templates and checklist documents.

Facility Needs: Private office at mayor's office or civil protection HQ with 24-hour access during Months 6–11 (2027-04-08 to 2027-09-08); desk, phone and network connectivity; backup command-post facility (civil protection or health department) with same connectivity in case primary office is unavailable; secure meeting room for daily SITREPs (10–12 person capacity, AV equipment); access to municipal procurement and budget-authority systems.

2. Cooling Center Network Manager

Contract Type: full_time_employee

Contract Type Justification: Cooling Center Network Manager must contract sites, conduct accessibility audits, oversee staffing, and ensure 80% planned-hours delivery at the Month 4 gate (2027-02-08). This is continuous core accountability from Month 0 (2026-10-08) through Month 12 (2027-10-08), with front-loaded site-contracting work (Months 0–2 = 2026-10-08 to 2026-12-08) and sustained operational oversight during the season (Months 6–11 = 2027-04-08 to 2027-09-08). Staffing and safety protocols at 10 sites require institutional knowledge and real-time decision-making that only a full-time dedicated manager can deliver.

Explanation: Owns the end-to-end delivery of the 10-site cooling refuge network: facility contracting, accessibility audits, staffing oversight, scheduling of opening hours by alert level, safety protocols (first-aid, AED, escalation), and utilization reporting. Ensures 80% of planned center-hours are delivered and ≥50% of places are fully accessible. Reports daily occupancy and any incidents to incident command during alerts.

Consequences: Without a single center manager, site contracting and accessibility will slip past the Month 2 (2026-12-08) gate. Staffing will be uncoordinated; openings will miss scheduled hours. The 80% planned-hours gate (Month 4 = 2027-02-08) will fail. Residents will arrive at closed or over-capacity sites, harming credibility and equity.

People Count: 1 center network manager (full-time, Months 0-12 = 2026-10-08 to 2027-10-08). Plus 18 FTE part-time center staff (14 core + 4 reserve) across 10 sites, hired in cohorts during Months 3-5 (2027-01-08 to 2027-03-08).

Typical Activities: Identifies and audits 10 cooling-center sites (libraries, community centers, parish halls) for accessibility (wheelchair ramps, water points, accessible toilets, quiet rooms); contracts facility-use MOUs specifying hours and staffing responsibility; hires and onboards 18 part-time center staff in cohorts; publishes center accessibility information (routes, toilets, parking) in plain language; ensures ≥1 first-aid-certified staffer and AED per site; schedules opening hours by alert level (10:00–20:00 at Level 2, 24-hour at Level 3); reports daily occupancy, staffing and incidents to command.

Background Story: Ricardo Martínez López, 45, from Castellón, holds a degree in architecture and has managed municipal facilities for 15 years, including libraries and community centers. He has overseen accessibility audits for disability compliance and has experience contracting maintenance and security services. His knowledge of heat-response infrastructure is new; he attended a 2-day climate-resilience training in Barcelona in 2024. He is detail-oriented, process-driven and skilled at managing relationships with external facility managers and contractors. He speaks Spanish and Valencian fluently.

Equipment Needs: Site-inspection checklist forms (printable, wheel-measure for distances, camera); accessibility audit tool (wheelchair-simulation, bathroom-door-width gauge, step height measure); first-aid certification tracking spreadsheet; AED procurement specifications and maintenance contracts; staffing rota software or shared spreadsheet; cooling-center occupancy/incident-reporting forms; communication devices (mobile phone, landline at office); cooling-center signage templates (printed, large-format for accessibility).

Facility Needs: Office space (0.5-desk footprint) at municipal facilities department or city hall; internet access and phone line; secure storage for site-audit documentation and facility contracts; access to all 10 cooling-center sites for inspections (transport/vehicle or reimbursement); meeting space at each site for handover briefings with facility managers (10 visits, ~2 hours each); access to municipal procurement and facilities-management systems.

3. Transport Dispatch and Mobility Coordinator

Contract Type: full_time_employee

Contract Type Justification: Transport Dispatch and Mobility Coordinator must recruit, vet and manage 30–50 volunteer drivers (4–8 week vetting process), negotiate and manage a taxi standby-retainer contract, and operate dispatch during peak alert-day demand. This role spans continuous procurement and safeguarding accountability (Months 0–4 = 2026-10-08 to 2027-02-08) and sustained operational leadership (Months 5–12 = 2027-03-08 to 2027-10-08). The 45-minute transport-time gate (Month 4 = 2027-02-08) depends on this coordinator's ability to execute complex multi-vendor coordination and volunteer-management infrastructure that cannot be built or maintained part-time.

Explanation: Recruits, vets and schedules volunteer drivers (target 40); manages the taxi standby-retainer contract; operates the transport dispatch center during alert days; coordinates with cooling centers on occupancy; tracks request-to-pickup time and escalates delays. Ensures mean pickup time <45 minutes and 100% of transport requests are attempted. Responsible for safeguarding vetting (background checks, insurance, training) and volunteer driver retention.

Consequences: Without a dedicated coordinator, volunteer recruitment will stall and vetting will not be completed by Month 2 (2026-12-08). Taxi retainers will be unsigned or unmanaged. Dispatch will lack capacity during peak alert days, causing wait times to exceed 45 minutes and the transport-time gate to fail. Safeguarding breaches are more likely if vetting is weak or decentralized.

People Count: 1 mobility coordinator (full-time, Months 0-12 = 2026-10-08 to 2027-10-08) + 2 dispatch operators (alert-day hours, May-September, ~40% FTE seasonal) + 1 backup coordinator (standby, ~20% FTE). Total 1.6 FTE equivalent. Plus volunteer driver recruitment support from Month 0 (2026-10-08) and taxi/paratransit vendor management.

Typical Activities: Recruits and vets 30–50 volunteer drivers via NGO networks and community outreach; conducts background checks, insurance verification and safeguarding training (4–8 weeks per cohort); manages a taxi standby-retainer contract with 2–3 suppliers; coordinates with dispatch operators to log transport requests, assign drivers and track time-to-pickup; escalates delays >45 minutes and reallocates drivers dynamically; conducts transport stress tests and drills; maintains volunteer driver rota and substitute coverage; reports mean pickup time and request-fulfillment rates daily during alerts.

Background Story: Ahmed Hassan El-Sayed, 52, originally from Egypt, settled in Valencia 18 years ago and holds Spanish citizenship. He has 20 years of experience in transportation and logistics, including fleet management for a taxi cooperative. He is fluent in Spanish, Valencian, Arabic and English. He has no formal training in heat response but has worked with vulnerable populations through volunteer ambulance-driver roles. He is known for reliability, problem-solving and an ability to build trust with drivers and community partners. He understands insurance requirements and background-check processes.

Equipment Needs: Transport dispatch software (spreadsheet or low-code platform) with real-time visibility to volunteer-driver location, transport requests, and arrival times; secure phone and mobile radio system for dispatchers; volunteer-driver insurance and vetting database (secure spreadsheet or minimal HR system); driver scheduling/rota software; stress-test scenario protocols and timing tools; transport-contract templates and vendor-management files; safeguarding incident-reporting forms.

Facility Needs: Dedicated dispatch office or workstation (3 FTE: 2 operators + 1 backup/coordinator) with dual monitors per operator; 24-hour phone line and mobile coverage; secure climate-controlled facility for volunteer-driver records (vetting, insurance); meeting space for volunteer-driver training (20–30 person capacity, 4-hour sessions, fortnightly cohorts Months 0–2 = 2026-10-08 to 2026-12-08); fleet-staging area or parking for volunteer vehicles pre-positioned on alert days; access to municipal vehicle insurance and background-check processes.

4. Outreach and Street Contact Lead

Contract Type: full_time_employee

Contract Type Justification: Outreach and Street Contact Lead must design outreach protocols, partner with 4–6 intermediary organizations, conduct escalation training for 25–35 staff, and manage the 60% contact-success gate (Month 4 = 2027-02-08). This role requires continuous engagement with partners, design iteration based on early feedback, and real-time monitoring during alert days. The scope spans governance (MOUs, training), operations (contact tracking, escalation), and equity (reach monitoring), all of which demand a full-time institution-facing role, not episodic consulting.

Explanation: Designs and deploys door-knock and street-contact protocols for high-risk residents. Works with housing associations, social services, NGOs and pharmacies to conduct phone and in-person outreach; manages a 'no wrong door' enrollment pathway via the heat line and in-person at cooling centers. Owns heat-illness escalation training for outreach staff, safety protocols for street-contact teams, and monitoring of the 60% contact-success gate. Reports daily outreach metrics to command during alerts.

Consequences: Without dedicated outreach leadership, intermediary partners (housing associations, NGOs, social services) will operate inconsistently or not at all. Contact success will fall below 60%, failing the Month 4 (2027-02-08) gate. Unhoused residents will be missed entirely if street-contact protocols are not designed. Escalation training will not occur, increasing risk of delayed EMS calls during heat illness.

People Count: 1 outreach lead (full-time, Months 0-12 = 2026-10-08 to 2027-10-08) + 6 FTE outreach staff (door-knock teams, phone check-in staff, street-contact coordinators) hired in Months 3-5 (2027-01-08 to 2027-03-08). Plus partner-coordination roles split with the partner-liaison officer.

Typical Activities: Co-designs heat-illness escalation checklists with clinical staff for outreach teams; partners with housing associations, social services and NGOs to establish call protocols and contact targets (300+ attempts/alert day); trains 25–35 outreach and street-contact staff on heat-illness recognition, de-escalation and escalation rules (test ≥80%); monitors daily contact attempts and success rates via shared tracking spreadsheet; conducts mid-season partner reviews to resolve capacity gaps; escalates if contact success drops below 60%; tracks reach by neighborhood deprivation, age and language; manages the no-wrong-door enrollment pathway via the heat line and in-person centers.

Background Story: Laura Fernández Serrano, 41, from Alicante, holds a master's degree in public health and has 14 years in municipal social services, including 6 years managing outreach to homeless and isolated elderly residents. She speaks Spanish, Valencian and English and has led successful enrollment campaigns for municipal health programs (reach 70–80% of target populations). Her experience with GDPR compliance is intermediate; she has managed confidentiality protocols for social-services client lists. She is experienced in motivating partner organizations and resolving conflicts over data-sharing and accountability.

Equipment Needs: Heat-illness escalation checklist (printed, laminated for outreach staff); phone triage protocols and decision-tree documents; partner-contact database (contact names, phone, email for housing associations, social services, NGOs, pharmacies); call-script templates (printed, translated); shared outreach-tracking spreadsheet (secure, visible to partners and city); training materials (slide decks, role-play scenarios); escalation phone numbers (112, nurse line, poison control); outreach incident-reporting forms; no-wrong-door enrollment intake forms (paper and digital).

Facility Needs: Office (1 FTE) at social services or outreach-coordination hub with phone, email and secure internet; meeting space for partner coordination (6–8 person capacity, Months 1–2 = 2026-11-08 to 2026-12-08 weekly); training facility (30–40 person capacity) for outreach and street-contact staff training (80 hours total, Months 1–2 = 2026-11-08 to 2026-12-08); access to municipal GP, pharmacy and NGO partner offices for joint briefings; secure storage for outreach escalation protocols and incident logs.

5. Heat Helpline and Phone Operations Manager

Contract Type: part_time_employee

Contract Type Justification: Heat Helpline and Phone Operations Manager can operate effectively as a part-time employee (0.5 FTE Months 1–12 = 2026-11-08 to 2027-10-08) because the phone line itself is mostly inactive (10–15 alert days per summer of 120 days peak season ≈ 12% utilization). The manager role is to build and maintain the system before Months 5–8 (2027-03-08 to 2027-06-08), then supervise reactive operations during alerts. Administrative setup dominates Months 1–4 (2026-11-08 to 2027-02-08); operational intensity is episodic, not continuous.

Explanation: Establishes and operates the heat-alert phone line (08:00-22:00 daily, 24-hour at Level 3); integrates phone intake with transport dispatch and cooling-center occupancy; trains phone operators on escalation protocols and multilingual service; manages call logging and escalation tracking. Ensures phone line is live and responsive by Month 2 (2026-12-08) readiness gate.

Consequences: Without a dedicated phone manager, the heat line will open late (missing the Month 2 = 2026-12-08 gate) or will operate at poor quality (long wait times, misrouted requests). Callers will not be connected to transport dispatch or cooling-center availability in real-time. The shared tracking system will not be built or maintained, causing dispatch/center coordination failures during peak alert demand.

People Count: 1 phone operations manager (part-time, ~0.5 FTE, Months 1-12 = 2026-11-08 to 2027-10-08) + 2-3 part-time phone operators (30 hours/week during alert season, ~0.75 FTE each, May-September) + 1 backup operator (on-call). Total 2.75-3.25 FTE seasonal equivalent.

Typical Activities: Establishes and operates the heat-alert helpline (08:00–22:00 daily, 24 hours on Level 3 days); hires and trains 2–3 part-time phone operators in heat-illness escalation, cooling-center locations and multilingual service; integrates phone intake with transport dispatch and center occupancy via a shared real-time spreadsheet; logs caller details (transport request, center preference, language) and confirms pickup time and center availability within 15 minutes; updates center occupancy every 30 minutes during alerts; conducts monthly call-quality audits; tracks wait times and call volume by alert level.

Background Story: Susana Ruiz Gómez, 38, from Castellón, holds a degree in business administration and has 12 years' experience running a municipal health-information line. She has managed call centers, trained phone operators in customer service and de-escalation, and set up shared tracking systems using spreadsheets and simple cloud tools. Her heat-response knowledge is minimal; she attended a half-day orientation on heat illness. She is calm under pressure, detail-oriented about protocol compliance and skilled at managing operator fatigue and quality during long shifts.

Equipment Needs: Phone-line equipment (dedicated number, answering system, call-recording for quality assurance); heat-helpline intake form (digital and printable); call-tracking spreadsheet (shared with dispatch and cooling centers in real-time); phone operator scripts and checklists (cooling-center locations, transport request workflow, escalation rules); cooling-center occupancy update forms (for centers to phone in every 30 min during alerts); multi-language phone-tree menus and automated prompts (Spanish, Valencian, Arabic, Portuguese, etc.); interpreter scheduling system; quality-monitoring and call-time-tracking logs.

Facility Needs: Dedicated phone-line operations space (2–3 operator workstations with headsets and dual monitors); climate-controlled office with 24-hour access during Months 5–11 (2027-03-08 to 2027-09-08); high-quality phone and internet connectivity (redundant line for backup); secure storage for call recordings and daily logs (confidential per data-protection rules); meeting space for operator training (8–10 person capacity, 4-hour sessions, Months 1–2 = 2026-11-08 to 2026-12-08 and monthly refreshers); access to municipal telephone and IT systems; contracted interpretation-service hub or on-call interpreter station.

6. Home Interventions and Handyperson Coordinator

Contract Type: full_time_employee

Contract Type Justification: Home Interventions and Handyperson Coordinator must manage a critical 4–5 month procurement and installation timeline (Months 0–7 = 2026-10-08 to 2027-05-08) with zero tolerance for supply-chain delays past February–April. This role owns €800k in kit budget, vetting and training of 10 handypersons, and meeting the implicit gate that 40–50% of kits are installed by Month 4 (2027-02-08). The compressed procurement schedule, backup-supplier vetting, quality audits and installation supervision demand continuous full-time focus. After Month 7 (2027-05-08), the workload drops to close-out; a full-time appointment supports peak-season intensity and reduces restarting cost if procurement slips.

Explanation: Procures cooling kits (shading, fans, blinds, thermometers, hydration supplies), manages the first-call supply chain and backup vendors, oversees handyperson recruitment and fan-safety training, schedules installations in priority homes (top-floor, social housing, by rubric score), conducts 10-20% quality audits of installs, and tracks installations against targets. Delivers first 40-50% of kits by Month 4 (2027-02-08) and 100% by Month 6 (2027-04-08).

Consequences: Without a kit coordinator, procurement will slip past February and home interventions will miss the May-June heat season (20-25% loss in estimated mortality reduction). Handyperson vetting and training will not happen, risking unsafe fan installations (fire hazard, misuse). Supplier delays will not be managed; backup vendors will not be pre-qualified. The €800k home-kit budget will be wasted if kits are not installed by June.

People Count: 1 home-kit coordinator (full-time, Months 0-12 = 2026-10-08 to 2027-10-08) + 10 handypersons/installers (contracted or part-time, Months 4-7 = 2027-02-08 to 2027-05-17) + 1 quality-assurance auditor (contract, 20% FTE). Total 12 FTE equivalent across the 12 months, concentrated Feb-May.

Typical Activities: Issues procurement specifications for cooling kits (shading material, reflective blinds, fans, thermometers, hygrometers) to suppliers; obtains quotes and lead-time confirmations; places first call-off order for 30–40% of kits by November 15; pre-qualifies 2–3 backup suppliers and signs backup agreements; negotiates expedited delivery premiums (10–15%); arranges interim storage at municipal facilities; hires 10 handypersons and conducts 2-hour fan-safety and installation-safety training; schedules installations in priority homes (top-floor, social housing) by rubric score; conducts spot-check quality audits of 10–20% of installations; tracks kit delivery, installations completed and budget spend weekly.

Background Story: Carlos Morera Tomás, 50, from Valencia, is a retired construction supervisor with 28 years' experience managing installations and safety on residential sites. He holds certifications in electrical safety and workplace health. His heat-response knowledge is new; he recently completed a 2-day online course on heat-illness first aid. He is pragmatic, cost-conscious and skilled at quality control and vendor management. He speaks Spanish and Valencian and has established relationships with local trade contractors and suppliers.

Equipment Needs: Kit procurement specifications and RFQ documents; supplier quotes and lead-time confirmations (spreadsheet); first call-off order contracts and backup-supplier agreements; expedited-delivery authorization and payment-processing forms; interim storage-facility management (inventory tracking, climate control, security); handyperson hiring and vetting records (background check, insurance, training certificates); fan-safety and installation-safety training materials (slide decks, videos, printed handouts); quality-assurance audit checklists; kit-delivery and installation-tracking spreadsheet; budget and spend-tracking by kit category.

Facility Needs: Office (1 FTE) at municipal procurement or public works with phone and email; secure storage facility (500–800 m² minimum, climate-controlled, lockable) for kit inventory during Months 2–6 (2026-12-08 to 2027-04-08); access to municipal procurement, contracts and payment systems; meeting space for handyperson vetting and training (15–20 person capacity, 2-hour sessions, Months 3–4 = 2027-01-08 to 2027-02-08); handyperson staging area or workshop for tool storage and kit assembly/checking before installation; access to supplier warehouses and delivery logistics (coordinate with municipal transport).

7. GDPR Compliance and Legal Officer

Contract Type: independent_contractor

Contract Type Justification: GDPR Compliance and Legal Officer can be delivered as an independent contractor (or hybrid: 0.5 FTE municipal staff + external specialist counsel). The role is expert-driven, bounded-scope legal work: template MOUs/DPAs (Months 0–2 = 2026-10-08 to 2026-12-08), partner briefings (Month 2 = 2026-12-08), and mid-season audit (Month 9 = 2027-07-08). Front-loaded deliverables (legal opinions by Month 1 = 2026-11-08) suit fixed-scope contracting. A dedicated municipal legal officer would underutilize during operations phases (Months 6–8 = 2027-04-08 to 2027-06-08). Specialist GDPR counsel (€15–30k contract) can be embedded; municipal support for partner engagement is 0.5 FTE (separate line item).

Explanation: Engages specialist GDPR counsel, oversees data-processing agreements (MOUs/DPAs) with all partner organizations (housing associations, social services, NGOs, pharmacies), ensures legal clearance for the intermediary-held-list model by Month 1 (2026-11-08), briefs partner staff on confidentiality and data-retention rules, and conducts mid-season GDPR audits. Protects the program from regulatory challenge and partner withdrawal.

Consequences: Without dedicated legal oversight, data-processing agreements will not be signed by Month 1.5 (2026-11-23), delaying partner engagement. Partner withdrawal due to perceived GDPR risk could drop outreach reach by 10-20%. A regulatory inquiry or resident data-protection complaint could halt operations mid-season and force retrospective remediation (€15-30k estimate). The program loses credibility and transferability to peer EU cities.

People Count: 1 GDPR/legal officer (0.5 FTE, Months 0-12 = 2026-10-08 to 2027-10-08), supported by an external specialist GDPR law firm (contract, ≤€30k). Officer must have EU data-protection knowledge or access to legal counsel.

Typical Activities: Engages specialist GDPR law firm for template data-processing agreements (MOUs/DPAs) with housing associations, social services, NGOs and pharmacies; reviews lawful basis for contact (public-task/consent hybrid), retention periods (one season, then deletion) and breach-notification rules; obtains written legal opinion confirming intermediary-held model compliance; briefs 50–80 partner staff on confidentiality and data-retention obligations before Month 2 (2026-12-08); conducts mid-season GDPR audit of partner consent records and training logs (Month 9 = 2027-07-08); escalates any suspected data breach to the data protection authority; drafts annual data-protection impact assessment (DPIA) summary if required.

Background Story: Isabel Montoya Riera, 43, from Barcelona, is a municipal legal adviser specializing in data protection and public procurement. She holds a master's degree in data protection law (GDPR focus) and has 10 years' experience drafting privacy notices, data-processing agreements and compliance audits. Her familiarity with heat-response law is zero; heat programs are outside her previous brief. She is meticulous, risk-aware and skilled at managing relationships with data protection authorities and external counsel. She speaks Spanish, Catalan and English.

Equipment Needs: GDPR legal templates (MOU/DPA drafts); data-processing agreement tracking spreadsheet; partner contact and signature documentation (secure files); partner-staff training attendance logs and confidentiality certification; consent-form templates (translated into 4–6 languages); data-retention and deletion schedules; breach-notification procedures and incident-reporting forms; audit checklists for partner compliance (consent records, staff training, data-handling); legal opinion documentation (signed, dated); communication letters to data protection authority (AEPD) if required.

Facility Needs: Office (0.5 FTE) at municipal legal department or health department with secure file storage and phone; external specialist GDPR law firm on retainer (contract €15k–30k, Months 0–2 = 2026-10-08 to 2026-12-08 intensive, then ad-hoc); meeting space for partner DPA signature sessions (6–8 partner organizations, 1–2 hours each, Month 1.5 = 2026-11-23); secure digital-signature or contract-management system (or secure email and filing); access to municipal data-protection register and AEPD contact information.

8. Communications, Language Access and Trusted Messenger Coordinator

Contract Type: full_time_employee

Contract Type Justification: Communications, Language Access and Trusted Messenger Coordinator must design multilingual messaging, recruit and train 8–12 community ambassadors, manage translation of 4–6 languages, and execute a pre-season campaign (Month 6 = 2027-04-08 launch) and misinformation correction (≤4 hours response time during alerts). This is continuous core accountability Months 0–12 (2026-10-08 to 2027-10-08), with sustained operational intensity during the communication-heavy period (Months 5–8 = 2027-03-08 to 2027-06-08). Ambassador recruitment, translation procurement, and campaign execution require full-time coordination; the role cannot be fragmented across part-time or episodic effort.

Explanation: Designs and executes the public communications strategy: pre-season campaign, heat-event messaging templates, myth-busting content, trusted-messenger briefings (pharmacists, GPs, caretakers, faith leaders), translation and interpretation services, and rapid misinformation correction (≤4 hours). Recruits and trains 8-12 paid community-language ambassadors. Ensures messages are accessible to offline, elderly and migrant residents. Reports media-monitoring and reach metrics to incident command.

Consequences: Without a dedicated coordinator, messages will not be translated into 4-6 local languages, excluding 5-15% of the population (estimated 500-1,500 residents in Castellón). Trusted messengers will not be briefed consistently, reducing uptake among offline and elderly residents. Misinformation (alcohol, fan misuse) will spread unchecked, causing unsafe behaviors and preventable heat illness. Public reach will drop by 10-20%, reducing enrollment and utilization by 500-2,000 residents.

People Count: 1 communications/language coordinator (full-time, Months 0-12 = 2026-10-08 to 2027-10-08) + 1 part-time communications officer or social-media monitor (10-15 hours/week during season, ~0.25 FTE) + 8-12 paid community-language ambassadors (10-15 hours/week during season, ~0.9 FTE equivalent). Total 2.15 FTE equivalent.

Typical Activities: Designs pre-season heat-safety campaign messaging (print, radio, SMS); focus-tests messages with older residents and migrants (Month 1 = 2026-11-08) to ensure clarity and cultural appropriateness; briefs trusted messengers (pharmacists, GPs, caretakers, faith leaders) with consistent scripts and leave-behind materials by Month 6 (2027-04-08); recruits and trains 8–12 paid community-language ambassadors to deliver messages in non-official languages during alert season; publishes alerts and public updates by 11:00 on Level 2–3 days; monitors social media and local forums for misinformation and responds with corrected facts within 4 hours; tracks message reach by demographic group and language; publishes translated door hangers, flyers and pictogram-first signage.

Background Story: Javier García Alonso, 47, from Castellón, holds a degree in journalism and has 18 years in municipal communications, including 8 years as communications director for the health department. He is fluent in Spanish and Valencian and has basic conversational skills in English. His heat-response communication experience is limited; he attended a 1-day workshop on climate-health messaging. He is creative, responsive to media inquiries and skilled at working with community leaders and NGO partners. He understands misinformation risk and social-media monitoring.

Equipment Needs: Pre-season campaign templates (radio scripts, poster graphics, flyer text, door-hanger designs, SMS templates); focus-group testing materials and feedback forms; trusted-messenger briefing packs (printed, translated, with role-play scenarios); community-language ambassador job descriptions, vetting forms and training materials; social-media monitoring dashboard (if available, or manual monitoring log); misinformation-correction fact-sheets (printed and digital); translation files for all key materials (4–6 languages); pictogram-based signage and instructional graphics (tested with non-literate users); media-contact list and press-release templates; campaign reach and demographic-tracking spreadsheet.

Facility Needs: Office (1 FTE) at municipal communications or health department with phone, email and design software (or contracted designer access); meeting space for focus-group testing (12–15 person capacity, Months 0–1 = 2026-10-08 to 2026-11-08); trusted-messenger briefing venues (pharmacies, GP practices, faith centers, caretaker offices) for in-person training (8–12 sessions, 2 hours each, Month 6 = 2027-04-08); translation contractor workspace or external language-service provider; social-media monitoring tools or log-management system; radio and print-media production contacts and submission processes; immigrant community center or NGO space for ambassador recruitment and training (20–30 person capacity, Months 2–4 = 2026-12-08 to 2027-02-08).

9. Project Coordination, PMO and Staffing Lead

Contract Type: full_time_employee

Contract Type Justification: Project Coordination, PMO and Staffing Lead must deliver compressed procurement by Month 2 (2026-12-08), hire and onboard 43 FTE seasonal staff in Months 3–5 (2027-01-08 to 2027-03-08), track budget and KPIs daily during operations, and manage contingency escalation. This is the critical-path role for both setup (Months 0–4 = 2026-10-08 to 2027-02-08) and operational oversight (Months 5–12 = 2027-03-08 to 2027-10-08). The role requires continuous presence, no-handoff ownership of timelines, and real-time decision-support for the incident commander. Procurement compression, hiring ramp, budget burn rate, and gate measurement all depend on a single dedicated PMO lead; splitting this role or using a contractor would fragment accountability and miss early-warning signals.

Explanation: Serves as the operational backbone: project management (timeline, milestones, budget tracking), HR/recruitment coordination (hiring, onboarding, shift rota, fatigue management), procurement administration (order placement, vendor management, delivery tracking), data and KPI reporting (daily/weekly metrics), and contingency management (risk monitoring, decision-trigger escalation). Owns Months 0-4 (2026-10-08 to 2027-02-08) compressed timeline; transitions to evaluation support by Month 8 (2027-06-08).

Consequences: Without a PMO lead, procurement will not meet Month 2 (2026-12-08) deadline, slipping delivery by 2-4 weeks. Hiring timelines will miss, leaving centers and dispatch under-staffed in May-June. Budget tracking will be poor, risking €200-400k overspend or mid-season funding crisis. Risk escalation will be slow, causing the Month 4 (2027-02-08) gate decision to be made without clear readiness data. The playbook will not be drafted on time by Month 12 (2027-10-08).

People Count: 1 project manager / PMO lead (full-time, Months 0-12 = 2026-10-08 to 2027-10-08) + 0.5 FTE HR/recruitment coordinator (Months 0-6 = 2026-10-08 to 2027-04-08, peak intensity Months 0-4 = 2026-10-08 to 2027-02-08) = 1.5 FTE equivalent.

Typical Activities: Creates and maintains project timeline and Gantt chart tracking procurement, hiring and key milestones against Month 2 (2026-12-08) and Month 4 (2027-02-08) gates; monitors budget spend by category weekly and reforecasts cash flow; coordinates recruitment of 43 FTE seasonal staff in cohorts (40% Month 3, 40 = 2027-01-08, 2030-02-08% Month 4, 20 = 2027-02-08, 2028-06-08% Month 5 = 2027-03-08); tracks procurement orders (placement date, supplier, delivery date, receipt confirmation); escalates risks (supply delays, hiring shortfalls, budget overruns) to incident command when decision trigger thresholds are crossed (e.g., <20 volunteers by Month 1.5 = 2026-11-23); produces gate readiness reports at Months 2 and 4 (2026-12-08, 2027-02-08) with corrective-action status; manages contingency budget reserve (€160k tranche 1, €120k tranche 2); transitions to playbook-support role from Month 8 (2027-06-08).

Background Story: Silvia Serrano Domínguez, 35, from Castellón, holds a degree in business administration and has 8 years' experience in municipal project management, including coordination of European-funded urban regeneration projects. She has managed procurement timelines, hiring workflows and budget tracking. Her heat-response knowledge is minimal; she volunteered on a 1-week climate adaptation project in 2023. She is organized, deadline-driven and skilled at cross-team coordination and risk escalation. She speaks Spanish, Valencian and English.

Equipment Needs: Project timeline/Gantt chart software (Excel, Asana, Monday.com, or similar); budget-tracking spreadsheet (by category and vendor); procurement order log (placement date, supplier, delivery date, receipt status); hiring and onboarding checklist (job descriptions, contracts, offer letters, orientation materials); risk register and decision-trigger log; gate-readiness report templates (Month 2 and 4 = 2026-12-08, 2027-02-08); KPI dashboard (center hours, transport time, outreach success, budget spend); contingency-fund authorization forms; staff absence and rota-tracking system; vendor-performance and payment-processing files.

Facility Needs: Office (1.5 FTE: 1 FTE PMO + 0.5 FTE HR coordinator, Months 0–6 = 2026-10-08 to 2027-04-08 intensive; then 1 FTE for M&E support Months 7–12 = 2027-05-08 to 2027-10-08) at municipal administration or health department; dual-monitor workstations with phone and email; access to municipal project-management, HR, procurement and budget systems; secure shared-drive or cloud workspace for all stakeholder documents (read access for incident commander, coordination team; write access for PMO); meeting space for weekly coordination-team touchbases (8–10 person capacity, Monday mornings, 1 hour); access to municipal HR records and payroll for seasonal-staff management; printing and document-scanning facilities for procurement and hiring files.

---

Omissions

1. No dedicated mental health or occupational health support for staff and volunteers exposed to distressing scenes or heat-illness incidents

Outreach, street-contact and cooling-center staff will regularly encounter residents in acute heat distress, potential heat stroke and vulnerable populations during multi-day heat waves. The risk register identifies psychological harm and staff turnover as operational risks, but the team structure lacks an occupational health coordinator or mental health liaison. This is critical for staff retention, reducing turnover costs (€10–20k per replacement) and maintaining service quality during peak-demand periods.

Recommendation: Designate a 0.25 FTE occupational health liaison (municipal occupational health service or contracted occupational health nurse) responsible for: (1) debriefing staff after any heat-illness incident or distressing scene; (2) coordinating access to counselling services within 24 hours at city expense; (3) training team leaders on fatigue-management and burnout-recognition; (4) monitoring staff absences and sick leave for patterns indicating psychological harm; (5) conducting peer-support group sessions monthly during alert season. Include occupational health review at Months 2, 6 and 10 (2026-12-08, 2027-04-08, 2027-08-08) to identify emerging mental-health risks early.

2. No dedicated data quality assurance or evaluation lead for rigorous gate measurement and attribution analysis

The Month 4 (2027-02-08) gates depend on accurate measurement of center-hour delivery, outreach contact success, and transport time. The plan includes an evaluation design framework but assigns no FTE to data management, validation or real-time quality assurance during operations. Without a dedicated data officer, metrics will be incomplete, noisy or inconsistent across partners, risking indefensible gate decisions and weak playbook credibility for other EU cities.

Recommendation: Assign a dedicated 1 FTE Data and Evaluation Coordinator (statistician or data analyst, Months 2–12 = 2026-12-08 to 2027-10-08) to: (1) validate baseline EMS/ED data by Month 1.5 (2026-11-23) and establish usable baseline by Month 3 (2027-01-08); (2) design and deploy real-time data collection forms for centers, transport, outreach and health partners; (3) conduct weekly data quality audits during operations (completeness, consistency, outlier flagging); (4) compute gate metrics (center hours, transport time, outreach success) by Month 3.9 (2027-02-04) with confidence intervals; (5) manage the evaluation database and prepare the Month 12 (2027-10-08) evaluation report. Link this role directly to incident command for daily KPI reporting during alerts.

3. No dedicated partner liaison and relationship manager for the 4–6 intermediary organizations and health system

The outreach model depends critically on housing associations, social services, NGOs, pharmacies and health providers maintaining engagement and consistent call-center capacity throughout the season. The plan mentions 'partner liaison officer' in stakeholder analysis but assigns no dedicated FTE; coordination is fragmented across outreach lead, GDPR officer and PMO. If a key partner faces capacity constraints or withdraws mid-season (15–20% risk), outreach reach could drop by 10–20%, failing the 60% contact-success gate.

Recommendation: Designate a dedicated 1 FTE Partner Liaison Officer (Months 0–12 = 2026-10-08 to 2027-10-08), reporting to the incident commander, to: (1) negotiate and sign MOUs with all 4–6 partner organizations by Month 1.5 (2026-11-23); (2) conduct joint quarterly planning meetings at Months 1, 4, 7, 10 (2026-11-08, 2027-02-08, 2027-05-08, 2027-08-08) to review capacity and resolve conflicts; (3) maintain monthly contact with each partner to monitor call volume, staff capacity and early-warning signals of withdrawal; (4) provide real-time feedback on outreach performance (success rates, wait times, escalations) to partners; (5) identify and brief backup partners by Month 2 (2026-12-08) in case a primary partner drops. This role is essential for the 60% contact gate and for equity reach tracking.

4. No capacity for policy learning and Year-2 planning within the core team structure

The plan requires delivery of a Year-2 roadmap by Month 12 (2027-10-08) recommending what to expand, what to stop and what to scale city-wide. This demands synthesis of lessons from operations, equity tracking, staff feedback and cost accounting. The playbook-and-evaluation officer role (0.5 FTE Months 9–12 = 2027-07-08 to 2027-10-08) is insufficient to simultaneously run end-of-season operations, draft the playbook, and conduct forward-looking policy analysis. Without dedicated capacity for reflection and planning, Year-2 roadmap will be rushed and will miss stakeholder input.

Recommendation: Add a 0.5 FTE Policy and Learning Officer (Months 8–12 = 2027-06-08 to 2027-10-08) working jointly with the PMO and evaluation lead to: (1) synthesize staff feedback, partner input and utilization data (Months 8–9 = 2027-06-08 to 2027-07-08); (2) conduct focus groups with high-risk residents about program experience (n=30–50, 2 groups, Month 9 = 2027-07-08); (3) cost out scenarios for Year-2 expansion (city-wide footprint, continued pilot, scale-back); (4) draft Year-2 roadmap with explicit go/no-go decisions for each service element (Months 10–11 = 2027-08-08 to 2027-09-08); (5) recommend budget and governance model for Year 2 (funder TBD). This role ensures transition from pilot to sustained program is informed, not reactive.

5. No dedicated quality assurance inspector for home-kit installation safety and building-code compliance

The plan includes 10 handypersons installing 2,000 cooling kits (exterior shading, fans) in homes during Months 4–7 (2027-02-08 to 2027-05-17). Safety checks (fan directional airflow, fire-hazard risk, building-code compliance) are mentioned in risk mitigation but no FTE is assigned to conduct them. A 10–20% audit rate (200–400 installs) requires ≥0.5 FTE site inspection capacity. Without dedicated inspection, unsafe installations or building-code violations could trigger enforcement action, litigation or media reputational damage.

Recommendation: Assign a 0.5 FTE Quality Assurance and Safety Inspector (municipal building inspector or contracted auditor, Months 4–7 = 2027-02-08 to 2027-05-17) to: (1) conduct spot-check inspections of 10–20% of home kit installations (prioritizing structural, fire and electrical safety); (2) verify handyperson certification and training records before installation begins; (3) issue corrective notices within 24 hours for any code violations or safety gaps; (4) track remediation completion; (5) maintain audit logs for liability protection. Integrate QA findings into weekly progress reports to the kit coordinator; pause installations if >3% of audited work is non-compliant.

---

Potential Improvements

1. Lack of explicit escalation decision tree and surge protocols for extreme-heat scenarios (40°C+ daytime or sustained multi-day heat)

The plan defines three alert levels with associated activations, but does not specify what additional actions trigger at sustained extremes (e.g., when forecast shows 40°C daytime for 5+ consecutive days, or national red warning persists). Extreme heat may require harder triage (directing oldest/frailest first), mutual-aid activation with hospitals, or temporary closure of some centers to concentrate staffing at largest sites. Without pre-set surge thresholds, incident command will improvise under crisis pressure, risking inconsistent decisions and reputational damage if a preventable death occurs during extreme heat.

Recommendation: Draft an Extreme-Heat Surge Protocol by Month 3 (2027-01-08) specifying: (1) Tier 3a activation threshold (forecast ≥40°C daytime for ≥3 days + night low ≥23°C) triggers: all centers 24-hour operation, priority transport for 75+ and wheelchair users, pre-positioned water/shading at all outdoor municipal work sites, and pre-notification to hospitals and EMS of expected surge; (2) Tier 3b (same + national red warning or ≥5 consecutive days) adds: mutual-aid activation with neighboring city (pre-agreed partner), surge staffing from municipal emergency-reserve pool, closure of smaller centers to concentrate service, and direct hospital-EMS escalation for any suspected heat illness; (3) Mutual-aid agreement signed by Month 2.5 (2026-12-23) with neighboring city (e.g., Villarreal, ~30 km) specifying resource-sharing (staff, center capacity, transport vehicles). Include surge protocol in the drill at Month 7 (2027-05-08).

2. Insufficient detail on how to handle conflicting operational decisions (e.g., transport demand spike vs. dispatch capacity, center over-capacity vs. safety protocols)

During an alert, the incident commander, center network manager, and transport coordinator may face decisions that conflict (e.g., a cooling center reaches 100% capacity but residents continue arriving; transport dispatch is 60 minutes behind; EMS call volume is at 1.8× baseline). The plan mentions escalation to incident command but does not specify decision algorithms, delegation limits or communication protocols that preserve speed and clarity under stress.

Recommendation: Develop an Operational Decision Matrix by Month 2.5 (2026-12-23) documenting: (1) Authority limits: incident commander has final authority on alert tier and stand-down; center network manager decides which sites to open and capacity adjustments; dispatch coordinator prioritizes by vulnerability (75+, wheelchair users, isolated residents) if wait times exceed 45 min; (2) Conflict resolution: if transport delay threatens the 45-min gate, dispatcher may request incident commander to authorize taxi-surge activation (additional vehicles at premium cost, up to €5k per day); (3) Safety thresholds: center closes entry if occupancy ≥110% fire-code capacity and transport redirects new arrivals to next-closest site with 15-min notice; (4) Health escalation: if EMS call volume reaches 1.5× baseline, commander notifies hospitals and prepares mutual-aid activation. Include conflict-scenario drills (e.g., capacity breach, dispatch overload) in the May full-system drill (Month 7 = 2027-05-08).

3. Limited clarity on financial accountability and mid-season budget re-forecasting if contingency is drawn or tranche-2 release is delayed

The plan allocates €280k contingency (8% of €3.5M) but does not specify: (1) who authorizes contingency draws >€10k; (2) how budget reforecasting occurs if tranche-2 (€1.5M) is delayed beyond Month 4 (2027-02-08); (3) which service elements are cut first if funding shortfalls occur; (4) how the city reports mid-season budget status to the funder and incident commander. Without clear financial governance, reactive spending and delayed decisions could cause missed gates or mid-season operational collapse.

Recommendation: Establish a Financial Governance Protocol by Month 1.5 (2026-11-23) specifying: (1) Contingency-draw authority: draws >€5k require incident commander and PMO sign-off; draws >€25k also require funder notification within 24 hours; (2) Monthly budget review: PMO produces a spend-vs-forecast summary by the 25th of each month (Months 0–12 = 2026-10-08 to 2027-10-08), with re-forecast of cash flow to Month 12 (2027-10-08); (3) Trigger thresholds: if spend exceeds forecast by >10% (€200k), incident commander and PMO convene a budget-rebalancing meeting within 48 hours; if rebalancing cannot close the gap, funder is notified; (4) Spending priorities if funding shortfall: maintain center and transport operations first (gates 1 and 3); maintain outreach phone line second (gate 2); defer home-kit installations third (defer to Year 2 if needed); (5) Delayed release contingency: if Month 4 (2027-02-08) release is not approved, draw up to €150k from tranche-1 contingency (if available) to cover May–June operations, with re-test decision at Month 5 (2027-03-08). Monthly budget reports are presented to incident command and funder on the last working day of each month.

4. Underspecified role clarity and handoff procedures if the incident commander or other critical staff are absent during multi-day heat events

The plan names a deputy public-health incident commander but does not specify: (1) what decisions the deputy can make autonomously (alert declaration, spending authorization, resource reallocation) versus what requires consultation with the primary; (2) how long the primary can be absent before the deputy assumes full command; (3) handoff procedures and documentation if absence extends beyond 48 hours; (4) cross-training for the center manager, transport coordinator and communications lead to substitute for each other in emergencies.

Recommendation: Draft a Continuity of Command and Succession Protocol by Month 2 (2026-12-08) specifying: (1) Primary incident commander (mayor's office or delegated) is the sole authority for alert declarations and spending authorization up to €50k per alert tier; above €50k, written approval required. (2) Deputy incident commander (public health) has full authority to declare and execute the approved response if the primary is unavailable for ≥2 hours; continuation ≥24 hours requires written notification to the mayor and funder. (3) If both primary and deputy are unavailable, written delegation passes to the civil protection operations lead (pre-signed, filed with municipal legal department) with the same authorities as the deputy, valid for ≤48 hours; beyond 48 hours, incident command returns to the mayor or funder decision. (4) Cross-training: center network manager and partner liaison officer can make operational (non-alert-declaration) decisions on center hours and partner coordination if incident commander is unavailable; dispatch coordinator can prioritize transport requests autonomously. (5) Handoff documentation: a brief incident-command log records all alert declarations, spending decisions, staffing adjustments and escalations daily; at shift-change (every 12 hours on multi-day events), the incoming commander reviews the log and confirms understanding with the outgoing commander.

5. No explicit feedback loop from residents using the program to improve service delivery mid-season

The plan tracks operational KPIs (center hours, transport time, outreach success) but does not include a mechanism to capture resident feedback about: accessibility barriers, quality of welcome at centers, comfort level with cooling spaces, perceived safety, language-access adequacy, or trust in the heat-illness escalation protocols. This feedback could identify equity gaps (e.g., elderly women avoiding mixed-gender day spaces) or low-quality implementations (e.g., dirty toilets, rude staff) early enough to fix in-season, improving both outcomes and equity.

Recommendation: Implement a Simple Resident Feedback Loop by Month 6 (2027-04-08) consisting of: (1) Post-visit feedback cards at each cooling center (2–3 questions, large print, multilingual: 'Was this space comfortable? Did you understand what to do? Would you come again?'); staff collect completed cards in a box daily; partner liaison officer reviews cards weekly and flags issues (e.g., >20% 'no' responses on comfort) for correction within 48 hours. (2) Quarterly focus groups (n=10–15 residents per group, 45 min) at Months 3, 6, 9 (2027-01-08, 2027-04-08, 2027-07-08) to explore barriers (e.g., 'Why don't you use the cool center?'; 'What would make you trust the phone line?'); held at convenient times/locations; light refreshments provided; insights inform mid-season protocol adjustments. (3) Heat-line call-log analysis: randomly sample 5% of calls monthly (Months 5–11 = 2027-03-08 to 2027-09-08) for call quality, script adherence and resident satisfaction; >10% of calls rated 'poor quality' triggers staff retraining. These mechanisms ensure resident voice informs operations without slowing decision-making.

6. Vague timelines and ownership for translation and community-ambassador recruitment in early months (critical path risk)

Language access is identified as a priority for migrants and non-native speakers (5–8% of Castellón's population, estimated 8,500–13,600 people), but the team document does not specify: (1) who conducts the Month 0 (2026-10-08) language-need assessment; (2) which four-to-six languages are prioritized (assumed candidates: Arabic, Romanian, Portuguese, but unconfirmed); (3) who owns translation procurement, testing and quality assurance; (4) how community-ambassador recruitment occurs (which NGO partners, what timeline, pay rate). If translation and recruitment slip beyond Month 2 (2026-12-08), multilingual messaging will not be ready for the May-June season, reducing reach to migrants by an estimated 10–20% and potentially failing equity targets.

Recommendation: Assign explicit ownership and timelines to the Communications Coordinator for language access: (1) By October 15 (Month 0.2 = 2026-10-14), conduct rapid language-need assessment via municipal integration office and NGO networks (e.g., housing associations, social services, migrant associations) to confirm top four-to-six languages; output: language list and estimated speaker counts per language. (2) By November 1 (Month 0.8 = 2026-11-01), commission professional translation of key materials (alert flyers, phone-line scripts, enrollment forms, cooling-center signage, fan-safety guidance) into the confirmed four-to-six languages; budget €15k–25k; delivery by Month 1.5 (2026-11-23). (3) By November 15 (Month 1.2 = 2026-11-14), launch community-ambassador recruitment through migrant associations and NGO partners, targeting 8–12 candidates (2 per language approximately); job description: 10–15 hours/week during alert season, hourly rate €12–15/hour (total ≈€50–75k for the season). (4) By December 8 (Month 2 = 2026-12-08), complete vetting and induction of 50% of target ambassadors (4–6 people) with de-escalation and heat-illness-recognition training; remainder by Month 3 (2027-01-08). (5) By April 15 (Month 6.1 = 2027-04-11), ambassadors are deployed at cooling centers and street-contact sites.

7. Insufficient specification of how to handle volunteers and partners experiencing safety incidents (assault, threat, witnessing severe distress)

The risk register identifies volunteer and street-contact staff safety as medium-to-high risk, and the Outreach Lead's responsibilities mention de-escalation training and safety protocols. However, the team document does not name an owner for: (1) incident-reporting systems and response procedures; (2) same-day debriefing and occupational-health referral; (3) investigation and learning from incidents; (4) communications with volunteers/partners after incidents (reassurance, peer-support offers). Without clear incident-response ownership, staff will feel unsupported after trauma, leading to turnover and liability exposure.

Recommendation: Designate the Occupational Health Liaison (0.25 FTE, see first omission above) as the Incident Safety Owner and establish an Incident-Response Protocol by Month 2 (2026-12-08): (1) Any assault, threat, or serious distress exposure triggers immediate reporting to the Incident Safety Owner and incident commander within 2 hours via phone/secure email (one-page form capturing incident date/time, location, people involved, what happened, and actions taken). (2) Same-day response: occupational health liaison contacts the affected person by phone within 4 hours; offers immediate peer-support contact (another trained staff member); arranges access to counseling if desired (city-funded, up to 6 sessions). (3) Next-day debrief: Incident Safety Owner holds a 30-minute meeting with the affected person and their team lead to process the event and identify any operational changes needed (e.g., '3-person teams always' instead of '2-person teams'). (4) Weekly safety review: Incident Safety Owner reports all incidents (anonymized) to incident command and convenes a monthly safety-committee meeting with partner liaisons, outreach leads and volunteer coordinators to identify patterns and implement systemic changes (e.g., additional de-escalation training, revised site-access rules). (5) Public accountability: funder is informed of any serious incidents (assault, injury) within 24 hours. This prevents secondary trauma and builds a culture of safety.

8. Missing explicit plan for how cooling centers will manage frail or confused residents who arrive but cannot remain alone and have no designated caregiver present

Older and isolated residents, including those with mild cognitive impairment or dementia, may arrive at cooling centers but lack the capacity to coordinate their own transport home or may resist leaving if they feel unsafe or disoriented. The plan specifies accessibility and welcome protocols but does not address: (1) who is responsible for the resident's safety and supervision during their stay; (2) whether centers can accommodate extended stays (overnight, multiple days) if transport home is unavailable; (3) how to manage situations where a resident becomes acutely confused or combative; (4) communication with family or designated contacts.

Recommendation: Draft a Frail and Vulnerable Resident Protocol by Month 2 (2026-12-08) to be implemented by cooling-center managers, specifying: (1) On arrival, center staff conduct a brief safety screen (using a simple checklist: alert/oriented? able to find toilet? able to communicate needs? has someone to contact?); (2) Residents who are alert and oriented are given a welcome card with center rules, phone numbers, and instructions for requesting help; (3) Residents who are confused, disoriented or alone and frail are assigned a staff member (or volunteer if available) to check in every 30 minutes, help with toileting and water, and identify any escalation needs; (4) If a resident is found to be at risk (e.g., very confused, showing signs of heat illness, no known contact), center staff immediately call the nurse triage line and the heat helpline to arrange transport home or to a hospital; (5) Centers may accommodate overnight stays (with AED, first aid and staff on-site) only if the resident is alert, consents, and transport home is unavailable; overnight stays are logged and escalated to incident command daily; (6) Center staff are trained in basic dementia-aware communication (calm tone, yes/no questions, patience) by Month 2 (2026-12-08) as part of the first-aid and customer-service induction.

9. No explicit mechanism for identifying and supporting outdoor municipal workers and private contractors during alert days before the formal alert is declared

The plan includes worker-protection clauses for municipal staff and guidance for private employers, but does not specify: (1) who monitors weather forecasts and alerts outdoor-work crews 24–48 hours in advance (before official alert declaration); (2) how private contractors outside municipal employment get timely warning; (3) what 'adjusted schedules' and 'mandatory breaks' mean operationally (e.g., start at 05:00, stop at 11:00, resume at 18:00?). Without proactive alerts to work sites, workers may not implement protections until the alert is declared at 12:00 mid-day, missing protection for the morning peak-heat period.

Recommendation: Assign the public-works compliance monitor (see Risk 16 mitigation above) to establish a Proactive Worker Alert Protocol by Month 2 (2026-12-08): (1) Each morning (by 07:00) during the April–September season, the climate monitor reviews the national weather forecast and checks if an alert is likely in the next 24–48 hours (forecast ≥35°C daytime or ≥22°C night low for ≥2 consecutive days). (2) If likely, issue a Proactive Worker Alert by 09:00 to all municipal work crews (public works, parks, water, waste, housing maintenance) and active contractors (via email and phone to site managers) advising: forecast conditions, suggested schedule adjustments (start early, extended midday break), water and shade requirements, and that a formal alert may follow. (3) For private employers, the same message is distributed via the municipal employer-association email list and published on the city website. (4) When an official alert is declared, incident commander issues a formal Worker Activation Order confirming mandatory protections and schedule changes. (5) Compliance monitor conducts ≥2 unannounced site visits during each Level 2–3 alert day (sampling different sectors—public works, construction, waste, landscaping) to verify workers have water, shade, breaks and adjusted schedules. This reduces heat-illness risk among the working population by 4–8 weeks annually (April/May and August/September shoulder seasons).

Critique and recommended actions from domain experts.

1 Expert: Municipal Public Health & Heat Action Coordinator

Knowledge: Public health program design, heat-health equity, vulnerable-population epidemiology, EU public-health regulation, municipal health systems, evaluation methodology for small-area health outcomes

Why: The plan's foundation rests on identifying and reaching vulnerable groups (65+, chronic disease, living alone, migrants) and measuring heat-related harm (EMS, ED, excess mortality). This expert advises on baseline data validation, equity metrics design, and whether the intermediary-list model actually reaches the most isolated residents, addressing a critical open question in the plan.

What: Review the outreach model (intermediary-held lists, 3,000 enrolled target, 60% contact gate) and baseline estimates (80–120 EMS calls, 15–25 excess deaths), then propose a health-equity audit framework to confirm reach parity across neighborhoods, age bands, and housing type by Month 9 (2027-07-08).

Skills: Population health assessment, equity metrics, health data governance, vulnerable-population engagement, EMS/ED coding standards, excess-mortality attribution

Search: municipal heat action coordinator, public health equity epidemiologist, vulnerable population health outcomes, EU climate health program

1.1 Primary Actions

• By Month 0.95 (2026-11-06), obtain written funder sign-off on the drill-based gate criteria and the 50% partial-release rule (€750k at Month 4 = 2027-02-08 if evidence is insufficient, remainder after Month 5 = 2027-03-08 re-test). Document the funder's acceptance of the cool-season testing limitation in a decision memo. If the funder refuses, convene an emergency steering meeting to rescope the gates or defer the scale decision to Month 5 (2027-03-08).
• By Month 1.08 (2026-11-10), issue detailed procurement specifications for cooling kits (products, quantities, lead times, acceptance criteria) to 3 primary suppliers and 2 backup suppliers. Request quotes and delivery commitments by Month 0.95 (2026-11-06). By Month 1.15 (2026-11-13), sign backup-supplier agreements with automatic activation triggers (>2-week primary-supplier slippage) and pre-authorized premium fees (up to 10% cost increase). Place the first-tranche order (30–40% of kits, 600–800 units) by Month 1.2 (2026-11-14); confirm delivery schedule or escalate to backup by Month 1.5 (2026-11-23).
• By Month 1 (2026-11-08), conduct a partner capacity audit: survey housing associations, social services, NGOs and pharmacies to establish baseline call-center staffing, call time per resident, and summer turnover rates. By Month 1.5 (2026-11-23), agree in partner data-processing agreements on minimum staffing reserves (80% availability during alert season), daily contact logging (aggregate only, no identifiable data), and an escalation trigger if <60% are reached within 4 hours of Level 2 alert. By Month 3.2 (2027-01-14), during the full-system drill, measure actual contact rates; if <60%, adjust the gate to 55–58% or activate additional outreach resources; brief the funder by Month 3.5 (2027-01-23).
• By Month 0.8 (2026-11-01), name the incident commander (mayor's office), public-health deputy, operations lead (civil protection), communications lead and partner-coordination lead in writing. Obtain mayoral delegation of authority by Month 1 (2026-11-08). These roles are prerequisites for the remaining procurement and hiring actions to proceed.
• By Month 0.5 (2026-10-23), engage a specialist GDPR law firm (€15–30k budget) to review the intermediary-held-list model and draft partner data-processing agreements. Obtain written legal opinion by Month 1 (2026-11-08) confirming GDPR compliance and whether a formal Data Protection Impact Assessment is required. Finalize and execute partner agreements by Month 1.5 (2026-11-23); brief all partner staff (50–80 people) on GDPR obligations and confidentiality by Month 2 (2026-12-08).

1.2 Secondary Actions

• By Month 0.95 (2026-11-06), launch volunteer driver recruitment via municipal website, GP practices, NGO networks and faith organizations; target 30–50 volunteers. Issue vetting requirements (background check, insurance, safeguarding training) and set cohort milestones: ≥15–20 vetted and in-post by Month 2 (2026-12-08), remainder by Month 3 (2027-01-08). Establish an HR coordinator (0.5 FTE) by Month 0.5 (2026-10-23) to manage hiring and vetting timelines.
• By Month 0.95 (2026-11-06), issue procurement specifications for taxi/accessible-transport standby retainers and request firm quotes for alert-day capacity (≥10 vehicles, ≥3 wheelchair-capable, ≥20-min response time). Negotiate and sign the retainer contract by Month 1.2 (2026-11-14) with a capped cost of €80k per season and 48-hour cancellation notice if heat events do not materialize.
• By Month 0.95 (2026-11-06), identify and contact 8–12 proposed cooling-center sites (libraries, community centers, parish halls, sports facilities). By Month 1.15 (2026-11-13), execute facility-use MOUs specifying hours (minimum 10:00–20:00 daily at Level 2–3), staffing, security, and liability insurance. By Month 1.5 (2026-11-23), conduct accessibility audits (wheelchair ramps, accessible toilets, quiet rooms, water, signage); remediate gaps ≤€10k and ≤4 weeks or categorize as 'defer to July'. Ensure ≥50% of planned capacity is fully accessible by Month 2 (2026-12-08).
• By Month 0.95 (2026-11-06), contract a telephone answering service or repurpose municipal health-line capacity for the heat-alert helpline (08:00–22:00 daily during alert season, 24-hour at Level 3). Hire 2–3 part-time phone operators (30 hours/week) fluent in Spanish and ≥1 non-official language by Month 1.5 (2026-11-23). Conduct 4-hour training on escalation protocols and cooling-center information by Month 2 (2026-12-08). By Month 2.5 (2026-12-23), run a mock helpline drill (5–8 transport requests, 3–5 escalations) to validate readiness.
• By Month 1 (2026-11-08), negotiate an MOU with hospitals, EMS and primary-care providers for daily aggregate heat-related ED and EMS call counts (no identifiable patient data). Define agreed coding (e.g., ICD-10 T67.0–T67.9 for heat illness). Conduct a 2-week validation pilot starting Month 1.8 (2026-12-02) to test data feeds. Establish a nurse-advice line for outreach staff triage by Month 2 (2026-12-08). Set escalation thresholds: notify the incident commander at ≥1.5× historical average heat volume; consider mutual-aid at ≥2×. Document in a signed protocol by Month 2 (2026-12-08).
• By Month 1.5 (2026-11-23), finalize the heat-illness escalation checklist with a senior emergency-medicine clinician. Train all 25–35 planned outreach and street-contact staff on recognition, decision rules (when to call 112 vs phone triage), and de-escalation language by Month 1.5 (2026-11-23). Conduct role-play scenarios (15 vignettes) and require written test (≥80% pass) before alert-day authorization. Log attendance and refresh training in May (Month 8 = 2027-06-08).
• By Month 1 (2026-11-08), co-design a street-contact protocol with local homeless-service NGOs for alert-day rounds to unhoused residents. Define consent models for acute heat illness, off-duty procedures if staff are threatened, and escalation rules. By Month 1.5 (2026-11-23), complete background checks and safeguarding-training certification (3-hour module on de-escalation, trauma-informed care) for all volunteers and street-contact staff. Establish a rapid incident-reporting system with same-day documentation and supervisor debriefing within 2 hours. Designate a safeguarding lead (0.25 FTE) to track incidents and identify training gaps.
• By Month 1 (2026-11-08), publish a heat-protection guidance package for private employers (schedule shifts, mandatory breaks, water, shade at Level 2–3). Establish one municipal compliance monitor to visit ≥50% of active contracts (outdoor workers, construction, municipal services) and issue corrective notices ≤48 hours if violations are found. Draft heat clauses into new municipal tenders and contracts from Month 1 (2026-11-08) onward.
• By Month 1 (2026-11-08), confirm locally common non-official languages through municipal registers (candidates: Arabic, Romanian, Portuguese). By Month 1.5 (2026-11-23), recruit 8–12 paid community language ambassadors (10–15 h/week); budget ≈€67k. Brief them as trusted messengers on heat-safety messages and enrollment referrals by Month 2 (2026-12-08). Contract telephone interpretation services (≥2 languages, ≥08:00–22:00 daily during alert season) by Month 1 (2026-11-08).
• By Month 2.5 (2026-12-23), finalize the full-system drill protocol (locations, realism criteria, observer roles, evaluation rubric). Conduct the drill Month 3.2 (2027-01-14) with independent observation. Track center hours, contact attempts/successes, and pickup times over ≥30 requests (including ≥5 wheelchair users). Complete an after-action report by Month 3.5 (2027-01-23) and close all corrective actions by Month 3.9 (2027-02-04) before the Month 4 (2027-02-08) gate decision.
• By Month 1 (2026-11-08), commission a university or public-health institute evaluation partner under a data-processing agreement. Pre-specify the evaluation protocol: comparison design (pilot vs matched districts and prior years, temperature-adjusted, aggregate counts only), baseline data (heat-related EMS, ED, mortality with caveats), and limitations in plain language. Obtain baseline estimates and agreed coding by Month 4 (2027-02-08). Publish results regardless of direction by Month 12 (2027-10-08).

1.3 Follow Up Consultation

At the Month 1 (2026-11-08) steering-committee meeting, review the three risks above with the funder, incident commander and public-health deputy. Confirm in writing: (1) drill-based gates and the 50% partial-release rule; (2) backup-supplier activation and premium-fee authorization; (3) partner capacity and contact-rate audit plan. Establish a weekly procurement and staffing dashboard to flag any slippage >1 week. Plan the Month 2.5 (2026-12-23) drill protocol refinement and the Month 3.2 (2027-01-14) full-system drill. Discuss contingency drawdown rules: if any single risk (procurement, staffing, partner capacity) forces a contingency spend >€70k, convene an emergency meeting to re-scope the program or defer scale activation. Confirm Year-2 funding source identification target by Month 9 (2027-07-08) to enable planning for expansion or continuation.

1.4.A Issue - Cool-Season Gates Create Unfalsifiable Evidence Problem

The Month 2 (2026-12-08) and Month 4 (2027-02-08) gates fall in winter; you cannot test 80% center hours, 60% outreach contact, or <45-min transport against real heat events. The plan relies on drills, which funders may treat as weak evidence. If June–July temperatures are cool, gates become untestable, the €1.5M release is at risk, and a €200–400k cash gap emerges mid-season. The partial-release rule (€750k at Month 4 = 2027-02-08, remainder after May re-test) is complex and may not be accepted by your funder in writing.

1.4.B Tags

• unfalsifiable_gates
• cool_season_testing
• funder_risk
• cash_flow_gap

1.4.C Mitigation

By Month 1 (2026-11-08), obtain written funder confirmation that drills satisfy the Month 2 (2026-12-08) and Month 4 (2027-02-08) gates, and that the 50% partial-release rule applies if evidence is insufficient. Pre-specify the drill protocol (locations, scripts, realism criteria) by Month 2.5 (2026-12-23) and conduct the full-system drill Month 3.2 (2027-01-14) with independent observation. Document drill results rigorously (center hours logged, contact attempts and successes counted, pickup times recorded over ≥30 requests). If the funder refuses drill-based gates, defer the scale gate to Month 5 (2027-03-08) and move the €1.5M release decision to post-June, accepting the cash-flow risk and contingency hit.

1.4.D Consequence

Without funder sign-off, you face a €200–400k unfunded gap at Month 4 (2027-02-08) if gates fail to release on schedule. This forces mid-season cuts to staffing, home kits or transport. The program risks operational collapse and reputational damage if a heat event occurs while services are incomplete. Partners and volunteers may disengage if funding becomes uncertain.

1.4.E Root Cause

The project timeline was compressed to fit a 12-month cycle, pushing both readiness gates into cool months. The gate structure prioritizes schedule over evidence quality. Funders typically prefer real-world validation over simulations; this mismatch was not surfaced early with the funder.

1.5.A Issue - Procurement Critical Path Compressed to 6 Weeks; Supply-Chain Failure Is High-Risk

Procurement specs must be issued by Month 0.8 (2026-11-01), and all tranche-1 orders (€1.6M estimate) by Month 2 (2026-12-08). This is 6 weeks from today (Month 0 = 2026-10-08). Cooling kits need 4–6 weeks lead time; if orders slip past Month 1.2 (2026-11-14), delivery pushes into April–May, missing early June peak-risk heat events. You have identified backup suppliers as mitigation, but backup activation (procurement redirection, premium fees of 10–15%) is not budgeted separately and consumes €50–100k of the €280k contingency, leaving little margin for staffing or transport overruns.

1.5.B Tags

• supply_chain_risk
• compressed_timeline
• backup_activation_unclear
• contingency_inadequate

1.5.C Mitigation

By Month 0.8 (2026-11-01), issue detailed specs (products, quantities, delivery dates, acceptance criteria) to 3 suppliers and request quotes by Month 0.95 (2026-11-06). By Month 1.08 (2026-11-10), benchmark quotes and pre-qualify backup suppliers with signed agreements specifying: (a) activation trigger: if primary supplier reports >2-week slippage from promised delivery, city activates backup within 2 business days; (b) premium acceptance: city pre-authorizes up to 10% cost premium (approximately €60–80k for kits) without additional approval; (c) expedited delivery: backup confirms 3-week lead time or cites inability immediately. Place first-tranche order (30–40% of kits) at Month 1.2 (2026-11-14) with primary supplier. By Month 1.5 (2026-11-23), receive delivery confirmation or escalate to backup. Establish a weekly procurement dashboard tracking all orders, expected vs actual delivery dates, and contingency budget draw. By Month 2 (2026-12-08), confirm 50% of kit stock is either in-hand or under firm 4-week delivery commitment.

1.5.D Consequence

If kit procurement slips 4+ weeks, 40–60% of home installations will miss May–June peak-risk heat season, reducing the home-intervention impact and the visible program credibility. Transport and refuge operations can launch, but the home-kit leverage (2,000 visible installations, tangible benefit to residents) is undermined. This increases political pressure to cut other elements, triggering staff or transport reductions. If you activate a backup supplier without budget authority, audit risk and funder trust are damaged.

1.5.E Root Cause

The brief requires a repeatable playbook without new legislation, and the 12-month timeline forces compressed procurement. No buffer was built into the critical path for normal supplier lead times or GDPR/accessibility delays. The plan assumes 'specs by Month 0.8 (2026-11-01)' as achievable, but the incident commander, civil-protection operations lead, and public-health deputy may not be named until Month 1 (2026-11-08), delaying spec approval.

1.6.A Issue - Intermediary-List Outreach Model May Underreach Isolated Residents; 60% Contact Success Gate Is Ambitious and Unvalidated

The plan assumes intermediary organizations (housing associations, social services, NGOs, pharmacies) can contact ≥60% of enrolled residents on demand. This is a gate criterion for the €1.5M release. However: (a) no baseline call-center capacity exists for these partners; (b) 'enrolled' residents are self-selected (opt-in via GPs, pharmacies, centers), typically biasing toward people already in contact with services; (c) isolated, offline and recently migrant residents—the highest-risk group—are least likely to self-enroll; (d) partner call-center staff turnover during summer peak season is typical 10–20%, risking capacity loss mid-alert. The 60% contact rate is plausible for a motivated cohort but brittle if partner staffing degrades or bad weather causes multiple simultaneous alerts.

1.6.B Tags

• reach_inequality
• unvalidated_assumption
• partner_dependency
• gate_contention_risk

1.6.C Mitigation

By Month 1 (2026-11-08), survey the partner organizations (housing associations, social services, NGOs) to establish baseline call-center capacity: number of available staff, average call time per person, number of calls per person per alert day (1 or 2?), and typical summer staff turnover. By Month 1.5 (2026-11-23), agree in the partner DPAs on: (a) minimum staffing reserve (e.g., 80% normal staffing maintained even if absence reaches 15%); (b) escalation rule (if <50% of enrolled residents are reached within 4 hours of Level 2 alert, city allocates emergency taxi transport vouchers or activates backup outreach teams). By Month 2 (2026-12-08), pre-define the contact-success audit: each partner logs call date, time, outcome (reached, unreachable, declined, transport accepted) and shares aggregate counts (not identifiable data) daily by 12:00. By Month 3.2 (2027-01-14), during the full-system drill, track actual contact rates and call-center staff availability. If <60% are reached in the drill, adjust the gate to 55% or activate escalation protocols; do not hide shortfalls. Brief the funder at Month 3.5 (2027-01-23) on actual contact performance and partner capacity; if a gap is identified, agree on revised target or added resources.

1.6.D Consequence

If the 60% contact gate is unachieved and contested, the €1.5M release is at risk again, creating the same cash-flow gap as the cool-season risk. Operationally, if the city cannot reach enrolled residents reliably, the outreach program loses credibility with residents (a 40% failure rate is not acceptable), and the isolation of the target population is reinforced—exactly the equity outcome the program should prevent. Partners may blame the city for ambitious targets, damaging relationships for Year 2.

1.6.E Root Cause

The plan adopted intermediary-list identification to avoid GDPR risk and to reach offline residents, but it did not validate whether partner call-center capacity actually exists to execute a 60% success rate on alert days. The assumption was borrowed from Barcelona and Paris references but not contextualized to Castellón's partner landscape. No baseline capacity audit was conducted before designing the gate.

---

2 Expert: GDPR & Health Data Protection Specialist

Knowledge: EU data protection regulation, lawful basis for health data processing, intermediary liability and data-processing agreements, Spanish AEPD practice, health-data minimization, consent and retention frameworks

Why: The plan's GDPR strategy is critical: intermediary-held lists keep personal data away from the city, but the legal basis, liability sharing, partner audit rights, and breach escalation are only sketched. This expert ensures compliance, mitigates regulatory challenge risk, and advises whether the intermediary model withstands AEPD scrutiny—directly supporting the Month 1.5 (2026-11-23) DPA signing deadline.

What: Co-author the template data-processing agreements (DPAs) for housing associations, social services, NGOs and pharmacies; specify controller/processor roles, audit rights (spot-check consent records), and breach-notification triggers; advise on whether heat-alert contact qualifies as a 'public task' under GDPR Article 6(1)(e) or requires explicit consent; deliver legal opinion by Month 1 (2026-11-08).

Skills: Data-processing agreements drafting, health-data minimization, GDPR Article 6 basis-selection, Spanish data protection law, partner liability frameworks, audit-trail design

Search: GDPR health data specialist, data protection officer EU public health, GDPR DPA templates, intermediary data processing health

2.1 Primary Actions

• By Month 0.9 (2026-11-04): Engage a specialist GDPR law firm (€20–30k budget, 8–10 week engagement) to deliver three legal documents in parallel: (1) joint-controller agreement (Article 26) for housing associations and social services; (2) data-processor DPA for NGOs with discretion; (3) memorandum allocating each partner to the correct category based on the city's control over contact strategy. Do not wait for Month 1.5 (2026-11-23) to discover the DPA template is legally insufficient.
• By Month 1 (2026-11-08): Obtain written legal opinion from GDPR counsel confirming the lawful basis for heat-alert contact (consent vs. public-task vs. hybrid) and specifying which Article 6(1) basis applies. If public-task: produce a draft municipal ordinance for city-council approval by Month 1.2 (2026-11-14). If consent: finalize a two-page consent form (translated into Spanish, Valencian, Arabic, Portuguese, Romanian; budget €3–5k) and obtain city-legal sign-off on the form and withdrawal procedures.
• By Month 1 (2026-11-08): Commission a formal Data Protection Impact Assessment (DPIA, €8–12k, 4–6 weeks) for the health-data loop (hospital/EMS aggregate-count sharing). The DPIA must address: (1) definition of 'heat-related' coding and clinician judgment; (2) re-identification risk and controls; (3) retention period and secure deletion procedures; (4) joint-controller vs. processor status. Deliver the DPIA to hospital legal teams by Month 1.3 (2026-11-17) to allow 4–6 weeks for their review and approval before Month 1.5 (2026-11-23).
• By Month 1.5 (2026-11-23): Finalize and execute data-processing agreements with all partner organizations (housing associations, social services, NGOs, pharmacies, hospitals, EMS) incorporating the legal opinions and DPIA findings. Agreements must explicitly define: (a) joint-controller vs. processor relationship; (b) lawful basis (consent form or ordinance text attached); (c) data types and retention period; (d) withdrawal procedures and deletion timelines; (e) breach-notification and escalation contacts; (f) audit rights (city spot-check of consent records and privacy-notice logs); (g) liability allocation if a partner breaches confidentiality. Obtain countersignature from each partner's legal/data-protection representative, not just operational staff.
• By Month 2 (2026-12-08): Brief all 50–80 partner staff (housing caretakers, social-services workers, NGO field staff, pharmacists, GP practice managers, EMS dispatch supervisors, hospital data officers) on GDPR obligations specific to their organization. Provide written one-page checklists covering: (1) what data they hold and how it is protected; (2) how to respond to a withdrawal request (48-hour escalation to the city's data-protection contact); (3) incident reporting: if staff suspect a breach (unauthorized access, loss of contact list, disclosure to a third party), call the city's data-protection contact same-day and file a written incident report within 24 hours; (4) never disclose the enrolled-resident list to anyone except the partner's own authorized staff; (5) log all contact attempts (date, time, language, outcome) for audit purposes. Attendance mandatory; maintain roster for AEPD evidence.
• By Month 1 (2026-11-08): Specify in writing which organization is the Data Protection Officer (DPO) or data-protection contact for the program. If the city has no existing DPO, appoint or contract one (expected role: 0.3–0.5 FTE, cost €20–30k per year, available by Month 1 = 2026-11-08). The DPO is the single escalation point for: (1) breach reports from partners or residents; (2) withdrawal requests; (3) AEPD enquiries. Publish the DPO's contact details in all resident-facing materials (flyers, posters, heat-line scripts, cooling-center signage) so residents know how to report concerns.

2.2 Secondary Actions

• By Month 0.9 (2026-11-04): Request the Spanish Data Protection Agency (AEPD) to provide written guidance (or consult published AEPD criteria) on whether heat-alert contact in a municipal welfare context is lawful under Article 6(1)(e) (public task), Article 6(1)(c) (legal obligation), or only under Article 6(1)(a) (consent). This clarification will inform the legal opinion due at Month 1 (2026-11-08) and avoid costly re-work if counsel's assumption differs from AEPD practice.
• By Month 1 (2026-11-08): Prepare a resident-facing privacy notice (1–2 pages, translated into 4–6 languages) explaining: (1) what data will be collected (name, address, phone, language preference, transport needs, cooling-center preference); (2) why (heat-alert contact during high-temperature events); (3) who has access (named partner organizations only, not shared with third parties); (4) how long data are kept (deleted within 30 days after the season ends unless resident re-enrolls); (5) the right to withdraw (call the heat line, visit a cooling center, or email the DPO; processed within 48 hours). Attach this notice to all enrollment materials (GP posters, pharmacy flyers, cooling-center registration forms). Post on the city's website. Provide a summary in plain language for residents with limited literacy.
• By Month 1.5 (2026-11-23): Complete a DPIA addendum for the outreach component (intermediary-held contact lists), addressing: (1) scale of personal data (number of enrolled residents, estimated 3,000); (2) types of partners (housing associations, social services, NGOs—each a separate data processor/controller); (3) volume of contact attempts (5,000 per month in season); (4) escalation pathways (how outreach staff report heat-illness concerns to EMS without disclosing resident names to non-health partners); (5) residual risk that a partner discloses the list to a third party and mitigation (contractual liability, breach-notification obligations, spot-check audits). This DPIA is distinct from the health-data DPIA and should be reviewed by the city's legal department and shared with the funder (if required by grant conditions).
• By Month 2.5 (2026-12-23): Schedule a compliance audit checkpoint with all partner organizations to verify: (1) staff training completion rates (target ≥90%); (2) logged contact attempts (sample audit of 10–20 partner contact logs to confirm format and completeness); (3) any breach reports received (expected: zero, but investigate any outlier quickly); (4) consent withdrawal requests received (expected: <1% of enrolled residents; log and process within 48 hours). Report findings to the city's data-protection contact and the funder.
• By Month 7 (2027-05-08): Conduct a formal partner audit (allow 2–3 weeks, expected cost €5–8k if contracted externally, or 10–15 staff-days in-house) covering: (1) physical storage of contact lists (locked cabinets, access logs); (2) electronic storage (password-protected, encrypted, access logs); (3) sample of withdrawal requests processed (all within 48 hours? all notified to city DPO?); (4) any accidental disclosures or suspected breaches (timeline for reporting and remediation); (5) compliance with retention period (no data held beyond season unless explicitly re-consented). Produce an audit report by Month 7.5 (2027-05-23) and share corrective actions with each partner and the funder.
• By Month 12 (2027-10-08): Prepare a Data Protection & Privacy chapter in the Heat Response Playbook documenting: (1) the lawful basis used (consent, public task, or hybrid) with legal justification; (2) template DPAs and consent forms for next-year replication; (3) partner vetting and training requirements; (4) incident-reporting procedures and escalation contacts; (5) a sample Data Protection Impact Assessment (so peer cities can adapt it); (6) lessons learned: which consent model achieved highest enrollment, which partners had compliance gaps, what training gaps were found. This chapter will be critical for scaling to other EU cities and for demonstrating compliance to the funder and AEPD.
• Ongoing (monthly during season Months 6.8–11.8 = 2027-05-08 to 2027-09-08): Maintain a breach-incident log accessible only to the city DPO and incident commander. Log any suspected or confirmed: (1) unauthorized access to contact lists (e.g., list left in a public place, found in trash); (2) disclosure to a third party without consent (e.g., a partner staff member forwards a list to a journalist); (3) data loss (e.g., laptop theft from an outreach vehicle); (4) resident complaint (e.g., contacted after requesting withdrawal). For each incident: document date, nature, people affected, immediate response, root cause, and corrective action. If a breach is confirmed, notify AEPD within 48 hours (Article 33) and affected residents within 72 hours (Article 34), unless there is low risk of harm. Budget €10–20k for potential breach-response costs (notification letters, credit monitoring if addresses/phone leaked, legal advice).

2.3 Follow Up Consultation

In the next consultation, confirm: (1) Which municipal department or external contractor will serve as the Data Protection Officer (DPO)? If no DPO exists, budget and hire by Month 1 (2026-11-08). (2) Has the city's legal department approved the intermediary-held contact model, or does it prefer consent over public-task authorization? Confirm by Month 0.9 (2026-11-04) so counsel can draft the correct legal basis. (3) Have hospitals and EMS been contacted informally to assess whether they will accept daily aggregate-count sharing? If resistance is high, plan alternative data sources (EMS alone, quarterly aggregates, or manual sampling). (4) What languages are most common among recent migrants in Castellón de la Plana? Confirm by Month 0 (2026-10-08) so consent forms and privacy notices can be translated accurately. (5) Will the city council need to approve a municipal ordinance authorizing heat-alert contact, or can the mayor delegate this by executive order? Confirm by Month 1 (2026-11-08) to avoid delays in the legal-basis foundation. (6) What is the funder's policy on GDPR compliance evidence? Do they require a pre-specified DPIA or just an audit trail of decisions? Clarify to calibrate the scope of legal documentation.

2.4.A Issue - Intermediary-held list model lacks explicit lawful-basis documentation and creates orphaned liability

The plan states partner organizations (housing associations, social services, NGOs, pharmacies) will 'make the calls on the city's behalf' without the city holding personal data. This inverts the controller-processor relationship incorrectly: if the city is directing the contact strategy (when, whom, what message), the city is a joint controller, not a data subject. GDPR Article 26 requires a joint-controller agreement specifying roles, liabilities and breach-notification responsibilities. The current DPA template approach treats partners as processors, but the contact decision-making is joint. If a partner breaches confidentiality or contacts someone who objects, the city cannot disclaim liability simply because data never transferred. Spanish AEPD practice (Criterios, 2023) holds the beneficiary (city) jointly liable for partner-driven contact campaigns in welfare contexts.

2.4.B Tags

• GDPR-joint-controller
• lawful-basis-undefined
• liability-orphaned
• DPA-insufficient

2.4.C Mitigation

By Month 0.9 (2026-11-04), request the GDPR counsel to prepare three documents in parallel: (1) a joint-controller agreement (Article 26) specifying that the city and partner jointly decide contact strategy, retention, and breach protocols; (2) a processor agreement (DPA) for cases where the partner only executes city-defined scripts with no discretion; (3) a memorandum documenting why each partner falls into which category. For housing associations and social services (city-directed scripts, no partner discretion on who/when): use joint-controller form. For NGOs with their own welfare expertise (partner discretion on outreach method): use processor form. For pharmacies (retail, limited capacity): negotiate individual consent at the point of service instead of pre-enrolled lists. Obtain the AEPD's written view (request formal guidance by Month 1 = 2026-11-08) on whether heat-alert contact constitutes a lawful basis (Article 6(1)(e) public task, Article 6(1)(c) legal obligation, or Article 6(1)(f) legitimate interest) or requires explicit consent (Article 6(1)(a)). If counsel advises joint control, add 2-4 weeks to the Month 1.5 (2026-11-23) DPA-signing timeline and brief the funder at Month 1 (2026-11-08).

2.4.D Consequence

Without explicit joint-controller agreements, if a partner breaches confidentiality (e.g., discloses an enrolled resident's contact to a third party, or contacts someone who revoked consent), the city cannot prove it delegated that decision or that the partner acted without city authority. AEPD investigation will find the city liable as a joint controller. Regulatory fine risk: 2-4% of annual revenue (Article 83(4)) for a municipality. Reputational damage: local media story about a data breach from a city 'trusted' intermediary. Partner withdrawal: if an NGO receives a breach notice, it may terminate its MOU mid-season, cutting outreach reach by 10-20% and threatening the 60% contact-success gate. Legal remediation cost: €50-100k for incident response, breach notifications and AEPD cooperation.

2.4.E Root Cause

The intermediary model was chosen for simplicity and GDPR avoidance, but it conflates 'data does not move to the city' with 'city has no controller responsibilities.' The city determines alert triggers, contact frequency (1-2 calls per alert day per enrolled resident), timing, and escalation rules. That is joint control. No joint-controller agreement is mentioned. The DPA template (Month 1.5 = 2026-11-23) assumes processor relationships and is legally insufficient.

2.5.A Issue - Consent model is ambiguous and may not meet the legal basis required by Spanish law

The plan mentions 'consent withdrawal protocols' and 'opt-in registries' at GPs and pharmacies, but does not specify what type of consent or lawful basis the city is claiming. GDPR Article 6 lists six lawful bases: consent (6(1)(a)), contract (6(1)(b)), legal obligation (6(1)(c)), vital interests (6(1)(d)), public task (6(1)(e)), and legitimate interest (6(1)(f)). Spanish LOPDGDD Article 9 restricts public-sector heat contact to either explicit consent or a legal obligation/public-task basis. If consent is chosen: GDPR Article 7 requires affirmative acts (not pre-ticked boxes), clear information on withdrawal, and evidence the subject provided it. If public-task is chosen: the contact must be authorized by law (e.g., a municipal heat-alert ordinance), the city must retain clear audit trails, and withdrawal is limited. The plan does not define which basis is claimed, does not specify withdrawal mechanisms, and does not attach a consent form or withdrawal request procedure. This creates a compliance gap: if AEPD challenges the legal basis, the city cannot defend enrolled residents' contact or data retention.

2.5.B Tags

• consent-model-undefined
• lawful-basis-article6-missing
• withdrawal-undocumented
• LOPDGDD-article9-conflict

2.5.C Mitigation

By Month 0.9 (2026-11-04), the GDPR counsel must prepare a legal-basis memorandum deciding whether heat-alert contact is: (1) Consent-based, in which case prepare a two-page consent form (translated into 4-6 local languages) stating the purpose, data types, retention period, and withdrawal method; and brief GPs, pharmacies and NGO staff on how to obtain affirmative consent (signature, verbal confirmation recorded, online click); or (2) Public-task-based, in which case draft or obtain a municipal ordinance (approved by Month 1.2 = 2026-11-14 by the city council) authorizing the heat-alert contact and defining the scope (who, frequency, duration, escalation). Include a DPIA template (€5-10k to complete, delivered by Month 1.2 = 2026-11-14) that documents the lawful basis, necessity and proportionality, and consent/withdrawal procedures. Attach the consent form or ordinance text to the partner DPA agreements (Month 1.5 = 2026-11-23). Brief partner staff on withdrawal procedures: if a resident calls the heat line or visits a cooling center and requests removal from the contact list, the city must confirm and de-enroll within 48 hours, and notify all partners. Log withdrawals in the audit trail for AEPD review.

2.5.D Consequence

If AEPD investigates (triggered by a resident complaint or a data breach), the city cannot produce: a) a valid legal basis for contact, b) evidence of affirmative consent, or c) a withdrawal procedure compliant with Article 17 (right to erasure). AEPD can issue a corrective order (Article 58(2)(d)) requiring deletion of all enrolled-resident data within 30 days. This terminates the outreach program mid-season, cutting contact attempts to near zero and failing the 60% gate. Regulatory fine: 2-4% of revenue (€500k-1M+ for a city of 170k). Reputational damage: 'City illegally harvested health data' headline. Resident class-action risk: if breach occurs and residents can prove non-consensual contact, they may claim damages under Article 82 (estimated exposure €10-50k per resident × 100-300 enrolled residents = €1-15M, though municipal immunity may apply under Spanish law).

2.5.E Root Cause

The plan treats 'opt-in' and 'consent' as synonymous with 'GDPR-compliant,' but does not distinguish between Article 6 lawful bases or specify how residents provide affirmative consent. The decision-makers (mayor's office, public health) probably assume consent is the safest route, but true consent requires: a) a free choice not to enroll (alternative channel?), b) a specific consent form, c) clear withdrawal instructions, and d) evidence of affirmative action (signature, checkbox, phone confirmation). None of these are detailed. Alternatively, if the city claims a public-task basis (emergency public health), it must cite a legal authority (municipal ordinance or regional decree) that authorizes heat-alert contact, and that legal authority is not mentioned in the plan.

2.6.A Issue - Health data flow (aggregate EMS/ED counts) lacks DPIA and data-processor agreement specificity; health-system partners may face regulatory pressure to refuse

The plan specifies that hospitals and EMS will send 'daily aggregate heat-related EMS/ED counts' and 'no identifiable patient data' by 10:00 a.m. the next day. No Data Protection Impact Assessment (DPIA) is mentioned. The health-data loop decision (Decision 7) states 'MOU by Month 1 (2026-11-08)' but does not detail: (1) which ICD-10 codes or clinician judgments define 'heat-related' (a coded diagnosis is subjective and variable by clinician); (2) how aggregate counts are computed (daily total by hour? by ED section? by hospital?); (3) which data fields reach the city (only counts, or also triage category, age band, postal code?); (4) whether the health system is a joint controller (if the city specifies which counts and breakdowns) or a processor (if the health system autonomously decides); (5) how long aggregate data are retained (plan says 'deleted after 12 months,' but interim storage location and access controls are not specified); (6) whether the health-system MOU includes patient-safe harbor language (assuring staff that the city is not requesting re-identification or seeking to contact patients). Spanish health-data law (LSSP and regional hospital regulations) imposes strict confidentiality on clinical data, and hospital legal teams will likely refuse to sign an agreement that permits aggregate data to leave the hospital unless a Data-Processing Agreement (DPA) explicitly limits use. The current MOU outline (plan Section 7) is too vague.

2.6.B Tags

• DPIA-missing
• data-processor-vague
• health-data-definition-ambiguous
• hospital-legal-risk

2.6.C Mitigation

By Month 0.8 (2026-11-01), request the GDPR counsel to prepare: (1) a Data-Processing Agreement (DPA, 2-3 pages) for hospital/EMS data sharing, specifying that the health system is the data controller (not joint) and the city is the recipient (not processor); the DPA must state the city will not re-identify individuals, will not match data to other municipal records, and will delete aggregate counts within 12 months; (2) a one-page definition of 'heat-related' (e.g., ICD-10 codes T67.0-T67.9 plus clinician coding of 'heat exhaustion/stroke,' OR clinician judgment if no code, OR a heat-attribution algorithm agreed with the health system in advance); (3) a Data Protection Impact Assessment (DPIA, 4-6 pages, €8-12k to complete) assessing the privacy risks of daily aggregate-count sharing, the controls (aggregation, 12-month retention, no re-identification), and residual risks, concluding with a recommendation to proceed; (4) a hospital-specific addendum to the heat-helpline MOU (separate from the GP/pharmacy MOUs) that incorporates the DPA and DPIA findings and includes a 'safe harbor' clause: 'The city acknowledges that no identified patient data will be requested or used to contact individual patients.' Obtain hospital legal approval (allow 4-6 weeks) by Month 1.5 (2026-11-23). If a hospital refuses, identify an alternative data source: EMS alone can provide call-volume trends (easier to anonymize), or negotiate a quarterly aggregate (instead of daily) and delete after season-end.

2.6.D Consequence

If a hospital legal team discovers the MOU is non-compliant with LSSP and Spanish DPA guidance (expected outcome: 60-70% probability), they will request a formal DPA and DPIA before signing. This extends the Month 1 (2026-11-08) MOU signing by 4-8 weeks, pushing the health-data agreement to Month 2 (2026-12-08) or later. In the interim, the city loses daily EMS/ED counts, which are needed for the Month 4 (2027-02-08) evaluation baseline and for mid-season escalation decisions. Missing data by Month 1.5 (2026-11-23) means the evaluation cannot establish a valid baseline (required by Month 4 = 2027-02-08), which weakens the credibility of outcome claims and may prompt the funder to delay the €1.5M release pending re-baseline after Month 5 (2027-03-08). Operational impact: without daily EMS/ED counts, the incident commander cannot monitor whether call volume is rising due to heat (escalation trigger in the plan); the city defaults to alert-forecast triggers only, losing early-warning signals from the health system. If no count data reach the city by Month 6.8 (2027-05-02, start of season), the evaluation is unfeasible, and the Year-2 funding case collapses.

2.6.E Root Cause

The plan treats aggregate counts as 'not identifiable' and therefore low-risk, but Spanish health law treats even coded aggregate heat-related data as sensitive health information. Hospitals are required by LSSP Article 5 to implement strict access controls and minimize third-party disclosure. The MOU outlined in the plan does not meet hospital legal requirements: it names only the city as recipient, does not specify joint-control versus processor status, does not define 'heat-related' coding, and does not include data-minimization language (e.g., 'the city will not use counts to infer individual patients, will not attempt re-identification, and will not match counts to EMS dispatch logs that could reveal patient identity'). Hospital legal teams (especially in larger networks like Valencia) will flag this as non-compliant with their data-governance policies and may require a formal DPA and DPIA before signing.

---

3 Expert: Operational Resilience & Surge Planning Lead

Knowledge: Heat-wave surge planning, staff fatigue and scheduling, supply-chain contingency, volunteer management, multi-day event operations, incident command systems, service degradation under extreme events

Why: The plan identifies three critical operational risks: cool-season gate testing (no real heat until June), supply-chain compression (kits and transport by Feb–Apr), and staff fatigue during multi-day heat waves (15–25% service loss expected). This expert designs operational contingencies, staffing rotas, and surge protocols to protect the gates and service continuity, directly supporting the Month 2.5–4 (2026-12-23 to 2027-02-08) drill and gate-release pathway.

What: Co-design the drill protocol (Month 2.5 = 2026-12-23) and full-system drill script (Month 3.2 = 2027-01-14) to validate the four gates (center hours, contact success, pickup time, after-action closure) with high realism; specify supply-chain stress-test triggers (if any vendor >2-week delay by Feb 28 → activate backup, authorize premium); draft fatigue-management protocols (shift limits, rest-day enforcement, counseling access) for the Month 3 (2027-01-08) training.

Skills: Incident-command systems, surge-capacity planning, volunteer fatigue and scheduling, supply-chain risk and contingency, service-continuity testing, operational stress drills

Search: heat wave surge planning coordinator, operational resilience municipal services, multi-day event fatigue management, supply chain contingency heat

3.1 Primary Actions

• By Month 0.5 (2026-10-23): Secure written funder pre-approval for the partial-release rule (€750k at Month 4 = 2027-02-08 if gates are unmeasurable/drill-only, remainder after May re-test) and a heat-event contingency (€100k additional release if May-June summer is mild). Request funder confirmation in email and lodge copy with mayor and PMO.
• By Month 0.5 (2026-10-23): Engage a specialist GDPR law firm (€15-30k budget) to pre-review the intermediary-held-list model and draft partner data-processing agreements. Obtain a written legal opinion by Month 1 (2026-11-08) confirming GDPR compliance and confirming no DPIA is required because personal data does not transfer to the city.
• By Month 0.3 (2026-10-17): Conduct a rapid supplier-capacity survey (email 5-8 shading/blind/fan suppliers: stock, lead time for 600-800 units, expedite cost for ≤8-week delivery). By Month 0.7 (2026-10-29), issue preliminary procurement specs and place non-binding purchase intentions with top 2 suppliers. By Month 1.2 (2026-11-14), place binding first-tranche orders split 50-50 across primary + backup suppliers to avoid single-point failure.
• By Month 1 (2026-11-08): Establish a Fatigue & Safety Task Force (incident commander, HR coordinator, union representative, occupational health lead). Publish a written fatigue-management protocol by Month 2 (2026-12-08) specifying max 3 consecutive alert shifts, mandatory 2-day breaks, peer-debrief, occupational health screening and 24-hour counseling access post-incident.
• By Month 0.8 (2026-11-01): Launch volunteer driver recruitment at 60 targets (to achieve 40 vetted). Recruit starting Month -1 (2026-09-08, before project start) to create a pre-project pipeline. Name a volunteer-safety lead (0.25 FTE) responsible for incident tracking and weekly contact during alert season.
• By Month 1.2 (2026-11-14): Execute facility-use MOUs with ≥8 of 10 cooling-center sites specifying hours, staffing, security, liability, and accessibility remediation plan. Conduct accessibility audit by Month 1.5 (2026-11-23); ensure ≥50% of planned capacity is fully accessible by May or defer to July.
• By Month 1.2 (2026-11-14): Negotiate and lock in a taxi standby-retainer contract (€50-80k capped, ≥10 vehicles within 20 min, ≥3 wheelchair-capable) with legally binding 48-hour cancellation terms. Confirm backup supplier relationships for transport if volunteer recruitment falls short.
• By Month 1.5 (2026-11-23): Finalize and execute data-processing agreements with 4-6 main partner organizations (housing associations, social services, NGOs, pharmacies). Brief 50-80 partner staff on GDPR, consent, and confidentiality by Month 2 (2026-12-08).

3.2 Secondary Actions

• By Month 0.5 (2026-10-23): Request verified baseline data from municipal hospital, EMS, and primary-care network: 3-year history of heat-related ICD-10 coding, call volumes, ED visit patterns by month and age group. Flag any coding inconsistencies to health partners for standardization before Month 2 (2026-12-08).
• By Month 1 (2026-11-08): Conduct a focus-group test of the 'Hot Night Guarantee' value proposition (call within X min, ride within 45 min, cooled home) with 20-30 high-risk residents (65+, living alone, poor housing). Measure enrollment intent and refine messaging for trusted messengers.
• By Month 1 (2026-11-08): Confirm the local migrant language mix via municipal demographic data (candidates: Arabic, Romanian, Portuguese). Commission language-access cost breakdown (interpretation services vs. paid ambassadors) and recruit 8-12 paid ambassadors from migrant associations by Month 2 (2026-12-08).
• By Month 1 (2026-11-08): Map existing home-care, social services, and NGO outreach infrastructure to identify 4-6 intermediary organizations willing to hold contact lists and make enrollment calls on the city's behalf. Estimate their call capacity (calls/day during alert season) and secure MOUs by Month 1.5 (2026-11-23).
• By Month 1.5 (2026-11-23): Finalize and brief all outreach staff (25-35 people) and partner street-contact teams on heat-illness escalation protocols (recognition, decision rules for 112 vs. home management, nurse triage line). Require written test (≥80% pass) and logged attendance.
• By Month 1.5 (2026-11-23): Design and conduct a mock heat-helpline drill (simulate 8-12 transport requests and 3-5 escalations over 2 hours). Test dispatch integration, center occupancy tracking, and operator readiness. Correct any gaps in scripts or procedures before the Month 2 (2026-12-08) gate.
• By Month 2 (2026-12-08): Establish a daily health-data loop: MOU signed with hospital/EMS for daily aggregate heat-related call/visit counts by 10:00 a.m. next day. Validate data feed during a 2-week pilot (Month 1.8 = 2026-12-02). Launch a simple shared dashboard (secure spreadsheet) accessible to incident commander, health coordinator, and dispatch supervisor.
• By Month 2.5 (2026-12-23): Finalize the full-system drill protocol, including test locations, simulation vignettes (heat illness, transport requests, center overcrowding, staff absence, misinformation), timing, and success criteria. Share with partners for sign-off.
• By Month 3 (2027-01-08): Increase planned staff reserve from 20-30% to 40% (hire 60 FTE, operate 43) by extending hiring cohorts or recruiting part-time seasonal staff from retirees and charity networks. Establish occupational-health partnership for pre-season fitness and mid-season fatigue surveys.
• By Month 9 (2027-07-08): Audit partner consent records, privacy-notice logs and any breach incidents; verify compliance with data-protection agreements. Report findings to GDPR counsel and data protection authority if required. Plan data deletion (≤30 days after Month 12 = 2027-10-08) unless re-consent is secured for Year 2.

3.3 Follow Up Consultation

"The next consultation (Month 2 = 2026-12-08 readiness gate review) should focus on: (1) Funder communication—has the partial-release rule been accepted in writing? If not, escalate immediately. (2) Supply-chain status—have first-tranche kits been ordered? If orders are delayed by >2 weeks, activate backup suppliers now. (3) Staffing pipeline—how many volunteers are vetted? If <15 by Month 1.5 (2026-11-23), scale the taxi retainer immediately and accept the €150-250k cost. (4) Drill readiness—what gaps were found in the mock helpline and accessibility audit? (5) Partner engagement—are all intermediary-held-list MOUs signed and staff briefed? If not, outreach reach will slip below the 60% gate. Finally, request a written go/no-go recommendation from the incident commander by Month 2.5 (2026-12-23) confirming whether the Month 3.2 (2027-01-14) drill should proceed as planned or be delayed if any critical infrastructure is incomplete."

3.4.A Issue - Cool-Season Gates Cannot Be Validated on Real Outcomes—Drill Evidence Alone Is Brittle

The Month 2 (2026-12-08) readiness gate and Month 4 (2027-02-08) scale gate fall entirely in the cool season (Months 0-4 = October 2026–February 2027). Heat events and multi-day surges will not occur until Months 6-11 (2027-04-08 to 2027-09-08). This means all gates rely on tabletop exercises, drills and simulated demand, not real operational performance under actual thermal stress. Funders, city councils and peer cities will view this as weak evidence. A failed real-world response in June will not be caught by April metrics. The plan acknowledges this ('drills are the evidence') but does not adequately prepare for funder rejection or the €200-400k cash-flow gap if release is delayed.

3.4.B Tags

• gate-validation-risk
• cool-season-timing
• funder-credibility
• cash-flow-gap

3.4.C Mitigation

Immediately (by Month 0.5 = 2026-10-23) request explicit written funder approval for the partial-release rule (€750k at Month 4 = 2027-02-08 if evidence is insufficient, remainder after May re-test). Negotiate a 'heat-event strike clause': if the Month 5-6 (2027-03-08 to 2027-04-08) summer is mild, release €100k additional contingency specifically for that scenario. Redefine the drill success criterion to include 30-50 real transportation requests from actual frail residents (not just test cases), and 5-10 real welfare calls to enrolled people during a 'amber weather' advisory to test partner call-center readiness under mild heat. Document the funder's acceptance in writing and lodge a copy with the mayor and PMO.

3.4.D Consequence

Without written funder pre-agreement, a cool May-June and failed April gates could trigger the funder to withhold the €1.5M, creating a €350-650k cash gap (€200-400k shortfall + the €160k tranche-1 contingency exhaustion). The city would then be forced to choose: cut 50% of planned interventions, axe the home-kit program, shift to taxi-only (€150-250k draw), or halt operations mid-season. This would damage the city's credibility, erode partner trust, and leave the most vulnerable residents unserved during the actual heat peak.

3.4.E Root Cause

The calendar constraint (project start October 2026, gates in December and February) forces gate testing before the natural heat season. The plan assumes funders will accept drill evidence, but this assumption is not negotiated upfront with the funder. No contingency plan exists if the funder refuses partial release and demands May/June real-world data before releasing €1.5M.

3.5.A Issue - Staffing and Volunteer Recruitment Timeline Is Compressed and Fatigue Risk Is Underestimated

The plan requires 43 FTE at peak (18 at cooling centers alone) plus 30-50 vetted volunteer drivers, all in place by Month 6.7 (2027-04-29) for a season that runs Months 6.8-11.8. Vetting of volunteers takes 4-8 weeks per person (background check, insurance, training). The hiring plan is compressed into three cohorts (Month 3, 4, 5 = January–March), with 40% of all staff hired in Month 3 and 40 (2027-01-08, 2030-02-08)% in Month 4 (2027-02-08). Multi-day heat waves (Months 7-9 = 2027-05-08 to 2027-07-08) will drive fatigue, absenteeism and burnout: the plan assumes 15-25% service degradation but holds only a 20-30% staff reserve, which is insufficient for a distributed network of 10 sites plus 50+ volunteers. No fatigue-management protocol (shift rotation, peer support, occupational health) is documented by name or with assigned ownership. Street-contact and outreach teams face particular risk: they work in heat, often encounter distressed people, and may face assault or safeguarding incidents with minimal support.

3.5.B Tags

• staffing-compression
• volunteer-fatigue
• surge-staffing-reserve
• staff-safety-protocols

3.5.C Mitigation

By Month 1 (2026-11-08), establish a Fatigue & Safety Task Force (commander, HR coordinator, union representative if applicable, occupational health lead). Publish a written fatigue-management protocol by Month 2 (2026-12-08) specifying: max 3 consecutive alert-day shifts, mandatory 2-day break between shifts, peer-debrief 30 min post-shift, occupational health screening pre-season and after multi-day events, and access to counseling within 24 h post-incident. Increase the staff reserve from 20-30% to 40% (hire 60 FTE, operate 43) to absorb absences and burnout. Partner with a local university occupational-health clinic for free pre-season fitness screening and mid-season fatigue surveys. For volunteers, target 60 recruits (to achieve 40 vetted) and begin recruitment at Month -1 (2026-09-08, before project start) to create a pipeline. Name a volunteer-safety lead (0.25 FTE) responsible for incident tracking, safeguarding training, and weekly contact during alert season.

3.5.D Consequence

If staffing falls short by 20-30% during a sustained multi-day heat wave (Months 8-9 = 2027-06-08 to 2027-07-08), cooling-center hours will drop below the 80% gate by 15-20%, transport pickup times will exceed 45 minutes, and outreach teams will miss welfare calls to enrolled residents. Staff assault, burnout, and media coverage of exhausted teams will trigger reputational damage. Turnover from burnout will force rehiring mid-season at premium rates (20-30% wage premium, estimated €80-120k cost), which may exceed available contingency. By the critical heat-mortality period (July–August), the response will be degraded below design intent.

3.5.E Root Cause

The brief specifies a 'pragmatic' pilot that avoids aggressive scaling, but the staffing plan attempts to run 10 cooling centers, 50 volunteer drivers, 6 dedicated outreach staff and a dispatch center with a skeleton crew that was hired on a compressed 3-month timeline. Fatigue is acknowledged ('limit shifts to 3-4 consecutive days') but no enforcement mechanism, peer-support structure or occupational-health partnership is named. Volunteer recruitment assumes a 50% success rate ('30-50 volunteers') without market evidence. Outdoor and street-contact work (hottest, highest-risk conditions) has the least staffing buffer.

3.6.A Issue - Supply-Chain Compression and Procurement Bottleneck Risks Are Not Backed by Supplier Pre-Engagement

The plan requires €800k in home kits (shading, fans, thermometers, hydration supplies) and a taxi standby retainer (€80k) to be contracted and the first 30-40% of kits ordered by Month 1.2 (2026-11-14) and fully ordered by Month 2 (2026-12-08). This demands procurement specifications to be finalized by Month 0.8 (2026-11-01)—within 3 weeks of project start, today (2026-10-08). Lead times for exterior-shading materials, reflective blinds and specialized window fans can be 6-12 weeks in Spain, especially if custom-fitted for top-floor flats. The plan names 'backup suppliers' but provides no evidence of pre-engagement, capacity confirmation, or pricing. A 4-week delay in first-tranche orders (slip to December) means kits arrive in April instead of February, shifting installation past the May heat peak. The €150-250k 'taxi-only fallback' and the €20-50k expedite premium are mentioned as options but no decision pathway or trigger is specified.

3.6.B Tags

• procurement-lead-time
• supplier-engagement
• kit-delivery-slippage
• contingency-clarity

3.6.C Mitigation

By Month 0.3 (2026-10-17), conduct a rapid supplier-capacity survey (email to 5-8 regional shading, blind and fan suppliers, asking: do you carry stock, lead time for 600-800 units, expedite cost if ≤8 weeks?). By Month 0.5 (2026-10-23), issue preliminary procurement specs (10 pages max: shading type, reflective-blind spec, fan safety/directional-only models, thermometer/hygrometer ranges, delivery schedule). By Month 0.7 (2026-10-29), place non-binding purchase intention with top 2 suppliers (e.g., 'we intend to order 2,000 units Q1 2027; can you commit to delivery Feb 28 at [price]?'). By Month 1.2 (2026-11-14), place the binding first-tranche order with primary + backup supplier split (600 units each from two suppliers to avoid single-point failure). Designate a procurement lead with decision authority to activate backup suppliers or expedite premium (cap €50k) without a second approval. Document all supplier communications in a log with escalation triggers (>2-week slip = activate backup).

3.6.D Consequence

If procurement slips by 4+ weeks, first-tranche kits will arrive in April instead of February, pushing installation to June-July when heat events are at peak frequency. Outreach teams will be unable to offer a completed home kit during enrollment, reducing enrollment uptake by 20-30% (estimate). The June-July heat wave will find 30-50% of target homes unprotected, directly harming vulnerable residents during the highest-risk mortality window. A reputational incident (news story: 'City Fails to Install Cooling Kits Before Heat Wave') will undermine trust in the program and funder confidence for Year 2 scaling. The €150-250k fallback (cutting kits from 2,000 to 1,000-1,500) will not be triggered in time if the slip is discovered late, and the city will face a €200-350k unbudgeted cost to expedite.

3.6.E Root Cause

The procurement timeline is driven by the Month 2 (2026-12-08) gate (ready to deliver, kits on hand) and the May heat season, but supplier relationships are not pre-negotiated. The plan assumes 'existing municipal framework agreements' exist for kits and transport, but this is not verified. No supplier capacity survey has been conducted; no quotations have been requested. The plan also conflates 'specifications finalized' with 'orders placed': specs can take 4 weeks, tender 3-4 weeks, and contracting 2-3 weeks, consuming the entire 7-week runway from Month 0 (2026-10-08) to Month 1.2 (2026-11-14).

---

4 Expert: Transport Access & Mobility Innovation Consultant

Knowledge: Accessible transport for mobility-limited residents, taxi and paratransit contracting, volunteer driver programs, pickup-time optimization, wheelchair-user accessibility, shared mobility models, transport equity metrics

Why: The 45-minute pickup gate depends entirely on the transport model (40 volunteers + €80k taxi retainer). The plan is exposed here: if <20 volunteers recruit by Month 1.5 (2026-11-23), the retainer scales up but budget headroom is unclear; wheelchair users are named in the gate (≥5 of ≥30 requests) but no modeling of their longer pickup times exists. This expert validates the dispatch design, tests realism, and advises whether the volunteer-plus-taxi hybrid can meet the gate under peak load and multi-day fatigue.

What: Model transport demand scenarios (advisory vs alert vs emergency levels) and simulate dispatch performance under fatigue (simulate 10 alert days, 30 requests/day, 5 wheelchair users/day, 20% volunteer absence); calculate volunteer-recruitment shortfall exposure (if only 15 recruits vs 40 target, estimate cost and gate impact); propose pickup-time optimization (fixed shuttle loops vs on-demand, pre-position vehicles near high-need housing blocks); deliver findings and gate-readiness assessment by Month 3 (2027-01-08).

Skills: Transport modeling and simulation, volunteer-driver vetting and management, taxi/paratransit contract negotiation, wheelchair-user accessibility standards, dispatch optimization, pickup-time metrics

Search: accessible transport mobility coordinator, volunteer driver program management, wheelchair user transport equity, taxi paratransit contracting, dispatch optimization

4.1 Primary Actions

• By Month 1.2 (2026-11-14), obtain detailed taxi operator cost and response-time data for 15, 20, 30 and 45-minute service tiers; model dispatch using a queue simulator assuming 100-150 requests/alert day, 40 active volunteers and 15-minute median drive; redefine the 45-minute gate to exclude wheelchair users (separate <35-minute target for mobility-limited priority) or increase taxi budget to €120-150k and reduce home-kit scope to 1,200 homes.
• By Month 0.3 (2026-10-17), issue public recruitment call targeting 60-70 volunteer drivers with intake deadline Month 1.5 (2026-11-23); hire a dedicated Volunteer Coordinator (1.0 FTE, Month 0 = 2026-10-08 through 12) and Safeguarding Lead (0.5 FTE, Month 0 = 2026-10-08 through 12); implement rolling vetting batches (weekly police submissions, expected 10-14 day turnaround) and safeguarding cohort training (8 people, 2 hours, fortnightly from Month 1 = 2026-11-08) with written test.
• By Month 1 (2026-11-08), conduct a rapid enumeration survey of 200-300 households in three sample neighborhoods to measure actual reach of each intermediary channel (GPs, pharmacies, housing associations, NGOs); calculate coverage uplift needed to achieve 20-25% of target population (8,000-12,000 residents); add a door-knock and ambassador pathway (50-80 paid ambassadors, €100-150/month) to reach isolated, top-floor and migrant residents missed by intermediary-only model.
• By Month 1.5 (2026-11-23), implement a consent-validation protocol: intermediaries log each consent call (name, date, language, transport preference); city samples 50-100 consents monthly for callback verification; define 'active enrollment' as documented consent within the last 30 days, not historical contact counts.

4.2 Secondary Actions

• By Month 1.5 (2026-11-23), finalize volunteer no-show protocol: if a committed driver does not appear within 15 minutes of dispatch on an alert day, mark unavailable for remaining alert, require post-alert debrief before re-deployment; model expected availability by Month 3.5 (2027-01-23) assuming 20-25% attrition and brief funder on taxi-scale-up trigger (if active roster <20 by Month 7 = 2027-05-08, escalate retainer proportionally).
• Establish an escalation protocol for volunteer-driver safeguarding: safeguarding lead receives all incident reports same-day, conducts supervisor debrief within 2 hours, arranges occupational-health counseling within 24 hours; cluster >2 incidents in one month triggers mandatory retraining and funder notification.
• Pilot a mobile transport option (e.g., shuttle loops between high-concentration housing blocks and anchor refuges on declared alert days) to reduce individual on-demand trips by 20-30% and lower mean pickup time variability, especially for mobility-limited residents.
• By Month 4 (2027-02-08), commission an independent evaluation of intermediary-held-list reach and bias (comparing enrolled population to census by age, housing type, language, deprivation); publish findings and adjust Year 2 outreach strategy.
• Create a contingency volunteer reserve pool of 15-20 (50% more than active roster) recruited and vetted by Month 3 (2027-01-08), activated only on declared Level 3 alerts or if active roster falls below 20 drivers.

4.3 Follow Up Consultation

At the next consultation, bring: (1) Preliminary taxi-operator cost quotes and response-time commitments for the 15, 20, 30 and 45-minute service tiers (Month 1.2 = 2026-11-14 target); (2) Rapid enumeration survey results and intermediary-channel reach analysis showing coverage gaps and uplift needed (Month 1 = 2026-11-08); (3) Volunteer recruitment intake numbers and vetting pipeline status by Month 1.5 (2026-11-23) and Month 2 (2026-12-08); (4) Dispatch simulator model output (mean pickup time by request type, volunteer availability, alert level) to validate or adjust the 45-minute gate; (5) Draft consent-validation protocol and pilot results from intermediary callbacks (sample 50-100, verify true active enrollment). These inputs will clarify whether the transport target is realistic, whether volunteer safeguarding capacity is sufficient, and whether intermediary-only outreach is achieving meaningful coverage of isolated, high-risk residents.

4.4.A Issue - 45-minute transport target is unachievable without wheelchair-user degradation or budget overrun

The plan assumes 40 volunteer drivers (30-50 range) plus a €80k taxi retainer (≥10 vehicles) can deliver <45-minute mean pickup including ≥5 wheelchair users per drill. Analysis: 40 volunteers active on alert days realistically cover 30-35 (fatigue, illness, competing calls). With 5-8 concurrent transport requests typical at Month 3.2 (2027-01-14) drill scale, each wheelchair-accessible request (requiring vehicle, transfer time, boarding wait) adds 12-18 minutes to non-wheelchair users. Volunteer dispatch has 10-15 minute radio/coordination lag. At surge (100+ requests across a multi-day event), the queue backs up 60-90 minutes. The taxi retainer's 20-minute threshold becomes 45+ minutes by booking and vehicle availability. Wheelchair users will breach 45 minutes by Month 8-9 (2027-06-08 to 2027-07-08) when demand peaks, or the taxi cost scales to €150-200k to guarantee sub-30-minute response.

4.4.B Tags

• transport-target-unrealistic
• wheelchair-access-degradation
• surge-capacity-shortfall
• volunteer-reliability-gap
• budget-creep

4.4.C Mitigation

Redefine the 45-minute gate as an average excluding wheelchair-users (to be measured separately with a <35-minute target for mobility-limited priority cases). Model dispatch using a simple queue-and-resource simulator: assume 100-150 requests over a 12-hour alert day, 40 active volunteers (30 active + 10 surge reserve), 10-minute dispatch lag, 15-minute median drive, 8 minutes wheelchair boarding. Output: mean 52 minutes overall, 32 minutes for priority wheelchair users. Commission a taxi operator to provide detailed cost and response-time data for 15, 20, 30, and 45-minute response tiers; set contractual response tiers tied to alert level (Level 2 = 30 min, Level 3 = 20 min). By Month 1.2 (2026-11-14), obtain written taxi operator commitments including surge premium (€5-10 per vehicle-minute above baseline) and a maximum-response-time service credit. Build a volunteer reserve pool of 15-20 (50% more than active roster) recruited and vetted by Month 3 (2027-01-08), activated only on declared Level 3 alerts.

4.4.D Consequence

If the 45-minute target remains unmodified and untested with realistic dispatch modeling, Month 4 (2027-02-08) gate will likely fail (mean >50 minutes under drill stress-test conditions), causing non-release of €1.5M scale funding and leaving the program underfunded mid-season. Alternatively, if taxi costs scale to €150-200k to meet the target, home-kit budget is cut to 1,000-1,200 homes (from 2,000), increasing equity disparity and reducing uptake. Worst case: wheel-chair users experience mean 60-90 minute waits by Month 8-9 (2027-06-08 to 2027-07-08), creating liability and reputational damage if a mobility-limited resident's heat illness worsens during transport delays.

4.4.E Root Cause

The plan conflates best-case drill conditions (30-50 requests, organized groups, light volunteer load, no competing emergencies) with real-season conditions (300-500 requests, scattered, competing with municipal/EMS duties, multi-day fatigue). Volunteer driver reliability research shows 15-25% attrition mid-season; the plan has no reserve pool or surge contract. The 45-minute gate was set without modeling dispatch overhead or wheelchair-specific access time. No internal service-level differentiation: mobility-limited residents should be prioritized (30-min target) at the cost of accepting 60-90 minutes for walking-capable residents.

4.5.A Issue - Volunteer driver recruitment and safeguarding timelines are compressed and under-resourced

The plan targets 40 volunteer drivers (30-50 range) with ≥20 vetted by Month 2 (2026-12-08) and the rest by Month 3 (2027-01-08). Vetting includes background checks (10-14 days via police), insurance verification (7-10 days), safeguarding training (3 hours), and dispatch-system orientation (2 hours per person). Realistic throughput: ~2-3 recruits per week vetted fully. To reach 20 by Month 2 (2026-12-08) means starting recruitment in Month 0.3 (2026-10-17) and closing intake by Month 1.5 (2026-11-23). The plan says recruitment starts Month 0 (2026-10-08) but does not specify a closure date, intake method, or recruitment-lead FTE. Safeguarding incidents (assault during transport, inappropriate contact with vulnerable residents, vehicle accident causing injury) require incident reporting, occupational-health follow-up and retraining; the plan assigns a 0.25 FTE safeguarding lead but no deputy or escalation protocol if multiple incidents cluster. Volunteer attrition research shows 20-30% mid-season drop during fatigue-heavy multi-day events; no contingency roster is described.

4.5.B Tags

• volunteer-recruitment-lag
• vetting-bottleneck
• safeguarding-under-staffed
• attrition-unmanaged
• incident-response-gap

4.5.C Mitigation

Designate a dedicated Volunteer Coordinator (1.0 FTE, Month 0 = 2026-10-08 through Month 12 = 2027-10-08) and a Safeguarding Lead (0.5 FTE, Month 0 = 2026-10-08 through Month 12 = 2027-10-08). By Month 0.3 (2026-10-17), issue a public call targeting retirees, charity/faith workers and young professionals via municipal website, GP surgeries, NGO networks and community centers; set initial recruitment target of 60-70 (to account for 25-30% attrition), intake deadline Month 1.5 (2026-11-23). Implement a rolling vetting pipeline: batch background checks (weekly submission to police, expected 10-14 day turnaround); pair insurance checks with recruitment (pre-qualify drivers with personal insurance before intake, no delays). Conduct safeguarding training in cohorts (8 people, 2 hours each) fortnightly from Month 1 (2026-11-08) onward; require written test (≥80% pass). Establish a no-show protocol: if a volunteer commits to an alert day and does not show within 15 minutes of dispatch, mark as unavailable for the remaining alert, do not re-deploy without a post-alert debrief. By Month 3.5 (2027-01-23), model expected availability (assuming 20-25% attrition by Month 8 = 2027-06-08) and brief funder on reduced capacity or recommend taxi-scale-up trigger (if <20 volunteers in active roster by Month 7 = 2027-05-08, escalate retainer).

4.5.D Consequence

If recruitment closes late (Month 2 = 2026-12-08 instead of Month 1.5 = 2026-11-23), only 12-15 volunteers will be fully vetted by Month 2 (2026-12-08), forcing immediate taxi-retainer scale-up (€100-150k additional) and reducing home-kit budget. If safeguarding staffing is not increased, mid-season incident clustering (e.g., 2-3 assault reports in Month 8 = 2027-06-08) will overwhelm a 0.25 FTE lead, causing delayed incident response, volunteer morale collapse and potential reputational damage. Volunteer attrition by Month 8-9 (2027-06-08 to 2027-07-08) without a contingency roster will drop active drivers to 25-30, extending mean transport time from 45 minutes (drill) to 60-75 minutes (real season), failing the gate retroactively and creating media exposure.

4.5.E Root Cause

The plan underestimates the total FTE cost of volunteer management (vetting, on-boarding, dispatch coordination, incident handling, retention). A single safeguarding lead (0.25 FTE) is insufficient for 40 volunteers across a 6-month alert season; literature suggests 1 FTE per 15-20 active volunteers. Background-check delays are common in Q4 (holiday season); no contingency for slow police-records units is described. The plan does not specify what happens if a volunteer is vetting-complete but unavailable on a declared alert day (no show-up rate assumption).

4.6.A Issue - Intermediary-held list model reaches only ~9% of high-risk seniors and leaves isolated residents undetected

The plan relies on housing associations, social services, NGOs and pharmacies to identify and contact high-risk residents without personal data moving to the city. Target: 3,000 enrolled by Month 7 (2027-05-08), ≈9% of estimated 34,000 seniors 65+. Research on intermediary-held registries shows typical coverage 5-15% of target populations because: (1) people already known to services (GP, social care, housing) are over-represented; (2) isolated, living-alone seniors with no prior contact are missed; (3) pharmacies reach repeat customers only, missing those who do not fill prescriptions during the survey window; (4) migrant residents distrust formal intermediaries. The plan counts outreach 'attempts' (5,000/month in season) but does not distinguish between successful enrollment (consenting to be called on alert days) and one-time contact (a flyer handed out). No validation sampling is proposed: the plan cannot measure if the 3,000 'enrolled' target reflects real consent or inflated contact logs.

4.6.B Tags

• coverage-gap
• isolated-residents-missed
• enrollment-validation-weak
• intermediary-bias
• equity-disparity

4.6.C Mitigation

Reframe the 3,000 enrollment target as a floor, not a cap. By Month 1 (2026-11-08), conduct a rapid enumeration survey of 200-300 households in three sample neighborhoods (high deprivation, mixed, affluent) to establish actual reach of each intermediary channel (GPs, pharmacies, housing associations, NGOs); calculate uplift needed to reach 20-25% coverage (8,000-12,000 residents if baseline is 5-7%). Add a low-cost door-knock and sentinel pathway: recruit 50-80 'heat ambassadors' (retired nurses, social workers, bilingual community members) paid €100-150/month to distribute flyers in target blocks (top-floor/elderly concentrations identified via postal data or municipal energy audits) and report back on uptake (Month 1-2 = 2026-11-08 to 2026-12-08). Partner with NGOs to conduct targeted outreach to migrant and unhoused groups monthly (not relying on one-time intermediary referral). Implement a simple consent-validation protocol: intermediaries log each consent call (date, name, language, transport yes/no, cooling center preference); city samples 50-100 consents per month (5-10%) via callback to verify active consent and update contact info (Month 7-12 = 2027-05-08 to 2027-10-08). Define 'active enrollment' as documented consent obtained within the last 30 days, not historical contact counts.

4.6.D Consequence

If coverage remains at 9% (3,000 enrolled from 34,000 seniors), the program reaches a biased sub-population (those already connected to services) and misses isolated, solo-living, top-floor residents who face the highest mortality risk during hot nights. When a multi-day heat event occurs (Month 8-9 = 2027-06-08 to 2027-07-08), the 25,000 unreached seniors aged 65+ depend entirely on passive cooling advice (flyers, radio, website) which research shows is ineffective for isolated offline residents; preventable heat-illness cases and deaths may occur that the program could have addressed. Equity metrics (coverage by deprivation index, housing type, migration status) will reveal large gaps, undermining the program's credibility with funders and other EU cities. The 60% outreach contact-success gate will appear to pass (3,000 enrolled ÷ 5,000 attempts = 60%) but may reflect inflated contact logs, not real preparedness.

4.6.E Root Cause

The plan assumes intermediary-held lists are GDPR-compliant (avoiding personal data transfer to the city), which is true, but conflates GDPR compliance with coverage. Intermediaries are motivated to report high contact numbers to funders, but not to validate consent or follow-up use. The 9% coverage reflects the design's fundamental tension: the more the city avoids holding personal data, the less able it is to verify reach or to identify who is missing. No building-level canvassing or sentinel-recruitment is planned (those were rejected as 'too aggressive' in Decision 3), leaving top-floor residents in non-affiliated housing blocks unreached. Migrant and recent-arrival residents are named priority groups but no language-specific enrollment pathway is described.

---

5 Expert: Volunteer Management & Safeguarding Lead

Knowledge: Volunteer recruitment and retention, background-check protocols, safeguarding incident response, insurance and liability frameworks, volunteer fatigue management, vetting workflows, multi-month retention under seasonal pressure

Why: The plan requires 30-50 volunteer drivers vetted and operational by Month 2-3 (2026-12-08 to 2027-01-08), with no demonstrated recruitment pipeline or safeguarding protocols. The risk mitigation cites 'clear off-duty procedures if staff are threatened or assaulted' but does not detail incident response, counseling, or liability coverage. If recruitment stalls or a safeguarding breach occurs mid-season, the 45-minute transport gate collapses and reputational damage follows. This expert validates the vetting timeline, designs incident protocols and ensures insurance adequacy.

What: By Month 0.5 (2026-10-23), co-design the volunteer recruitment campaign (target 40, launch Month 0 = 2026-10-08) and specify vetting steps: background check turnaround (4-8 weeks/person), insurance requirements (personal vehicle or municipal policy), and safeguarding training (3-hour de-escalation module). By Month 1 (2026-11-08), establish an incident-response SOP: assault/threat triggers same-day supervisor debrief, 24-hour occupational-health counseling, and a safeguarding log reviewed fortnightly. By Month 1.5 (2026-11-23), audit insurance coverage (liability, assault trauma, vehicle damage) and confirm that the recruitment target (20 by Month 2, 40 = 2026-12-08, 2030-02-08 by Month 3 = 2027-01-08) is on track; if <20 in pipeline, escalate to incident commander and activate taxi-retainer scaling.

Skills: Volunteer vetting and background-check processes, safeguarding and incident reporting, insurance broker relationship, fatigue-informed rostering, trauma-informed peer support, recruitment-campaign design and tracking

Search: volunteer coordinator safeguarding training, background check vetting procedures, volunteer incident response protocol, volunteer fatigue management, municipal volunteer insurance

5.1 Primary Actions

• By Month 0.1 (2026-10-11), obtain written funder acceptance of drill-based evidence for the Month 4 (2027-02-08) gate and explicit endorsement of the 50% partial-release rule (€750k if unmeasurable). If the funder will not commit, secure a contingent credit line (€200–400k) from the municipality by Month 1 (2026-11-08) to cover cash-flow gaps.
• By Month 0.2 (2026-10-14), launch volunteer driver recruitment with a detailed pipeline plan (target 50 recruits, weekly cohorts starting now, 4–6 week vetting, 25% attrition assumption). Hire a 0.5 FTE volunteer coordinator to track cohorts, absences and fatigue. Define operationally: shift caps ≤3 consecutive alert days + 1–2 mandatory rest days per driver.
• By Month 0.5 (2026-10-23), commission a rapid social-network survey (200–300 high-risk residents) to identify which intermediaries reach whom and which 'isolation islands' exist (unhoused, private-rental, no service touch). By Month 1 (2026-11-08), design and cost a parallel building-level canvassing track for top 15–20 high-deprivation blocks, targeting ≥15% of enrollment from direct outreach by Month 7 (2027-05-08).
• By Month 0.3 (2026-10-17), finalize and commit to a written drill protocol and gate evidence criteria: ≥100 transport requests, ≥200 outreach contact attempts, ≥2,000 center-hour activations in Month 3.2 (2027-01-14) drill satisfy the Month 4 (2027-02-08) gate; <100 requests = re-test required. Brief the incident commander, CFO and funder monthly on progress.
• By Month 0.8 (2026-11-01), issue detailed procurement specifications for cooling kits, transport retainer and refuge fit-out to at least 3 suppliers per category; request quotes and lead-time confirmation by Month 1 (2026-11-08). Place first-tranche 30–40% kit order by Month 1.2 (2026-11-14); pre-qualify backup suppliers with expedited-delivery premium (10–15%) and activate if primary supplier misses February delivery.
• By Month 1 (2026-11-08), execute the taxi/accessible-transport standby-retainer contract (capped €80k, ≥10 vehicles within 20 minutes, ≥3 wheelchair-capable). Embed the retainer scale-up trigger in writing: if volunteer recruitment falls below 15 vetted by Month 1.5 (2026-11-23), increase retainer negotiation to cap €120k or shift taxi-only model for contingency.
• By Month 1.2 (2026-11-14), confirm completion of cooling-center facility-use MOUs (≥8 of 10 sites), staffing hire start for 12–18 part-time managers and assistants, and accessibility audit plan. Schedule remediation completion by Month 1.5 (2026-11-23) for any gaps <€10k and <4 weeks; categorize sites as 'fully accessible' or 'defer to July' and ensure ≥50% of planned capacity is fully accessible by May.
• By Month 1.5 (2026-11-23), complete vetting of first cohort of ≥20 volunteer drivers (background check, insurance, 2-hour safeguarding training). Finalize and execute all partner data-processing agreements (housing associations, social services, NGOs, pharmacies) with signed MOUs specifying lawful basis for contact, data retention (one season only), and breach notification (48-hour reporting). Brief 50–80 partner staff on GDPR and confidentiality by Month 2 (2026-12-08).

5.2 Secondary Actions

• By Month 0.5 (2026-10-23), engage a specialist GDPR law firm (€15,000–30,000) to pre-review the intermediary-held-list model and draft template MOUs. Obtain written legal opinion confirming GDPR compliance by Month 1 (2026-11-08).
• By Month 1 (2026-11-08), confirm local demographics (verified 65+ population, living-alone prevalence, top-floor housing concentration) from municipal data and census; audit baseline heat-related EMS calls and ED visits (80–120 call estimate, 15–25 excess-death estimate) from hospital and EMS records; confirm heat-coding practice with clinicians.
• By Month 1 (2026-11-08), finalize alert-trigger thresholds (proposed: Level 1 ≥33°C/≥20°C; Level 2 ≥35°C/≥22°C; Level 3 same + ≥3 days) in writing with the national meteorological service (AEMET) and incident commander; obtain approval for declaration procedures and authority delegation.
• By Month 1.2 (2026-11-14), hire the 0.5 FTE HR coordinator and partner-liaison officer (or assign to existing staff) with clear accountability for hiring, vetting, fatigue tracking and partner engagement. Establish a weekly staffing and pipeline status report (submitted to the incident commander by Fridays).
• By Month 1.5 (2026-11-23), identify 4–6 non-official languages most common in Castellón de la Plana (candidates: Arabic, Romanian, Portuguese) and hire 8–12 paid community language ambassadors (10–15 h/week) via migrant associations by Month 2 (2026-12-08). Budget ≈€67k for language work.
• By Month 2 (2026-12-08), conduct mandatory de-escalation, trauma-informed care and heat-illness escalation training for all 25–35 outreach and street-contact staff (3-hour modules); achieve ≥80% pass rate on written test; maintain audit trail of certifications.
• By Month 2 (2026-12-08), establish a heat-helpline phone service (08:00–22:00 daily during alerts, 24-hour at Level 3) staffed by 2–3 part-time operators with customer-service and language skills; integrate a shared real-time call-tracking spreadsheet (name optional, address/postcode optional, transport need, language, cooling-center preference) accessible to dispatch and center managers.
• By Month 2.5 (2026-12-23), finalize and distribute to all staff the heat-illness escalation checklist and de-escalation cards (laminated, pocket-sized); establish a nurse-advice line for real-time telephone triage of suspected heat illness; brief all staff on the line and its use.
• By Month 2.5 (2026-12-23), finalize the drill protocol and evidence criteria in writing, shared with the funder and all operational leads. Schedule the full-system drill for Month 3.2 (2027-01-14); reserve a 2-week after-action cycle (draft Month 3.5 = 2027-01-23, actions closed Month 3.9 = 2027-02-04, gate decision Month 4 = 2027-02-08).
• By Month 3 (2027-01-08), complete training for all 43 planned FTE on fatigue management, safe working hours and mandatory rest protocols. Publish a roster that enforces ≤3 consecutive alert days and 1–2 rest days; model surge capacity (20–30% reserve) and test it in the drill.
• By Month 3 (2027-01-08), agree with the hospital and EMS on daily aggregate heat-related call/visit counts (by 10:00 next day) and an escalation protocol: notify incident commander at ≥1.5× historical average, mutual-aid review at ≥2×. Conduct a 2-week validation pilot (Month 1.8 = 2026-12-02); resolve any IT or coding gaps by Month 2 (2026-12-08).
• By Month 6 (2027-04-08), complete focus-group testing of pre-season communications (radio, flyers, pharmacy posters, door hangers, SMS) with at least 2–3 high-risk resident groups (65+, living alone, migrants). Correct messaging for clarity and cultural sensitivity. Brief all trusted messengers (pharmacists, GPs, caretakers, faith leaders) on heat-safety talking points by this date.
• By Month 9 (2027-07-08), audit 10% of partner organizations (housing associations, social services, NGOs) for GDPR compliance, spot-checking consent records and privacy-notice logs. Flag any breaches for immediate remediation.
• By Month 12 (2027-10-08), delete all personal data from intermediary partners and city records unless re-consented; retain only aggregated outcome data (EMS calls, ED visits, participation) for evaluation and playbook development.

5.3 Follow Up Consultation

At the next meeting, review (1) funder's written acceptance of drill evidence and partial-release rule; (2) volunteer recruitment pipeline status and first cohort progress; (3) results of the social-network survey to validate intermediary reach and identify canvassing needs; (4) accessibility audit findings and remediation plan; (5) drill protocol finalization and evidence criteria; (6) partner GDPR opinions and MOU execution status; (7) any scope or timeline changes that trigger restart criteria. Request a monthly staffing pipeline report and drill rehearsal schedule by Month 1 (2026-11-08).

5.4.A Issue - Volunteer Recruitment and Fatigue Management Are Severely Underspecified, Risking the 45-Minute Transport Gate

The plan targets 40 volunteer drivers but provides no recruitment pipeline, no attrition assumption, and no fatigue-rotation protocol. Vetting 20 volunteers by Month 2 (2026-12-08) requires recruitment to start immediately (now), yet no recruitment campaign exists. Multi-day heat waves will drive absences; a 20–30% reserve is mentioned but not operationalized into shift caps or mandatory rest days. Without a staffing model that survives fatigue, the plan risks missing the <45-minute pickup gate and defaulting to expensive taxi-only operation mid-season.

5.4.B Tags

• volunteer_recruitment_pipeline_missing
• fatigue_rotation_undefined
• gate_risk_transport_time
• staffing_attrition_not_modeled
• vetting_timeline_too_aggressive

5.4.C Mitigation

By Month 0.2 (2026-10-14), issue a detailed volunteer recruitment brief specifying: target 50 recruits to net 40 vetted (25% attrition assumption), weekly cohorts of 5–8 starting now, and vetting SLA of 4–6 weeks per person. Define shift caps: ≤3 consecutive alert days, then 1–2 mandatory rest days. Assign a 0.5 FTE volunteer coordinator (not just HR) to track cohorts, absences and fatigue. Test this model against the gates by simulating a 10-day heat wave at Month 3.2 (2027-01-14) drill; if pickup times exceed 45 minutes under fatigue assumptions, trigger the taxi retainer scale-up plan (capped €80k → negotiable if needed) before May.

5.4.D Consequence

Without volunteer recruitment starting now and a tested fatigue model, the city risks deploying too few drivers by May, missing the <45-minute gate in the full-system drill (Month 3.2 = 2027-01-14), and forcing a costly taxi-only fallback (+€150–250k, straining the €160k tranche-1 contingency) or, worse, failing the Month 4 (2027-02-08) gate and losing the €1.5M scale release. Service degradation during multi-day waves will harm the program's credibility and strain remaining volunteers.

5.4.E Root Cause

The plan names volunteer drivers as a core lever but treats recruitment and fatigue as secondary. No one is assigned as volunteer lead with recruitment accountability. Fatigue management is abstract ('20–30% reserve') rather than concrete (shift caps, rest-day enforcement, cohort scheduling). The vetting timeline (4–8 weeks per person) is longer than the recruitment window (8 weeks to Month 2 = 2026-12-08), creating an impossible math unless hiring begins immediately.

5.5.A Issue - Cool-Season Gates Depend on Drill Evidence, Creating Funder Ambiguity and Cash-Flow Risk

The Month 4 (2027-02-08) gate (80% center hours, 60% outreach contact, <45-minute transport) must be tested by a drill in Month 3.2 (2027-01-14) because real heat events are unlikely in January. The pre-project assessment acknowledges this but proposes a 50% partial-release rule (€750k) if evidence is 'unmeasurable.' This rule is not written into the gate definition, is not accepted by the funder in writing, and leaves ambiguity: if the funder rejects drill evidence, the city faces a €200–400k cash gap (only €160k contingency available), forcing mid-season cuts to home kits, outreach or transport. No mitigation plan specifies who decides on partial release or how to proceed if the funder says 'no drill evidence, full gate or restart.'

5.5.B Tags

• cool_season_gate_credibility
• funder_ambiguity_on_drill
• cash_flow_risk_200k_400k
• partial_release_rule_not_binding
• contingency_insufficient

5.5.C Mitigation

By Month 0.1 (2026-10-11), secure a written letter from the funder confirming acceptance of drill evidence for the Month 4 (2027-02-08) gate and endorsing the 50% partial-release rule (€750k if evidence is insufficient, remainder after Month 5 = 2027-03-08 re-test with real data). Define 'insufficient evidence' in writing: <100 drill transport requests, <200 outreach contact attempts, or <2,000 center-hour drill activations mean re-test is required. If the funder will not commit in writing, de-risk by securing a contingent credit line (€200–400k) from the municipality or funder by Month 1 (2026-11-08). Brief the incident commander and CFO monthly on cash-flow scenarios.

5.5.D Consequence

If the funder rejects drill evidence at Month 4 (2027-02-08) and withholds the €1.5M, the city cannot fully fund outreach, home kits or transport through the May–August heat season. This forces mid-summer service cuts (e.g., pausing kit installations, reducing outreach frequency, capping transport to taxis only), harming vulnerable residents and destroying program credibility. The city may face media criticism ('promised help, then retreated') and reduced political support for Year 2.

5.5.E Root Cause

The plan treats the drill-based gate as an acceptable compromise but does not lock funder agreement in writing. The 50% partial-release rule is mentioned in the pre-project assessment and SWOT but not formalized as a funder commitment. No fallback funding source (credit line, reserve, year-2 carry-forward) is identified. The contingency (€280k) is too small to absorb a €200–400k gap.

5.6.A Issue - Intermediary-Held Identification May Underserve the Most Isolated Residents, Leaving Equity Goals at Risk

The plan relies on intermediary-held lists (housing associations, social services, NGOs, pharmacies) to reach 3,000 enrolled high-risk residents (≈9% of 65+). These intermediaries may not contact hard-to-reach people: those living alone without social services, residents in private rentals not tracked by housing associations, migrants avoiding official institutions, and unhoused people absent from all lists. The 60% outreach contact-success gate measures success among enrolled residents, not overall reach. Without a parallel universal or building-level canvassing component, the plan risks serving 'insiders' (known to services) while missing 'outsiders' (isolated, no institutional touch points). This contradicts the equity mandate to prioritize isolated residents.

5.6.B Tags

• identification_equity_gap
• intermediary_reach_limited_to_insiders
• unhoused_and_isolated_underrepresented
• 60percent_gate_measures_enrolled_not_coverage
• private_rental_gap

5.6.C Mitigation

By Month 0.5 (2026-10-23), commission a rapid social-network survey of 200–300 high-risk residents (65+, living alone, top-floor housing, self-reported health conditions) to identify which intermediaries can reach them and which 'islands' exist (unhoused, private-rental, isolated without services). By Month 1 (2026-11-08), design a second parallel identification track: building-level canvassing (door-knock or postcard-invite) in the top 15–20 blocks with highest deprivation/isolation scores, reaching households intermediaries do not touch. Set a equity KPI: ≥15% of enrolled residents from the canvassing track by Month 7 (2027-05-08). Measure coverage (not just success among enrolled) as a secondary gate: ≥20% of estimated high-risk population contacted by Month 4 (2027-02-08), including ≥10% from canvassing.

5.6.D Consequence

If the intermediary-held model serves only 'insiders,' the city enrolls residents already known to services and misses the program's intended highest-need population. This damages equity, fails to reach isolated residents who die at highest heat risk, and undercuts the program's credibility ('pilot reached only the connected'). Scaling to other EU cities will replicate this bias. The program also misses an opportunity to build trust with isolated groups who may be more receptive to a direct, low-pressure outreach approach than to intermediary-mediated contact.

5.6.E Root Cause

The plan adopts intermediary-held lists for GDPR safety and ease but does not validate that these intermediaries reach the full range of high-risk residents. The 3,000 enrollment target and 60% contact-success gate measure activity within the enrolled pool, not population-level coverage. No one is accountable for coverage equity. The decision to avoid building-level canvassing (justified as 'cost per person found') is not tested against actual network data.

---

6 Expert: Municipal Procurement & Contract Law Specialist

Knowledge: EU public-procurement law (thresholds, frameworks, tenders), Spanish procurement rules, contract design and risk allocation, competitive tendering, below-threshold purchasing, supplier qualification and audit, amendment and change-order procedures

Why: The plan's critical path compresses €500-700k of orders into Months 0-1 (2026-10-08 to 2026-11-08).5 (2026-10-08 to 2026-11-23) via 'framework call-offs/below-threshold' purchasing to meet the Month 2 (2026-12-08) readiness gate. However, the plan does not specify: (1) which framework agreements exist and are suitable; (2) the threshold breakpoints (€50k EU below-threshold, varying by region); (3) audit risk if orders are deliberately split to avoid thresholds; (4) contract-clause conflicts (heat-protection clauses in worker contracts slow tendering). This expert ensures compliance, reduces audit exposure, and verifies that the procurement route supports the schedule without legal challenge.

What: By Month 0 (2026-10-08), map the existing municipal framework agreements (coolers, transport, services) and identify which are suitable for call-offs without competition; confirm they include heating/cooling kits, handyperson services and transport. By Month 0.8 (2026-11-01), issue detailed procurement specifications for kits, handypersons, transport and center fit-out, specifying quantity, quality, delivery date and performance standards. By Month 1 (2026-11-08), determine the lowest-risk route for each category (framework call-off, below-threshold simplified, or open-tender); confirm that no single order or order-splitting pattern creates audit risk under Spanish law. By Month 1.5 (2026-11-23), audit-proof the procurement files (documented specs, quotes, selection rationale, change orders) and advise on contract-clause prioritization (speed vs heat-protection requirements).

Skills: EU public-procurement law and thresholds, Spanish procurement regulations, contract drafting and risk allocation, below-threshold purchasing, framework-agreement call-off procedures, audit-trail documentation, supplier relationship management

Search: EU public procurement law specialist, municipal procurement officer Spain, below-threshold purchasing compliance, contract law Spain procurement, audit-ready procurement documentation

6.1 Primary Actions

• By 2026-10-22 (Month 0.5 = 2026-10-23), engage a specialist GDPR law firm (€15–30k budget) and request written legal opinion on the intermediary-held-list model. Confirm that personal data does not transfer to the city and that the lawful basis for contact (public task + consent) is sound. Concurrently, identify 4–6 main partner organizations (housing associations, social services, NGOs, pharmacies) and schedule in-person meetings by 2026-11-08 to discuss data-processing agreements and contact protocols. Obtain their letter of commitment by 2026-11-15 (Month 1.3 = 2026-11-17).
• By 2026-11-01 (Month 0.8 = 2026-11-01), issue detailed RFQs to 5+ qualified vendors per procurement category (shading kits, reflective blinds, fans, thermometers, installation labor, transport/taxi services). Request firm price quotes, lead-time commitments and expedite-cost options. By 2026-11-08, select primary and 2 backup suppliers per category; document any price premiums for accelerated delivery. Place the first 30–40% kit call-off order by 2026-11-08 (not 2026-11-14) with signed delivery SLAs for February 2027 receipt. Simultaneously, issue transport RFQ to taxi/accessible-transport operators, request standby-retainer quotes for 10–15 vehicles within 20 min response, and sign a binding contract by 2026-11-15 (Month 1.3 = 2026-11-17) at the capped €80k rate (or scale to €120k if volunteer recruitment is lagging by Month 1.5 = 2026-11-23).
• By 2026-10-31 (Month 0.9 = 2026-11-04), secure written commitment from the funder (or funder's designated representative) confirming that drill-based evidence is acceptable for the Month 4 (2027-02-08) gates. Document the partial-release rule in writing: €750k (50%) released at Month 4 (2027-02-08) if gates are measurable but gates are not met, and the remaining €1.5M released after a Month 5 (2027-03-08) real-event re-test. Include a contingency plan ('Plan B') that specifies which services would be cut if tranche-2 funding does not release (e.g., home kits reduced from 2,000 to 1,000, refuges scaled to 6 core sites). Obtain funder sign-off on this Plan B before Month 2 (2026-12-08).
• By 2026-11-08 (Month 1 = 2026-11-08), obtain the mayor's signed delegation of authority document appointing the incident commander (mayor's office), public-health deputy, operations lead (civil protection), and communications lead (municipal communications). Ensure the delegation specifies alert-declaration authority, spending approval limits per tier, and escalation paths for cross-department requests. File the document with the municipal secretary and circulate to all partners and operational staff.
• By 2026-11-15 (Month 1.3 = 2026-11-17), establish a weekly procurement tracking dashboard (shared spreadsheet or low-code system) listing all categories (refuges, kits, transport, staffing, comms), order status, delivery dates and any delays. Assign a procurement lead (0.5 FTE) to manage the dashboard and trigger backup suppliers if any item slips by >1 week vs. target. By 2026-12-08 (Month 2 = 2026-12-08), confirm receipt or scheduled delivery of 40–50% of kit stock; if any supplier reports >2-week delay, immediately activate backup supplier and authorize expedite shipping premium.
• By 2026-12-08 (Month 2 = 2026-12-08), hire all permanent and contract staff for Month 2 (2026-12-08) readiness: cooling-center managers (1 per site, 10 FTE), outreach team lead (1 FTE), dispatch lead (1 FTE), phone-line manager (1 FTE), and HR/recruitment coordinator (0.5 FTE for Months 0–4 = 2026-10-08 to 2027-02-08). Conduct first-aid and customer-service training (1 day minimum) for center and phone staff. By 2026-11-08 (Month 1 = 2026-11-08), launch volunteer driver recruitment campaign via job centers, faith organizations and social media; target 60–80 applicants to achieve 40 vetted by Month 3 (2027-01-08). Run vetting cohorts every 2 weeks (background checks, insurance verification, 2-hour safeguarding training) and track completion on a live recruitment dashboard.
• By 2026-11-22 (Month 1.5 = 2026-11-23), finalize and execute data-processing agreements with all 4–6 partner organizations. Agreements must specify: data controller/processor roles, staff confidentiality clauses, audit rights for the city, breach-notification procedures (48-hour reporting to data protection authority), and retention period (one season, deleted by October 2027). Obtain countersigned agreements from each partner's authorized representative.
• By 2026-12-08 (Month 2 = 2026-12-08), conduct a full-system drill protocol planning session with operations, comms, and dispatch leads. Define the drill scope: 3+ consecutive hot-night alert events, 40+ simultaneous transport requests, 80%+ refuge occupancy, outreach fatigue (12+ hours), and escalation decision-points. Schedule the full-system drill for Month 3.2 (2027-01-14). Publish the drill protocol document (with roles, scripts, escalation trees) by 2026-12-23 (Month 2.5 = 2026-12-23) to allow 3 weeks of staff rehearsal before the live drill.

6.2 Secondary Actions

• By 2026-11-08 (Month 1 = 2026-11-08), coordinate with the regional meteorological service (AEMET) to confirm alert-threshold definitions (Level 1: high ≥33°C or low ≥20°C for 2+ days; Level 2: high ≥35°C and low ≥22°C for 2+ days; Level 3: same for 3+ days). Request historical summer temperature and heat-event data for Castellón (2015–2025) to validate thresholds post-hoc after the first season. Establish a standing weekly call (Mondays 09:00) with AEMET from May to September (Months 6–11 = 2027-04-08 to 2027-09-08) to review 7-day forecasts.
• By 2026-11-15 (Month 1.3 = 2026-11-17), work with the municipal occupational health service or a senior emergency-medicine clinician to co-design a heat-illness escalation checklist for outreach and street-contact staff. Checklist must include: recognition signs (confusion, loss of consciousness, hot/dry or profusely sweating skin, inability to stand), decision rules for EMS call (any severe sign, unconsciousness) vs. phone triage (mild dehydration, no severe signs), and de-escalation language. Conduct role-play training with 2–3 realistic vignettes per staff member; require written test (pass ≥80%) before authorization.
• By 2026-12-08 (Month 2 = 2026-12-08), establish a nurse-advice line (contracted or in-house) that outreach staff can call for real-time telephone triage of suspected heat illness. Document call protocols, referral pathways (escalate to 112 EMS, advise home management, refer to 111-style non-emergency service) and post-call logging. By Month 5 (2027-03-08), review first 10 calls to validate protocol and retrain staff if gaps are found.
• By 2026-11-22 (Month 1.5 = 2026-11-23), design and focus-test public messages with a sample of 20–30 high-risk residents (recruited via partner organizations). Test key messages: heat-alert recognition ('daytime high ≥35°C, night low ≥22°C'), cooling-center locations and hours, transport booking (heat line phone number), home-kit benefits, fan safety (directional use only, not opposing), and hydration importance. Identify any misinformation concerns (alcohol myths, incorrect fan advice) and design rapid-response talking points.
• By 2026-12-01 (Month 1.9 = 2026-12-05), recruit and train 8–12 paid community language ambassadors (10–15 h/week starting Month 2 = 2026-12-08) to co-create translated messages, accompany door-knock teams, and staff cooling-center welcome desks. Ambassadors should be selected from migrant associations and represent the locally most common non-official languages (to be confirmed by Month 0 = 2026-10-08 from municipal registers; candidates: Arabic, Romanian, Portuguese). Provide ambassadors with consistent scripts and weekly briefings.
• By 2027-01-08 (Month 3 = 2027-01-08), conduct a 'surge simulation' drill: run a continuous 72-hour alert drill with all staff, volunteers, partners and dispatch. Measure stress indicators (call-queue depth, refuge occupancy, transport wait times, staff fatigue reports). Use results to adjust shift rotations, staffing levels, and volunteer call-out procedures before the May season.
• By 2027-02-08 (Month 4 = 2027-02-08), hold a debrief meeting with all stakeholders (city leadership, partners, funders, evaluation team) to review drill results and after-action corrective actions. Confirm funder agreement on scale-gate evidence and final tranche-2 release. If gates are unmet but gates are measurable, activate the 50% partial-release rule and schedule a re-test for May (Month 7 = 2027-05-08) using real heat events.
• By 2027-04-08 (Month 6 = 2027-04-08), conduct trained-messenger briefings for pharmacists, GPs, caretakers and faith leaders across the city. Provide each group with: heat-alert recognition criteria, cooling-center and transport information, escalation protocols (when to refer residents to the heat line), and translated flyers. Measure attendance and knowledge via short post-briefing quiz.
• By 2027-05-08 (Month 7 = 2027-05-08), conduct a second full drill and transport stress test. Measure performance vs. Month 3.2 (2027-01-14) drill baseline; identify any degradation in reliability or speed. Confirm staffing, volunteer and equipment readiness before peak summer (July–August = Months 9–11 = 2027-07-08 to 2027-09-08).
• By 2027-07-08 (Month 9 = 2027-07-08), conduct a partner audit: spot-check consent records and privacy-notice logs at 2–3 partner sites to verify GDPR compliance. Review any heat-related incidents, data breaches or escalations reported by partners. Document audit results and corrective actions.
• By 2027-09-08 (Month 11 = 2027-09-08), draft the Heat Response Playbook, cost model and evaluation report. Include: SOPs and checklists for alert declaration, center operations, transport dispatch, outreach protocols and escalation; procurement lists and vendor contact information; partner MOUs; staffing templates; comms templates and scripts; baseline data, outcome counts and evaluation limitations. Share draft with two peer cities (e.g., Valencia, Barcelona) for external review by 2027-09-30 (Month 11.2 = 2027-09-14).

6.3 Follow Up Consultation

At the next meeting (recommend 2026-10-22, Month 0.5 = 2026-10-23), confirm: (1) funder's written acceptance of drill-based gates and partial-release rule; (2) procurement RFQ results and backup supplier commitments; (3) volunteer recruitment partnerships in place; (4) GDPR legal opinion timeline and partner data-processing agreement draft; (5) incident commander delegation document signed. Discuss the 'Hot Night Guarantee' killer-app concept (one simple promise to enrolled residents: call within X hours, ride within 45 min, cool home). Identify any political or organizational blockers to speed. Schedule a third meeting at Month 1 (2026-11-08) to review vendor quotes, partner commitments and drill protocol draft.

6.4.A Issue - Procurement timeline is critically compressed and supply-chain risk is understated

The plan requires 100% of tranche-1 orders placed by Month 2 (2026-12-08)—only 2 months away. Kit specifications must be issued by Month 0.8 (2026-11-01), first call-offs placed by Month 1.2 (2026-11-14). February delivery is assumed for 30–40% of stock to reach homes by April–May. This leaves zero margin for vendor quotes, design iteration, or supply-chain delays. If any category (shading, fans, installation labor) slips by 4 weeks, home installations miss the peak-risk window (Months 6–7 = 2027-04-08 to 2027-05-08). The contingency (€280k) cannot cover both a taxi-only fallback and procurement delay. No expedite-cost benchmark is documented.

6.4.B Tags

• supply_chain_compression
• delivery_schedule_risk
• contingency_inadequacy
• lack_of_vendor_quotes

6.4.C Mitigation

By 2026-10-15 (Month 0.3 = 2026-10-17), issue detailed RFQs to 5+ vendors per category (shading, fans, thermometers, installation labor) requesting firm quotes and lead-time commitments. By 2026-11-01, select primary and 2 backup suppliers per category; document price and timeline for expedited delivery (+10–15% cost). Place first 30% order by 2026-11-08 (not 2026-11-14) with signed SLAs for February delivery. Hold €80–120k expedite reserve inside contingency. Establish a weekly procurement dashboard tracking delivery vs. plan; trigger backup supplier activation if primary misses target by >1 week. Confirm all tranche-1 orders by 2026-12-01 (1 week early) to detect gaps before Month 2 (2026-12-08) gate.

6.4.D Consequence

Kit installation slips past May heat season, leaving 1,500+ highest-risk homes unprotected during peak-mortality months. Home intervention becomes an ineffective demonstrator. The €800k home-kit budget partially wasted on post-season work. Month 4 (2027-02-08) scale gate fails on lack of visible early-season impact. Funder holds back €1.5M, creating a €200–400k cash gap. Service degradation forces taxi-only operation mid-summer, adding €150–250k unbudgeted cost.

6.4.E Root Cause

Plan assumes procurement and hiring run in parallel with zero contingency. No vendor relationship established; quotes are not in hand. Expedite costs and lead-time uncertainty are not quantified. Procurement team likely does not yet exist (HR coordinator starts Month 0 = 2026-10-08). Unrealistic 8-week timeline for spec-to-order for a complex, multi-vendor, cross-category bundle.

6.5.A Issue - Month 2 (2026-12-08) and Month 4 (2027-02-08) readiness gates rest on drills in cool season; real-world validation is deferred until summer, creating a funding-release cliff

The €1.5M tranche-2 release depends on four gates at Month 4 (2027-02-08): 80% center hours, 60% outreach contact success, <45 min transport time, after-action closure. All evidence comes from drills and simulated alert days conducted in January–February—months with no historical heat events in Castellón. If evidence is deemed insufficient by the funder or regulator, partial-release rules allow only €750k (50%) at Month 4 (2027-02-08), leaving a €200–400k cash gap. Full June–July heat season will test operations without a confirmed second tranche. This forces a high-stakes re-test in March–April to unlock funds, with zero margin for operational tuning. Funder risk appetite for drill-only evidence is not documented.

6.5.B Tags

• gate_validation_timing
• cool_season_evidence
• cash_flow_cliff
• funder_alignment_missing

6.5.C Mitigation

Obtain written funder commitment by 2026-11-08 (Month 1 = 2026-11-08) that drill evidence is acceptable and details the partial-release rule (€750k at Month 4 = 2027-02-08 if gates are measurable but incomplete, full release by Month 5 after June real-event re-test). Design drills to mirror real alert stress: simulate 3+ consecutive hot-night events, peak transport demand (40+ simultaneous requests), refuge surge (80%+ occupancy), and outreach fatigue (12+ hours continuous). Document drill assumptions and limitations in the after-action report. Establish a 'summer validation checkpoint' at Month 8 (2027-06-08): if June–July real events occur, reconcile drill vs. actual performance and confirm final funding. Hold €120k tranche-2 contingency until Month 7 (2027-05-08) re-assessment. Pre-agree a 'plan B' if gates are unmet: identify which services would be cut to fit into tranche-1 only (e.g., reduce kits to 1,000, scale refuges to 6 sites).

6.5.D Consequence

Funder disputes drill evidence at Month 4 (2027-02-08) and withholds €1.5M pending real-event proof. City faces a €200–400k cash gap mid-February; must cut or delay refuge staffing, transport retainer, or home kits. Outreach momentum is lost; volunteer drivers stand down; emergency hiring and retraining in May under crisis pressure. If re-test is deferred to June and heat events are mild, the second tranche may never release. Playbook credibility damaged: other EU cities view the model as unproven and risky.

6.5.E Root Cause

Plan accepts cool-season gates as a given constraint but does not secure prior funder commitment in writing. Partial-release rule was added late and is untested. No 'Plan B' budget scenario for tranche-2 non-release. Evaluation design does not pre-specify what drill evidence constitutes 'success' in funder's eyes. Assumes good-faith interpretation by funder rather than contractual clarity.

6.6.A Issue - Staffing and volunteer recruitment are aggressive, compressed, and lack documented recruitment pipelines or retention strategy

The plan requires 43 FTE at peak (Months 4–7 = 2027-02-08 to 2027-05-17), including 10 handypersons, 18 center staff, 3 dispatchers, 6 outreach workers and 40 volunteer drivers. Hiring is staggered (40% Month 3 = 2027-01-08, 40% Month 4 = 2027-02-08, 20% Month 5 = 2027-03-08), with all in post by Month 6.7 (2027-04-29). Volunteer recruitment must produce 40 vetted drivers by Month 3 (2027-01-08) with only 4–8 weeks of lead time per vetting. No recruitment pipeline evidence is documented (partnerships with job centers, faith organizations, universities). Fatigue management is listed but assumes 3–4 day rotations; multi-day heat events (July–August at Months 9–11 = 2027-07-08 to 2027-09-08) will test retention and reliability. No documented exit or turnover plan if volunteers burn out mid-season.

6.6.B Tags

• aggressive_hiring_timeline
• volunteer_recruitment_unproven
• fatigue_risk_understated
• turnover_risk_no_plan
• no_recruitment_partnerships

6.6.C Mitigation

By 2026-10-22 (Month 0.5 = 2026-10-23), identify and sign MOUs with 3–5 recruitment partners (job centers, faith organizations, charitable networks, universities, retired professional associations). By 2026-11-08 (Month 1 = 2026-11-08), launch volunteer driver recruitment campaign with a clear value proposition ('Help save lives. 20–30 h/month, flexible, €12–15/h, safeguarding training provided'). Target 60–80 applicants to achieve 40 vetted by Month 3 (2027-01-08). Establish a rolling vetting cohort every 2 weeks (Months 1–4 = 2026-11-08 to 2027-02-08) rather than a single batch. For paid staff (center, dispatch, outreach), hire an HR/recruitment coordinator at Month 0 (2026-10-08) (0.5 FTE, €25k for 6 months). Create a staff retention plan: competitive pay (€16–18/h for center assistants), mental-health support during surge, peer debriefing after alerts, and a 'hero' recognition scheme. If volunteer recruitment falls short of 20 by Month 1.5 (2026-11-23), immediately scale the taxi retainer (from €80k capped to €120k) and reduce kit targets to 1,500 to free budget. Conduct a 'surge simulation' at Month 5.5 (2027-03-23): run a 72-hour continuous alert drill to test staff and volunteer endurance; use results to adjust rotations and staffing before the season.

6.6.D Consequence

Volunteer shortfall at Month 3 (2027-01-08) forces unplanned budget reallocation: taxi retainer scaled up (+€40–80k), home kits cut to 1,500 or 1,000, outreach reach reduced by 20–30%. Mean transport pickup time exceeds 45 min; Month 4 (2027-02-08) gate fails on transport-time criterion. Volunteer burnout mid-season (July–August, Months 9–11 = 2027-07-08 to 2027-09-08) leaves refuge shifts unstaffed or dispatch queues unmanaged. Multi-day heat wave triggers emergency recalls or unpaid overtime, damaging staff morale and retention into Year 2. Project credibility damaged: other EU cities question model's sustainability with limited funding.

6.6.E Root Cause

Plan assumes availability of volunteer drivers without evidence of recruitment market or partnerships. Vetting timeline (4–8 weeks per person) is realistic but aggressive given zero lead time. No contingency plan if recruitment underperforms. Fatigue and burnout are listed as risks but the mitigation (rotations + training) is generic; no real-world pilot data from other EU heat programs. Assumes municipal HR capacity to hire 43 FTE in 6 months without documented capacity.

---

7 Expert: Community Engagement & Trust-Building Practitioner

Knowledge: Migrant integration and language access, community co-design methods, faith-leader and peer-ambassador recruitment and training, trust-building in marginalized communities, misinformation counter-narratives, multilingual messaging design and testing, enrollment referral networks

Why: The plan names recent migrants and people living alone as priority groups but provides only generic 'trusted-messenger briefings' and 'focus-tested messages' without: (1) a local migrant-language audit (4-6 languages 'to be confirmed' Month 0 = 2026-10-08); (2) a co-design protocol with migrant organizations and faith leaders; (3) risk mitigation for misinformation (alcohol, fan misuse) beyond '≤4 h correction'; (4) enrollment validation (will intermediary calls succeed with migrants distrustful of official channels?). The SWOT identifies 'weak trust among migrants' as a threat. This expert designs enrollment pathways that actually reach migrants, tests messaging with them, and builds referral networks through trusted local figures.

What: By Month 0 (2026-10-08), audit the local migrant population (census data, NGO networks, faith leaders, language communities) and confirm the 4-6 non-official languages and a map of trusted organizations per language. By Month 0.5 (2026-10-23), recruit 8-12 paid community ambassadors (10-15 h/week, ~€7k total per person for 12 months) from migrant and faith organizations; brief them on the program and role. By Month 1 (2026-11-08), co-design enrollment messages, cooling-center welcome scripts and escalation language with ambassador focus groups; test drafts with ≥20 residents per language. By Month 2 (2026-12-08), train ambassadors on heat-illness signs, de-escalation and referral; establish a rapid-response process for misinformation (ambassador reports → communications lead reviews ≤4 h → corrected message deployed same day); track referral volume and contact outcomes by language.

Skills: Community co-design and participatory methods, multilingual communication design and testing, migrant community engagement, faith-leader partnerships, peer-ambassador recruitment and training, misinformation identification and counter-narrative design, trust-building in marginalized groups

Search: community engagement migrant integration, multilingual public health messaging, peer ambassador training, co-design health programs, faith leader partnerships public health

7.1 Primary Actions

• By Month 0.5 (2026-10-23), commission rapid resident-research (focus groups + interviews with ≥150 older isolated residents, recent migrants, homeless people) to identify what trust-building offer (e.g., trusted messenger first call, visible cooling kit, named contact guarantee) would drive enrollment among the most distrustful cohorts; use findings to redesign enrollment strategy beyond intermediary lists alone.
• By Month 1 (2026-11-08), conduct language-mapping survey of Castellón de la Plana's migrant and elderly neighborhoods (20–30 interviews per area across 5–7 high-concentration zones) to verify actual language mix and geographic clusters; allocate ≥€120k additional language budget and hire 2–3 full-time bilingual outreach coordinators to lead field enrollment and first-contact teams (not just interpretation).
• By Month 1 (2026-11-08), appoint a dedicated 'Community Trust Lead' (0.75 FTE) and allocate ≥€150k to immediately map and engage faith leaders, migrant associations, Roma representatives, homeless-service NGOs, and peer-support networks; schedule 5–7 co-design workshops by Month 1.5 (2026-11-23) asking communities 'What would make you believe this?' and 'Who would you trust to deliver it?'
• By Month 2 (2026-12-08), contract 8–12 community-vetted peer ambassadors (not part-time volunteers, but paid trusted community members with 15–20 h/week capacity) in each priority neighborhood; finalize messaging through co-design (not central templates); brief all messengers on heat-illness escalation, misinformation rebuttals, and rapid-response protocols.
• By Month 1.5 (2026-11-23), finalize GDPR-compliant data-processing agreements with all partner organizations AND document a secondary consent pathway for residents who refuse official intermediaries but will provide contact details to trusted community messengers; ensure bilingual staff capacity to conduct these consent conversations.
• Redefine the Month 4 (2027-02-08) outreach-contact-success gate to measure geographic coverage within high-risk neighborhoods (≥60% contact success among residents living in the top 3–5 high-deprivation areas, including unhoused populations), not just among enrolled registry members; this forces equitable reach, not registry convenience.

7.2 Secondary Actions

• By Month 2 (2026-12-08), require each cooling-center site to have at least one bilingual staff member (Spanish + one local minority language) on duty during alert hours; integrate bilingual hire into the 18-FTE refuge staffing plan, not as an add-on.
• By Month 3 (2027-01-08), establish a weekly 'Community Messenger Feedback Loop' where peer ambassadors and faith leaders report back on what misinformation, fears, and false beliefs they are hearing in informal networks; feed this into daily operational briefings and activate rapid-response counterspeech within 4 hours of each alert.
• By Month 4 (2027-02-08), conduct a qualitative enrollment audit: for each of the 3,000 enrolled residents, document source of enrollment (which intermediary, which messenger, which channel); disaggregate by age, language, housing type, and neighborhood; publish disaggregated data as equity metric; if any neighborhood or group is <30% of proportional target, trigger immediate outreach surge.
• By Month 6 (2027-04-08), before the public pre-season campaign launch, hold a 'community-messenger validation workshop' where peer ambassadors, faith leaders, and residents review all campaign materials (radio, flyers, SMS templates, center signage) and certify that messages are credible, culturally appropriate, and will not trigger distrust; revise any material that community validators flag.
• By Month 9 (2027-07-08), conduct a post-hoc audit of alert-day enrollment and service uptake, disaggregated by community and language; for any group that underutilized services, interview non-users about barriers (trust, language, accessibility, belief); document findings for Year-2 community co-design.
• From Month 0 (2026-10-08) forward, ensure that the Community Trust Lead (or equivalent) has a seat in the incident-commander daily SITREP at 08:30 and in monthly strategic reviews; this ensures community-trust risk surfaces alongside operational risk.
• Identify and pre-contract (by Month 1.5 = 2026-11-23) at least one university or independent research partner with expertise in migrant health and community trust-building to conduct a concurrent qualitative evaluation of trust dynamics; use findings to iterate the model mid-season (Month 7 = 2027-05-08) and to strengthen Year-2 design.

7.3 Follow Up Consultation

"In the next consultation, address: (1) Which specific communities in Castellón de la Plana are highest-risk and most distrustful? Bring neighborhood-level health and social data, and preliminary interviews with community leaders. (2) What evidence exists that intermediary-held lists and official phone lines work with isolated, mistrustful populations? Bring examples from other EU cities or research citations. (3) What is the actual budget flexibility for community-trust infrastructure (language staff, peer ambassadors, co-design workshops)? Bring a detailed line-item budget for the €170k communications category, with recommendations on reallocation. (4) Who will lead community engagement—is it embedded in the municipal team or outsourced to an NGO? Bring a proposed staffing model and accountability structure. (5) How will you measure whether trust has improved by Month 12 (2027-10-08)? Bring a qualitative-evaluation framework (not just enrollment numbers, but resident beliefs and attitudes)."

7.4.A Issue - Enrollment and outreach strategy bypasses the most isolated residents—intermediary-held lists alone will miss 80% of high-risk people who distrust formal services

The plan targets 3,000 enrolled residents (≈9% of 65+) via housing associations, social services, NGOs and pharmacies. However, these intermediaries predominantly reach people already connected to services. The most isolated—particularly older residents living alone, recent migrants with language barriers, and people with historical trauma regarding authorities—are systematically absent from these lists. Canvassing by building and street sentinels are mentioned but not resourced as primary routes, leaving a coverage gap of 15,000–20,000 high-risk people unreached by alert calls. Without a 'no-wrong-door' enrollment strategy that meets people where they are (markets, religious settings, soup kitchens), the program will concentrate resources on the easiest-to-reach 10% and miss those with highest mortality risk.

7.4.B Tags

• outreach-coverage-gap
• isolation-exclusion
• trust-deficit-migrant-elderly
• enrollment-bottleneck
• equity-blind-design

7.4.C Mitigation

By Month 1 (2026-11-08), commission rapid resident research (10–15 focus groups, 100–150 interviews) with older isolated residents, recent migrants, and people experiencing homelessness to identify what trust-building offer would drive enrollment (e.g., a trusted community messenger making the first call, a visible cooling kit as proof of benefit, a named human contact guarantee). Use findings to design a dual-track enrollment: intermediary-held lists for the reachable 10%, plus a community-ambassador-led outreach-to-isolation strategy for the remaining 90%. Allocate ≥€80k and 2 FTE from the communications budget to deploy 12–15 paid 'heat guides' in markets, places of worship, migrant/Roma associations, and soup kitchens from Month 3 (2027-01-08). Redefine the 60% outreach-success gate to measure contact attempts within 200 m of the target population's geographic clusters, not just the enrolled registry.

7.4.D Consequence

Without mitigation, 80% of the highest-risk isolated residents will remain outside the program, defeating the equity mandate. A heat event in July will reveal that enrolled residents are predominantly already-connected, employed older adults in formal housing—not the most vulnerable. The program's legitimacy with migrants, Roma, and homeless communities will collapse; subsequent Year-2 outreach will face active mistrust. Media coverage will frame the program as 'helping the connected and abandoning the isolated.' Reputational damage will undermine municipal capacity to run future public-health programs in marginalized communities.

7.4.E Root Cause

The intermediary-list model was selected for GDPR simplicity and speed, not for reach. The plan conflates legal safety with equitable coverage. No resident research was done to validate what would drive enrollment among the most distrustful cohorts (e.g., undocumented migrants, older people who have never called a government helpline). The plan also conflates 'opt-in' with 'accessible': an opt-in registry run by housing associations will miss people who are not tenants (subletting, informal arrangements).

7.5.A Issue - Language-access architecture is under-resourced and will fail to reach non-Spanish speakers at point of urgent need; interpretation is a compliance checkbox, not a trust-building lever

The plan allocates ≈€67k and 8–12 ambassadors (10–15 h/week) to serve 4–6 non-official languages across a city where migrant populations are concentrated in specific neighborhoods. The helpline will have telephone interpretation, but the outreach model depends on partner staff (housing caretakers, social workers, pharmacists) who are predominantly Spanish-monolingual. Door-knock teams will arrive with flyers in multiple languages but no bilingual staff. Cooling-center welcome desks will rely on pictograms and short phrases, which fail to convey safety-critical advice (fan use in extreme heat, medication interactions, heat-illness escalation). Recent migrants—identified as a priority group—will receive alert messages but not consent-based enrollment conversations in their preferred language, reducing uptake by an estimated 30–50%. Language access has been framed as a translation task, not as a trust-building infrastructure that requires bilingual staff presence in the field.

7.5.B Tags

• language-access-failure
• compliance-checkbox
• migrant-exclusion
• trust-infrastructure-missing
• point-of-contact-gap

7.5.C Mitigation

By Month 0.5 (2026-10-23), conduct a rapid language-mapping survey of Castellón de la Plana's migrant and elderly neighborhoods (20–30 short interviews in each of the 5–7 highest-concentration areas, plus municipal social services data) to identify the actual top 4–5 languages and geographic clusters. Allocate ≥€120k (€50k additional language budget) to hire 2–3 full-time bilingual outreach coordinators (one per major language cluster) from Month 2 (2026-12-08) onward, with authority to make enrollment calls and lead first-contact door-knock teams. Train these staff as 'heat health navigators' with brief clinical training (2-hour heat-illness recognition module), not just interpreters. Relocate ≥30% of the ambassador budget to support these coordinators. By Month 6 (2027-04-08), require all cooling-center sites to have at least one bilingual staff member on duty during alert hours, not just access to a phone line.

7.5.D Consequence

Without mitigation, non-Spanish speakers will fail to understand heat alerts, will not enroll, and will not seek cooling even when alerted. A multi-lingual heat event with media coverage will show that migrant residents were unreached, creating political pressure for a response that comes too late. Healthcare systems will see heat-related ED visits concentrated in non-Spanish-speaking cohorts, signaling a failed targeted intervention. Loss of trust among migrant communities will ripple into future public-health programs. The City will be seen as having allocated €67k to language work but not delivering accessible services to the named priority group.

7.5.E Root Cause

Budget and hiring constraints pushed language access to the margins. The plan treats translation as a cost item (leaflets, interpretation line) rather than as core field capacity. No labor model exists for bilingual outreach staff, and the ambassador model is part-time and concentrated in a narrow budget. The plan also lacks mapping of migrant neighborhoods and demographic data on which languages are spoken where; decisions are being made on assumed language mix ('candidates: Arabic, Romanian, Portuguese, to be confirmed') rather than verified local data.

7.6.A Issue - Trust infrastructure is entirely missing; there is no strategy to activate faith leaders, peer networks, and community organizations as credible messengers before the first heat event, making the program dependent on official channels that marginalized residents avoid

The plan mentions 'trusted messengers'—pharmacists, GPs, caretakers, faith leaders—but allocates no budget, no hiring, and no institutional relationship-building before Month 6 (2027-04-08), when the pre-season campaign launches. There is no evidence that faith leaders, Roma association heads, migrant mutual-aid networks, or peer-support groups have been contacted, briefed, or contracted to co-design heat-safety messaging. The 8–12 language ambassadors are part-time and paid, not embedded in community structures. When the first alert arrives in June, the city will attempt to reach isolated residents via official phone lines and cooling centers—the exact channels these residents distrust. No counterspeech infrastructure exists to counter misinformation (alcohol, misused fans) that will inevitably circulate in informal networks. The plan frames communication as a campaign (messages broadcasted to a mass audience) rather than as a dialogue-and-relationship ecosystem that makes people believe a safety message enough to act on it.

7.6.B Tags

• trust-infrastructure-absent
• community-partnership-shallow
• misinformation-undefended
• faith-leader-engagement-tokenistic
• peer-network-bypassed

7.6.C Mitigation

By Month 0 (2026-10-08), immediately allocate ≥€150k and one dedicated 'Community Trust Lead' (0.75 FTE, reporting to the incident commander) to map and engage faith leaders, migrant associations, Roma community representatives, homeless-service NGOs, older-resident peer groups, and women's networks in Castellón de la Plana. By Month 1 (2026-11-08), hold 5–7 structured co-design workshops with representatives of each community, asking: 'What would make you believe a heat-health message?' and 'Who in your community would you trust to deliver it?' Use findings to design community-specific heat-safety messaging (not centralized campaign templates) and to identify and contract 8–12 peer ambassadors per community (not language interpreters, but trusted community members). By Month 2 (2026-12-08), finalize and brief all contracted messengers on heat-illness recognition, escalation rules, and misinformation rebuttals (specific scripts for alcohol myths, fan misuse, etc.). Allocate a rapid-response budget (€30k) to activate messenger networks within 4 hours of a misinformation alert (e.g., WhatsApp groups, phone trees, local radio spots) to correct false advice. Establish a weekly 'messenger feedback loop' where community members report back on what they're hearing in informal networks, feeding into daily operational briefings.

7.6.D Consequence

Without mitigation, the program will spend €170k on communications that do not reach or persuade the most isolated residents. When the first heat event occurs, isolated older residents and migrants will not answer official calls; they will rely on family advice, street gossip, and informal networks—many of which will promote unsafe practices (opening windows, alcohol, lying in the sun). Heat-illness cases will spike in populations the program claimed to serve. Media investigation will reveal that the city paid for multilingual flyers that sat in community centers but never reached residents. Community leaders will report (privately, then publicly) that the city never asked them to help. Trust in municipal public health will drop for a generation; subsequent interventions will be met with skepticism and refusal to participate.

7.6.E Root Cause

The plan is a municipal operations document, not a community-trust document. Trusted-messenger engagement is a secondary decision (Decision 9), allocated ≈€50–70k, and scheduled to happen after procurement and operational setup are complete. The underlying logic is that official channels (phone lines, centers, flyers) can deliver messages, and trusted messengers are a nice-to-have amplifier. But for migrants, Roma, homeless people, and isolated older residents, official channels have low credibility; the messenger IS the message. The plan also has no community-co-design process; it was written by a municipal team with external input, not co-designed with the priority communities themselves.

---

8 Expert: Heat-Health Evaluation & Data Science Lead

Knowledge: Heat-attribution epidemiology, small-area health data analysis, temperature-adjusted mortality modeling, EMS/ED coding standards, time-series analysis with seasonal adjustment, heat-threshold calibration, comparison-group design, data-quality and validation workflows

Why: The plan's evaluation strategy is sketched lightly: 'pilot vs matched districts and prior years, temperature-adjusted, aggregate counts only.' However, four critical gaps exist: (1) baseline EMS/ED/mortality data is provisional (80-120 EMS, 15-25 deaths) and unvalidated; (2) coding practice for 'heat-related' varies by hospital and EMS service (explicit ICD-10 codes vs clinician judgment vs proxy indicators); (3) small-area counts in a 170k city are noisy, so the evaluation may be unable to detect real effects within one season; (4) the Month 4 (2027-02-08) gate includes no mortality outcome, only operational KPIs, so credibility of 'harm reduction' claims rests on EMS/ED data quality. This expert validates baselines, agrees coding standards with health partners, and specifies a realistic evaluation design that accounts for small-area limitations.

What: By Month 0 (2026-10-08), request detailed EMS and hospital baseline data (heat-coded calls, ED visits, timestamps) for ≥2 prior summers, and clarify coding practice (which ICD-10 codes count as 'heat-related'?). By Month 1 (2026-11-08), audit the data quality: completeness (% of records with heat coding), consistency (same codes across services), and temporal pattern (do peaks match known heat events?). By Month 2 (2026-12-08), finalize definitions and agree a temperature-adjusted baseline (e.g., average heat-related calls per 1°C above 32°C). By Month 4 (2027-02-08), pre-specify the evaluation protocol (comparison group selection, adjustment variables, statistical methods, subgroup analyses) and register it with a university partner; specify realistic power to detect a 10-15% reduction. By Month 12 (2027-10-08), deliver evaluation report with explicit confidence ranges and attribution limits (e.g., 'attributable to the program' vs 'coincident with').

Skills: Epidemiologic analysis and attribution methods, time-series temperature adjustment, small-area analysis and privacy protection, EMS/ED data validation and coding, comparison-group design, statistical power calculation, heat-health thresholds and calibration, data visualization for non-technical audiences

Search: heat health epidemiology evaluation, EMS ED coding standards heat illness, small-area health data analysis, temperature attribution mortality, heat threshold calibration

8.1 Primary Actions

• Obtain written funder sign-off on the drill-as-evidence protocol and the partial-release rule (€750k at Month 4 = 2027-02-08 if insufficient real evidence, remainder after May re-test) by Month 0.5 (2026-10-23). If the funder will not accept this, immediately escalate and renegotiate the funding structure (full disbursement with clawback, or identify contingency funding) before proceeding to any other work.
• Replan procurement timeline: issue specs by Month 0.5 (2026-10-23), pre-qualify backup suppliers with emergency-activation agreements by Month 1 (2026-11-08), place first-tranche kit orders by Month 1 (2026-11-08) (not Month 1.2 = 2026-11-14), and arrange interim storage by Month 1.5 (2026-11-23). Commit the €200k expedite premium immediately; do not hold it contingent. Confirm all first-tranche deliveries locked in for February 2027 by Month 1.5 (2026-11-23).
• Expand outreach target from 3,000 enrolled to 5,000–6,000 total contact attempts, aiming for ≥2,500 enrolled + 1,500–2,500 one-time reached. Add a targeted door-knock phase for top-floor and social-housing blocks in Months 5–6 (2027-03-08 to 2027-04-08) with 3 temporary staff to reach isolated residents missed by intermediaries. Redefine the 60% contact-success gate to measure contact rate by neighborhood deprivation index and housing type, not just enrollment rate.
• Place cooling-center facility contracts and execute accessibility audits by Month 1.5 (2026-11-23). Confirm ≥50% of places are fully accessible (wheelchair ramps, accessible toilets, quiet rooms) by Month 2 (2026-12-08). Any site that cannot meet accessibility by Month 2 (2026-12-08) should be deferred to July or replaced; do not defer until later.
• Engage a GDPR specialist law firm and obtain written legal opinion confirming that the intermediary-held-list model complies with Spanish law and GDPR by Month 1 (2026-11-08). Finalize and execute data-processing agreements with all partner organizations (housing associations, social services, NGOs, pharmacies) by Month 1.5 (2026-11-23). Brief 50–80 partner staff on confidentiality and consent protocols by Month 2 (2026-12-08). Do not rely on informal verbal agreement.

8.2 Secondary Actions

• Commission verified baseline data on heat-related EMS calls, ED visits and mortality coding from the municipal hospital, EMS service and primary-care network by Month 1 (2026-11-08). Compare to the plan's provisional estimates (80–120 EMS calls, 15–25 excess deaths); flag any material gaps and adjust the evaluation design and gates if baseline is much smaller or larger than estimated.
• Establish a monthly risk-review checkpoint at the project steering committee: Month 1 (2026-11-08), Month 2 (2026-12-08), Month 3 (2027-01-08), and Month 4 (2027-02-08, 2026-12-08, 2027-01-08, 2027-02-08). At each checkpoint, review: (1) funder confirmation status, (2) procurement order status and delivery confirmation, (3) volunteer recruitment pipeline and vetting progress, (4) partner DPA and consent tracking, (5) facility accessibility audit results. If any item is >2 weeks behind, escalate to the incident commander and activate contingency plans (e.g., scale taxi retainer if volunteers lag).
• Conduct a focus group test of the 'Hot Night Guarantee' messaging (call within X hours, ride within 45 minutes, cool home) with 15–20 high-risk residents (age 70+, living alone, low digital literacy) by Month 1 (2026-11-08). Measure: Would this offer make you enroll? What changes would make it more credible? Use results to refine enrollment messaging and ensure the promise is realistic given transport and staffing capacity.
• Pre-specify the drill protocol (final by Month 2.5 = 2026-12-23) with explicit realism criteria: simulate multi-day heat event (48–72 hours), include 3–5 volunteer failures/absences, test center occupancy surge to 80% capacity, simulate 2–3 escalations to EMS, and measure staff fatigue/error rates after 48 hours. Document drill evidence standards in writing and share with the funder by Month 2.5 (2026-12-23) so no surprises emerge at the Month 4 (2027-02-08) gate.
• Recruit volunteer drivers in fortnightly cohorts starting Month 0.5 (2026-10-23), with vetting and training 4–8 weeks. Require background checks, insurance verification, and 2-hour safeguarding training per person. Target ≥20 vetted by Month 2 (2026-12-08); if <15 are in the pipeline by Month 1.5 (2026-11-23), immediately scale the taxi retainer proportionally (estimate +€20–40k per 10-volunteer shortfall). Do not wait until Month 4 (2027-02-08) to discover insufficient volunteer capacity.
• Establish a nurse-advice triage line (0.5 FTE) by Month 2 (2026-12-08) for outreach staff to call with suspected heat-illness cases. Develop a checklist of escalation criteria (confusion, loss of consciousness, skin temperature, core-temperature indicators) and train all 25–35 outreach staff on the protocol by Month 2 (2026-12-08). Test the line with 3–5 mock calls during the month-2 readiness gate drill to ensure it integrates with EMS dispatch.
• Identify and lock in a Year-2 funding source (EU climate funding, national health budget, regional authority co-financing, or phased municipal budget) by Month 9 (2027-07-08), before the playbook is finalized. If no source is identified by Month 10 (2027-08-08), recommend to the funder and municipality which components would be cut to fit a reduced Year-2 budget (likely: home kits and handyperson service, retaining refuges and transport). Include this tradeoff in the Year-2 roadmap.

8.3 Follow Up Consultation

At the next consultation (recommended Month 0.5 = 2026-10-23), bring: (1) written funder response to the drill-as-evidence and partial-release rule; (2) preliminary supplier quotes and lead-time confirmations for kits and transport; (3) baseline EMS/ED/mortality data from hospital and EMS; (4) confirmed facility-use commitments from ≥8 of 10 proposed cooling-center sites; (5) volunteer-recruitment progress (numbers in pipeline, vetting timeline per candidate); (6) GDPR counsel engagement letter and preliminary legal advice on the intermediary-list model; (7) results of the 'Hot Night Guarantee' focus group. These six items are the leading indicators of whether the Month 2 (2026-12-08) and Month 4 (2027-02-08) gates are achievable. If any is stalled or shows negative indicators, escalate immediately to incident command.

8.4.A Issue - Cool-Season Gates Create Unmeasurable Evidence Problem

The Month 2 (2026-12-08) and Month 4 (2027-02-08) gates fall entirely in the cool season (November–February in Spain). Real heat events will not occur until June at earliest. The plan proposes drill-based evidence instead, but drills cannot replicate multi-day fatigue, heat-stress decision-making, or volunteer/staff burnout under real conditions. Funders and regulators may reject drill evidence as insufficient. If the €1.5M tranche-2 release is delayed pending real heat data, a €200–400k cash gap emerges that exceeds the €160k available tranche-1 contingency. This is a structural flaw, not a minor risk.

8.4.B Tags

• gate-evidence-gap
• cash-flow-risk
• funder-assumption-undocumented
• seasonal-timing-mismatch

8.4.C Mitigation

Immediately (by Month 0.5 = 2026-10-23) obtain written funder sign-off on the partial-release rule and drill-as-evidence protocol before any other work begins. If the funder will not accept drills, propose three alternatives: (a) redefine gates to require only operational readiness (contracts signed, staff hired, no performance thresholds) and defer performance gates to post-season; (b) negotiate a full €3.5M front-loaded disbursement with a clawback clause if gates are missed; (c) identify contingency funding (EU climate or health grants) to cover the €200–400k gap if tranche-2 is delayed. Document the chosen path in a signed amendment to the funding agreement by Month 1 (2026-11-08).

8.4.D Consequence

Without funder written agreement before Month 2 (2026-12-08), the program faces a 40–60% risk of tranche-2 withholding at Month 4 (2027-02-08). This forces mid-season cuts to transport retainer (raising pickup times above 45 min), cooling-center hours, or outreach staff. Service will degrade during the first real heat event, causing harm to enrolled residents and generating reputational damage ('pilot failed when it mattered'). The playbook becomes unusable for other cities because the pilot could not demonstrate operational success.

8.4.E Root Cause

The plan was designed to meet a two-month delivery deadline (Month 0 = 2026-10-08 to Month 2 = 2026-12-08 to 2026-12-08) in a cold climate. The gates were set to happen early to release tranche-2 before the funding year ends, but early means cool-season. No one documented the funder's appetite for drill-based evidence, so the gap was not surfaced until now. The root cause is compressed timeline + seasonal mismatch + undocumented assumption about evidence standards.

8.5.A Issue - Procurement Critical Path Compressed into 8 Weeks; Supply-Chain Buffer Missing

The plan requires all tranche-1 procurement orders placed by Month 2 (2026-12-08)—a hard gate. This means specs by Month 0.8 (2026-11-01), framework/below-threshold orders by Month 1.5 (2026-11-23), and all tenders closed by Month 2 (2026-12-08). For home kits and transport, delivery windows are extremely tight: first-tranche kits must arrive by Month 4 (2027-02-08) and be 80% installed by Month 5 (2027-03-08) to enable May–June deployment. If any supplier slips 4–6 weeks (normal for EU industrial supply), kits arrive in June–July after the first heat event. The plan notes the supply-chain risk but does not allocate enough schedule or budget buffer to absorb it.

8.5.B Tags

• procurement-schedule-risk
• supply-chain-buffer-insufficient
• delivery-window-tight
• contingency-not-pre-committed

8.5.C Mitigation

Replan procurement timeline: (1) Issue detailed specs to suppliers by Month 0.5 (2026-10-23), 5 days earlier than planned; request quotes + lead-time confirmation by Month 0.8 (2026-11-01). (2) Pre-qualify all backup suppliers and negotiate 'emergency activation' agreements by Month 1 (2026-11-08) specifying that 20–30% of first-tranche stock can be ordered at 7-day notice with expedited freight. (3) Place the first-tranche kit order (600–800 units) by Month 1 (2026-11-08), not Month 1.2 (2026-11-14), to gain one week of buffer. (4) Arrange interim storage (≥200 units) at a municipal facility by Month 1.5 (2026-11-23) so kits can be received and staged early if primary supplier delivers ahead of schedule. (5) Include in the retainer contract a 10% buffer-stock allowance (100–200 extra units) so if one tranche is lost in transit, a backup exists. Commit the €200k expedite premium immediately; do not hold it contingent.

8.5.D Consequence

If procurement slips 4–6 weeks, 60–80% of home kits will not be installed until July–August, missing the May–June peak-risk season entirely. The program will then have claimed a 2,000-home intervention on paper but delivered it after the first major heat event has already occurred. This breaks the enrollment promise ('your home will be cooler by May') and undermines trust for Year 2. Alternatively, the city cuts home kits from 2,000 to 1,000–1,500 to fit the revised timeline, which reduces coverage and the program's flagship tangible benefit.

8.5.E Root Cause

The procurement timeline was planned optimistically without realistic EU supplier lead times (6–8 weeks for mass-production items) or buffer for specification changes, supplier price renegotiation, or first-article inspections. No pre-commitment of backup suppliers or interim storage was made early enough. The €200k expedite budget was not actively deployed; it remained a contingency line instead of an active risk-mitigation lever.

8.6.A Issue - Outreach Reach Severely Constrained: 3,000 Enrolled ≈9% of 65+, Misses Most Isolated Residents

The outreach model targets 3,000 enrolled high-risk residents by Month 7 (2027-05-08), approximately 9% of the estimated 34,000 residents aged 65+. The plan uses intermediary-held lists (housing associations, social services, NGOs, pharmacies), which are GDPR-safe but depend on existing service contact. Residents who are isolated, living outside formal housing, mistrustful of services, or recently arrived will not appear on any list and will not be contacted unless a 'no wrong door' heat-line call reaches them. The 60% contact-success gate (Month 4 = 2027-02-08) measures reach only for enrolled residents; it says nothing about the 91% not enrolled. This is a coverage failure disguised as an operational gate.

8.6.B Tags

• outreach-coverage-gap
• isolated-residents-missed
• enrollment-rate-9-percent
• gate-measures-wrong-denominator
• equity-goal-not-met

8.6.C Mitigation

Redefine success metric and expand enrollment strategy: (1) Set an absolute outreach goal of 5,000–6,000 contact attempts (not 3,000 enrolled), aiming for 50% enrollment = 2,500–3,000 signed up, plus 1,500–2,500 people reached once via heat-line or street teams (even if not formally enrolled). (2) Add a targeted door-knock phase in Month 5–6 (2027-03-08 to 2027-04-08) for top-floor and social-housing blocks with low intermediary reach (neighborhoods with <50% coverage). Use the 6 outreach FTE and hire 3 temporary door-knock staff (Months 5–7 = 2027-03-08 to 2027-05-08) to cover ≤1,000 additional households in priority blocks. This finds isolated residents who avoid formal services. (3) Require intermediary partners to report their outreach attempt rate and their base (how many residents do they have access to per organization?), so gaps are visible. (4) Measure equity: track enrollment by neighborhood deprivation index and housing type. Report what percentage of the 65+ population in each neighborhood was ever reached, not just what percentage was enrolled.

8.6.D Consequence

Without expanded outreach, the program will have reached only the 'easy' 9% of residents who were already known to services. When a heat event occurs, the 91% unreached will not have transport pre-arranged, will not be enrolled in the phone-check-in list, and will not know about cooling centers. Mortality and morbidity will be concentrated in the unreached group. A post-event analysis will reveal that the program helped its enrollees but missed its most isolated targets, undermining the 'equity' claim and the pilot's credibility for scaling. The playbook will be seen as a service for already-registered residents, not as a program for vulnerable populations.

8.6.E Root Cause

The plan conflated 'operationally safe and GDPR-compliant' (intermediary-held lists) with 'equitable reach.' It set a gate (60% contact success among enrolled residents) that measures operational fidelity for the people already enrolled, not coverage of the hardest-to-reach. The plan rejected building-level canvassing as too labor-intensive but did not cost a hybrid model: intermediary reach + targeted door-knock for low-reach neighborhoods. The root cause is a design bias toward legal safety and operational simplicity over equity and population reach.

Level 1	Level 2	Level 3	Level 4	Task ID
Castellón Heat Response Pilot				6676d5e5-1541-4c7f-8c47-4894882d185c
	Governance, Legal & Authority Establishment			d9dfc343-a90f-4151-9e6b-787dbc336da0
		Secure mayoral delegation of authority and incident-command structure		2a5c8fa3-670d-46b1-a15b-446dbd4ba73a
			Draft mayoral delegation letter and incident-command role matrix	e51bf5bb-affe-454c-a46f-6ec8b0ac9242
			Schedule and conduct mayoral delegation signature meeting	66fbf7a1-6a71-4a4a-9340-2ce730fa51ee
			Establish incident-command governance and inter-agency coordination protocols	d28b652b-7433-457e-8f36-b11c08f56f43
			Confirm incident commander and public-health deputy availability and delegation authority	e9bd4acc-2b3c-4cda-9124-ad8dfe376c6c
		Obtain written funder confirmation of drill-based gate evidence and partial-release rules		78f7337a-7aeb-42f4-b658-59b902df883b
			Draft funder communication protocol and gate criteria memo	03623e6e-23dc-48df-a655-fdd2acb11aff
			Schedule synchronous funder briefing call or in-person meeting	40b4dc60-2074-41a0-8395-316a2e185734
			Obtain written funder sign-off on drill acceptance and partial-release rule	f0feca88-7a6d-4564-bf29-554a19d7f9f0
			Draft and execute funding-agreement amendment incorporating gate terms	d4b59956-b276-4982-a8f3-9f9236f05db8
			Distribute signed funder decision framework to all governance stakeholders	b601137b-9e63-4a4f-90e5-5a17a4f8b7ff
		Engage GDPR legal counsel and obtain compliance opinion on intermediary-held lists model		95449008-5588-456b-877b-1843374577af
			Prepare scope-of-work brief for GDPR counsel	d0ff0cfa-c973-4d38-aa8a-79f3f9572134
			Identify and engage GDPR specialist law firm	564f61e9-34d3-4e09-b450-67405fcaf1c7
			Conduct interviews with partner organizations on data practices	efa0b97e-26fa-48d7-b505-7ae79e94165f
			Obtain draft GDPR legal opinion and review with municipal leadership	eebdaad3-bc22-4a8b-a23e-1a8afe93ae95
			Finalize and distribute template DPAs, consent forms and partner briefing materials	d45de88a-5e38-47d2-bf3a-d2f65d6fce80
			Execute signed DPAs with all partner organizations by Month 1.5 (2026-11-23)	2f98552c-fb64-4845-aa12-57e126ad0a53
		Negotiate and sign data-processing agreements with all partner organizations		34ef8a43-d2f0-42bd-bc3f-baefb4b0d7c0
			Prepare DPA templates and legal framework	067033ef-85a4-415f-bdae-564ef0051aba
			Conduct partner readiness assessment and identify blockers	7a01451a-8c4c-409c-9a33-035c79f577b2
			Engage partner legal and operations leads for DPA negotiation	52d34408-8764-4d43-9837-6cceac6d2799
			Execute DPA revisions and secure organizational sign-offs	d813df71-be49-453d-a576-b99863bc39e3
			Execute DPA signatures and confirm compliance read-in	e239bbe5-70a8-4384-88db-a36b38b256f6
		Establish municipal heat-response governance and crisis-communication protocols		e85c7aa9-9888-489b-96ee-1263753968be
			Prepare DPA template and one-pager for circulation	54912b5c-7dca-440d-aecf-9d6fac52c318
			Engage all 4–6 partner organizations in parallel negotiations	fe1df7d5-3ee4-4134-9372-438eb6b6d1e1
			Negotiate specific data-sharing terms and dispute resolution	4e3eddff-570f-46ab-8c2a-671f480d57b7
			Obtain internal municipal approvals and insurance/liability clearance	0332db7b-1eca-42ac-96e7-c17f252007ba
			Execute DPA signatures and maintain signed copies	dd638f2a-8ce5-46bc-8c29-162b60f7b4d4
	Procurement, Supply Chain & Vendor Management			687d0ff7-813b-47c6-8433-898d13555cb3
		Conduct supplier market research and issue RFQs for cooling kits and home-fitting supplies		459a7288-0b07-492a-a0f3-ba7776c9a0d0
			Map cooling-kit product categories and specifications	821c4f57-6dee-4bb5-a137-80e6774c1a9a
			Identify and pre-screen 5–8 candidate suppliers per product category	c71a950b-22f1-40ab-886a-89277d29b987
			Prepare RFQ template and detailed specifications document	c4effc7c-9c7b-46b5-a213-4aa1d96d2932
			Issue RFQs to primary and backup suppliers with deadline and response tracking	097596e7-e703-4112-8e66-44f3d0c9f84c
			Validate supplier capacity and expedite-cost scenarios against procurement timeline	4a0efafe-78a9-4f5a-bfde-98ed9ccd55d6
		Pre-qualify primary and backup kit suppliers with emergency-activation agreements		bdac102e-ac3c-47cb-9518-0f454cf1fef8
			Identify and contact 5–8 regional and national kit suppliers	24277dec-103b-4326-85ec-f56cb73a80d8
			Pre-qualify primary and 2 backup suppliers with written commitments	0e1b8fdb-68df-4f13-a649-0e59f347d085
			Secure interim storage facility and finalize delivery schedule	4e8af646-aa14-4206-b39d-8efd67ae9678
			Place first-tranche order (600–800 units) with fixed delivery window	e21a797c-15c1-41b2-bbfc-b3b81ae2e82d
			Conduct delivery timeline simulation and escalation stress-test	f2b661ae-9e2f-4f6d-85fc-83e82a031c86
		Secure interim storage facility and place first-tranche kit orders by Month 1.2 (2026-11-14)		d33d0786-20a2-410d-ab0d-add21fa60e32
			Identify and secure interim storage facility	09e17317-ee84-4737-a12b-9d3e9184ee69
			Finalize supplier contracts and delivery terms	fcc4a0e2-e560-4e33-aa41-347baa7b7ce1
			Establish kit receiving, QA and inventory-tracking workflows	9e7a58ef-5f0d-4541-9087-0aa4fb114642
			Place first call-off order (30–40% of 2,000 kits) by Month 1.2 (2026-11-14)	a99e6e3b-1ea1-4335-9abe-0a4a4fb424db
			Monitor supplier performance and activate backup if slippage occurs	d54d1e14-6d59-45b3-a9c8-dc00f3cd6d92
		Contract taxi and accessible-transport standby retainer with response-time guarantees		65cab99e-b312-4780-abb7-3ff186a203a2
			Identify and pre-qualify taxi and accessible-transport operators	0da64510-96d7-4db1-b318-bf08c63b11f8
			Issue RFQ with fixed response-time SLAs and dispatch protocols	65c83c1f-280c-4d9f-bde2-fc1f7f6c95a1
			Negotiate contract terms, pricing and mutual-aid activation clauses	1b89b17d-8adb-4850-8abe-5481388a4f22
			Secure insurance, liability and municipal procurement approvals	81a31817-5dec-4e2c-8e93-541784941cf0
			Sign retainer contract and establish operational coordination procedures	e94f5200-083a-46fa-9581-a6877a3137d2
		Procure refuge fit-out materials (water, first-aid kits, AEDs, signage) and complete installation		2722d851-11a0-4b55-9da4-90f6589adf22
			Identify refuge sites, secure facility-use agreements and insurance	68b66edb-ca40-4cec-8883-899b8f3cd40e
			Conduct accessibility audit and complete remediation for eight sites	f85014f4-84d6-46c3-9116-525b39635791
			Procure and deliver water, first-aid kits, AEDs and signage to all sites	150bc732-e89d-445a-9faf-356d00d2b836
			Recruit, background-check and train refuge-center managers and staff	eb846f8d-604a-45d8-8dc8-370ecd01af3f
			Install fit-out materials, confirm operational readiness and conduct mock activations	9ed5f1c2-01ec-4fbb-be90-aaabe588da1d
	Cooling Refuge Network Planning & Accessibility			71d82d86-af74-4ced-a988-da81408b390f
		Conduct accessibility audit of 10 proposed cooling-center sites		495be06f-b246-4c6f-ac44-d394d24e1517
			Schedule and contract independent accessibility auditor	ebcef830-82d3-4570-a6d3-4af39968ac1b
			Prepare internal pre-audit site checklist and accessibility rubric	e122b6f3-3b93-4a40-9268-bb3a1df43536
			Execute professional accessibility audits across all 10 sites with photo evidence	a826dc39-67f1-4ad7-bd30-f49b90234e02
			Deliver detailed audit report with remediation cost estimates and site ratings	a210b2da-7582-4ae7-bc4d-c4b87ecadea6
			Consult disability advocates and wheelchair-user groups on audit findings	bfbeb0f5-bfd1-470d-87af-f7db867bd0b1
			Produce remediation scorecard and prioritization for Month 2 (2026-12-08) opening	c1a8cd66-12d9-4245-86e1-cfd2b487445e
		Complete accessibility remediation for yellow-rated sites and confirm ≥50% places accessible		4f974862-ee3e-437b-bc67-502342c1729f
			Conduct accessibility audit of all 10 cooling-center sites	725b2b1f-bb4a-403b-8dc4-b92170e631ba
			Prioritize sites and obtain remediation cost estimates	4581a216-8dde-42f7-ac5a-e1ed5d66a818
			Execute accessibility remediation for yellow-rated sites	8937805b-e514-446f-9860-91a943060282
			Confirm final site network: ≥8 sites with ≥50% places accessible	8bf947eb-c29f-42e3-befe-0e948a829606
			Prepare and execute site-opening readiness checklist	66ddc784-c1f5-47a3-8264-df00901313ae
		Negotiate and sign facility-use agreements and liability insurance for each site		f0dc50cd-8741-4697-9333-85b3a14173a3
			Engage municipal legal counsel and insurance broker	e9afd34a-5c19-4e78-8b24-521b6535ee9a
			Draft template facility-use and liability insurance agreements	e6b688cd-5d64-43a2-865d-f448445707a6
			Identify and contact all 10 facility partners; confirm availability and scheduling constraints	898ec13e-128a-42a3-ace5-94b6c4aeee1e
			Conduct parallel review streams for facility-use agreements and insurance policies	a60c7c75-9d17-4402-bdde-c0d4a78de64f
			Negotiate liability insurance coverage terms and execute blanket/framework policy	fe3631ef-b3a8-4780-95c5-b7d9d6496185
			Collect executed agreements and insurance certificates; verify completeness and readiness	64401251-599b-43ce-b875-b5853ee1fb20
		Recruit, train and assign refuge-center managers and staffing teams		34631b04-a5ea-4db6-bdbf-c8301b09475b
			Design refuge-center manager job descriptions and competency rubric	2d6d9af9-1f56-4476-b9ce-318caf5e58c6
			Launch recruitment campaign via job centers, municipal networks and partner referrals	6a8f05cd-e9f6-45e8-8f04-97cb0f8a16f1
			Conduct candidate screening, interviews and reference checks	00d48ba6-1d09-4f21-8a71-6944e380d186
			Initiate background checks and first-aid certification for selected candidates	3cd231d2-f18f-4a7b-979a-eaf6eb1631f5
			Secure final hiring approvals and issue appointment letters by Month 2 (2026-12-08)	d6800d53-72cd-4026-ae79-650f7096b62c
			Assign managers to specific refuge sites and confirm facility-use agreements	f4537518-4ce3-45c8-b367-9bde5cf1260c
			Recruit and onboard cooling-center operational staff (10–14 FTE) in two phases	41b4b3d4-6683-4202-bb09-478b4843ebb0
			Deliver heat-safety, first-aid and fatigue-management training to all refuge staff	374f09bb-c921-4b7d-929c-03777cf9ff38
			Establish site-specific staffing rotas and on-call procedures for alert days	84890f21-27c6-406e-b66b-ed73fcbb3965
		Establish cooling-center operational standards, escalation procedures and incident documentation		6bea5490-0777-431b-afd1-2c6b6750f142
			Design and finalize cooling-center operational standards, escalation procedures and incident documentation	13ec16ae-9b42-4047-bba3-3dcc8f96b617
			Conduct tabletop and live mock drills at cooling centers to test procedures and staff readiness	f36ab06b-1196-4d81-9eca-59be068628d4
			Implement staff training on heat-illness recognition, escalation and incident response	a228eb36-297a-4351-8430-1d365fb84252
			Establish refuge-site coordination network with daily operational check-ins and escalation routing during alert season	241c3381-49b0-4014-9245-44577dc82d60
			Finalize refuge-site staffing rotas, contingency coverage and leave scheduling for Months 6.8–11.8 (2027-04-23 to 2027-09-23) season	418cabb4-16da-409c-a4b3-17883cd2ebe7
	Transport & Mobility Support Deployment			82e86ba5-7314-4ecd-8f4b-c3193bea8100
		Launch volunteer driver recruitment via job centers, faith organizations and community networks		8a0a4eff-5142-4c0e-976a-f3be4699433f
			Develop recruitment brief and eligibility criteria	0cc90403-c3d5-47a6-ab29-488158d001ae
			Engage partner organizations and establish intake processes	f50913cf-43e5-43b2-b7b1-025081abce93
			Establish rolling vetting cohorts and police background-check coordination	9c3d7895-ca0e-4eef-8d7b-e8b0418afe1b
			Secure volunteer driver insurance and schedule safeguarding training	63e14581-4aa7-4da9-b245-7d5066c3bc01
			Maintain recruitment pipeline buffer and monitor attrition through Month 3 (2027-01-08)	f5431a23-9996-4caf-b129-e6d669bdd20d
		Conduct police background checks and vetting for volunteer drivers in rolling cohorts		26b9afbf-f369-40da-ba3a-a2d8c99d89b8
			Establish police vetting service level and cohort protocols	e7e470ec-1f3e-4b3d-aad5-b49bb7904b54
			Design and pre-populate vetting documentation templates	57909435-43eb-4275-83e2-1e77525d68be
			Organize and execute rolling vetting cohorts fortnightly from Month 0.5 (2026-10-23)	30b67e79-11fb-426a-aa3b-ac8cb2f95fa9
			Validate candidate fitness and conduct reference verification in parallel	6eca45d2-9bf3-4330-baca-4a7d54e45151
			Communicate outcomes and complete administrative closure per cohort	d62fe398-bc2d-4ed0-9c42-dcdaf1633d4e
		Secure volunteer driver insurance and complete safeguarding training for all recruits		638ecbb0-cc01-4377-bd9d-53401d639029
			Obtain volunteer vehicle liability insurance quotes and framework policy	678df0a1-6ee1-4270-a181-0c549be14586
			Design and deliver safeguarding training curriculum for all volunteer cohorts	feec52cf-fe56-4c53-ae3b-e6173cd3802a
			Establish volunteer recruitment and vetting-cohort batching timeline	01a4603f-c857-4361-9354-d137f4d63235
			Conduct police background checks and driving-record verification per cohort	42e47c89-4f3c-45e3-9a22-326f3b33a4ae
			Verify insurance binding and conduct final volunteer approval before operational activation	30bda9e3-f0f2-4fb4-a8ef-0a0f480327a7
		Establish dispatch coordination center and systems (phone lines, real-time tracking, escalation routing)		ae006567-7a3b-4dc1-943c-a00238830601
			Procure telephony system and shared tracking platform	fae8daad-52bd-4d6a-adbe-ee7c59a37610
			Design call-handling workflows and escalation routing logic	aee58913-ed0b-462c-9bc8-599f95c28d59
			Build and test shared tracking spreadsheet with real-time data capture	ca6e7cd3-6dfc-489c-93a7-5056fbe0ffd2
			Recruit, train and onboard phone-line operators for call-taking and dispatch support	a27dba2d-bdbf-4a33-aae2-4201c548ec18
			Conduct integration testing and run heat-line drills before Month 2 (2026-12-08) gate	432ee75a-fcf1-4b2d-b04e-7b6a0f852bba
		Test transport systems in drill with wheelchair-user simulation and measure response times		b99a5694-8106-4bab-b353-3fa4133dd3d0
			Recruit and brief wheelchair-user testers and accessibility advocates	77e11d31-2ff6-44c6-8e31-8c9a7b9b6a7c
			Develop drill protocol with scripted transport scenarios and performance metrics	0c5f7482-cb21-4b8c-b482-3343f58aaa86
			Conduct pre-drill rehearsals at individual sites and dispatch center	5f53073b-d5ce-41db-a66a-fe9fbe22058d
			Execute full-system drill at Month 3.2 (2027-01-14) with real-time monitoring and escalation testing	4fbe1ad8-73c8-48c4-9bc5-5e412a1f7da2
			Analyze drill data and generate transport-performance report	99be070f-36aa-4cc3-b0af-500496efe9fe
	Outreach, Identification & Enrollment			631e198f-ef59-45df-ada6-1420b7113b4e
		Validate outreach-partner capacity (housing associations, social services, NGOs, pharmacies) by survey		132aa26d-0fb0-430f-969f-b8c4c085a24f
			Survey partner call-center capacity and current staffing	315cf8aa-6c5c-425a-8c32-e2c94d65ed53
			Model and validate combined outreach capacity against target	01183ef5-be59-4820-8c01-3bdecb6a9776
			Conduct mock-call simulation and validate tracking systems	8bdd9d8a-b805-40a0-b59e-f3608366398d
			Obtain written partner capacity commitments and finalize MOUs	3be52e97-0916-477a-8dc0-c730fd41e3cb
			Brief call-center operations expert and finalize capacity recommendations	0853f788-aa3f-4bf6-9e61-fb2500264509
		Design enrollment scripts, consent forms and contact-tracking systems for intermediary partners		21045b09-29e7-4b81-a567-529db087358f
			Draft enrollment scripts and consent forms in Spanish, Valencian	dc9b5ef5-c84c-47d1-8603-3e7e98e57f44
			Translate materials into 4-6 non-official languages	66c10201-ba52-446e-a0c7-af4538b14858
			Design contact-tracking system (spreadsheet or lightweight CRM)	2212d316-6d4e-44bf-97be-49a40009e2da
			Test materials and system with 50-100 sample households	8dd77fbc-b473-4c3a-b63a-7eadab919853
			Finalize and distribute systems to all 4-6 intermediary partners	d68a5843-832e-4aa5-8bff-db232eadfb85
		Train 50-80 partner staff and outreach workers on heat-illness recognition and escalation		86bbf009-5d75-4ee8-8ae5-895a26f6f003
			Assess training needs and develop curriculum	56ef138b-0cfd-4168-aa1b-0cdbeaf01984
			Recruit and vet qualified training instructors	7e04795e-9e0a-4d7b-927a-deffbfff869b
			Schedule cohort sessions and coordinate partner attendance	b1455dca-5aad-4234-aed7-d1755f2059d7
			Deliver classroom and practical heat-illness training	5c6033e2-fe3a-4e24-80f6-ff0945a4b551
			Document completion, remediate low performers and deliver refresher briefing	2e199b51-5321-4390-ab14-3b890880d9a3
		Launch enrollment campaign via partners targeting 3,000 high-risk residents by Month 7 (2027-05-08)		96da7434-0bc3-495f-9ee8-b65cf0788dab
			Design enrollment scripts and consent forms	5b1e42f5-3b19-4008-bcfd-6025ab79049b
			Conduct partner capacity and infrastructure survey	ca7ed209-ddc8-451f-ba19-4e4d3c541bb6
			Develop heat-illness recognition and escalation training curriculum	b46974ba-8f27-45de-99ed-0ef9977b6552
			Execute enrollment campaign targeting 3,000 high-risk residents by Month 7 (2027-05-08)	168493e1-0ed8-49f5-83a8-3ec22041cbfe
			Manage contact-list quality and escalate bottlenecks to partners	f4a51edd-f8f7-4cbe-bd6c-a73725196149
		Establish street contact pathway with NGOs for unhoused residents and drop-in cooling points		ce8147da-b0e2-496e-bf44-25c55e1fca82
			Identify and engage NGO partners for street outreach	dcb36ad2-ca12-4cb2-a487-13008c6b4576
			Locate and co-design drop-in cooling points at day centers	e6f48533-ac0e-416d-b731-52146de37fc6
			Recruit, vet and train NGO street-outreach team	c3cd2abe-41d4-4860-b4ce-d40f1642733f
			Supply and distribute street-contact kits (water, shade, referral cards) for alert days	ed9cffa4-caf7-4981-a0f9-a67f8710a13b
			Establish alert-day activation protocol and integration with heat-line dispatch	f121e26b-e6b1-40fd-9f94-0a588a629b86
	Home Kits, Installation & Equipment			5f2c06a6-b716-4ca6-9a50-4c231b2a07ed
		Develop household-eligibility rubric and targeting methodology for 2,000 homes		c2c26088-fc4a-4b2c-b45d-7ae97f579a23
			Co-design eligibility criteria and weighting framework	6598a382-222c-4bb4-9021-03025f4a2b24
			Validate data quality and obtain partner contact lists	6b6fca4c-cbee-4fc5-8840-d67b0063f817
			Conduct rapid pre-test with 50-100 sample addresses per category	8e42260e-e2ac-4dae-8eb4-28783a0e7d13
			Finalize methodology and document sign-off by Month 1.2 (2026-11-14)	d6b84467-97d6-47a1-a6e6-e07f9b3993c7
		Receive and stage 600-800 first-tranche kits in secure interim storage by Month 4 (2027-02-08)		80db734b-6ec7-4f7d-ae9c-ee52ebefcf25
			Place first-tranche kit orders with primary and backup suppliers	abb10f13-97c3-437b-9762-fd6855a3eed4
			Secure interim storage facility and prepare for kit receipt	13c921a9-9b6e-4922-aa79-a1b77f245709
			Validate kit quality and manage acceptance testing at arrival	199c7321-cbfb-4509-9da8-c5f53e2ac4b4
			Prepare buffer stock and spare parts for installation and replacement	210e27bd-d2a3-490f-9d98-58e9d28f6130
			Schedule and coordinate delivery logistics with handyperson teams	07dd01ba-946c-4c77-a010-15454c3bdce4
		Hire and train 10 handypersons on safe installation, fan safety checks and customer service		a1925980-718a-4d9c-aed4-345793212476
			Define handyperson job description and competency rubric	c82f8f59-1b4c-4baa-b543-6a8288352c7a
			Launch recruitment via job centers and temporary staffing agencies	3f1f676e-6a48-4f3a-bce3-0c6b0dbd94eb
			Conduct background vetting and first-aid certification of selected candidates	1560de3d-08d9-4c53-a1f4-1b92780fa952
			Deliver modular safety and installation training in two phases	28308b99-38cf-4107-af5f-f08c33270ed5
			Assign rotas, conduct on-site shadowing and establish fatigue-management protocols	5a16f033-16c1-460b-934f-8b9d10cbc6da
		Execute home visits, obtain resident consent and install kits (shading, fans, thermometers) Months 4-7 (2027-02-08 to 2027-05-08)		e044d556-bde3-43c2-9197-65a9365fb57c
			Prepare and issue home-visit scheduling protocol and resident consent process	ffadaec5-e9b8-4807-a85f-e731b32565f9
			Recruit, vet and train 10 handypersons on safe installation, fan protocols and customer service	3bc9a207-6a97-488a-a166-09595519b452
			Receive, inspect and stage first-tranche kits (600–800 units) in secure interim storage	311dd4b7-1139-439a-9542-084ed4d4a06e
			Execute home visits: consent, install kits and document outcomes by Month 7.3 (2027-05-17)	360c6567-fba2-464f-91d6-32ff074c7894
			Conduct quality-assurance inspections of installed kits and manage warranty/returns	8349b2d8-282e-481a-9def-fadae99e2654
		Conduct quality-assurance inspections of installed kits and maintain warranty/return logistics		7dc27b05-728f-4c3c-8187-d91b6b981471
			Appoint independent QA inspector and define inspection checklist	d997e2b7-102e-4ec2-9595-ae73d41a4699
			Conduct 10–20% sample inspections concurrent with installation	5770e7e1-72a3-484a-959d-00cdcb14e74f
			Establish rework SLA and rapid-defect corrective action (<5 days)	189d3c9d-f160-4341-85f4-12b427dc2c54
			Maintain spare-parts inventory and coordinate warranty claims and returns	303ac06c-af1d-4744-aea5-d2a8ae43d92e
			Conduct post-installation resident training and safety verification	8b0d0c7a-2802-46cd-ba48-bda7b7d7ad36
			Compile QA metrics and lessons-learned report for kit delivery cycle	30fd08c9-838d-49de-ad28-28bcdc1cc2bc
	Health System Integration & Worker Protection			69566e65-5986-4ab5-a219-3b7b5de1c38e
		Negotiate and sign MOUs with hospitals, EMS and primary care for daily aggregate heat-data reporting		cc39aef2-1359-4e93-a5d5-6317bf6609c2
			Map hospital, EMS and primary-care IT systems and data definitions	609458ec-2fee-4b62-bf9b-84ff78896418
			Prepare data-processing agreements (DPA) and MOU templates aligned with GDPR and Spanish law	2608ca71-dee5-4d4f-be66-83b6972cec27
			Schedule and conduct data-governance negotiation meetings with each partner organization	c1897a99-1c7a-4957-a1aa-d57aaa1a3033
			Execute signed data-processing agreements and MOUs from all three partner types	82e53c7f-2d27-4a0a-8c1a-4523fdc60adc
			Plan and execute Month 1.8 (2026-12-02) validation pilot: test daily data feeds and mock escalations	8a976b19-7bdf-4804-a9a9-fbfa57af668a
		Establish nurse triage phone line for heat-illness assessment and escalation during alert periods		a10ff8d0-396e-4d03-b7aa-48e23e0becb7
			Post nurse position and conduct recruitment	44183acf-379e-46b7-85c5-05989e9a259e
			Procure telephony system and conduct UAT	37fa2da8-f38d-42d6-a25b-65fb8175c14f
			Design and test triage protocols and escalation logic	2eb969af-27b6-4cad-93ee-5f0c30b9a4cb
			Recruit and train backup nurse and call-center operators	c448f826-438a-4436-ac87-b44bc8aacce1
			Run call-handling drills and finalize procedures before go-live	972a2b35-a3a4-4923-ac17-8a525054820f
		Develop heat-protection work clauses for municipal staff and municipal-contract workers		03af48d4-f8a7-4d07-b47c-c14db23da2a1
			Develop heat-protection work clauses for municipal and contracted workers	70af4bf9-2e5a-47b5-8f24-82f5416a961d
			Publish private-employer heat-protection guidance and recognition scheme	267178de-aefb-4265-be30-8ba84594a03e
			Monitor municipal and contractor compliance during peak season	725a1ba2-6faf-4cee-8029-3bb3d6e176fa
		Publish private-employer heat-protection guidance and establish recognition scheme		6ec78436-684d-4f56-9317-02a78d5d8eff
			Co-design guidance with employer stakeholders	df116375-b52e-49ec-9842-a836bb8a2e2c
			Design recognition scheme and incentive structure	ae531123-0193-489e-815c-02d08e3e95a1
			Publish guidance and launch recognition program announcement	f65ee4dc-1868-4a2c-b372-4271d88d1dfd
			Conduct employer outreach and uptake campaign	a1b3633c-13b9-4461-9fa1-813ddf97ea41
			Monitor recognition scheme adoption and publish annual recognition list	9cbf334f-0c69-4ce1-b660-ac273a0d4f95
		Monitor municipal and contractor compliance with heat-protection rules during season		06a8f715-6840-4947-91a7-3f5c8bc68294
			Hire compliance monitor and define inspection mandate	70138533-931d-4c76-93b3-a4f695b08294
			Develop standardized heat-protection compliance checklist and inspection toolkit	a8a33a5e-b96a-4e50-b041-f5793748eb6a
			Schedule site-inspection calendar and coordinate access with contractors	154ff772-3a2c-472d-ac75-f6cc321c237e
			Conduct compliance inspections and issue corrective notices	5c852704-9b57-4cf1-bcc3-8894f12995b4
			Track corrective-action closure and conduct follow-up inspections	cb119286-e756-49df-8e67-3663011b8897
	Communications, Language Access & Public Engagement			283a3562-0d39-47f0-b3b3-91be13311fc0
		Identify non-official languages (4-6) and recruit 8-12 paid community language ambassadors		f6be152e-3255-4a8f-a968-3c293fa3e10e
			Validate priority non-official languages from census and community leaders	1ebe081a-c207-4234-bdef-61197f973b0d
			Launch recruitment of 8–12 language ambassadors with flexible availability	de4fcb3e-66bd-40e3-80a1-a650b037801e
			Conduct focus groups and co-design heat-safety messages with 20–30 residents and trusted messengers	c0152a9b-378d-488b-8c38-6acd33ba7194
			Translate core materials into Spanish, Valencian and non-official languages	546b2d0d-c49d-48a7-bc54-9a45d54029f1
			Prepare and deliver heat-safety training to ambassadors and outreach partners	cc7467b6-97e3-43b1-aabe-6302e68c9f83
		Focus-test heat-safety messages with residents and co-design with trusted messengers		fe8d50d9-5f6e-443c-a589-29d80aa6f823
			Recruit and schedule resident focus-group participants	c16559dd-7c41-473e-97fc-5a5c51a8ee3f
			Prepare draft heat-safety messages and testing materials	73d05ca3-359a-4523-a0c3-9ec5c630b546
			Conduct 3–4 resident focus groups and document feedback	c3ef7b82-80ce-4a06-9368-9cd29c052cc0
			Convene trusted-messenger co-design workshops with pharmacists, GPs, caretakers and faith leaders	87015e4f-ebd9-4318-80e7-b7216394c0c8
			Synthesize feedback and revise messages; lock version 1.0 by Month 1.5 (2026-11-23)	91ef0569-ccf3-4415-974f-5d93dc3c9ac8
		Translate core materials into Spanish, Valencian and priority non-official languages		1661c485-688e-4c80-8260-05dad75df4a8
			Identify priority non-official languages and confirm speaker population	11b88753-297f-4976-a5f9-b10caba890c4
			Recruit and vet professional translation vendors and in-house language ambassadors	083627de-472b-4c5d-a8fe-85017b2cebbc
			Develop translation brief and glossary for heat-safety and program terminology	a3a35e6b-bc45-4f14-b618-97e3656634b9
			Translate core materials (flyers, door hangers, SMS templates, signage) into all priority languages	81acedd7-cbe2-40bf-b100-53672424d633
			Conduct focus-group testing and cultural adaptation of translated messages	36f4f3d7-63a9-4c23-8d78-43ced3988c19
			Produce and distribute printed and digital multilingual materials to partner sites and public channels	8fd4c9fb-bb90-4326-9790-67d5a9d6af73
		Conduct trusted-messenger briefings (pharmacists, GPs, caretakers, faith leaders) on heat risks and referral		0c372888-7b5d-4555-8665-2ab4d53cb7f8
			Identify and contact trusted-messenger organizations	9eb093f0-bf7e-4de2-bb9b-01d80ca3dbc0
			Develop messenger-briefing content and presentation materials	8b43a05a-d3b9-4b86-a33d-8570381da79c
			Schedule and deliver Phase 1 briefings (urban centers)	8cb48dc8-4346-4a25-be6f-b3b51e2f6047
			Schedule and deliver Phase 2 briefings (outlying and faith-based sites)	25896ced-3321-4054-894f-ae07134244c3
			Distribute take-home materials and schedule refresher reminders	5ad26377-9fc3-409f-9121-98f58dd06c2e
		Launch pre-season public campaign (radio, flyers, posters, door hangers, SMS) and establish misinformation-response protocols		52236bf9-8e22-4775-a1d0-15c5e3b87f00
			Book media slots and procure campaign materials	84e9475d-a3de-4532-801e-3c042dc20771
			Finalize misinformation-correction protocol and media partnerships	779bde1b-1ec9-4470-8121-b2fc8614ca59
			Pre-position printed materials at pharmacy, clinic and community sites	6dbbf07b-73ff-418c-8b77-a488a688241e
			Launch radio ads and social-media campaign	7ab098fc-73b2-4c3a-ba32-b40683baacc5
			Execute trusted-messenger briefings and co-design messaging with community leaders	25d6b3f9-1ffc-4bd9-979a-242fe478dec8
	Alert System, Heat Line & Operations Readiness			6e34b9e8-6a64-471b-ba4e-600badbd1f03
		Finalize alert-trigger thresholds (Levels 1-3) based on national forecast and AEMET partnership		44228c9c-013b-4e5a-9ec1-729c4741d09d
			Establish AEMET partnership and data-sharing agreement	35845473-1a8a-43bd-8667-0fac8e27c68c
			Validate threshold candidates using historical temperature and incident data	ab2fcce9-c150-4152-880c-c563a7256cd8
			Co-design thresholds with stakeholders and agree on Level 1 Advisory criteria	6763b0f9-23a2-4ffd-b1d6-8ce3177d7193
			Test threshold logic and integration with heat-line alerting system	557b5099-15bf-43e2-b3c3-05b6a4de5f63
			Finalize and document alert-trigger protocol in operational manual	98d7ba69-c79b-47ab-bf15-fcc886be7719
		Procure and test heat-helpline telephony system and shared tracking spreadsheet		dc4b13fc-3882-4ce2-8789-f66b7ce4a7b2
			Issue RFQ and procure VoIP telephony system	7f72305d-fac0-43a4-817d-544bc76c7f02
			Design and build shared call-tracking spreadsheet and escalation logic	5e577add-13aa-42b4-9144-dd7f6362d29a
			Conduct UAT and load testing with 5–8 mock inbound calls	32b0e409-e0fb-4203-b106-8f7269409a34
			Train phone-line operators and establish 08:00–22:00 call roster	820451e9-7589-42bd-928a-a1d7df5ced26
			Execute Month 2 (2026-12-08) readiness-gate heat-line test with 5–8 scripted requests	11dcce48-a1c7-4fb9-a489-1e0aa8546b5b
		Hire phone-line operators and train on call-taking, triage and escalation protocols		26ef28f3-920b-4a44-b810-1ef6aaf56ba0
			Recruit 3-4 phone-line operators via job centers and municipal networks	29ae6573-87fc-4662-92e6-6ca036cf0efc
			Obtain telephony system and install heat-line infrastructure by Month 1.5 (2026-11-23)	34336766-17a8-4a20-8ab7-24d9d935374c
			Design call-taking scripts, triage decision trees and escalation protocols	a8a547c3-2cce-4275-8a38-af9e70c0b2a7
			Conduct classroom and simulation training for phone operators on heat-illness recognition, de-escalation and system use	24f74589-c488-4c0a-9980-826f911f14d2
			Execute heat-line mock test and measure call-handling performance before Month 2 (2026-12-08) gate	7f9d6d4d-39e1-4dba-abe4-5153033c3bc7
		Establish command-seat activation procedures, delegation letters and inter-agency communication protocols		de0832d8-ccc9-4221-86c9-db47b49ef7ec
			Draft delegation letters and authority matrix	f4ba0d88-1f4b-461f-aeee-cda16a31f6d6
			Establish inter-agency communication protocols and escalation decision trees	7e6f07d6-ac75-498f-bc55-c0b6ac20cb8c
			Schedule formal signature meeting and secure executive sign-off	bf9b9af7-b269-44dd-983d-dde3e70834d4
			Test inter-agency protocols in tabletop and heat-line mock drills	13cd6a59-f43d-4657-8410-985a5fd6abba
			Clarify 24/7 on-call and deputy-contact procedures for weekend and holiday alerts	3ad5ecbd-0cf8-4645-9796-6602cd906d27
		Run heat-line drills and operational readiness tests before Month 2 (2026-12-08) gate		dccb407f-007c-40d9-8662-08fd638f401d
			Finalize heat-line alert trigger thresholds and AEMET partnership terms	48fd7e0e-7e31-47e7-9d82-401f740d7ec9
			Procure and test heat-helpline telephony system	c6db9c65-bbf6-429f-954d-7ba30c7c4e17
			Hire and train phone-line operators on call-taking and triage protocols	e4f5472f-02df-4720-8fd5-02e6c34d2c5a
			Establish command-seat activation procedures and inter-agency communication	cbd1ee3c-a187-45f7-ac2a-a8e132b5defb
			Conduct heat-line drills and operational readiness validation	952bdbd5-6dad-413b-b007-c0d7c0e5ef7d
	Evaluation, Baseline & Playbook Development			6396d0a1-fabb-4f01-93b5-e14d923d3193
		Request and validate 3-year baseline heat-related EMS calls, ED visits and excess-mortality data		48d4b8ba-4c8e-483f-a145-39515aaf26db
			Submit formal baseline-data requests to EMS, hospital and regional authority	0a7d9962-a01f-4c21-b698-362664cb7aa7
			Conduct data-quality audit on received historical records	9cc57819-1fd8-46c4-9790-bd2f9287e90a
			Engage heat-health epidemiologist to validate coding practice and build temperature-adjusted baseline model	55ef63ce-e217-4b01-902e-4b986354eee4
			Reconcile baseline figures across health services and assess statistical power for evaluation	3cb2fa74-73d2-4d9d-ae05-86572bb6ad98
			Obtain written confirmation of real-time data-reporting procedures for season	1d310c72-5f66-44cd-a26e-dc48b459e295
		Commission heat-health epidemiologist to audit baseline coding and assess evaluation power		27b15c5e-9a0a-4bb8-a645-6eabb1e38f96
			Identify and recruit heat-health epidemiologist	6a773df1-6de6-4589-93a8-438e14a2d3ae
			Deliver formal contract with audit scope and deliverables	dacabc10-025b-44c6-87c2-6577fc969497
			Coordinate baseline-data provision and quality review	b02744fb-26e4-4aec-b31d-8b933cee5b20
			Conduct manual coding review and case-definition validation	c0b0be60-2c20-49c8-9259-51dae9ad34fa
			Assess statistical power and evaluation-design implications	eb82c90c-19c3-4f3b-95f1-814782649314
		Finalize evaluation design (comparison groups, temperature adjustment, data-sharing agreements)		586022bc-2290-45e9-9f85-4260e29a2fd8
			Coordinate baseline data request from hospital, EMS and regional health authority	d88b5005-3089-46d8-803a-b61910b94544
			Commission heat-health epidemiologist audit of baseline coding and power	8c0f8212-68f2-465b-9e2d-65d4f1b3c568
			Validate data quality and reconcile baseline estimate assumptions	1a7b3071-265a-49d2-8fe7-fb5be2cbca7b
			Finalize evaluation design with university partner and establish comparison-group methodology	a65aaa88-0b5f-4f01-8e63-1f2626ed112d
			Document evaluation-design report and power-limitation disclosure	7c46fcf9-5a61-44e4-9e1f-6fb57bf9ff0b
		Conduct Month 3.2 (2027-01-14) full-system drill and generate after-action report with corrective actions		6203a084-4c8d-4be3-9bcb-2b1635bbcbc9
			Execute full-system drill at Month 3.2 (2027-01-14)	1054da05-877a-4a59-999d-5216d9378f87
			Draft after-action report and close 100% of corrective actions by Month 3.9 (2027-02-04)	cf10b17e-4406-49c4-9330-7b0c014ceddb
			Validate gate-measurement data: center hours, outreach success, transport time and after-action closure	de9bc8ff-a56e-44b7-b66d-5d7dea78ad00
			Convene gate-evaluation steering group and prepare funder decision brief	8f69b2ac-3544-4f35-b8d8-c33ddfa33fb7
		Draft Heat Response Playbook, scaling cost model and Year-2 roadmap for peer cities by Month 12 (2027-10-08)		f82bf409-f2d5-4bc9-8c74-8b24725863b6
			Commission and finalize playbook outline with evaluation partner	f2e12919-4833-460e-9921-94ffdb4245d6
			Integrate baseline data, drill outcomes and operational costs into draft sections	0daccc17-ad20-4274-aea8-5d355d6c680f
			Recruit 2–3 peer cities and conduct playbook-readiness testing by Month 11 (2027-09-08)	99cf1bab-511e-428f-9d9c-4f159703603b
			Finalize scaling cost model with sensitivity analysis and Year-2 funding roadmap	6190dfdd-906a-47c0-bd5b-1d1cd7cdc20c
			Conduct internal playbook-review cycle and stakeholder sign-off	c39e84b0-d16f-40af-b96d-37a5900a7c26
			Produce final playbook, evaluation report and Year-2 roadmap for delivery at Month 12 (2027-10-08)	ef50fac0-baa2-4bd4-92d6-e6e7fbe7da40
	Staffing, Training & Organizational Readiness			4e3250a8-3303-47c1-9e1c-3ac0b68ed534
		Recruit PMO coordinator, HR coordinator and administrative support staff		335e866a-e0e8-477b-95f1-b28ed8cf3c93
			Pre-clear position codes and salary bands with municipal HR	a146d889-353c-4a8d-b96e-bd3c59d75f45
			Develop job descriptions and competency rubrics	48068291-6ce0-4a6f-93b2-991b021fb5a0
			Issue recruitment announcements via civil-service roster and job boards	ede15c17-ea0a-48ba-a1d6-57049e02fa08
			Screen candidates and conduct interviews for all three roles	c058746d-a149-482e-82e2-cdf8901fc1c5
			Extend offers and initiate background checks in parallel	f2ff7bf5-12e9-47a5-807e-0247dddd7cbd
			Complete onboarding and system access provisioning by Month 0.8 (2026-11-01) start	7d5be587-441c-4e16-ac31-07f4d1e3635e
		Hire cooling-center staff, outreach workers, dispatch coordinators and phone-line operators in phases		4ceaf927-fce0-4fbf-b00f-7ad415a447a8
			Design role definitions, competency rubrics and recruitment brief	92b024ab-f33c-428f-9cfc-927412f5656d
			Coordinate with municipal HR and pre-authorize budget and position codes	3e3a053d-0254-4024-b115-0c9682097211
			Issue job announcements and launch recruitment in three tranches	21de443b-8bc6-488f-bf14-8da63207e580
			Conduct interviews, background checks and conditional offers by role cohort	13b0ce25-b3ae-420a-8d14-86652e469b43
			Onboard first cohort and begin core training (Month 3 = 2027-01-08)	07cf295f-e5da-4ed3-b870-0123e0f27129
			Stagger tranche-2 and tranche-3 hiring and training to build team capacity	11283828-8505-413a-bdc3-b6623090645c
			Establish rotas, on-call schedules and fatigue-management protocols	cdbdf963-26e1-4546-b55b-e3c8bf7b28c7
		Develop and deliver heat-safety, first-aid and fatigue-management training to all operational staff		f7231c49-9dbc-427d-b07e-a0090de1c4b0
			Design heat-safety and first-aid curriculum for operational roles	add36d57-21ec-428e-94dc-928623a3b05a
			Recruit and contract qualified training providers for cohort delivery	18749fac-686a-4b04-b4cf-c948eff491af
			Schedule and conduct staggered training cohorts by staff role and timeline	71a25e16-b819-463d-ac63-400aa44c806c
			Deliver fatigue-management and crisis-decision training for multi-day heat events	7f922626-a2d6-4f75-a4d7-68d8c65fda2b
			Validate training effectiveness via proficiency testing and competency sign-off	591b2332-6792-4192-a1be-b17cd8af1d0a
		Establish staff rotas, on-call procedures and crisis-leave policies for multi-day heat events		8c3af9bb-d851-4d46-bc05-edd626bb2dfb
			Draft staff rotas and on-call procedures for multi-day heat events	86b37b6a-1533-45b8-a1b3-8c582673bbb4
			Secure legal and labor-law review of crisis-leave and on-call policies	c9a4309a-5886-4bc0-9d80-42d791f07c95
			Pilot rotas during Month 3 (2027-01-08) drill and validate feasibility	4de969aa-f0fd-441c-b4f7-acb5234aae4e
			Establish fatigue-management thresholds and monitoring protocols	7e415fc4-677a-4dd5-8e14-bed5ec1e6745
			Define crisis-leave and compensation framework for alert-day activation	233c3a6c-179f-4f63-a8ad-8c16de441575
		Conduct organizational stress tests, team-cohesion exercises and safeguarding incident protocols		86485aca-fcc6-46a9-ba6c-2fcf0de77ee0
			Recruit and contract organizational-development facilitator	5d9563a5-4d6a-4247-9095-d9cbf41b186e
			Design stress tests and incident-protocol modules by role cohort	c38b811e-11c8-48ec-9a1c-e4e49c9b9520
			Conduct Month 2.5 (2026-12-23) cohort exercises and assess team dynamics	53a64164-31e3-4653-a737-1e4841c318ad
			Finalize safeguarding incident protocols and train all staff	7ec5131f-deda-44aa-9d78-945581d883ea
			Conduct Month 3 (2027-01-08) full-team exercise with stress debrief post-drill	d3755229-97f6-436f-99cd-ce5b32c4b7ec
	Gates, Testing & Program Continuation Decision			0e9e4c6d-a5c2-46fe-aaae-8472d8fa6f65
		Execute Month 2 (2026-12-08) readiness gate: verify procurement orders, accessibility, staffing and heat-line functionality		84cf8d6a-8d77-42ac-80c2-7957bb66ca58
			Verify procurement orders placed and tranche-1 budget spend authorization confirmed	1a958a89-9b4c-42c5-b3b5-07592b0caf51
			Audit accessibility of 8+ refuge sites and confirm ≥50% places fully accessible	f7d90506-ddb8-4664-a8e5-16902fdb0bd2
			Confirm all 8+ refuge sites have signed facility-use MOUs, named managers, and liability insurance in place	2d031f7a-9a6b-4318-9e85-df7b0044d02a
			Verify ≥20 volunteer drivers fully vetted and ≥30 in pipeline by Month 2 (2026-12-08)	33a9b4de-4508-4a5b-8f56-07882c7a1075
			Confirm heat-response heat line live and operationally ready (08:00-22:00 minimum)	f57df2e2-f6af-48ee-b16c-596088d1a6af
			Confirm outreach/escalation training delivered to ≥80% of operational partner and street staff	148ee668-1c3f-4041-a3dd-2f52c1300471
			Verify retainer contract signed with taxi/accessible-transport operator	1ff6a358-0352-4fd6-b2c2-c805ab6f835a
		Conduct Month 3.2 (2027-01-14) full-system drill (center hours, outreach contact, transport response, after-action closure)		9cf32591-450c-4c29-882e-c2b2b16f8d14
			Finalize drill protocol and circulate to operational teams	4c21d477-480c-48fe-9227-48c7dbf91cbf
			Recruit wheelchair-user testers and accessibility advocates	e6163e95-8f85-41b7-98c2-941b59f42287
			Stage drill observation, real-time data capture and communications	b66cec33-de53-4b12-baff-a09790662314
			Execute full-system drill with all operational sites and partners	c5cd59d5-e18f-4b4e-b679-b5946dd4fee4
			Conduct immediate post-drill debrief and after-action data consolidation	8b757e64-032b-444f-bf49-cdbd62a82edf
			Draft and circulate after-action report with corrective-action assignments	89405e63-9ee3-439d-acb2-1da9722de8f8
			Execute daily corrective-action closure tracking through Month 3.9 (2027-02-04)	a9652d75-572c-43da-b86e-e7dd64fce35c
		Evaluate Month 4 (2027-02-08) gates: ≥80% center-hour delivery, ≥60% outreach contact success, <45 min transport, after-action 100% closed		85df6645-f19a-4f99-8159-821726d1aba8
			Collect and reconcile drill data from all operational partners	774a24d5-ed69-4cb4-b706-f36597177374
			Verify center-hour delivery against ≥80% planned threshold	b10a2e0c-f500-4ed3-9ef9-6e127650a52b
			Measure outreach contact success rate from ≥300 enrollment attempts	e53fa399-9830-49c6-84d6-eceb6e03ee12
			Analyze transport response times for ≥30 requests under <45 min mean threshold	89e3a984-bb1a-4dd7-a93b-fb553f6f170d
			Validate completion of after-action corrective actions by Month 3.9 (2027-02-04)	ea5bb314-a486-410a-98bc-2a0290a4fb71
			Prepare gate-evaluation summary report and funder decision brief	b73fefa6-21de-482c-af1e-cbf2987dc95d
		If gates failed, execute Month 5 (2027-03-08) remediation and re-test; document scaling-back decisions if needed		677e48cc-c741-4f54-b3b4-0eb39c4cd102
			Pre-identify remediation pathways for each gate-failure scenario	6db2f4f2-ebe6-42bc-80d2-bc079fb3d770
			Negotiate Month 5 (2027-03-08) re-test window and timeline with funder	c09abac0-8727-4012-be30-5d6d6d252f8c
			Establish remediation budget reserve and pre-authorize procurement/staffing changes	61225d26-4bee-4d0f-8e61-274b64cbc6fd
			Maintain 20–30% staff reserve and design redeployment plan for bottleneck areas	624c694a-e97f-4aba-bc6b-20c829bdc3db
			Execute Month 5 (2027-03-08) remediation re-test and gate-outcome communication	48fdd241-ff48-4740-a555-1854b2016511
		Prepare funder decision brief: gate outcomes, contingency costs, funding request for Year 2		56a167b6-a81d-4227-8c3a-a4ef8ad4bb99
			Collate and validate gate-evaluation data from all sources	7faa4d7e-dabe-4be6-9c51-b3fb6c8e728e
			Reconcile contingency-reserve draw and actual tranche-1 spend	68816730-f80a-412c-a2a1-211f497c29ce
			Draft Year-2 scaling cost model and funding-sustainability analysis	657e1010-6c94-4bee-bacf-5f3d396749e1
			Prepare funder communication package: executive summary and supporting annexes	d0c176cc-3442-46cc-bd33-0e745e63696c
			Conduct pre-brief with funder and align on format, decision criteria, and timeline	8c404ec0-819a-4021-bbde-d57470ffbbac

Review 1: Critical Issues

1. Cool-season gate evidence creates unfalsifiable release cliff risk. The Month 4 (2027-02-08) gates (80% center hours, 60% outreach contact, <45-min transport) must be tested via drill alone because real heat events will not occur until June. If the funder rejects drill evidence, the €1.5M tranche-2 release is withheld, creating a €200–400k cash gap (€40–240k above the €160k available tranche-1 contingency). This forces mid-season service cuts to home kits, transport or outreach during peak summer heat, directly harming enrolled residents and destroying program credibility with funders and peer cities. No written funder pre-agreement on drill acceptance exists; this must be obtained by Month 0.5 (2026-10-23) before procurement begins.

2. Supply-chain compression leaves 4–8 week slippage exposure on home kits. Kits must be ordered by Month 1.2 (2026-11-14) and 40–50% delivered by Month 4 (2027-02-08) to enable installation by Month 7.3 (2027-05-17) during peak-risk May–June. EU supplier lead times are 6–8 weeks; a 4-week slip delays 60–80% of kits past the first heat events, rendering the 2,000-kit intervention ineffective for the highest-risk season. This forces either cuts to kit targets (500–1,000 homes lost) or an expedite premium (€50–100k, estimate) funded within the €800k kit category, which already holds the ≈€200k bundle for expedite premium, storage, buffer stock, QA and hydration; contingency is drawn only if costs exceed that category. Backup suppliers by Month 1 (2026-11-08) and the first call-off at Month 1.2 (2026-11-14) are critical but not yet pre-committed.

3. Intermediary-list outreach model reaches only 9% of high-risk 65+ population, leaving 91% unreached. The plan targets 3,000 enrolled residents from an estimated 34,000 seniors aged 65+, using housing associations, social services, NGOs and pharmacies that systematically exclude isolated, mistrustful and offline residents—exactly the highest-mortality group. The 60% contact-success gate measures fidelity among enrolled residents, not coverage of the unreached majority. When a multi-day heat event occurs in July–August, the 31,000 unreached seniors (before expansion) will depend on passive messaging (flyers, radio) proven ineffective for isolated populations, leading to preventable excess mortality and media exposure that the program claims to serve but abandons the most vulnerable. Adding door-knock and sentinel outreach for 1,500–2,500 additional contacts by Month 5–7 (2027-03-08 to 2027-05-08) would cost €50–80k and is not budgeted.

Review 2: Implementation Consequences

1. Successful Year 1 operationalization establishes foundation for scaled Year 2 replication at €2.3M/year recurring cost, but funding source and interagency coordination remain unidentified. If Month 4 (2027-02-08) gates pass and the pilot delivers measurable outcomes (operational KPIs: 80% center hours, 60% contact success, <45 min transport), the municipality gains credibility to scale from 3,000 enrolled to 8,000–12,000 by Year 2, extending coverage from 9% to 25–35% of high-risk 65+ population. This unlocks EU peer-city interest and strengthens the playbook's transferability. However, Year 2 requires €2.3M/year recurring (unidentified funding source) plus an estimated €50–100k for playbook refinement and cross-city training. Without pre-identified Year 2 funding by Month 9 (2027-07-08), scaling discussions will stall, leaving pilot infrastructure stranded, and the €400k spent on governance/PMO will yield no institutional continuity or policy change.

2. Successful home-kit installation by Month 7.3 (2027-05-17) creates visible, tangible benefit to enrolled residents and drives sustained enrollment and retention through peak-mortality July–August, multiplying the program's equity reach and harm-reduction effectiveness. If 2,000 homes receive kits (shading, fans, thermometers) by May, residents perceive real protection and word-of-mouth referrals accelerate street and intermediary enrollment by 20–30% (estimated 500–1,000 additional contacts). This also validates the home-kit model for scaling and strengthens the business case for Year 2 expansion. However, supply-chain delays of 4+ weeks (4–8 week exposure at Month 1 = 2026-11-08) push 1,200–1,600 kits into June–July, missing the enrollment-leverage window and reducing installed coverage to 400–800 homes by peak season. This forces either an expedite premium (€50–100k, estimate) funded within the €800k kit category or a kit-scope cut to 1,000–1,500 homes, undermining equity claims and the visible program credibility that drives Year 2 political support.

3. Intermediary-held-list outreach model preserves GDPR compliance and avoids municipal data-holding liability (legal exposure <€50k if designed correctly), but underfunding of door-knock and sentinel capacity leaves 80–90% of isolated high-risk residents unreached, resulting in preventable excess mortality during the July–August peak heat season. The GDPR-compliant design (€30k legal work + partner MOUs) removes the risk of a €2–4% regulatory fine and reputational damage from unauthorized health-data collection. However, the 3,000-enrolled-9%-reach model misses about 31,000 seniors aged 65+ (about 29,000 after door-knock expansion) living alone or in disconnected housing, who will suffer the highest heat-related mortality. A targeted door-knock phase for high-deprivation blocks (Months 5–7 = 2027-03-08 to 2027-05-17) costs €50–80k (11–18% of the €450k outreach budget) and could add 1,500–2,500 additional contact attempts and 500–750 enrollments from the unreached population. Without this investment, post-event analysis will reveal excess mortality concentrated in unreached neighborhoods, triggering media scrutiny ('program helped the connected and abandoned the isolated') that destroys municipal credibility and Year 2 political support.

Review 3: Recommended Actions

1. Secure written funder pre-agreement on drill-based gate evidence and partial-release rule by Month 0.5 (2026-10-23); high priority, risk reduction €200–400k. Cool-season gates depend entirely on drills; if funder rejects evidence, the €1.5M tranche-2 release is withheld, creating a €200–400k unfunded gap that exceeds the €160k available tranche-1 contingency. Written confirmation by Month 0.5 (2026-10-23)—before any procurement—eliminates this ambiguity and unlocks contingency-funding negotiation if needed. Immediate action: incident commander and PMO lead schedule a synchronous funder briefing, present the partial-release rule (€750k at Month 4 = 2027-02-08 if unmeasurable, remainder after Month 5 = 2027-03-08 re-test), and obtain written sign-off within 48 hours.

2. Issue detailed procurement specifications and place first-tranche kit orders (600–800 units) by Month 1.2 (2026-11-14); critical priority, cost exposure €50–100k expedite premium. Cooling kits have 6–8 week EU supplier lead times; any 4-week slip pushes 60–80% of stock into June–July, after peak-risk May season and first heat events. Pre-qualifying 2–3 backup suppliers and placing orders 7 days earlier (Month 1.2 = 2026-11-14 vs. Month 1.5 = 2026-11-23) provides one-week buffer. Immediate action: procurement lead finalizes specs by Month 0.8 (2026-11-01) (a supplier market sounding may run at Month 0.3 (2026-10-17)), selects primary and backup by Month 1 (2026-11-08), and places the first call-off by Month 1.2 (2026-11-14), with the expedite premium (€50–100k, estimate) held within the €800k kit category.

3. Add 1,500–2,500 contact attempts via targeted door-knock and sentinel outreach to high-deprivation neighborhoods Months 5–7 (2027-03-08 to 2027-05-17); medium priority, equity cost €50–80k (~11–18% of the €450k outreach budget), reach +500–750 enrollments from unreached population. Intermediary-held lists reach only 3,000 enrolled (≈9% of 34,000 high-risk 65+), leaving about 31,000 isolated, mistrustful residents unreached before expansion (about 29,000 after) and at highest mortality risk. Allocating 2–3 temporary outreach staff (Months 5–7 = 2027-03-08 to 2027-05-17) to canvass top-floor and social-housing blocks identified via deprivation index adds 1,500–2,500 contact attempts with an estimated 30–50% conversion to enrollment. Immediate action: outreach lead designs canvassing rubric and site-selection methodology by Month 1 (2026-11-08), secures budget reallocation from the €450k outreach category by Month 2 (2026-12-08), and launches recruitment of 2–3 temporary door-knock staff by Month 4 (2027-02-08).

Review 4: Showstopper Risks

1. Volunteer driver recruitment and retention pipeline may collapse mid-season, forcing taxi-only fallback (+€150–250k unbudgeted cost). Likelihood: Medium. Vetting timeline (4–8 weeks per person) is compressed into 8 weeks (Months 0–2 = 2026-10-08 to 2026-12-08) to achieve ≥20 recruits by Month 2 (2026-12-08) gate. Attrition during multi-day July–August heat waves is projected 15–25%, requiring 50–52 recruits at Month 0 (2026-10-08) to sustain 40 active by Month 11 (2027-09-08). If fewer than 20 recruits are in the pipeline at Month 1.5 (2026-11-23), the taxi retainer scales up proportionally, capped at €80k; anything above that is the taxi-only fallback (+€150–250k), which needs an approval decision and would draw 54–89% of the €280k contingency (only €160k available before Month 4 = 2027-02-08) or cut kits. Compounding: if procurement also slips (+€50–100k expedite premium, held within the kit category), the combined exposure with the taxi-only fallback reaches €200–350k, exceeding all free contingency. Contingency: establish a standby volunteer reserve pool of 15–20 pre-vetted candidates (30–40% above active roster target) recruited and trained by Month 3 (2027-01-08), activated only on Level 3 alerts or if active roster falls below 20.

2. Intermediary-held outreach model fails to reach isolated high-risk residents; coverage remains 9% of 65+ population, leaving about 31,000 people at peak mortality risk and exposing the program to media criticism and Year-2 funding loss. Likelihood: High. Housing associations, social services, NGOs and pharmacies predominantly contact residents already known to services, not isolated living-alone seniors or recent migrants who distrust official channels. The 3,000-enrolled target from 34,000 seniors represents inadequate reach; the 60% contact-success gate measures fidelity among enrolled only, not population-level coverage. If door-knock and sentinel outreach for high-deprivation neighborhoods (Months 5–7 = 2027-03-08 to 2027-05-17, estimated €50–80k cost) is not added, July–August excess mortality will concentrate in unreached populations, triggering post-event media investigation and political backlash that blocks Year-2 scaling. Compounding: equity gaps undermine the playbook's credibility for peer-city adoption and funder confidence. Contingency: Pre-identify and budget 2–3 temporary door-knock outreach staff (Month 1 = 2026-11-08) and execute neighborhood-level equity audit (coverage by deprivation index, housing type, language) by Month 9 (2027-07-08); if <20% of high-deprivation residents are reached by this date, add door-knock capacity for the final 6 weeks of season.

3. Baseline heat-related EMS/ED data validation may reveal small-area counts insufficient for statistically credible evaluation, undermining Year-2 funding case and playbook transferability to peer cities. Likelihood: Medium. Provisional baseline estimates (80–120 EMS calls, 15–25 excess deaths per summer) are unverified pending data audit at Month 1 (2026-11-08). If actual baseline is 50% smaller (40–60 EMS calls, 8–12 deaths), statistical power to detect a realistic 10–15% program reduction collapses; the evaluation becomes underpowered and the final report must document this limitation explicitly, weakening the scaling cost model. Compounding: if procurement or staffing slips so that the program does not operationalize fully until June, real-season outcome data collection begins late, further reducing sample size and power. If Month 4 (2027-02-08) drill-based gates are passed but real-season data show no measurable harm reduction by Month 12 (2027-10-08), the playbook loses credibility and peer cities will reject the model as unproven. Contingency: Conduct baseline data audit by Month 1 (2026-11-08); if actual baseline is ≤50 EMS calls per summer, reframe evaluation focus to secondary outcomes (utilization, equity reach, partnership fidelity) instead of mortality attribution, and extend evaluation timeline to include Year 2 data (Months 13–24 = 2027-11-08 to 2028-10-08) to accumulate adequate sample size for credible analysis.

Review 5: Critical Assumptions

1. Intermediary organizations possess adequate call-center capacity to execute ≥5,000 contact attempts per month at 60% success rate during alert season. Impact if incorrect: contact success drops to 40–50%, failing the Month 4 (2027-02-08) gate and withholding €1.5M tranche-2 release. Capacity shortfall of 20–30% forces either reduced enrollment targets (2,000 vs. 3,000) or emergency activation of €100–150k in municipal outreach staff, consuming 94% or more of the €160k tranche-1 contingency. Compounding: if transport also falters due to volunteer shortfall, both gates fail simultaneously and the city has no recovery path within budget. Validation: conduct rapid partner capacity survey (housing associations, social services, NGOs, pharmacies) by Month 1 (2026-11-08); model combined call attempts and success rate under multi-day fatigue; place written capacity commitments in partner MOUs by Month 1.5 (2026-11-23); mock-call drill at Month 1.5 (2026-11-23) so fixes can land before the Month 2 (2026-12-08) gate.

2. EU kit suppliers deliver 40–50% of cooling-kit stock (600–800 units) by Month 4 (2027-02-08) and 100% by Month 6 (2027-04-08), enabling 100% installation by Month 7.3 (2027-05-17) before peak-risk May–June. Impact if incorrect: 4–8 week slip (realistic for EU industrial lead times) pushes 60–80% of kits into June–July, after first heat events and peak-risk season; 500–1,000 homes miss protected windows. Cost exposure: €50–100k expedite premium or €150–250k kit-scope reduction (from 2,000 to 1,000–1,500 homes). Compounding: if procurement slips AND volunteer recruitment fails, both transport and home-kit leverage vanish, eliminating the program's dual protective pathways. Validation: finalize specs by Month 0.8 (2026-11-01) (supplier market sounding at Month 0.3 (2026-10-17) only); pre-qualify 2–3 backup suppliers by Month 1 (2026-11-08); place binding first-tranche order (600 units) by Month 1.2 (2026-11-14)—one week earlier than planned—with signed delivery SLAs; confirm secondary stock arrives by Month 4 (2027-02-08) by Month 2 (2026-12-08) or activate backup supplier immediately.

3. Funder accepts drill-based evidence (operational KPIs from full-system drill at Month 3.2 = 2027-01-14) as sufficient proof of gate success; partial-release rule (€750k at Month 4 = 2027-02-08 if unmeasurable, remainder post-May re-test) is documented in writing before Month 1 (2026-11-08). Impact if incorrect: funder withholds €1.5M at Month 4 (2027-02-08) citing insufficient real-event data; €200–400k cash gap emerges (€40–240k above available €160k tranche-1 contingency), forcing service cuts to home kits, transport or outreach during peak summer season, directly harming enrolled residents and destroying Year-2 credibility. Compounding: if cool May–July occurs naturally and no heat events test operations until August, gates become unmeasurable on any evidence (drill + real), triggering complete funding withhold. Validation: obtain written funder sign-off on partial-release rule and drill acceptance criteria by Month 0.5 (2026-10-23)—before procurement begins; document in signed funding amendment; brief incident commander and CFO monthly on funder alignment to flag ambiguity early.

Review 6: Key Performance Indicators

1. Heat-related EMS call volume change (non-gating expectation of a 10–15% reduction, hypothesis only, reported with confidence ranges, by Month 12 = 2027-10-08; baseline 80–120 calls/summer, provisional). Success requires year-on-year comparison of aggregate heat-related EMS dispatch volumes during the season (Months 6.8–11.8 = 2027-04-23 to 2027-09-23) against the provisional 3-year baseline (80–120 calls estimated; audit pending Month 1 = 2026-11-08). Impact: A 10–15% reduction (8–18 fewer calls) validates the program's operational reach and protective effectiveness; <5% reduction signals outreach, home-kit or cooling-center underutilization requiring mid-season course correction. Interacts with: supply-chain delays (if kits slip past June, home-intervention effect is lost); intermediary-reach gaps (if 91% of 65+ remain unreached, EMS call reduction concentrates only in enrolled 9%, understating true population impact). Monitor: daily aggregate EMS count reporting (MOU by Month 1 = 2026-11-08); weekly trend analysis by incident commander; post-season epidemiologic attribution analysis by Month 12 (2027-10-08) with temperature adjustment and confidence ranges; recomputed against validated baseline after Month 1 (2026-11-08) audit.

2. Outreach contact success rate ≥60% among enrolled high-risk residents (Month 4 = 2027-02-08 gate; tracked via drill + season Months 6.8–11.8 = 2027-04-23 to 2027-09-23). Success requires intermediary partners and city teams to reach ≥60% of enrolled residents (estimated 3,000 by Month 7 = 2027-05-08) within 4 hours of Level 2 alert declaration. Impact: 60% success = 1,800 residents contacted; <60% success fails the gate (65% (proposed threshold) is the early-warning level; results of 55–59% trigger corrective action within 48 hours and re-test before the gate), withholding €1.5M tranche-2 and forcing service cuts during peak heat. Interacts with: intermediary-capacity shortfall (if housing associations, social services lack call-center staffing, success drops to 40–50% mid-season); volunteer fatigue (if dispatch slows, residents cannot follow up on alerts with transport offers, reducing perceived reliability and future enrollment). Monitor: daily contact-attempt logs from all intermediary partners (shared spreadsheet, aggregate counts only); weekly success-rate calculation (contacts reached ÷ enrollment base); real-time escalation if weekly rate falls below 60% for ≥2 consecutive weeks; corrective action (additional staff, script revision, partner re-briefing) within 48 hours.

3. Equity coverage: Year-1 expectation 13–16% overall of high-risk 65+ population (estimate); 20–25% (≈7,000–8,500 of 34,000 residents) is the Year-2 target, reached via enrollment + one-time contact; priority: ≥30% coverage in top-3 highest-deprivation neighborhoods. Success requires outreach expansion beyond intermediary lists to door-knock and sentinel pathways (Months 5–7 = 2027-03-08 to 2027-05-17, estimated €50–80k investment). Impact: 13–16% coverage in Year 1 validates population reach; <15% signals equity failure and leaves 85% unreached at peak mortality risk during July–August, triggering post-event media criticism and Year-2 funding loss (estimated €2.3M/year in jeopardy). Interacts with: intermediary-capacity gaps (if partner calls are 40–50% successful, baseline enrollment stalls at 1,500–1,800, floor coverage at 4–5%); kit-delivery slips (if homes lack visible protection by May, word-of-mouth enrollment growth stalls, depressing neighborhood-level reach). Monitor: monthly enrollment and contact audit by neighborhood deprivation index and housing type (top-floor, social housing, private rental, unhoused); disaggregate contact source (intermediary vs. door-knock vs. street) to identify gaps; Month 7 (2027-05-08) interim equity review; add door-knock capacity if high-deprivation coverage <20% by Month 9 (2027-07-08).

Review 7: Report Objectives

1. Primary objectives: operationalize a gate-driven, replicable heat-response pilot in Castellón de la Plana (Month 0–12 = 2026-10-08 to 2027-10-08) that demonstrates measurable harm reduction and generates a transferable playbook for other EU cities. The report documents strategic decisions (11 primary, 12 secondary), operational plans, risk registers, and staff/procurement requirements to meet four scale gates at Month 4 (2027-02-08): ≥80% refuge hours, ≥60% outreach contact success, <45-min transport, after-action closure. Key deliverables: Heat Response Playbook with SOPs; scaling cost model (≈€2.3M/year estimated); evaluation report with temperature-adjusted baselines and attribution limits; Year-2 roadmap with funding recommendations.

2. **Intended audience: municipal leadership (mayor, health officer, CFO) deciding immediate approval and resource commitment by Month 1 (2026-11-08); funder requiring written confirmation of drill-based gate evidence and partial-release rule by Month 0.5 (2026-10-23); peer EU cities (Barcelona, Valencia, Poznań, Modena) evaluating replicability post-Month 12 (2027-10-08). The report informs: (a) funder decision on cool-season gate acceptance (€200–400k cash-flow risk if rejected); (b) procurement and hiring timelines with supply-chain buffer validation; (c) Year-2 funding source identification (€2.3M/year unidentified).

3. Version 2 should differ from Version 1 by: (1) documenting funder's written sign-off on drill evidence and partial-release rule (gate 0, pre-requisite before Month 1 = 2026-11-08); (2) replacing provisional baseline estimates (80–120 EMS calls, 15–25 deaths) with validated audit results from hospital/EMS (due Month 1 = 2026-11-08); (3) confirming supplier quotes and backup-supplier emergency-activation agreements for kits and transport (Month 1.2 = 2026-11-14 commitment); (4) adding granular equity coverage targets by neighborhood deprivation index (Year-2 target ≥20–25% of 65+ population, ≥30% in top-3 deprived areas; Year-1 expectation 13–16%); (5) pre-specifying drill protocol and gate measurement SLAs (final Month 2.5 = 2026-12-23).

Review 8: Data Quality Concerns

1. Baseline heat-related EMS/ED coding and volume estimates remain provisional and unvalidated; audit deferred to Month 1 (2026-11-08). The provisional baseline (80–120 EMS calls, 15–25 excess deaths per summer) underpins the evaluation design and power calculation; if actual baseline is 50% smaller (40–60 calls), statistical power to detect a realistic 10–15% program reduction collapses, and the final report must document this limitation explicitly. Consequence: playbook credibility for peer-city adoption weakens; Year-2 funding case becomes harder to justify if outcomes appear inconclusive. Validation approach: request hospital/EMS administrative data (3-year history, heat-coded calls by date/hour/age) by Month 0 (2026-10-08); conduct manual chart review for 50–100 cases to validate clinician coding practice (which ICD-10 codes or symptom patterns count as heat-related); deliver audit and temperature-adjusted baseline model by Month 1 (2026-11-08); if baseline is materially different from provisional estimate, recompute evaluation power immediately and adjust attribution design.

2. Intermediary partner call-center capacity and summer staffing availability are estimated but not surveyed; capacity survey deferred to Month 1 (2026-11-08). The outreach gate (60% contact success from ≥300 attempts) assumes housing associations, social services, NGOs and pharmacies can sustain ≥5,000 contact attempts/month during May–September season with 80–90% staffing availability (15–20% typical summer turnover). If actual capacity is 20–30% lower (inadequate call staffing, competing priorities mid-season), contact success drops to 40–50%, failing the Month 4 (2027-02-08) gate and withholding €1.5M tranche-2. Consequence: outreach reach collapses from 3,000 to 1,800–2,400 enrolled, and the program must either reduce targets or draw €100–150k in emergency municipal staff (63–94% of contingency). Validation approach: issue a brief partner survey by Month 0.8 (2026-11-01) asking each intermediary current staff count, typical call-center hours/person/day, summer turnover forecast; model combined capacity and stress-test it in a mock-call drill (50–100 simulated calls) at Month 1.5 (2026-11-23); obtain written capacity commitments and staffing reserves in partner DPAs by Month 1.5 (2026-11-23).

3. Cooling-kit supplier lead times and expedite-cost benchmarks are not quoted; supplier capacity is assumed at 6–8 weeks and expedite premium is capped at 10–15%, but actual offers remain unknown. Procurement of 2,000 kits (€800k total including expedite) requires first call-off placement by Month 1.2 (2026-11-14) and 40–50% delivery by Month 4 (2027-02-08); if suppliers report lead times ≥10 weeks or expedite premiums >15%, the €50–100k budget reserve is insufficient and kits slip into June–July, missing peak-risk May season and reducing home-intervention effectiveness by 30–50%. Consequence: if both kit delivery and volunteer recruitment slip simultaneously (compound risk), transport and home-kit leverage both degrade and the program loses dual protective pathways. Validation approach: issue detailed RFQs to 5–8 kit suppliers after specs at Month 0.8 (2026-11-01) (market sounding at Month 0.3 (2026-10-17) only) requesting firm quotes, standard and expedite lead times, and minimum-order requirements; pre-qualify 2–3 backup suppliers with written emergency-activation agreements (7-day notice, price cap, premium fee acceptance) by Month 1 (2026-11-08); lock in primary order with confirmed delivery SLAs by Month 1.2 (2026-11-14) and hold the expedite premium (€50–100k, estimate) within the €800k kit category.

Review 9: Stakeholder Feedback

1. Funder's written acceptance of drill-based gate evidence and partial-release rule by Month 0.5 (2026-10-23); critical for €1.5M release timing and contingency-funding strategy. The cool-season gates (Month 4 = 2027-02-08) depend entirely on drill performance (center hours, outreach contact, transport time from simulated alert scenarios). If funder rejects drill evidence and demands real heat-event validation, the €1.5M tranche-2 release is delayed to Months 5–6 (2027-03-08 to 2027-04-08), creating a €200–400k unfunded gap (€40–240k above the €160k available tranche-1 contingency). This forces mid-summer service cuts to home kits, transport or outreach during peak July–August heat season, directly harming enrolled residents and undermining Year-2 credibility. Obtain written confirmation of the partial-release rule (€750k at Month 4 = 2027-02-08 if unmeasurable, remainder after Month 5 = 2027-03-08 re-test) and drill-acceptance criteria in a signed funding amendment by Month 0.5 (2026-10-23), before procurement begins.

2. Validated baseline heat-related EMS/ED coding practice and volume confirmation by Month 1 (2026-11-08); necessary to assess evaluation power and playbook credibility for peer-city replication. Provisional baseline estimates (80–120 EMS calls, 15–25 excess deaths per summer) are unverified pending hospital and EMS data audit. If actual baseline is 50% smaller (40–60 calls), statistical power to detect a realistic 10–15% program reduction collapses; the final report must document this limitation, weakening the playbook's transferability and Year-2 funding case. Consequence: if peer cities adopt the model and see no measurable harm reduction in their own pilots, credibility cascades downward across EU networks. Request 3-year historical EMS and ED administrative data by Month 0 (2026-10-08); conduct manual chart review (50–100 cases) to validate clinician coding for heat-related presentations; deliver audit and temperature-adjusted baseline model by Month 1 (2026-11-08); if actual baseline differs >30% from provisional, recompute evaluation power and revise attribution design immediately.

3. Intermediary partner capacity commitment and written staffing-reserve guarantee by Month 1.5 (2026-11-23); essential to validate the 60% outreach contact-success gate (Month 4 = 2027-02-08) and prevent mid-season collapse. Housing associations, social services, NGOs and pharmacies are assumed to sustain ≥5,000 contact attempts per month at 60% success during May–September season with ≥80% staffing availability. If actual capacity is 20–30% lower (competing priorities, summer turnover ≥20%), contact success drops to 40–50%, failing the gate and withholding €1.5M tranche-2. This forces either reduced enrollment (1,500–2,000 vs. 3,000 target) or emergency activation of €100–150k municipal outreach staff (63–94% of tranche-1 contingency). Conduct partner capacity survey (email questionnaire) by Month 0.8 (2026-11-01) asking each intermediary current call-center FTE, call duration per resident, summer turnover forecast; model combined capacity and validate in a mock-call drill (50–100 simulated enrollment calls) at Month 1.5 (2026-11-23); obtain written capacity commitments and minimum-staffing reserves in partner DPAs by Month 1.5 (2026-11-23).

Review 10: Changed Assumptions

1. Pilot-city climate and heat-event frequency assumptions (Mediterranean 15–25 excess deaths/summer provisional baseline) may not match actual historical patterns; re-evaluation required by Month 1 (2026-11-08) data audit. Castellón de la Plana's baseline is provisionally estimated at 80–120 EMS calls and 15–25 excess deaths per summer, sourced from published literature and peer-city benchmarks, not from verified municipal records. If actual 3-year historical data reveals ≤40–50 EMS calls per summer (50% lower), the evaluation will be underpowered to detect a realistic 10–15% program reduction, requiring evaluation design revision and extended data collection to Month 24 (2028-10-08). This directly impacts playbook credibility for peer-city adoption and Year-2 funding case. Validate by requesting hospital and EMS administrative data by Month 0 (2026-10-08); conduct baseline audit and temperature-adjusted modeling by Month 1 (2026-11-08); if baseline differs >30% from provisional estimate, recompute statistical power immediately and adjust evaluation scope.

2. Intermediary-partner staffing stability and call-center capacity during multi-day July–August heat surges assumed at 80–90% availability; actual summer turnover and fatigue patterns unvalidated. The outreach model assumes housing associations, social services, NGOs and pharmacies can sustain ≥5,000 contact attempts per month and 60% success rate under multi-day alert conditions (Months 9–11 = 2027-07-08 to 2027-09-08). Summer staff turnover and competing priorities (vacations, concurrent crises) are projected at 10–20% but not benchmarked against actual municipal-partner data. If real turnover reaches 25–30%, contact success drops to 40–50%, failing the Month 4 (2027-02-08) gate and forcing €100–150k emergency municipal outreach staffing (63–94% of tranche-1 contingency). Re-evaluate by issuing partner capacity survey (Month 0.8 = 2026-11-01) and stress-testing in mock-call drill (Month 1.5 = 2026-11-23); lock written staffing reserves into partner DPAs (Month 1.5 = 2026-11-23).

3. Year-2 funding source (€2.3M estimated recurring cost) and political continuity assumed available; no identified source, no mayoral term guarantee, no guarantee of cross-party support post-election cycle. The playbook is intended for scaling to other EU cities and establishing a sustained municipal program beyond Month 12 (2027-10-08). However, Year-2 funding is entirely unfunded and municipal political continuity is not guaranteed (elections occur periodically, administration changes). If Year-2 funding is unavailable by Month 9 (2027-07-08), the municipality cannot sustain refuges, transport or outreach beyond Month 12 (2027-10-08), orphaning infrastructure and violating implicit commitments to enrolled residents. This undermines peer-city credibility ('pilot program abandoned after Year 1'). Identify and pre-commit Year-2 funding source by Month 9 (2027-07-08) via EU climate grants, national health budget co-financing or municipal budget mainstreaming; include a 'continuity of command' clause in the mayoral delegation (Month 1 = 2026-11-08) ensuring heat-response priorities persist across electoral transitions.

Review 11: Budget Clarifications

1. Contingency reserve allocation and draw-down authority remain undefined; free contingency €280k (€160k tranche 1 + €120k tranche 2) may be consumed by a single risk (taxi-only fallback +€150–250k, or delayed-release cash gap €200–400k), leaving zero buffer for compound failures. Impact: if supply-chain expedite premium (€50–100k, estimate, inside the kit category) + volunteer recruitment shortfall (taxi scale-up +€40–80k) occur simultaneously, exposure is €90–180k; only the taxi-only fallback plus expedite reaches €200–350k, exceeding the €160k pre-Month-4 free contingency by €40–190k. This forces mid-season service cuts or reallocation between home kits, transport and outreach, reducing program effectiveness. Clarification needed: (1) approve explicit contingency-draw authority and approval workflow (who authorizes draws >€10k, >€50k?); (2) pre-identify contingency sources if free reserve is insufficient (e.g., credit line, clawback from tranche-2, reallocation between categories); (3) publish decision tree: if supply-chain slips +€80k AND volunteer recruitment lags +€60k, which services are deferred/cut first (kits to 1,500, refuges to 6 sites, or taxi-only operation).

2. Year-2 recurring cost (€2.3M/year estimated) lacks a committed funding source; if not identified by Month 9 (2027-07-08), municipal leadership may not authorize continuation beyond Month 12 (2027-10-08), stranding infrastructure and enrolled residents. Impact: playbook transferability to peer cities is undermined (pilot abandoned after Year 1); political credibility for heat-health spending is damaged; accumulated staff and volunteer relationships are lost. Year-2 continuation is critical for the program to demonstrate sustained harm reduction and to validate scaling assumptions. Clarification needed: (1) identify and pre-commit ≥1 Year-2 funding source (EU climate grants, national health budget line, municipal mainstreaming) by Month 9 (2027-07-08); (2) quantify what components are viable under a reduced budget (€1.5M–€2.0M) if full €2.3M is unavailable (e.g., retain refuges + transport, defer home kits to Year 2); (3) document in funder correspondence and municipal strategic plan.

3. Home-kit installation buffer and remediation/replacement costs not explicitly budgeted; €800k home-kit category includes a ≈€200k bundle (expedite premium of €50–100k (estimate), storage, buffer stock (10–15%), QA and hydration) but does not itemize rework, QA audit costs (0.5 FTE inspector, ~€25k annually), or warranty/returns reserve. Impact: if 10–20% of 2,000 installations fail safety checks or customers require rework, the QA and rework cost could consume €50–100k (6–12% of kit category), forcing either a cut to final installations (100–200 fewer homes) or a draw from contingency. Clarification needed: (1) approve and itemize QA, rework and warranty reserves within the €800k kit budget (recommend €25–40k QA + inspection + €30–50k warranty/returns = €55–90k explicit line item); (2) confirm installer safety-check protocol and QA audit sample rate (proposed 10–20% of 2,000 installs = 200–400 homes); (3) define rework SLA and budget for rapid corrective action (target <5 days if defects found) before homes enter the season.

Review 12: Role Definitions

1. Incident Commander: single point of authority for alert declaration, spending authorization and cross-department coordination; currently named as 'mayor's office' role but lacks written delegation, backup chain, and decision authority limits. Why critical: unclear authority delays alert decisions by 6–12 hours (loss of response time during critical morning heat peaks), invites conflicting orders across departments (refuges, transport, health system), and creates accountability gaps if response fails under media scrutiny. Impact: €3.5M program credibility depends on demonstrable command clarity; without written delegation by Month 1 (2026-11-08), municipality faces legal challenge to alert validity and inter-agency disputes mid-season. Actionable steps: (1) draft mayoral delegation letter by Month 0.8 (2026-11-01) specifying incident commander name, role, spending limits per tier (PMO lead ≤€25k, incident commander plus CFO €25–50k, above €50k with funder notice), alert-declaration triggers, and backup authority chain if primary is unavailable >2 hours; (2) obtain mayor's signature by Month 1 (2026-11-08) and file with municipal legal; (3) brief all partner organizations (health, civil protection, transport, refuges) on the delegation to embed understanding independently of municipal staff turnover.

2. Partner Liaison Officer: owns outreach-partner engagement, capacity monitoring, and performance tracking for 4–6 intermediary organizations (housing associations, social services, NGOs, pharmacies); currently assigned as a shared coordination role with no dedicated FTE or written accountability. Why critical: partner capacity is the sole gatekeeper for the 60% outreach contact-success gate (Month 4 = 2027-02-08); if partner call-center staffing is unclear or capacity agreements are informal, mid-season deterioration goes undetected until gates fail and €1.5M release is withheld. Impact: partner withdrawal or reduced staffing could drop contact success from 60% to 40–50%, failing the gate and forcing €100–150k emergency municipal outreach staff draw (63–94% of tranche-1 contingency). Actionable steps: (1) designate a dedicated Partner Liaison Officer (1 FTE, Months 0–12 = 2026-10-08 to 2027-10-08) reporting directly to incident commander; (2) by Month 1 (2026-11-08), conduct formal capacity survey of all 4–6 partners (staff count, call-center hours, summer turnover forecast) and obtain signed capacity commitments in partner DPAs by Month 1.5 (2026-11-23); (3) establish weekly partner performance reporting (call volumes, contact success %, staff absences) and monthly liaison contact to flag emerging capacity gaps.

3. Project Manager (PMO Lead): owns procurement timeline, staffing ramp, budget burn tracking, and gate-readiness attestation; currently fragmented across HR coordinator, procurement lead, and incident commander with no single owner or written decision authority. Why critical: the compressed 8-week procurement window (Month 0 = 2026-10-08 to Month 2 = 2026-12-08) and staggered hiring of 43 FTE across 6 months are the critical paths for both gates; delays compound exponentially (if kits slip by 4 weeks AND volunteers lag recruitment, both transport and home-kit leverage degrade). Impact: procurement-path mismanagement could cost €50–100k in expedite premiums or lose €1.5M tranche-2 if gates are unmet; hiring delays of 3+ weeks could leave centers and dispatch under-staffed by May, degrading service by 10–25%. Actionable steps: (1) designate a dedicated Project Manager (1 FTE, Months 0–12 = 2026-10-08 to 2027-10-08) reporting to incident commander; (2) by Month 0.5 (2026-10-23), build and maintain a critical-path Gantt chart tracking all procurement orders, hiring cohorts, and gate milestones; (3) issue weekly status reports to incident commander flagging any item >1 week behind plan and pre-authorize contingency drawdown (PMO lead up to €25k per draw; €25–50k needs incident commander plus CFO) if slippage is detected early.

Review 13: Timeline Dependencies

1. GDPR compliance and partner DPA execution must occur by Month 1.5 (2026-11-23) before intermediary outreach staff can begin enrollment; delay risks partner withdrawal and eliminates the sole outreach model. Impact: if DPA negotiation slips 4+ weeks (typical for multi-org legal review), partner recruitment and briefing cannot begin until Month 2.5 (2026-12-23), compressing training into 1 month. This delays enrollment start to Month 4 (2027-02-08), reducing the 5,000 contact-attempt target to 2,500–3,000 by Month 7 (2027-05-08) and dropping enrollment from 3,000 to 1,500–1,800 enrolled (50% shortfall). Interacts with: if intermediary reach collapses AND door-knock outreach is not added, coverage remains ≤5% and isolation equity fails. Action: engage GDPR counsel by Month 0.5 (2026-10-23) with strict Month 1 (2026-11-08) legal-opinion deadline; pre-draft template DPAs by Month 0.8 (2026-11-01) to shorten negotiation cycle.

2. Procurement spec finalization and first-tranche order placement compressed into 6 weeks (Month 0.8 = 2026-11-01 to Month 1.2 = 2026-11-14); spec delays of 2+ weeks cascade into kit-delivery slippage by Month 4 (2027-02-08) and force €50–100k expedite premium or kit-scope cut. Impact: EU suppliers require 6–8 week lead times; placing orders at Month 1.5 (2026-11-23) instead of Month 1.2 (2026-11-14) shifts 40–50% kit delivery from February to March–April, reducing February buffer stock to <15% of planned 600–800 units. This creates pressure to install kits in June–July (post peak-risk May) and reduces home-intervention ROI by 20–30%. Interacts with: if procurement slips 4+ weeks AND volunteer recruitment underperforms, both transport and kit leverage degrade simultaneously. Action: issue detailed specs to suppliers by Month 0.8 (2026-11-01); place the first call-off by Month 1.2 (2026-11-14), with all tranche-1 orders by Month 2 (2026-12-08); commit the ≈€200k kit bundle (expedite premium €50–100k (estimate), storage, buffer, QA, hydration) within the €800k category upfront (not contingent).

3. Month 3.2 (2027-01-14) full-system drill completion and Month 3.9 (2027-02-04) after-action closure must occur on schedule to support Month 4 (2027-02-08) gate decision; any delay >4 days compresses corrective-action time into <1 week, preventing remediation and forcing gate escalation to Month 5 (2027-03-08). Impact: if drill is delayed to Month 3.5 (2027-01-23) due to unavailable staff or facility access, after-action report slips to Month 3.8 (2027-02-01), leaving only 5 days to close corrective actions before the Month 4 (2027-02-08) gate decision. Critical gaps (transport time >50 min, contact success <55%) cannot be remediated in 5 days, forcing the funder to declare gates unmeasurable and trigger the partial-release rule (€750k at Month 4 = 2027-02-08, remainder after Month 5 = 2027-03-08 re-test), creating a €200–400k cash gap. Interacts with: drill delays compound if hiring is staggered (only 30–40% of staff in post by Month 3 = 2027-01-08), reducing drill realism and forcing re-test. Action: lock drill date at Month 3.2 (2027-01-14) by Month 2 (2026-12-08) in writing; schedule after-action closure cadence (draft Month 3.5 = 2027-01-23, actions closed Month 3.9 = 2027-02-04); identify parallel drill observation team (independent from operations) to detect and escalate gaps in real-time.

Review 14: Financial Strategy

1. Year-2 funding source identification and budget sustainability model (€2.3M/year recurring, estimate) remain unfunded; absence of committed source by Month 9 (2027-07-08) risks municipal abandonment of infrastructure post-Month-12 and destroys peer-city credibility if pilot cannot demonstrate sustained operations. Financial impact: if Year-2 funding is unavailable, the municipality cannot maintain refuges, transport or outreach beyond Month 12 (2027-10-08), orphaning €3.5M in setup costs and €800k in home kits. Peer cities viewing Year-1-only operation will reject the model as unproven and unsustainable. Interacts with: playbook transferability (core deliverable, user constraint) depends entirely on demonstrable Year-2 continuity; delayed-release cash gap (€200–400k exposure if tranche-2 withheld) compounds if Year-2 funding is also unavailable, creating a €400–800k total funding cliff. Action: identify and pre-commit ≥1 Year-2 source (EU climate grants, national health budget, municipal mainstreaming) by Month 9 (2027-07-08); if unavailable, document scaled-back Year-2 scope (refuges only, defer kits; estimated €1.2–1.5M/year) and obtain mayoral commitment to that minimum by Month 11 (2027-09-08).

2. Contingency reserve draw-down authority and priority-sequencing rules undefined; free €280k (€160k before Month 4 = 2027-02-08) may be consumed by a single risk (taxi-only fallback +€150–250k OR delayed-release cash gap €200–400k), leaving zero buffer and forcing mid-season service cuts with no decision pathway. Financial impact: if supply-chain expedite premium (€50–100k) + volunteer recruitment shortfall (€40–80k) + unplanned staffing gap (€50–80k) occur simultaneously, the expedite and volunteer items alone sum to €90–180k; with the taxi-only fallback plus expedite exposure reaches €200–350k, exceeding free contingency by €40–190k. This triggers unplanned cuts to home kits (€150–250k loss), refuges (scale to 6 sites, -€100k), or outreach reach (500–1,000 fewer households). Interacts with: procurement timeline (if orders slip by 4+ weeks, expedite premium consumes €50–100k immediately); volunteer pipeline (if recruitment lags, taxi retainer scale-up consumes €40–80k within weeks). Action: publish explicit contingency-draw decision tree by Month 1.5 (2026-11-23): authorize draws ≤€25k (PMO lead), €25–50k (incident commander + CFO), >€50k (incident commander + CFO + funder notification within 24 h); specify service-cut priority: maintain refuges + transport first (gates 1–3), defer home kits to Year 2 if budget exhausted.

3. Procurement budget allocation across categories (€3.5M total) leaves no explicit reserve for cost escalation in specific line items (refuge fit-out €850k, home kits €800k, transport €380k); if a single category overruns by 15% (typical EU inflation), total cost exceeds €3.5M cap by €150–200k (estimate) with no reallocation path documented. Financial impact: refuge sites may require unexpected accessibility remediation (€50–100k overrun if >3 sites need structural work beyond the €10k per-site cap, proposed threshold); kit suppliers may raise prices mid-contract (€50–100k escalation on €600k hardware); transport retainer may increase if volunteer recruitment fails earlier than forecast (€40–80k scale-up at Month 1.5 = 2026-11-23 vs. Month 3 = 2027-01-08). Combined exposure: €150–280k. Interacts with: free contingency (only €160k available before Month 4 = 2027-02-08) is already at risk from transport fallback and delayed-release scenarios; any category overrun forces immediate cascading cuts to other services. Action: by Month 1 (2026-11-08), conduct a cost-sensitivity analysis for each budget category (refuge fit-out, kits, transport, staffing) identifying which items have locked-in pricing (procurement contracts by Month 1.2 = 2026-11-14) vs. which remain at risk; establish explicit reallocation rules: if refuge remediation exceeds €10k per site cap, reduce site count from 10 to 8–9 rather than dip into contingency; if kit price escalation >5%, accept delivery delay (shift from February to March–April) rather than pay premium.

Review 15: Motivation Factors

1. Clear early operational wins and visible resident benefit (home-kit installation completion by Month 7.3 = 2027-05-17) sustain staff, volunteer and partner morale through peak-stress July–August heat season. If 2,000 kits are visibly installed in enrolled homes by May–June, residents perceive tangible protection, word-of-mouth referrals accelerate enrollment by 20–30% (500–1,000 additional contacts estimated), and street-contact and intermediary staff see immediate evidence their work matters. Loss of this motivation driver occurs if supply-chain slips >4 weeks: 60–80% of kits arrive post-May, installation is compressed into June–July during operational peak, staff encounter enrolled residents without promised protection, and volunteer/partner engagement erodes mid-season. Interacts with: procurement timeline (Month 1.2 = 2026-11-14 order critical) and staff fatigue (multi-day heat waves July–August will test commitment if home-kit promise is already broken). Action: lock kit order by Month 1.2 (2026-11-14) with delivery SLA; conduct installation ceremony or resident testimonial communications by Month 8 (2027-06-08) to reinforce staff-team impact narrative.

2. Cross-departmental incident-command alignment and demonstrated inter-agency coordination eliminate silos and build operational trust, preventing mid-season command-structure collapse and morale breakdown. If the incident commander (mayor's office) and deputies (public health, civil protection, communications) establish and rehearse protocols together by Month 2 (2026-12-08), daily SITREPs at 08:30 become routine, decisions are delegated transparently, and partners know who to escalate to during alerts. Loss of alignment occurs if incident command remains unclear: delayed alert declarations (6–12 hour loss), conflicting cross-department orders (refuges vs. transport vs. health system), unclear accountability mid-season when fatigue sets in (Months 9–11 = 2027-07-08 to 2027-09-08). Interacts with: volunteer and staff fatigue (if command is fragmented, staff see mixed signals and morale fractures); partner capacity (NGO and intermediary teams lose confidence in city coordination). Action: draft and execute written mayoral delegation by Month 1 (2026-11-08); conduct joint inter-agency tabletop drill at Month 2.5 (2026-12-23); confirm daily SITREP cadence and backup-authority chain before Month 3.2 (2027-01-14) full-system drill.

3. Concrete performance feedback from Month 3.2 (2027-01-14) full-system drill validated against gate criteria (80% center hours, 60% contact success, <45 min transport) provides staff and leadership confidence that Month 4 (2027-02-08) gates are achievable and motivates corrective action. If drill results show 85% center hours and 65% contact success, the team enters the real season with confidence and media framing shifts to 'pilot validated.' Erosion of motivation occurs if drill data are murky, incomplete or contested: after-action report slips (Month 3.5 = 2027-01-23 draft, Month 3.9 = 2027-02-04 closure compressed into 6 days), corrective actions are unclear, leadership questions whether gates are realistic, and staff enter May season with doubt. Interacts with: funder confidence (if gates are ambiguous, funder may withhold €1.5M tranche-2, creating €200–400k cash gap that forces service cuts and staff notice immediately); contingency exposure (if drill reveals major gaps—e.g., transport time 60+ min—corrective spend may exhaust €160k tranche-1 contingency, signaling organizational distress). Action: lock drill date at Month 3.2 (2027-01-14) by Month 2 (2026-12-08); assign independent observation team (not operations staff) to capture gate-metric data in real-time; deliver draft after-action report by Month 3.5 (2027-01-23) with clear pass/fail/remediation decisions before Month 4 (2027-02-08) gate evaluation.

Review 16: Automation Opportunities

1. Automate outreach contact-attempt logging and success-rate tracking via shared real-time spreadsheet (accessible to all 4–6 intermediary partners and city) instead of manual daily reporting. Impact: reduces partner reporting overhead by ~5 hours/week per organization (€40–60k annual FTE cost savings estimate) and enables daily success-rate visibility (target ≥60%) instead of weekly delays, allowing incident commander to escalate shortfalls within 24 h instead of waiting until end-of-month gate measurement. Interacts with: outreach gate (Month 4 = 2027-02-08) depends on real-time contact tracking; automated logging eliminates reconciliation delays that compress Month 3.9 (2027-02-04) corrective-action window. Action: design shared spreadsheet template (partner ID, attempt date/time, resident name optional, contact outcome, language) by Month 1 (2026-11-08); pilot with 2 partners in Month 2 (2026-12-08) drill; deploy to all partners by Month 3 (2027-01-08).

2. Automate cooling-center occupancy reporting and transport-dispatch routing via a simple shared real-time dashboard (centers log occupancy every 30 min during alerts) instead of manual phone updates. Impact: eliminates dispatch phone-tree delays (currently 10–15 min coordination lag per request) and enables transport to reroute residents to available sites within 5 min instead of 15–20 min. Estimated transport time improvement: 5–10 min per request, supporting the <45-min gate target with margin. Interacts with: transport-time gate (Month 4 = 2027-02-08) depends on fast center-dispatch integration; manual updates add 10–15 min of system latency per request, risking gate failure if volume peaks. Action: build simple secure spreadsheet or low-code platform (center occupancy, capacity, access restrictions) by Month 2 (2026-12-08); integrate with dispatch system during Month 3.2 (2027-01-14) drill; confirm <5-min update latency before season.

3. Automate heat-illness escalation decision-making for outreach staff via a simple laminated checklist and pre-recorded phone protocols (e.g., 'if confused + hot skin → call EMS; if mild dehydration only → phone triage line') instead of ad-hoc staff judgment. Impact: reduces escalation errors and delays (estimated 5–10 min saved per ambiguous case), improves consistency across 25–35 outreach and street-contact staff, and reduces occupational-health incident risk (safer decisions, clearer liability). Interacts with: staff fatigue risk (Months 9–11 = 2027-07-08 to 2027-09-08) worsens decision-making under pressure; automated checklists reduce cognitive load and burnout. Action: co-design checklist with senior clinician by Month 1.5 (2026-11-23); laminate and distribute to all outreach staff by Month 2 (2026-12-08); integrate into training and drill scenarios; measure escalation accuracy post-drill at Month 3.5 (2027-01-23).

Q1: What does the 'Alert Trigger Ladder' mean, and why is it critical to the program's success?

A1: The Alert Trigger Ladder is a three-tiered forecast-based system that defines when cooling centers and support services activate. Level 1 (Advisory): daytime high ≥33°C or night low ≥20°C for 2+ days triggers phone check-ins only. Level 2 (Alert): high ≥35°C and low ≥22°C activates centers 10:00–20:00. Level 3 (Emergency): same for 3+ days or national red warning extends to 24-hour operation. The thresholds balance 'alert fatigue' (too-frequent false alarms waste budget) against 'missed hot nights' (underestimating nights with high mortality risk). Success is measured by false-alarm rates and missed-event counts post-season.

Q2: What is the 'Cooling Refuge Network Shape,' and how does it affect who can access help?

A2: Decision 2 (Critical) specifies whether the city builds 10 small neighborhood refuges within walking distance (favored option) or fewer large anchor sites requiring transport. The chosen design prioritizes small refuges in libraries, community centers and parish halls so ≥70% of enrolled residents are within 800 meters (10-minute walk). This design trades staffing complexity for equity: residents who cannot travel far or lack transport can still reach shelter. Overnight cooling is offered at 3 fully accessible sites only during Level 3 emergencies. The document raises a core tension: many small sites are expensive to staff and secure; few large sites save money but depend entirely on transport working for frail and mobility-limited residents.

Q3: What is the 'Consent-Light Identification Routes,' and why does the city avoid holding personal health data?

A3: Decision 3 (Critical) uses intermediary-held contact lists to identify high-risk residents without the city holding personal health data. Housing associations, social services, NGOs and pharmacies call their own clients directly to enroll them, and only report aggregate results to the city (e.g., '100 residents contacted, 65 enrolled'). This design avoids GDPR exposure (no city-held health registry = lower regulatory fine risk) and reaches offline residents (older people who distrust digital channels). The trade-off: isolated residents not already known to these intermediaries—the highest-mortality group—are systematically missed. The document acknowledges this coverage gap and raises the equity cost of the GDPR-safe design.

Q4: What is the 'Mobility Support Delivery' and why is the 45-minute transport target difficult to meet?

A4: Decision 4 (Critical) chooses how residents reach cooling centers: 40 volunteer drivers coordinated by dispatch, with a taxi standby retainer (capped €80k) as backup. The under-45-minute mean pickup time gate is measured from request to vehicle arrival. The document raises that this is ambitious because volunteer availability varies (illness, fatigue, competing duties), wheelchair-accessible vehicles take longer to board, and peak-demand periods (early morning hot-day peaks) overwhelm dispatch. If volunteers fall short of 40 recruits, the taxi retainer must scale up to €100–120k, consuming 63–75% of the contingency and forcing home-kit scope cuts from 2,000 to 1,000–1,500 homes.

Q5: What are the four 'scale gates' at Month 4 (2027-02-08), and what happens if they fail?

A5: The Month 4 (2027-02-08) gates are user-mandated thresholds (user constraints): (1) ≥80% of planned cooling-center hours delivered (from a full-system drill); (2) ≥60% contact success among enrolled residents (from ≥300 outreach attempts); (3) mean request-to-transport time <45 minutes (from ≥30 requests including ≥5 wheelchair users); (4) 100% of after-action corrective items closed. If all four gates pass, €1.5M tranche-2 funding releases. If gates fail or are unmeasurable (cool June–July = no real heat events), only €750k (50%) releases at Month 4 (2027-02-08), and the remainder is deferred to Month 5 (2027-03-08) after a re-test. Gate failure creates a €200–400k cash gap (€40–240k above the €160k available tranche-1 contingency), forcing mid-summer cuts to home kits, transport or outreach—directly harming enrolled residents during peak-risk July–August.

Q6: What is the ethical trade-off between legal safety and equity reach in the intermediary-list outreach model, and what populations are systematically left out?

A6: The intermediary-held-list model (housing associations, social services, NGOs, pharmacies contact their own residents without personal data transferred to the city) avoids GDPR regulatory fines (€2–4% revenue, €500k–1M+ exposure) and reputational harm from unauthorized health-data collection. However, this legal-safety design systematically excludes high-mortality populations: isolated, living-alone seniors not known to any intermediary (~25,000–30,000 of 34,000 seniors aged 65+ are unreached); recent migrants distrustful of formal services; unhoused people absent from all lists; private-rental residents not tracked by housing associations. The 3,000-enrolled target (~9% of 65+) represents inadequate population reach. The equity cost: preventable excess mortality concentrated in unreached neighborhoods during July–August, exposed post-event in media investigation and local analysis.

Q7: What does the 'cool-season gate-testing cliff' mean, and why does it create a €200–400k financial risk if the funder rejects drill evidence?

A7: The Month 4 (2027-02-08) scale gates (≥80% center hours, ≥60% outreach contact, <45-min transport, after-action closure) fall entirely in the cool season (November–February), when real heat events will not occur in Castellón de la Plana. Gates must be tested via a full-system drill (Month 3.2 = 2027-01-14) using simulated alert scenarios, not real operational performance under thermal stress. If the funder rejects drill evidence as insufficient and demands real heat-event validation, the €1.5M tranche-2 release is withheld at Month 4 (2027-02-08). This creates a €200–400k unfunded gap (€40–240k above the €160k available tranche-1 contingency), forcing mid-season cuts to home kits (500–1,000 fewer homes), transport capacity (taxi-only fallback), or outreach staff (reduced contact attempts) during peak July–August heat season, directly harming enrolled residents. No written funder pre-agreement on drill acceptance exists; this must be obtained by Month 0.5 (2026-10-23).

Q8: How do volunteer driver recruitment shortfalls cascade into budget cuts to home kits, and what is the exposure if recruitment and kit supply both slip?

A8: If volunteer driver recruitment falls short of 40 vetted drivers (target ≥20 by Month 2 = 2026-12-08) and fewer than 15 are in the vetting pipeline by Month 1.5 (2026-11-23), the taxi standby retainer must scale from €80k (capped) to €100–120k immediately to maintain transport capacity and protect the <45-minute gate. This consumes 63–75% of the €160k available tranche-1 contingency. Simultaneously, if kit suppliers slip delivery by 4+ weeks (6–8 week EU lead times are realistic), 60–80% of kits do not arrive until June–July, after peak-risk May–June, necessitating a €50–100k expedite premium (10–15% cost premium) or a kit-scope cut from 2,000 to 1,000–1,500 homes. If both risks occur—volunteer shortfall AND supply-chain slip—the combined exposure reaches €200–350k (€80k taxi scale + €100k expedite OR €250k kit reduction), consuming 125–219% of the €160k free contingency by Month 4 (2027-02-08). This forces a choice: accept transport-only fallback (no home kits, home-intervention equity goal abandoned) or defer home-kit installation to Year 2 and lose the visible program credibility that drives sustained enrollment and Year-2 political support.

Q9: What are the safeguarding and occupational-health risks for street-contact and outreach staff, and how are they managed?

A9: Outreach, street-contact and cooling-center staff will regularly encounter residents in acute heat distress, heat stroke, and vulnerable populations during multi-day heat waves (July–August). Risks include: (1) Delayed escalation of heat illness (outreach staff may misjudge severity, delaying EMS calls by 10–30 minutes); (2) Staff assault or threat during street contact (estimated medium likelihood, medium–high severity; potential injury, psychological harm, litigation); (3) Fatigue and burnout during multi-day surges (staff work 7+ consecutive alert days, increasing decision errors and emotional exhaustion); (4) Occupational-health incident response gaps (if safeguarding protocols are not clear, incident debriefing is delayed, or counseling access is slow, staff psychological harm cascades into turnover). Mitigation: heat-illness escalation checklist with nurse-triage-line access (ready by Month 2 = 2026-12-08); de-escalation and trauma-informed-care training for all street and outreach staff (3-hour module, test ≥80%, refresher in May); safeguarding incident-reporting protocol (same-day supervisor debrief, 24-hour occupational-health counseling access); mandatory peer-support group monthly during alert season; shift limits of ≤3–4 consecutive days then 1–2 rest days enforced; 20–30% staff reserve to absorb absences and surge capacity.

Q10: Why is there no identified funding source for Year 2 (€2.3M/year recurring estimated), and what does this mean for the program's sustainability and peer-city replicability?

A10: The plan delivers a 12-month pilot (Month 0–12 = 2026-10-08 to 2027-10-08) funded entirely by the €3.5M grant (€2.0M initial + €1.5M conditional at Month 4 = 2027-02-08). Year-2 continuation at the same footprint (10 refuges, 3,000+ enrolled residents, 40 volunteer drivers, 2,000-home kits deployed) requires an estimated €2.3M/year recurring cost (estimate, not inflation-adjusted). However, no Year-2 funding source is identified in the plan—no committed EU climate grants, national health budget line, municipal budget mainstreaming, or regional authority co-financing. If Year-2 funding is not secured by Month 9 (2027-07-08), the municipality has three options by Month 12 (2027-10-08): (1) Abandon infrastructure and enrolled residents after Year 1 (reputational catastrophe: 'pilot program abandoned'); (2) Scale back to a reduced footprint (e.g., refuges only, defer home kits; estimated €1.2–1.5M/year, partial coverage); (3) Negotiate a municipal budget mainstreaming without external funding (likely requires deprioritizing other health/social spending). For peer-city replication, sustainability beyond Year 1 is critical: if Castellón's pilot collapses after Month 12 (2027-10-08), other EU cities will view the model as unproven and unfundable at scale, destroying the playbook's transferability and funder confidence.

A premortem assumes the project has failed and works backward to identify the most likely causes.

Assumptions to Kill

These foundational assumptions represent the project's key uncertainties. If proven false, they could lead to failure. Validate them immediately using the specified methods.

ID	Assumption	Validation Method	Failure Trigger
A1	The funder will accept drill-based evidence for the Month 4 (2027-02-08) gates and the €750k partial-release rule, with no written agreement yet.	Send the funder a protocol memo by Month 0.5 (2026-10-23). Require a signed funding amendment from a budget-authorizing officer (target Month 0.5 (2026-10-23); hard tripwire Month 1 (2026-11-08)). Hold binding orders above the contingency-covered amount until sign-off.	Funder refuses in writing, or gives no signed sign-off, by Month 1 (2026-11-08).
A2	Kit suppliers and the taxi operator will deliver on the stated lead times, with 40-50% of kits arriving by Month 4 (2027-02-08), and volunteer drivers will be vetted in time for the 45-minute transport gate.	Hold a supplier market sounding with 5-8 suppliers by Month 0.3 (2026-10-17); specs final Month 0.8 (2026-11-01), first call-off Month 1.2 (2026-11-14), all tranche-1 orders by Month 2 (2026-12-08). Obtain firm quotes with delivery penalties and a taxi retainer quote. Track the volunteer pipeline weekly.	Fewer than 2 suppliers commit to February delivery for 600-800 units. Or fewer than 20 volunteers are in the pipeline at Month 1.5 (2026-11-23).
A3	Intermediary partners (housing associations, social services, NGOs, pharmacies) have the call capacity, the lawful basis and the willingness to contact enrolled residents and reach isolated, offline and migrant residents.	Survey all 4-6 partners by Month 0.8 (2026-11-01). Collect written capacity commitments. Run a mock-call test of 50-100 calls at Month 1.5 (2026-11-23).	Combined capacity is under 4,000 attempts/month, mock-call success is under 60% (results of 55-59% trigger a defined corrective action before the Month 2 = 2026-12-08 gate), or counsel finds no workable lawful basis.
A4	At least 8 of 10 candidate refuge sites (libraries, community centers, parish halls) will sign facility-use agreements, be accessible within the remediation limit (<=€10k and <=4 weeks per site, proposed threshold), and have staff to open at Level 2-3 hours.	Hold site visits and an independent accessibility audit of all 10 sites by Month 1.5 (2026-11-23). Ask each site owner for written commitment to 10:00-20:00 opening and liability terms.	Fewer than 8 sites are signable, or places in fully accessible sites fall below 50% after remediation caps, by Month 1.5 (2026-11-23).
A5	The municipality can hire and retain about 43 peak FTE, with 20-30% reserve (proposed threshold), within the staggered hiring plan, and staff will sustain multi-day heat waves without major absence or turnover.	Pre-clear position codes with municipal HR by Month 0.5 (2026-10-23). Post the first roles and measure applicants per role, time-to-offer and offer acceptance over 4 weeks.	Median time-to-offer exceeds 8 weeks, or fewer than 2 qualified applicants per role, or offer acceptance is under 70% (proposed threshold).
A6	Hospitals and EMS will sign the data MOU by Month 1 (2026-11-08) and supply daily aggregate heat-related counts by 10:00 next day, with coding good enough to support a usable baseline and escalation triggers.	Meet EMS and hospital data and legal leads by Month 0.5 (2026-10-23). Submit the baseline data request at Month 0 (2026-10-08) and ask for a sample extract showing coding and completeness.	A partner refuses daily counts, requires a DPIA that delays signature beyond Month 2 (2026-12-08), or the extract shows heat coding is too incomplete to define a baseline.
A7	The alert thresholds (Level 1 >=33°C/20°C; Level 2 >=35°C/22°C for >=2 days; Level 3 >=3 days, proposed thresholds) trigger on the right days, producing neither alert fatigue nor missed hot nights, using AEMET forecasts alone.	Obtain 10 years of AEMET temperature records for Castellón by Month 0.8 (2026-11-01). Count how many days per season each level would have triggered, and compare with local heat-related EMS peaks.	Thresholds would have triggered Level 2-3 on more than 40 days per season (estimate), far above the 25 planned full-activation days, or missed hot-night peaks in EMS data.
A8	The 2,000-home kit rubric and handyperson model will reach top-floor and social-housing residents who consent to installation, and fans and shading will be used safely and kept through the season.	Pre-test the rubric on 50-100 sample addresses by Month 1.2 (2026-11-14). Phone a sample of 30 eligible households and record consent to a home visit and installation.	Consent to installation is under 50% (proposed threshold), or fewer than 1,200 homes scoring >=60 can be identified from partner data.
A9	Public and media trust will hold: residents, including migrants and older people, will believe the program's messages, and a single refuge or outreach incident will not trigger a backlash that suppresses use.	Run 3-4 focus groups with 65+ and migrant residents by Month 1 (2026-11-08). Test message credibility and a scripted incident scenario, and ask which messengers they trust.	Fewer than 60% of participants (proposed threshold) say they would use a refuge or answer a partner call, or most name channels the plan does not use.

Failure Scenarios and Mitigation Plans

Each scenario below links to a root-cause assumption and includes a detailed failure story, early warning signs, measurable tripwires, a response playbook, and a stop rule to guide decision-making.

Summary of Failure Modes

ID	Title	Archetype	Root Cause	Owner	Risk Level
FM1	The Winter Gate Cliff	Process/Financial	A1	Project Manager (PMO Lead)	CRITICAL (15/25)
FM2	The Empty Crates and Idle Cars	Technical/Logistical	A2	Home Interventions and Handyperson Coordinator	CRITICAL (16/25)
FM3	The Calls Nobody Answers	Market/Human	A3	Outreach and Street Contact Lead	CRITICAL (16/25)
FM4	The Locked Doors	Technical/Logistical	A4	Cooling Center Network Manager	HIGH (12/25)
FM5	The Empty Rota	Process/Financial	A5	Project Manager (PMO Lead)	CRITICAL (16/25)
FM6	The Silent Dashboard	Market/Human	A6	Public-Health Deputy Incident Commander	HIGH (9/25)
FM7	The Thermostat That Burned the Budget	Process/Financial	A7	Incident Commander (Mayor's Office)	HIGH (12/25)
FM8	The Fans Nobody Wanted	Technical/Logistical	A8	Home Interventions and Handyperson Coordinator	HIGH (9/25)
FM9	The Rumor That Emptied the Refuges	Market/Human	A9	Communications, Language Access and Trusted Messenger Coordinator	HIGH (12/25)

Failure Modes

FM1 - The Winter Gate Cliff

• Archetype: Process/Financial
• Root Cause: Assumption A1
• Owner: Project Manager (PMO Lead)
• Risk Level: CRITICAL 15/25 (Likelihood 3/5 × Impact 5/5)

Failure Story

• Gates fall in the cool season, so the evidence is a drill.
• Funder acceptance was never obtained in writing.
• At Month 4 (2027-02-08) the funder withholds the €1.5M and wants real heat data.
• Cash gap of €200-400k (estimate) exceeds the €160k tranche-1 contingency.
• Staff, transport and kits are cut before the summer peak.
• Partners and volunteers disengage, and credibility is lost.

Early Warning Signs

• No signed funding amendment by Month 1 (2026-11-08)
• Funder asks for real-event data or a different drill scale
• Drill protocol not shared with funder by Month 2.5 (2026-12-23)
• Monthly burn above forecast by 10%

Tripwires

• No written funder sign-off by Month 1 (2026-11-08)
• Drill protocol not final by Month 2.5 (2026-12-23)
• Forecast cash gap >= €160k at the Month 3.5 (2027-01-23) reforecast

Response Playbook

• Contain: Freeze new commitments above €25k and defer discretionary hiring until funder position is confirmed in writing.
• Assess: Reforecast cash to Month 12 (2027-10-08) with the CFO within 5 days, and quantify the gap against the €160k contingency.
• Respond: Negotiate the €750k partial release or a municipal credit line, and re-scope services to the tranche-1 minimum if needed.

STOP RULE: If the funder gives no written acceptance of the drill or partial-release rule by Month 2 (2026-12-08) and no bridging line of at least €200k exists, restart or re-scope the project to the tranche-1 minimum.

---

FM2 - The Empty Crates and Idle Cars

• Archetype: Technical/Logistical
• Root Cause: Assumption A2
• Owner: Home Interventions and Handyperson Coordinator
• Risk Level: CRITICAL 16/25 (Likelihood 4/5 × Impact 4/5)

Failure Story

• Kit lead times prove longer than the 6-8 weeks assumed, with no pre-committed backup supplier.
• 60-80% of kits arrive after May.
• Volunteer vetting lags, so pickups stretch past 45 minutes and wheelchair users wait longest.
• The taxi-only fallback (+€150-250k, estimate) collides with the expedite premium.
• Kits are cut from 2,000 to 1,000-1,500.
• The transport gate fails in the drill.

Early Warning Signs

• Supplier quotes show lead time over 8 weeks
• Supplier misses an interim milestone by over 7 days
• Vetting cohort falls over 1 week behind
• Drill pickup times trend above 45 minutes

Tripwires

• First call-off not placed by Month 1.2 (2026-11-14)
• Fewer than 20 volunteers in the pipeline at Month 1.5 (2026-11-23)
• Less than 40% of kits delivered by Month 4 (2027-02-08)

Response Playbook

• Contain: Activate the pre-qualified backup supplier within 2 business days and scale the taxi retainer proportionally, capped at €80k; anything above is the taxi-only fallback (+€150-250k) and needs an approval decision.
• Assess: Rerun the delivery and dispatch simulation with actual numbers within 5 days, and cost the kit versus transport trade-off.
• Respond: Reduce the kit scope to 1,000-1,500 homes if needed, protect transport and refuges, and brief the funder.

STOP RULE: If fewer than 20 volunteers are vetted and no taxi retainer is signed by Month 2 (2026-12-08), pause scale-up and re-scope transport before any Month 4 (2027-02-08) release request.

---

FM3 - The Calls Nobody Answers

• Archetype: Market/Human
• Root Cause: Assumption A3
• Owner: Outreach and Street Contact Lead
• Risk Level: CRITICAL 16/25 (Likelihood 4/5 × Impact 4/5)

Failure Story

• Partners are short of staff or lack a clear lawful basis.
• Contact success falls to 40-50%.
• Enrolled residents are mostly people already known to services; enrollment is about 9% of 65+ (estimate).
• Isolated, migrant and offline residents stay unreached.
• A summer heat event shows deaths concentrated among the unreached.
• Media coverage says the pilot served only the connected.
• Partners withdraw and Year-2 support erodes.

Early Warning Signs

• Partner capacity survey shows under 4,000 attempts/month
• Mock-call success under 65% (proposed threshold; 55-59% triggers a defined corrective action, under 60% is a failure)
• A partner delays or refuses to sign its DPA
• Fewer than 5% of calls in non-official languages

Tripwires

• Contact success <60% in the drill (Month 3.2, 2027-01-14)
• Fewer than 4 partner DPAs signed by Month 1.5 (2026-11-23)
• Enrollment below 1,500 by Month 5 (2027-03-08)

Response Playbook

• Contain: Reassign call targets from weak partners to backup partners and start daily contact logging.
• Assess: Audit enrollment by neighborhood, housing type and language within 7 days, and sample 50-100 consents for validity.
• Respond: Add door-knock teams and ambassador-led enrollment in high-deprivation blocks, and renegotiate partner targets and the gate.

STOP RULE: If contact success stays below 60% after the Month 5 (2027-03-08) re-test, or counsel finds no valid lawful basis, stop the intermediary model and redesign outreach.

---

FM4 - The Locked Doors

• Archetype: Technical/Logistical
• Root Cause: Assumption A4
• Owner: Cooling Center Network Manager
• Risk Level: HIGH 12/25 (Likelihood 3/5 × Impact 4/5)

Failure Story

• Site owners decline or add conditions on hours, liability or insurance.
• Audits find ramps, toilets or quiet rooms unusable at several sites.
• Remediation exceeds the cap, so sites are dropped.
• Network shrinks below 8 sites and accessible places fall under 50%.
• Drill delivers under 80% of planned hours; wheelchair users concentrate at a few sites.
• Transport demand and the Month 4 (2027-02-08) gate suffer.

Early Warning Signs

• Site owners not responding to agreement drafts within 10 days
• Audit rates 3 or more sites red
• Insurance cover for refuge use not bound by Month 1.5 (2026-11-23)
• Named site manager missing at any signed site

Tripwires

• Fewer than 8 signed sites at Month 1.5 (2026-11-23)
• Accessible places <50% of planned ~400 at Month 2 (2026-12-08)
• More than 3 sites rated red in the audit

Response Playbook

• Contain: Stop fit-out spending at red-rated sites and hold remediation orders above €10k per site.
• Assess: Re-map walking distance coverage (800 m) with the remaining sites within 5 days and recompute planned site-hours.
• Respond: Recruit replacement sites such as sports halls, or concentrate on accessible sites with transport support, and brief the funder.

STOP RULE: If fewer than 6 accessible, signed sites exist by Month 2.5 (2026-12-23), re-scope the network design before the drill.

---

FM5 - The Empty Rota

• Archetype: Process/Financial
• Root Cause: Assumption A5
• Owner: Project Manager (PMO Lead)
• Risk Level: CRITICAL 16/25 (Likelihood 4/5 × Impact 4/5)

Failure Story

• Municipal HR approvals and seasonal recruiting are slower than the plan.
• Hiring cohorts slip, so the Month 3.2 (2027-01-14) drill runs with few staff.
• Reserve is used up in the first heat wave.
• Overtime and agency replacement push payroll above plan.
• Burnout drives turnover mid-season.
• Payroll overruns compete with the €280k contingency.

Early Warning Signs

• Position codes not approved by Month 1 (2026-11-08)
• Offer acceptance under 70%
• Drill rota filled by fewer than 80% of planned staff
• Overtime hours above plan for 2 weeks

Tripwires

• Less than 40% of staff hired by Month 3 (2027-01-08)
• Staff in post <90% of plan at Month 6.7 (2027-04-29)
• Payroll forecast >10% over budget at any monthly review

Response Playbook

• Contain: Freeze non-essential roles and shift overtime approval to the PMO lead.
• Assess: Compare hires, absences and cost to plan by role within 5 days and identify gate-critical gaps.
• Respond: Use agency or part-time retirees for centers and phone line, cross-train staff, and trim lower-priority roles to protect gates.

STOP RULE: If staff in post are more than 4 weeks behind plan at Month 3 (2027-01-08), trigger the funder restart or re-scope review.

---

FM6 - The Silent Dashboard

• Archetype: Market/Human
• Root Cause: Assumption A6
• Owner: Public-Health Deputy Incident Commander
• Risk Level: HIGH 9/25 (Likelihood 3/5 × Impact 3/5)

Failure Story

• Hospital legal teams stall the MOU and ask for a DPIA.
• Heat coding is inconsistent, so counts are late or unreliable.
• Commander gets no escalation signal at 1.5x volume.
• Nurse line and outreach staff lack agreed escalation rules.
• Evaluation baseline is weak, and results are disputed.
• Clinicians distrust the program and local credibility drops.

Early Warning Signs

• MOU unsigned at Month 1 (2026-11-08)
• Sample extract shows large share of uncoded heat cases
• Validation pilot misses 10:00 delivery on over 30% of days
• Clinical leads decline to endorse escalation guidelines

Tripwires

• MOU not signed by Month 2 (2026-12-08)
• Daily counts delivered on <70% of days in the validation pilot
• Baseline not usable by Month 4 (2027-02-08)

Response Playbook

• Contain: Switch to the weekly aggregate fallback and rely on forecast triggers plus EMS-only counts.
• Assess: Audit coding on 50 sampled records within 7 days and recompute evaluation power.
• Respond: Negotiate a narrower EMS-only agreement with the university partner and reframe evaluation on operational outcomes.

STOP RULE: If no health data agreement exists by Month 3 (2027-01-08), drop mortality attribution claims and re-scope the evaluation.

---

FM7 - The Thermostat That Burned the Budget

• Archetype: Process/Financial
• Root Cause: Assumption A7
• Owner: Incident Commander (Mayor's Office)
• Risk Level: HIGH 12/25 (Likelihood 3/5 × Impact 4/5)

Failure Story

• Thresholds were set from national levels without local calibration.
• Season triggers far more Level 2-3 days than the 25 planned.
• Each extra full-activation day costs about €324 per planned site-hour across 10 sites (estimate).
• Refuge and transport spending exceeds plan; contingency is drawn early.
• Leadership raises thresholds mid-season, and a hot night is then missed.

Early Warning Signs

• Back-test shows more than 30 Level 2-3 days per season
• Spend per alert day above forecast for 2 reviews
• Partner complaints of alert fatigue
• Raise-the-threshold requests from departments

Tripwires

• Back-test triggers >40 full-activation days per season (estimate) by Month 1 (2026-11-08)
• Refuge spend >10% above forecast at any monthly review
• More than 30 full-activation days declared by Month 10 (2027-08-08)

Response Playbook

• Contain: Freeze threshold changes and hold extra Level 3 extensions until the commander and CFO approve each one.
• Assess: Rerun the back-test with local EMS data within 7 days and cost each alert tier per day.
• Respond: Shift marginal days to the Level 1 advisory tier, reset thresholds with public-health sign-off, and brief the funder.

STOP RULE: If projected alert-driven spend exceeds the free contingency of €280k before Month 9 (2027-07-08), cut refuge hours to the tranche-minimum and reset the ladder.

---

FM8 - The Fans Nobody Wanted

• Archetype: Technical/Logistical
• Root Cause: Assumption A8
• Owner: Home Interventions and Handyperson Coordinator
• Risk Level: HIGH 9/25 (Likelihood 3/5 × Impact 3/5)

Failure Story

• Partner data cannot identify enough homes scoring >=60.
• Residents decline visits, citing mistrust or fear of landlords.
• Landlords or heritage rules block exterior shading.
• Handypeople install fewer homes per day than planned.
• Fan misuse or a fire-safety incident draws enforcement.
• Installs fall short of 2,000 by Month 7.3 (2027-05-17).

Early Warning Signs

• Consent rate under 50% in the pre-test
• Installations per handyperson per day below plan for 2 weeks
• Landlord refusals above 20% of blocks
• QA inspections fail more than 3% of installs

Tripwires

• Consent rate <50% in the Month 1.2 (2026-11-14) pre-test
• Fewer than 500 homes installed by Month 5 (2027-03-08)
• QA failure rate >3% in inspected installs

Response Playbook

• Contain: Pause installs at failing sites and quarantine any unsafe fan models.
• Assess: Review consent, access and productivity by block within 7 days.
• Respond: Switch to a lending scheme or landlord bulk deals, retarget unclaimed kits, and reduce scope with funder notice.

STOP RULE: If under 1,000 homes are installed by Month 7.3 (2027-05-17), stop new kit purchases and redirect remaining funds to refuges and transport.

---

FM9 - The Rumor That Emptied the Refuges

• Archetype: Market/Human
• Root Cause: Assumption A9
• Owner: Communications, Language Access and Trusted Messenger Coordinator
• Risk Level: HIGH 12/25 (Likelihood 3/5 × Impact 4/5)

Failure Story

• Residents distrust official channels and refuges.
• An incident at a refuge or a street-outreach assault is reported in local media.
• Unsafe advice (alcohol, fan misuse) spreads faster than corrections.
• Utilization and enrollment fall; migrant and older residents stay home.
• Partners hesitate to be associated; political support weakens.

Early Warning Signs

• Refuge utilization under 50% of capacity on Level 2 days
• Misinformation not corrected within 4 hours
• Complaints or negative media about refuge safety
• Ambassador reports of community distrust

Tripwires

• Fewer than 60% of focus-group participants would use a refuge by Month 1 (2026-11-08)
• Utilization <50% on 2 consecutive Level 2 days
• Misinformation uncorrected for >4 h on 3 occasions

Response Playbook

• Contain: Issue a corrected message through trusted messengers and ambassadors within 4 hours, and pause any contested material.
• Assess: Interview ambassadors, faith leaders and 20 residents within 7 days to find the source of distrust.
• Respond: Co-design replacement messages with community leaders, publish incident findings openly, and shift effort to peer-delivered outreach.

STOP RULE: If utilization stays under 30% of capacity after two corrective campaigns by Month 10 (2027-08-08), pivot to door-to-door and peer-delivered cooling support.