The Continuity Gap — Ops Edition

Central Thesis

Operational labour systems revealed a deeper organizational continuity problem — and OCI^™/OCRA^™ emerged as the framework for understanding and stabilizing it.

“Continuity is not what organizations buy. It is what organizations discover they were quietly losing while they were buying everything else.”

A Note on Operational Origins

This edition does not begin from theory. It begins from work.

UnionEyes was not designed in a research lab. It was built inside the operational reality of grievances, governance interpretation, evidence handling, committee continuity, leadership turnover, and the quiet labour of representation. The continuity category emerged from that work — not the other way around.

Over time, recurring operational patterns made one fact undeniable: most labour and governance-heavy organizations are operationally capable but structurally forgetful. The records exist. The workflows exist. The dashboards exist. What disappears, repeatedly, is the organizational context that gives those records, workflows, and dashboards meaning.

This whitepaper is the public synthesis of that pattern.

Contents

• Executive Summary
• Section 1 — Where Representation Actually Happens
• Section 2 — The Hidden Problem Beneath Operational Work
• Section 3 — Why Existing Systems Preserve Records but Not Continuity
• Section 4 — How UnionEyes Discovered the Continuity Layer
• Section 5 — Introducing OCI^™
• Section 6 — Introducing OCRA^™
• Section 7 — Continuity-Aware Operations
• Section 8 — Two Ways Organizations Begin
• Section 9 — Governance-Safe Intelligence
• Section 10 — From Operational Tooling to Organizational Continuity Infrastructure
• Section 11 — Practical Frameworks and Adoption Roadmap
• Section 12 — Sector Implications
• Section 13 — The Continuity Gap, Quantified Honestly
• Objections and Counterarguments
• Legal and Regulatory Alignment
• Category Declaration
• Closing Statement
• References

Executive Summary

Modern organizations have invested heavily in workflow software, case management, dashboards, and governance documentation. Operational throughput has improved. Operational visibility has improved. Yet the deeper organizational capability that allows organizations to remain themselves across leadership turnover, modernization, restructuring, and time has not improved at the same rate. In many organizations, it has measurably degraded.

The pattern is most visible in operational labour environments where UnionEyes is deployed. Grievances are tracked, but the interpretive precedent behind them is held in a small number of people. Governance decisions are recorded, but the rationale for those decisions is rarely preserved in a form successors can inherit. Onboarding documentation exists, but new representatives still rely on long conversations with veterans to become operationally effective. Investigations close, but the operational lineage of evidence and reasoning rarely survives a reassignment intact.

These are not anomalies. They are continuity fragility expressed through operational work.

This whitepaper introduces two frameworks that emerged from this operational reality:

• Organizational Continuity Infrastructure (OCI) — the structured operational foundation that preserves organizational memory, governance lineage, operational evidence, and continuity intelligence across time, systems, and leadership transitions.
• Organizational Continuity Risk Analysis (OCRA) — the adaptive interpretation layer that helps organizations understand where continuity is fragile, where reconstruction burden is concentrated, and where modernization is silently creating continuity debt.

Argument in one sentence

“Operational workflow systems answer the question "What happened?". Organizational continuity infrastructure answers the question "What must survive when the people who understood why it happened are no longer here?"”

Key Findings

• Operational software systems excel at preserving records, but typically do not preserve organizational interpretation.
• Most continuity failures appear first in everyday workflows — grievances, investigations, governance handoffs — long before they appear in formal continuity exercises.
• Stewardship concentration is the dominant root cause of continuity fragility in labour, federated, and governance-heavy organizations.
• Modernization initiatives frequently increase continuity debt by replacing organizational context with workflow surfaces.
• Continuity intelligence is most credible when it emerges from operational reality — not when it is layered on top of unrelated abstract frameworks.

Where Representation Actually Happens

The visible operational surface

Representation does not happen in dashboards. It happens in a grievance that arrives at 5:47 p.m. on a Friday because the member could not get a private moment earlier in the week. It happens in a committee meeting where a steward must reconstruct, from memory, why the local accepted a particular interpretation of a collective-agreement clause three rounds of bargaining ago. It happens in an investigation that suddenly has to be reassigned because the original investigator took a long-planned leave and nobody else has been close enough to the file to inherit the judgment behind it.

It happens in onboarding conversations that begin with a binder and end, hours later, with the sentence: "and here are the things the binder does not tell you."

The live UnionEyes platform was built around this operational surface. It captures grievances, governance interpretation, evidence trails, investigations, committee continuity, intelligence routing, and the workflows that hold democratic representation together day after day. It is, by design, operational software grounded in real labour practice — not an abstract platform looking for a problem to solve.

The realities the platform exposes daily

Within ordinary use, several operational realities recur across organizations, regardless of sector, size, or governance structure:

• A grievance is inherited from a previous steward. The files transfer cleanly. The interpretation of why this grievance is structurally different from a superficially similar one does not.
• A governance decision made in a prior committee cycle is difficult to reconstruct. The minutes exist. The rationale behind the minutes is held by two people, both of whom are now retired or reassigned.
• Evidence collected for one investigation must be re-contextualized when a successor takes over. The evidence is intact. The chain of judgment that turned it into a case is not.
• Onboarding a new representative requires repeated explanation of unwritten operational logic — how to read a particular employer, which escalations require pre-conversations, what the local history says about a recurring issue.
• A modernization project replaces a fragmented workflow with a cleaner workflow, and quietly removes the organizational memory that was embedded in the old one's exception paths.

Each of these realities is operational. Each of them is also, on closer examination, a continuity problem. The organization did not lose its records. It lost the connective tissue around them.

Why this matters before continuity is even named

Naming the continuity problem is the second move, not the first. The first move is to recognize that the operational surface is already producing continuity signals. The organizations that benefit most from OCI^™/OCRA^™ are the ones whose operational teams have already felt these signals — they simply did not yet have a name for what they were feeling.

This matters because most continuity frameworks fail in the opposite direction: they arrive abstractly, demand organizational buy-in for a concept the organization has not yet grounded in its own experience, and consequently get filed under "future maturity initiatives" rather than treated as present, operational reality.

OCI^™/OCRA^™ are designed to arrive after the organization already knows something is wrong. The framework names it. It does not invent it.

“Most organizations already know they are losing something. They do not yet have a way to name what it is.”

The Hidden Problem Beneath Operational Work

The continuity pattern under recurring operational failures

When operational failures repeat across grievances, governance handoffs, investigations, and onboarding, the underlying pattern is almost always the same: the organization preserved the artifact but lost the interpretation. The shape of the failure looks operational. The structure of the failure is continuity.

Three recurring continuity scenarios

Scenario A — The Grievance Transition Problem

A senior steward with eleven years of contextual grievance interpretation moves into a regional role. The replacement inherits a clean file set: grievance records, timelines, correspondence, prior settlements, employer responses. Within three months, the local notices something it cannot quite name. New grievances are being filed cleanly. Old grievances are being managed competently. But the interpretive backbone — which employer behaviour is escalation-worthy this cycle, which clauses are being actively contested across the sector, which exceptions are tactical and which are precedential — is no longer landing in the right places at the right time.

The replacement is operationally equipped. The local is continuity-impoverished. The gap is invisible to any system the local owns, because every artifact the previous steward produced is still present. What is missing is the reading of those artifacts.

This is not a failure of the new steward. It is the predictable expression of stewardship concentration meeting transition without continuity infrastructure.

Scenario B — Executive Turnover

A new executive director takes over a federated organization eighteen months after the previous one departed. The interim period was managed competently. The policy library is intact. Board minutes are searchable. Strategic plans are documented.

Within the first quarter, the new executive begins encountering a pattern: she can describe what the organization decided over the past five years, but she cannot reliably reconstruct why. A specific committee policy looks restrictive on its face; only after a long conversation with a long-serving board member does she learn it was deliberately written that way because of an incident a previous board had agreed never to allow to recur. A program that appears under-resourced turns out to have been deliberately scoped narrowly for governance reasons that exist nowhere in the strategic plan. A vendor relationship that looks anomalous on paper exists for an interpretive reason that two former staff members carried out of the organization.

The organization still has its policy library and its meeting minutes. It does not have the connective tissue that explains them. The continuity loss is real, and it is structural, but it does not appear on any dashboard the new executive inherits.

Scenario C — Modernization Fragmentation

A mid-size organization modernizes its case management, document management, and member-services workflows over an eighteen-month digital transformation. The new systems are well-chosen and well-implemented. Operational throughput improves. Surface visibility improves. Reporting improves.

Nine months later, two unrelated symptoms emerge. First, onboarding new representatives is taking measurably longer, even though documentation is now better than it has ever been. Second, governance interpretation has become more inconsistent across the federation, even though governance documentation has been formally standardized.

The cause is the same in both cases. The previous, messier system carried interpretive context in its exception paths, its informal annotations, the tribal knowledge of who-knew-what. The modernization preserved the workflow but not the interpretive scaffolding. The result is a more efficient organization that is, structurally, slightly less able to remain itself across time.

This is modernization fragmentation. It is one of the most common — and most unmeasured — sources of continuity debt in the organizations OCI^™/OCRA^™ serve.

The continuity concepts these patterns name

These scenarios introduce the canonical continuity vocabulary used throughout the rest of the paper:

“The artifact survives. The interpretation does not. Continuity is the difference between the two.”

Why Existing Systems Preserve Records but Not Continuity

Records are necessary and insufficient

Records management, case management, ticketing, workflow automation, and documentation systems are essential operational infrastructure. They are not, however, continuity infrastructure. They preserve activity. They do not preserve interpretation, inheritance, or organizational meaning.

The distinction is not academic. Canada's demographic position makes it unavoidable. An estimated 5.2 million baby boomers have already exited the labour force, and an additional 2.7 million Canadians aged 60–64 are expected to exit within the next five years ¹². The Labour Market Information Council has reported that the share of mature workers aged 55+ in the Canadian workforce grew from 12.6% in 2000 to 21.6% in 2023 — a 184% absolute increase in that cohort ³. The Canadian Federation of Independent Business has estimated that more than $2 trillion in business assets will change hands as 76% of small-business owners plan to exit within the decade, while only 9% have formalized succession plans ⁶.

These numbers describe a labour-supply event. Beneath the labour-supply event is a continuity event. The organizations losing these workers are also losing the interpretive layer those workers were quietly maintaining. Records remain. Interpretation does not.

What each existing category does — and what it does not

The illusion of visibility

Visibility is not continuity. A dashboard can light up the right indicators while the underlying organization silently loses its ability to explain why those indicators look that way. Organizations can become data-rich and continuity-poor simultaneously.

The objections this section answers

• Why not use our existing case-management system? Because most operational tooling preserves records, tasks, and workflow states, but not operational interpretation, onboarding survivability, governance continuity, or organizational inheritance.
• Is this consulting or software? UnionEyes combines continuity intelligence, continuity-aware operational infrastructure, governance continuity tooling, and longitudinal continuity support.
• Is this employee surveillance? No. UnionEyes does not monitor productivity, score workers, conduct behavioural analysis, or rank individuals. It exists to stabilize organizational continuity.

How UnionEyes Discovered the Continuity Layer

A category that emerged from work

The OCI^™/OCRA^™ framework was not designed in advance and then applied to labour operations. It was discovered through years of operating real workflows in real organizations. Continuity language emerged because operational language was no longer sufficient to describe what was actually breaking.

The pattern that crossed every domain

Across grievance handling, governance interpretation, investigations, evidence work, onboarding, and modernization, the same shape repeated: organizations kept the trace and lost the meaning. Once that shape became visible, the next question naturally followed — what kind of infrastructure would preserve meaning, not only trace?

Why the continuity layer is operationally credible

The continuity layer is credible precisely because it did not arrive abstractly. It arrived as the necessary next layer of an operational system that was already serious about real labour and governance work. OCI^™/OCRA^™ are best understood as the structural consequences of taking operational continuity seriously over time.

“We did not invent continuity theory. We slowly discovered that operational software, taken seriously enough, becomes continuity infrastructure.”

Introducing OCI^™

Definition

Organizational Continuity Infrastructure (OCI) is the structured operational foundation that preserves organizational memory, governance lineage, operational evidence, organizational intelligence, and continuity resilience across time, systems, and leadership transitions.

OCI^™ treats continuity not as administrative overhead but as organizational infrastructure.

Why OCI^™ now reads as operationally justified

OCI^™ is introduced only after the operational reality has been established and the recurring continuity pattern has been named. By this point in the document, OCI^™ is no longer an abstract category. It is the structural answer to a problem the reader has already recognized in their own organization.

Operational translations

What OCI^™ is not

OCI^™ is not a productivity system. It is not surveillance infrastructure. It is not an attempt to replace organizational judgment. It is not a substitute for formal continuity standards, audits, or governance certifications. It is the operational layer that makes organizational continuity practiceable, observable, and survivable.

Introducing OCRA^™

Definition

Organizational Continuity Risk Analysis (OCRA) is the adaptive interpretation layer that helps organizations understand where continuity is fragile, where stewardship is concentrated, where governance interpretation is drifting, and where modernization is creating continuity debt.

OCRA^™ is reviewer-led. Its outputs are interpretive readings, not deterministic scores.

What OCRA^™ is not

OCRA^™ is not:

• behavioural analysis,
• workforce ranking,
• organizational scoring,
• surveillance AI,
• a replacement for governance judgment,
• a substitute for formal audit.

What OCRA^™ does

OCRA^™ layers on top of operational reality to surface:

• continuity fragility patterns,
• stewardship concentration topology,
• governance interpretation drift,
• modernization-driven continuity risk,
• reconstruction burden distribution,
• onboarding survivability indicators.

The OCRA^™ posture

OCRA^™ is intentionally cautious. It uses confidence-aware interpretation, contradiction-aware reading, and reviewer-led judgment. It is designed to surface continuity insight an organization can act on — never to produce organizational verdicts an organization must accept.

“OCRA^™ exists to deepen organizational understanding, not to replace organizational judgment.”

Continuity-Aware Operations

The convergence layer

Continuity intelligence and operational workflows must converge. If continuity exists only in dashboards, it is decoration. If operations exist only in workflows, they are exposed. The continuity-aware operating posture brings the two together.

Domains of convergence

What changes in daily practice

For an operational team, continuity-aware operations look like ordinary work that no longer silently destroys organizational context. Reassignments happen, but interpretive history follows the case. Committee cycles change, but precedent rationale is inherited intentionally. Modernization happens, but operational meaning is preserved alongside operational surfaces.

A practical way to see the shift: in a continuity-aware operation, every transition event — a steward reassignment, a committee turnover, an investigation handoff, a system migration — is treated as a continuity moment, not only an operational moment. The organization asks not only "is the work continuing?" but "is the organization remembering enough of itself to keep continuing?" That second question is the difference between operational competence and organizational survivability.

What continuity-aware operations are not

Continuity-aware operations are not slower operations. They are not more bureaucratic operations. They are not surveillance-adjacent operations. They are not operations that require every decision to be exhaustively documented before it can be made. The continuity-aware posture is calibrated, proportional, and reviewer-led. It strengthens organizational inheritance without burdening organizational practice.

Two Ways Organizations Begin

Path A — OCRA^™-first

Some organizations enter through strategic continuity intelligence. They feel governance fragility, modernization strain, onboarding instability, dependency concentration, or organizational continuity uncertainty before they feel a specific workflow pain.

Flow:

OCI → OCRA → continuity roadmap → operational continuity activation → governance continuity → longitudinal continuity

Path B — Operations-first

Other organizations enter because they need grievance workflows, governance operations, investigations support, evidence continuity, onboarding stabilization, or operational coordination. Continuity awareness emerges naturally once the operational layer becomes credible.

Flow:

Operations Core → continuity pain visibility → OCI activation → OCRA intelligence → governance continuity → longitudinal continuity

Convergence rule

Both paths converge into the same continuity-aware operational infrastructure. The category must never be split into a separate "ops product" and "OCI^™ product"; the organizational reality is single.

“Two valid entry paths. One continuity architecture.”

Governance-Safe Intelligence

Anti-surveillance posture

UnionEyes does not monitor productivity, rank workers, infer behaviour, score individuals, infer political alignment, or conduct workforce surveillance in any form. This is doctrine, not configuration.

Reviewer-led AI

All AI used inside OCI^™/OCRA^™ is assistive interpretation, governed by explicit human oversight. No AI surface concludes on the organization's behalf. No AI output is treated as organizational truth without a named human reviewer accepting it on the organization's behalf.

Explainability

Every interpretation surfaces the structural facts that justify it. No black-box output is published as continuity intelligence. Confidence states and uncertainty are made visible to the reader, not hidden by polish.

Democratic governance safeguards

OCI^™ and OCRA^™ respect organizational sovereignty. Continuity outputs are governance-receivable artifacts the organization can adopt, amend, or decline. The organization remains the author of its own continuity practice.

From Operational Tooling to Organizational Continuity Infrastructure

The synthesis

The arc of the document is now complete. Operational reality came first. Recurring continuity failures became visible. The continuity pattern was named. OCI^™ gave it structure. OCRA^™ gave it interpretation. Continuity-aware operations brought everything back into daily work. Dual-entry GTM acknowledged that organizations discover this category from different starting points.

The organizational shift

What was previously experienced as "good operational software" is now visible as something deeper: continuity-aware operational infrastructure. The same daily work continues, but it now strengthens organizational survivability rather than silently eroding it.

The category statement

Continuity is infrastructure. It is not a project. It is not a memo. It is not a one-time audit. It is the operational discipline that determines whether an organization can remain itself across time.

“The future organization will not merely process activity. It will remember its obligations.”

Practical Frameworks and Adoption Roadmap

The Continuity Debt Audit

Before adopting OCI^™/OCRA^™, organizations benefit from a structured continuity debt audit. The audit is qualitative and reviewer-led. It is not a maturity score. It produces an honest, defensible picture of where continuity is currently fragile.

A continuity debt audit asks:

• Can governance decisions be reconstructed without the people who made them?
• Can operational history be validated independently of veteran memory?
• How much continuity depends on specific individuals, by role and by domain?
• Can leadership and steward transitions occur without major operational degradation?
• Where does the continuity burden concentrate unfairly?
• Which operational practices are documented but not operationally trusted?
• Which modernization initiatives are improving surface and quietly degrading interpretation?

The OCI^™ Adoption Roadmap

OCI^™ adoption follows the canonical five phases. They are not a maturity ladder; they are a sequence of capability layers an organization acquires deliberately.

Organizations do not need to complete all five phases simultaneously. Most begin with Recognition and Stabilization, and progressively layer in Mapping, Runtime Infrastructure, and Intelligence Network as confidence and operational readiness grow.

Proportionality principle

Continuity infrastructure must be proportional. A small local does not need the same continuity surface as a national federation. A community-governed organization does not need the same evidence infrastructure as a regulated enterprise. Proportionality is doctrine; it is how OCI^™ avoids becoming the bureaucracy it is designed to dissolve.

Sector Implications

OCI^™/OCRA^™ are most legible in labour and governance-heavy organizations, but the continuity pattern they describe is present across many sectors. The shape of the fragility differs; the underlying pattern does not.

Indigenous, oral, and community-governed continuity traditions

The continuity traditions of many Indigenous, oral, and community-governed systems demonstrate that organizational continuity does not depend solely on formalized enterprise structures. Many governance cultures preserve continuity through intergenerational stewardship, oral continuity traditions, relational accountability, and collective memory. OCI^™ is designed to learn from these traditions rather than assume Western enterprise documentation is the only valid continuity model.

Why the framework generalizes

OCI^™/OCRA^™ generalize because the continuity pattern is not sectoral. It is structural. Wherever organizational interpretation is carried by people, where transition is inevitable, and where artifacts outlast meaning, OCI^™/OCRA^™ describe a recognizable shape. The intervention is calibrated to the sector; the pattern is not.

The Continuity Gap, Quantified Honestly

Why this section exists

A whitepaper that introduces a category must be honest about what it can and cannot quantify. OCI^™/OCRA^™ are reviewer-led and confidence-aware by design. They do not produce deterministic organizational verdicts. They do, however, sit on top of an evidentiary base that is increasingly difficult to dismiss.

The Canadian evidence base in one paragraph

Canada is entering the final and largest phase of the baby-boom retirement wave ¹². The proportion of mature workers aged 55+ has grown from 12.6% to 21.6% of the labour force in two decades ³⁴. The support ratio of working-age Canadians per senior has fallen from 7.7 in 1966 to 3.4 in 2022 ⁵. More than $2 trillion in SME assets is positioned to change hands within the decade, while only 9% of small businesses have a formal succession plan ⁶. MNP has reported that 64.1% of Canadian SME owners lack a formal succession plan, and only 8.5% have clear actionable changeover goals ⁷. Public-sector retirement pressure is compounding with deliberate workforce reductions and early-retirement incentives ¹²¹⁴. Healthcare workforce growth is not keeping pace with demographic demand ¹⁷¹⁸. Education systems are reporting persistent shortages and high retirement intent ¹⁹²⁰.

What the evidence supports — and does not support

The evidence supports the claim that Canadian organizations are entering a continuity-stress period of historic scale. It does not support the claim that any single organization can be assigned a deterministic continuity score from population data alone. OCI^™/OCRA^™ respect that distinction. They use the evidence to justify the seriousness of the category, not to overclaim about specific organizational readings.

“Continuity intelligence is most credible when it is least willing to overstate itself.”

Objections and Counterarguments

Legal and Regulatory Alignment

OCI^™/OCRA^™ intersect with privacy law, records management obligations, governance frameworks, cybersecurity controls, and AI governance standards. OCI^™ implementations are designed to remain compatible with Law 25, GDPR where applicable, SOC 2, ISO 27001, NIST AI RMF, public-sector records retention requirements, and organizational audit standards.

Compatibility is not equivalence. OCI^™/OCRA^™ do not certify governance, do not replace formal audits, and do not claim standards equivalence. They are continuity infrastructure, not compliance infrastructure.

Category Declaration

This whitepaper formally positions Organizational Continuity Infrastructure (OCI) as a category of operational modernization.

OCI^™ is a continuity-native operational category focused on preserving organizational intelligence, governance coherence, operational trust, evidence integrity, continuity resilience, and continuity-aware modernization across complex organizations.

OCI^™ extends beyond workflow software, knowledge management, governance documentation, or traditional digital transformation. It represents a foundational shift toward continuity-native organizations.

Closing Statement

The organizations that endure the next decade will not simply digitize faster. They will preserve operational memory, governance lineage, operational trust, and continuity intelligence more deliberately. They will treat continuity not as a project, not as a memo, not as a one-time audit, but as infrastructure — quiet, consistent, governance-safe, reviewer-led, and proportional.

The Canadian evidence base now makes the continuity question impossible to defer. The operational evidence inside organizations deploying UnionEyes makes it impossible to abstract. The framework presented in this paper — OCI^™ as structural layer, OCRA^™ as interpretive layer, continuity-aware operations as convergence layer — is the synthesis of that operational and demographic reality.

The future belongs to continuity-native organizations. Not because continuity is fashionable, but because the alternative — organizations that process activity beautifully while quietly forgetting themselves — is no longer survivable at the scale and speed at which organizational memory is now leaving.

— Nzila OS Research Initiative

References

The references for this edition share the canonical evidence base with The Continuity Gap | Evidence-Enhanced Edition v3.0. The numbered list below is preserved for citation continuity across editions.

¹ RBC Economics / Cynthia Leach reporting on Canada entering "peak aging" and the final boomer retirement wave, September 2025. ² Statistics Canada, Canadian labour force: What will happen once baby boomers retire?, August 2024. ³ Labour Market Information Council, Labour market resilience in the face of an aging population, November 2025. ⁴ Statistics Canada, The Daily — Study: Occupations with older workers, July 2019. ⁵ Canadian demographic and seniors population summaries cited in Organizational Continuity in Canada. ⁶ Canadian Federation of Independent Business, Over $2 trillion in business assets are at stake, January 2023. ⁷ MNP Succession Readiness Report, summarized by Lexpert, February 2025. ⁸ Ghasemi et al., How to Utilize Tacit Knowledge in Health Organizations, PMC/NIH, 2018. ⁹ Panopto, Workplace Knowledge and Productivity Report, 2018. ¹⁰ Gallup, 42% of Employee Turnover Is Preventable but Often Ignored, July 2024. ¹¹ Randstad Canada, Focusing on the High Cost of Employee Turnover, August 2023. ¹² Statistics Canada, Federal Public Service Retirements: Trends in the New Millennium, May 2008. ¹³ Treasury Board of Canada Secretariat, Succession Planning and Management Guide, May 2009. ¹⁴ Province of British Columbia, Knowledge Transfer Best Practices, February 2020. ¹⁵ Union of New Brunswick Municipalities, Partner Article: Succession Planning in Municipal Government, October 2025. ¹⁶ Federation of Canadian Municipalities / Green Municipal Fund, Preserving Asset Management Knowledge, June 2024. ¹⁷ Canadian Institute for Health Information, The State of the Health Workforce in Canada, 2024. ¹⁸ Canadian Nurses Association, Health Human Resources policy materials. ¹⁹ RTOERO / education workforce survey reporting, 2024. ²⁰ CBC News, Teacher shortages persisted this school year, June 2025.