Critical services · continuity evidence
Continuity board
Public-safe operating view of cross-cutting emergency planning, cyber, water, and power continuity documentation. The board exposes evidence state, owner-verification work, exercise/incident evidence, and cross-sector interfaces without publishing restricted response or infrastructure detail.
Board source20 indexed controlsdata/critical-services/town-critical-services-document-review-register.csv
5
controls indexed1 without open-verification language4 open verification
6
controls indexed1 without open-verification language5 open verification
3
controls indexed0 without open-verification language3 open verification
6
controls indexed0 without open-verification language6 open verification
Interpretation
Board doctrine
Open verification ≠ operational failure.A capability can exist and operate while current public-safe metadata remains unverified.
Public absence ≠ plan absence.Controlled, regulator-held, vendor-held, or security-sensitive continuity plans may appropriately remain nonpublic.
Interface state ≠ readiness score.Dependency rows show evidence and ownership questions only; they do not score municipal preparedness.
Exercise · incident · review evidence
5 AAR metadata openExercise & incident evidence
2public real-incident fixtures
1independent plan reviews
3exercise metadata requests
6corrective-action metadata open
ER-001
publicly verified reviewMay 2017 Comprehensive Emergency Operations Plan reviewed in 2023
January 2023 Town Fire/EMS analysis states CPSM reviewed the May 2017 CEOP and found the content valid at that time
Plans / controls: CEOP / Emergency Support Function structure
After actionnot applicableCorrective actionowner confirmation open
Next: Verify current CEOP revision approval date last full review date and whether review recommendations were closed
Review target: Current CEOP revision and biennial review cycleER-002
publicly verified real incidentFebruary 2026 winter storm and extended power outage response
Town public incident records summarized in the EOP/storm-policy review document EOC calls restoration coordination municipal closures public communications warming/charging and shelter support
Plans / controls: CEOP / storm policy / COOP-power interfaces not established from public evidence
After actionowner confirmation openCorrective actionowner confirmation open
Next: Verify whether a hotwash/AAR occurred which plan families were reviewed and aggregate corrective-action state
Review target: February 2026 hotwash/AAR and plan-update metadataER-003
publicly verified real incidentJanuary 12 2026 Water Division main break response
Town notice documents Water Division response temporary service/pressure impacts resident contact routing and Smart911/Rave notification availability
Plans / controls: Water ERP / public notification / Water-to-EOC and Public Health interfaces
After actionowner confirmation openCorrective actionowner confirmation open
Next: Verify whether the event triggered formal emergency reporting review or corrective action and whether any public-safe ERP metadata changed
Review target: Water incident reporting/AAR applicability and ERP update metadataER-004
owner confirmation openCybersecurity incident-response tabletop or exercise history
FY24 municipal cybersecurity grant evidence establishes a written Town/School incident-response plan project and state program expectations include tabletop testing; Plymouth completion/date is not publicly established
Plans / controls: Cybersecurity Incident Response Plan / CEOP-COOP interface / Town-School interface
After actionowner confirmation openCorrective actionowner confirmation open
Next: Verify whether a tabletop/exercise occurred after plan delivery participating owner classes interfaces tested and aggregate corrective-action closure state
Review target: Most recent owner-verified tabletop/exercise year and aggregate corrective-action stateER-005
owner confirmation openWater ERP exercise tabletop and emergency-report review history
Current MassDEP guidance requires maintained ERP procedures and provides emergency/after-action reporting mechanisms; Plymouth current exercise and qualifying-report history is not publicly established
Plans / controls: Water ERP / power loss / cyber disruption / notification / EOC-Public Health-IT interfaces
After actionowner confirmation openCorrective actionowner confirmation open
Next: Verify last exercise/tabletop year whether qualifying after-action reporting occurred and aggregate corrective-action state
Review target: Most recent Water ERP exercise/tabletop year and qualifying after-action metadataER-006
owner confirmation openCEOP COOP and storm-policy exercise/review cadence
2023 CPSM review recommended biennial CEOP review and COOP development; public evidence does not establish the current exercise/review cadence or integrated cross-sector testing
Plans / controls: CEOP / COOP / storm policy / cyber / water / power continuity interfaces
After actionowner confirmation openCorrective actionowner confirmation open
Next: Verify whether integrated continuity exercises or real-incident reviews test cyber water power communications alternate-facility and reconstitution governance interfaces
Review target: Current exercise calendar last integrated exercise/review date and next review targetReal incident ≠ proof every plan control was exercised. Missing public AAR/exercise metadata ≠ no review occurred. Real-incident fixtures establish that publicly documented operations occurred; they do not prove every plan control was exercised. Exercise/AAR/corrective-action entries marked owner-confirmation-open are metadata questions, not evidence that the activity did not occur. Restricted findings and implementation details remain outside this transport.
Owner verification
16 high priorityContinuity verification queue
| Priority | Lane | Evidence / owner | State | Next action |
|---|---|---|---|---|
| HIGHAQ-001 | cross cutting | Current controlling Comprehensive Emergency Operations Plan metadataEmergency Management / Town ManagerPublic route ↗ | owner confirmation open | Use Emergency Management owner-verification packetRequested metadata: current revision date; approval authority; current/superseded state; public-safe annex index; last review/exercise date |
| HIGHAQ-002 | cross cutting | Town-wide Continuity of Operations Plan metadataEmergency Management / Town ManagerPublic route ↗ | owner confirmation open | Use Emergency Management owner-verification packetRequested metadata: existence; current revision/approval date; department annex model; exercise date; CEOP relationship |
| HIGHAQ-003 | cross cutting | Operational Policies for Storms and Other EmergenciesSelect Board / Town ManagerPublic route ↗ | public route verified content retrieval open | Acquire directly or confirm current copy with Town ownerRequested metadata: current document body; adoption/revision date; in-force status; CEOP/COOP cross-reference |
| HIGHAQ-004 | cross cutting | CEOP review and revision historyEmergency ManagementPublic route not established | owner confirmation open | Verify whether biennial review recommendation was implementedRequested metadata: public-safe dates of reviews/revisions since May 2017 and current plan identifier |
| HIGHAQ-006 | cyber | Current Cybersecurity Incident Response Plan metadataInformation Technology / Cyber Security AdministratorPublic route ↗ | owner confirmation open | Use cyber owner-verification packetRequested metadata: FY24 deliverable completion; current approval/revision date; custodian class; current/superseded state; last tabletop; corrective-action state; CEOP/COOP interface |
| HIGHAQ-007 | water | Current Water Division Emergency Response Plan metadataWater Division / MassDEPPublic route ↗ | owner confirmation open | Use Water owner-verification packetRequested metadata: current revision date; custodian class; current/superseded state; current compliance/certification metadata; public-safe coverage categories; last exercise |
| HIGHAQ-008 | power | Power outage municipal continuity annex or equivalent interfaceEmergency Management / Facilities / Town Manager / EversourcePublic route not established | verification packet ready owner confirmation open | Use power owner-verification packet and coverage matrixRequested metadata: existence; owner; revision date; utility liaison category; critical-service continuity categories; last exercise |
| HIGHAQ-009 | cross cutting | Cyber-water-power integrated dependency annex or equivalentEmergency Management / IT / Water / Facilities / Town ManagerPublic route not established | owner confirmation open | Verify after CEOP COOP cyber water and power plan metadata are knownRequested metadata: existence; controlling plan family; owner; current revision; exercise state |
| HIGHAQ-010 | cyber | Town/School cybersecurity incident-response governance interfaceInformation Technology / School technology and administrationPublic route ↗ | owner confirmation open | Confirm current Town/School plan relationship using cyber owner-verification packetRequested metadata: whether FY24 written plan was joint Town/School; current controlling relationship; owner classes; separate-plan cross-reference if applicable; last joint exercise year |
| HIGHAQ-011 | cyber | Cyber incident-response exercise and corrective-action metadataInformation Technology / Cyber Security Administrator / Emergency ManagementPublic route not established | owner confirmation open | Verify exercise state before considering cyber plan governance closedRequested metadata: most recent tabletop/exercise year; cross-functional participation categories; CEOP/COOP interface tested yes/no; aggregate corrective-action state |
| HIGHAQ-012 | water | Current MassDEP/EPA ERP compliance and AWIA cycle metadataWater Division / MassDEP / EPAPublic route ↗ | owner confirmation open | Verify using PWS ID 4239000 and owner/regulator metadataRequested metadata: current compliance-checklist/certification state; authoritative current system population category; applicable cycle/deadline; completion state |
| HIGHAQ-013 | water | Water ERP exercise after-action and corrective-action metadataWater Division / Emergency Management / Public Health / ITPublic route not established | owner confirmation open | Verify against Water owner-verification packet and MassDEP reporting requirementsRequested metadata: most recent exercise/tabletop year; participation categories; whether qualifying AARs occurred; aggregate corrective-action state |
| HIGHAQ-014 | water | Water power cyber and EOC interface attestationsWater Division / Facilities / IT / Emergency Management / Public HealthPublic route not established | owner confirmation open | Close public-safe interface matrix before any supplemental-plan buildRequested metadata: power-loss coverage yes/no; cyber-disruption coverage yes/no; Water-to-IT interface yes/no; Water-to-EOC interface yes/no; Public Health interface yes/no; alternate-water and backup-power capability categories |
| HIGHAQ-015 | power | Critical municipal function emergency-power capability categoriesFacilities / Emergency Management / department ownersPublic route not established | owner confirmation open | Route power owner-verification packet Packet BRequested metadata: owner-verified capability categories; recurring verification owner; current review date |
| HIGHAQ-016 | power | Utility liaison and prolonged-outage escalation metadataEmergency Management / Town Manager / EversourcePublic route ↗ | owner confirmation open | Route power owner-verification packet Packets A and CRequested metadata: current municipal liaison owner class; alternate escalation owner class; current controlling plan family; last exercise/review year |
| HIGHAQ-018 | power | Accessible public-support continuity during extended outagesEmergency Management / Public Health / HHS / transportation and shelter partnersPublic route ↗ | owner confirmation open | Route power owner-verification packet Packet ERequested metadata: owner classes for accessible warming/shelter transportation and public information; controlling plan family; exercise/review state |
| MEDIUMAQ-005 | cross cutting | 2026 winter-storm after-action/corrective-action metadataEmergency Management / Town Manager / participating departmentsPublic route ↗ | owner confirmation open | Verify public-safe AAR existence and plan-update effectsRequested metadata: whether AAR/hotwash occurred; date; aggregate open/closed improvement state; affected plan families |
| MEDIUMAQ-017 | power | Power continuity exercise and February 2026 corrective-action metadataEmergency Management / Facilities / participating departmentsPublic route ↗ | owner confirmation open | Route power owner-verification packet Packet DRequested metadata: whether hotwash/AAR occurred; most recent exercise/review year; aggregate open/closed improvement state; affected plan families |
Queue requests are deliberately metadata-first. Restricted technical, facility, utility, cyber, medical, and tactical implementation details remain outside the public board.
Cross-sector continuity
10 interfacesDependency board
CD-001cross cutting→cyber
Emergency coordination to municipal IT continuity activation
owner confirmation openA municipal technology disruption may affect continuity of administrative and emergency-support functions; exact systems and procedures remain restricted.
Owners: Town Manager / Emergency Management / Information TechnologyNext: Verify CEOP/COOP-to-cyber activation and escalation at public-safe metadata levelCD-002cyber→cross cutting
Municipal IT and communications continuity to Town emergency operations
owner confirmation openLoss of municipal technology or communications may affect coordination and public information; no architecture or fallback method is recorded here.
Owners: Information Technology / Emergency Management / CommunicationsNext: Verify continuity-communications and essential-information-system ownership categoriesCD-003power→cross cutting
Extended electric outage to municipal continuity operations
owner confirmation openExtended outages can create continuity demands across municipal facilities and services; protected facility priorities and backup configurations are excluded.
Owners: Emergency Management / Facilities / department owners / EversourceNext: Verify current prolonged-outage continuity annex and public-safe facility capability categoriesCD-004power→water
Electric service continuity to Water Division operations
owner confirmation openPower degradation may affect water-service continuity; no generator, pump, source, treatment, or interconnection detail is retained.
Owners: Water Division / Facilities / Emergency Management / EversourceNext: Obtain owner attestation for power-loss coverage and utility/EOC interface categoriesCD-005cyber→water
IT/cyber continuity to Water Division operational governance
owner confirmation openTechnology disruption may require coordinated water continuity response; no SCADA/ICS architecture or control pathway is retained.
Owners: Information Technology / Water Division / Emergency ManagementNext: Verify Water-to-IT escalation and cyber-disruption coverage at yes/no interface levelCD-006cross cutting→water
Emergency coordination and public-health interface for water incidents
owner confirmation openWater incidents may require coordinated operational response and public-health/public-information action; regulatory determination authority remains separate.
Owners: Emergency Management / Water Division / Public Health / CommunicationsNext: Verify Water-to-EOC Public Health and Communications handoffs and decision-authority boundariesCD-007cross cutting→power
Municipal coordination to electric-utility liaison
owner confirmation openUtility restoration remains external while Town manages municipal consequences and support; exact escalation contacts and protected priorities are excluded.
Owners: Emergency Management / Town Manager / EversourceNext: Verify current municipal utility liaison role and prolonged-outage escalation categoryCD-008water→cross cutting
Water-service disruption to continuity communications and public support
owner confirmation openWater-service disruption may require coordinated public information and continuity support; a public notice does not establish ERP activation or regulatory determination.
Owners: Water Division / Public Health / Emergency Management / CommunicationsNext: Verify current notification authority chain and whether real incidents feed corrective-action reviewCD-009power→cyber
Electric outage to municipal technology and communications continuity
owner confirmation openPower loss may affect municipal technology and communications continuity; no backup topology or runtime detail is retained.
Owners: Facilities / Information Technology / Emergency ManagementNext: Verify public-safe continuity capability categories and escalation ownership onlyCD-010cross cutting→cross cutting
CEOP and COOP synchronization
owner confirmation openEmergency operations and continuity-of-operations governance may require synchronized activation and recovery responsibilities; controlled plan contents are not inferred.
Owners: Town Manager / Emergency ManagementNext: Verify current CEOP and COOP existence revision dates relationship and exercise cycleDependency entries describe public-safe governance and handoff questions. They do not expose protected infrastructure topology, restoration priorities, backup configurations, contact trees, or attack-relevant detail.
Evidence register
20 recordsCritical-service control register
cross cutting
5 recordsCS-001
ceop 2017 verified current revision owner confirmation openComprehensive Emergency Operations Plan
Owner: Town Manager / Emergency Management
Town-commissioned CPSM analysis verifies the May 2017 CEOP and ESF structure; it does not establish the current 2026 controlling revision or annex set.
Next: Verify current CEOP revision approval owner public-safe annex index last review and exercise cycle
Public evidence ↗CS-002
public policy listed content review openOperational Policies for Storms and Other Emergencies
Owner: Select Board
Select Board policy is currently listed but is not assumed to replace the CEOP or COOP; contents are not inferred from title.
Next: Acquire current PDF body and verify adoption date closure authority staffing rules and CEOP/COOP interfaces
Public evidence ↗CS-003
current public route verifiedEmergency Management public operating route
Owner: Town of Plymouth Emergency Management
Emergency Management owns municipal emergency coordination; page routes public outage reporting to Eversource and lists public warning channels.
Next: Bind EOP/COOP activation and communications authorities to current owner verification
Public evidence ↗CS-014
integrated annex owner confirmation openCyber-water-power integrated dependency annex
Owner: Emergency Management / IT / Water / Facilities / Town Manager
Absence of a public document does not prove absence of an internal annex. Build only after owner verification identifies a gap.
Next: Verify whether EOP or COOP already contains integrated cyber water power dependency procedures
No public source route establishedCS-015
coop current existence owner confirmation openTown-wide Continuity of Operations Plan
Owner: Emergency Management / Town Manager
CPSM recommended preparing and implementing a COOP; this does not prove no continuity procedures existed or that a COOP was not completed after 2023.
Next: Verify whether Town-wide COOP now exists plus revision approval department annexes exercise state and CEOP synchronization
Public evidence ↗cyber
6 recordsCS-004
current public route verified owner plan verification openInformation Technology mission and continuity responsibility
Owner: Town of Plymouth Information Technology
IT is publicly identified as supporting emergency response and municipal operational continuity; this establishes owner class but not current IR-plan completeness.
Next: Use cyber owner-verification packet for current plan custodian approval exercise and CEOP/COOP interface
Public evidence ↗CS-005
it continuity responsibility and critical service scope publicly evidencedTown IT Services continuity and incident-response responsibility
Owner: Town of Plymouth Information Technology
Document assigns IT cybersecurity policy risk management disaster recovery incident response and business continuity responsibilities including public safety and water utilities; it does not prove current IR-plan approval or exercise state.
Next: Verify current plan authority plus critical-service interface categories without collecting technical architecture
Public evidence ↗CS-006
cyber ir awarded delivery and current state owner confirmation openCybersecurity Incident Response Plan grant
Owner: Town of Plymouth / Massachusetts OGR
Award proves funded written incident-response-plan work; public evidence does not establish final delivery acceptance current revision tabletop or controlled contents.
Next: Verify deliverable completion approval date custodian tabletop CEOP/COOP interface and Town/School relationship
Public evidence ↗CS-007
cyber governance capability publicly evidenced plan validation openCybersecurity procedures training and Cyber Security Administrator
Owner: Town of Plymouth
Public packet states cybersecurity procedures/processes regular employee training and a funded/filled full-time Cyber Security Administrator role; no restricted details are inferred.
Next: Verify plan custody tabletop cadence and corrective-action sustainment at public-safe metadata level
Public evidence ↗CS-016
town school written ir scope verified current interface owner confirmation openWritten Town/School cybersecurity incident-response plan project authorization
Owner: Select Board / Town and School
Select Board packet explicitly describes the grant purpose as development of a written Town/School cybersecurity incident response plan; this establishes intended joint scope but not completion or current governance.
Next: Verify whether final deliverable was joint Town/School and whether that relationship remains controlling
Public evidence ↗CS-017
continued cyber investment evidenced ir relationship openFollow-on Municipal Local Cybersecurity grant
Owner: Town of Plymouth / Massachusetts EOPSS
A further $9361 municipal cybersecurity grant was authorized for cybersecurity-system improvement; no relationship to the IR plan is inferred.
Next: Verify whether follow-on work changed IR governance continuity or exercise state without collecting technical control details
Public evidence ↗power
3 recordsCS-011
power authority boundary publicly verified plan openUtility outage reporting and municipal coordination
Owner: Town Emergency Management / Eversource
Eversource is the public outage/restoration utility route; Town Emergency Management coordinates municipal consequences and support.
Next: Verify current municipal utility liaison and prolonged-outage continuity annex
Public evidence ↗CS-012
power continuity operationally evidenced integrated plan openFebruary 2026 prolonged-outage EOC response
Owner: Town of Plymouth Emergency Management / Eversource
Public incident record shows EOC coordination Eversource restoration activity and warming/power/charging and regional shelter support; it does not prove all continuity controls are documented or current.
Next: Use incident as tabletop baseline and verify after-action/corrective-action documentation
Public evidence ↗CS-013
owner confirmation openCritical-facility emergency power verification
Owner: Facilities / Emergency Management / department owners
Do not publish generator configuration fuel quantity or sensitive facility details; retain only public-safe owner attestations.
Next: Obtain owner verification for capability categories and continuity dependencies
No public source route establishedwater
6 recordsCS-008
water erp existence verified current state owner confirmation openWater Division Emergency Response Plan
Owner: Plymouth Water Division / MassDEP
2019 master-plan draft states ERP completed 2009 and updated 2018; historical reporting language is not assumed to describe the current MassDEP document-handling process.
Next: Verify current ERP revision custodian current compliance/certification metadata exercise history and cross-sector interfaces
Public evidence ↗CS-009
current water route verified erp owner verification openWater Division current public route
Owner: Town of Plymouth Water Division
Water Division owns municipal water operations and publishes the current water-quality-report route; public page does not establish ERP currency or continuity capability.
Next: Use Water owner-verification packet for current ERP and continuity metadata
Public evidence ↗CS-010
current after hours route verified interface verification openWater emergency after-hours route
Owner: Town of Plymouth Water Division / Police
Public directory routes after-hours water emergencies and main breaks through Plymouth Police; this is a public contact route not the complete escalation tree.
Next: Verify EOC Public Health IT and Water escalation interfaces
Public evidence ↗CS-018
current regulatory contract verified plymouth compliance metadata openCurrent MassDEP ERP requirements and sensitive-document handling
Owner: MassDEP Drinking Water Program
Current MassDEP guidance requires an accessible ERP and directs systems not to send the sensitive ERP itself to MassDEP; compliance/checklist/reporting metadata should be used for public-safe verification.
Next: Verify Plymouth current compliance checklist/certification state and authoritative current ERP revision
Public evidence ↗CS-019
current pws identity verified erp cycle open2025 Water Quality Report and current PWS identity
Owner: Plymouth Water Division
Report identifies Plymouth Water Division PWS ID 4239000 and current water-quality/public contact structure; it does not establish ERP or AWIA certification state.
Next: Use PWS identity for authoritative regulatory lookup without inferring current population category
Public evidence ↗CS-020
water real incident fixture verified aar state openJanuary 2026 main-break response and public notification fixture
Owner: Plymouth Water Division / Town Communications
Town notice documents Water Division response service/pressure impacts resident contact routing and Smart911/Rave availability; it does not prove ERP activation or AAR requirement.
Next: Verify whether incident activated ERP procedures or produced public-safe corrective-action metadata
Public evidence ↗Critical-service controls, queue items, and dependency interfaces describe documentation and owner-verification state only. Open verification is not evidence of operational failure, and public-source absence is not evidence that a controlled continuity capability is absent.