A tailored course, built for your situation
Mastering ISO 22301 for Critical Infrastructure Project Engineers
A structured path to owning business continuity decisions in high-impact engineering projects.
$199 one-time
24-hour access provisioning
30-day money-back guarantee
Hand-built implementation playbook
12 modules. 12 chapters per module. 144 chapters total.
12 modules, each with 12 chapters (144 chapters total), text-based, plus downloadable templates and a hand-built implementation playbook delivered alongside course access.
Generic continuity plans fail when field conditions shift, this course ensures yours don’t.
The situation this course is for
Most ISO 22301 implementations are built by compliance teams with minimal engineering input, leading to rigid, unworkable plans. When incidents occur, engineers are forced to follow protocols that don’t match field realities, causing delays and compliance drift.
Who this is for
Project-focused engineers in consulting or municipal roles who lead pipeline, infrastructure, or asset-intensive programs and need to own continuity decisions without escalation.
Who this is not for
Junior coordinators, corporate compliance officers without field experience, or consultants focused solely on documentation.
What you walk away with
- Define recovery time objectives for pipeline systems without requiring senior review
- Approve continuity test schedules and evidence collection cycles independently
- Set tiered incident escalation thresholds tailored to field operations
- Own the sign-off on vendor continuity readiness for third-party service providers
- Document decision logic in audit-ready formats that satisfy municipal and federal requirements
The 12 modules (with all 144 chapters)
Module 1. ISO 22301 in Engineering Contexts
How business continuity applies to pipeline integrity, field operations, and municipal infrastructure projects where downtime risks public safety and regulatory compliance.
12 chapters in this module
- Continuity vs. safety: understanding the overlap
- Municipal liability frameworks in Alberta
- When ISO 22301 intersects with CSA Z662
- Defining incident severity in pipeline terms
- Mapping RTOs to field intervention capacity
- Regulator expectations for public infrastructure
- Common gaps in consultant-led implementations
- Integrating BC into project lifecycle gates
- Role of the project engineer in continuity ownership
- How municipal procurement ties to BC readiness
- Vendor BC requirements in engineering contracts
- Documenting continuity decisions for audit
Module 2. Scoping Business Impact Analysis
Tailoring BIA to engineering projects with physical assets, public safety exposure, and cascading failure risks.
12 chapters in this module
- Identifying critical pipeline functions
- Estimating downtime cost per hour
- Public safety thresholds as BIA inputs
- Mapping dependencies on power and comms
- Defining maximum tolerable downtime
- Using GIS data in BIA mapping
- Stakeholder interviews for field teams
- Documenting assumptions for auditors
- Aligning BIA with municipal emergency plans
- Versioning BIA for project phases
- Linking BIA to vendor SLAs
- Presenting BIA findings to non-engineers
Module 3. Recovery Time Objectives
Setting realistic, defensible RTOs based on field logistics, asset availability, and repair timelines.
12 chapters in this module
- RTO vs. repair crew availability
- Spool and valve inventory lead times
- Weather windows for field access
- Road closure impact on response
- Mutual aid agreements as RTO factors
- Regulatory reporting deadlines
- Setting RTOs for control systems
- RTOs for telemetry and monitoring
- Escalation paths when RTO is breached
- Documenting RTO rationale
- Review cycles for RTO updates
- RTOs in contract handover packages
Module 4. Continuity Framework Ownership
Establishing authority over framework design decisions without requiring senior approval.
12 chapters in this module
- When to initiate a continuity review
- Defining incident declaration criteria
- Setting threshold for internal alerts
- Authorizing test participation
- Modifying framework after incidents
- Documenting decision trails
- Handling pushback from operations
- Updating framework post-audit
- Version control for continuity plans
- Integrating lessons from drills
- Reporting changes to municipal leads
- Maintaining independence from audit
Module 5. Incident Response Triggers
Designing field-validated alerting logic that activates response without delay or overreaction.
12 chapters in this module
- Pressure drop thresholds
- SCADA alarm validation steps
- Field crew proximity triggers
- Weather-based pre-activation
- Third-party pipeline interference
- Automated notification rules
- Human-in-the-loop checkpoints
- Escalation to emergency services
- Internal comms tree activation
- Documenting incident initiation
- False alarm review process
- Trigger tuning post-event
Module 6. Vendor Continuity Readiness
Setting and enforcing continuity requirements for third-party service providers and contractors.
12 chapters in this module
- BC requirements in RFPs
- Reviewing vendor test evidence
- Onboarding continuity documentation
- Audit rights for vendor plans
- Penalties for non-compliance
- Mutual exercise participation
- Remote monitoring dependencies
- Cloud service continuity
- Fallback procedures for comms
- Verifying backup power at sites
- Response time guarantees
- Termination clauses based on BC
Module 7. Test Design and Execution
Planning and running continuity tests that reflect real operational conditions, not just compliance checkboxes.
12 chapters in this module
- Choosing test scope and depth
- Field team availability windows
- Simulated vs. live failure modes
- Involving emergency services
- Documentation requirements
- Post-test review structure
- Fixing gaps without blame
- Publishing test outcomes
- Updating plans based on results
- Auditor access to test records
- Test frequency by risk tier
- Lessons for future projects
Module 8. Decision Authority Mapping
Clarifying when you have final call , and when escalation is required , in continuity matters.
12 chapters in this module
- Incident declaration authority
- When to notify municipal leadership
- External agency coordination triggers
- Legal counsel involvement points
- Environmental reporting thresholds
- Public communication approvals
- Media response workflow
- Internal escalation timelines
- Delegating during absence
- Joint decision frameworks
- Documenting authority changes
- Handover during leadership transitions
Module 9. Audit-Ready Evidence Packaging
Structuring documentation to pass regulatory scrutiny while minimizing rework.
12 chapters in this module
- Evidence collection checklist
- Linking controls to ISO clauses
- Version control for documents
- Storing test results digitally
- Field log integration
- Redacting sensitive data
- Preparing audit briefings
- Responding to finding requests
- Maintaining independence from auditor
- Evidence retention timelines
- Municipal access requirements
- Updating packages post-audit
Module 10. Continuity in Municipal Governance
Navigating municipal reporting lines, interdepartmental dependencies, and public accountability frameworks.
12 chapters in this module
- Calgary emergency management structure
- Cross-department coordination
- Provincial oversight expectations
- Public disclosure thresholds
- Council reporting requirements
- Integrating with city-wide BC plans
- Budgeting for continuity activities
- Workforce continuity considerations
- IT systems continuity
- Physical site resilience
- Third-party assurance needs
- Annual reporting cycle prep
Module 11. Framework Evolution
Updating continuity practices as projects, technology, and threats evolve.
12 chapters in this module
- Change triggers for framework updates
- Incorporating post-incident learnings
- Technology refresh impacts
- Climate change adaptation
- Regulatory changes in Alberta
- New construction impacts
- Decommissioning phases
- Lessons from peer projects
- Feedback loops from field teams
- Documenting evolution history
- Version control for updates
- Change communication plan
Module 12. Sustaining Command
Ensuring continuity ownership persists through team changes, leadership shifts, and project handovers.
12 chapters in this module
- Onboarding new project engineers
- Knowledge transfer protocols
- Municipal handover checklists
- Documenting decision rationale
- Reference materials for auditors
- Mentoring junior staff
- Maintaining institutional memory
- Standardizing across projects
- Building internal reputation
- Proving continuity value
- Scaling ownership model
- Graduating to leadership roles
How this maps to your situation
- Project engineer leading pipeline continuity design
- Consultant managing municipal compliance deliverables
- Field team lead preparing for incident response
- Vendor oversight lead enforcing BC requirements
Before vs. after
Before
Continuity decisions are escalated, delayed, or overridden by teams without field context.
After
You define and own the continuity framework , from incident triggers to recovery timelines , without requiring approval.
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 6-8 hours total, designed to be completed in short sessions aligned with project milestones.
If nothing changes
Without clear ownership, continuity plans remain theoretical, leading to failed audits, delayed responses, and eroded trust in engineering leadership.
How this compares to the alternatives
Unlike generic ISO 22301 training, this course is built for project engineers in consulting and municipal roles , with field-specific examples, decision frameworks, and audit-proof documentation strategies.
Frequently asked
Is this course suitable for someone working on municipal infrastructure projects in Alberta?
Yes. The content is tailored to engineers working on public works, pipeline, and asset-intensive projects under municipal or provincial oversight.
How is the course structured?
12 modules, each containing 12 chapters (144 chapters total).
Does this course assume prior knowledge of ISO 22301?
No. It starts from foundational concepts and builds to field-level command, making it suitable for engineers new to continuity planning.
$199 one-time. Approximately 6-8 hours total, designed to be completed in short sessions aligned with project milestones..
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
30-day money-back guarantee·
144 chapters·
Hand-built playbook included·
Account access within 24 hours