Public Education / Organized Labor · Ontario

A strike-coordination system for an entire union, in time for the action.

Customer
One of Canada’s largest education-sector unions (named under reference)
Sector
Public education / organized labor
Region
Ontario, Canada
Membership
Tens of thousands of members across the province
Use case
Custom job-action coordination and member self-service
Challenge
Build a coordination system for the full membership at once, live before a fixed, externally imposed job-action date
Solution
A custom coordination application built on WorkAxle's configurable workforce platform
Status
Delivered on deadline, kept available to restart for future actions
Headline Result
On deadline, before the job action began

A logistics operation across an entire province.

The customer is one of Canada's largest education-sector unions, representing tens of thousands of members across the public-education workforce in Ontario. A union does most of its work in negotiation, but when bargaining reaches an impasse and the membership authorizes a job action, the work changes shape overnight, from a conversation across a table to a logistics operation across an entire province, run against a clock nobody controls.

A coordination problem with no off-the-shelf answer.

When a province-wide job action is authorized, every one of tens of thousands of members has to be reached, assigned, accounted for, and kept informed, all at the same time, all in the days before the action begins. The phone trees, spreadsheets, and local-by-local relays that work for ordinary union business do not bend to that scale. They break.

The union needed a single system that could hold a current profile for every member, let members interact with it directly rather than routing every question through stretched coordination staff, give the people running the action a live picture of who was where, and do all of it for the entire membership concurrently. Strike coordination is not a category workforce-software vendors build for. There is no module to switch on.

And the deadline made it severe. A job action does not wait for a software project to finish. The system had to be standing, tested, and trusted before the first member needed it. There would be no second window, no soft launch. Either the platform was ready when the membership moved, or it was not built at all.

A platform general enough to answer a question its category never named.

The union did not buy a strike-coordination product, because no such product exists in the way it needed. It got one anyway, because the underlying capabilities, member profiles, assignment against a population, self-service at scale, are the same capabilities that run any large workforce.

WorkAxle answered the deadline by not starting from zero. The platform already knew how to hold member profiles, manage assignments against a population, and present a self-service interface to large numbers of people. Configuring a proven platform is a far shorter path than coding an application, and the shorter path is what fit inside the deadline.

Building it on a platform, not from scratch.

Configurable Workforce Platform Member Self-Service

The coordination application was custom-built, but it was built on WorkAxle's configurable workforce platform rather than written as new software end to end. That distinction is the whole story of how it shipped in time.

The platform carried a current profile for every member, the backbone of the whole operation, in one place instead of scattered across locals and spreadsheets. Members could engage with the system themselves: at the scale of a full provincial membership, self-service is not a convenience feature, it is the only thing that keeps a coordination staff of dozens from being overwhelmed by a membership of tens of thousands. And the people running the action had one platform to run it from, built and tested for the full population acting concurrently.

The system was not treated as a single-use deliverable. Once the action passed, it was kept available to restart for a subsequent action rather than rebuilt from nothing. Bargaining is cyclical, and the readiness the union paid for once was designed to carry into the next cycle.

What the union got.

Deadline
On time
Delivered and operational before the province-wide job action began
Scale
Province-wide
Built and tested to coordinate the full provincial membership at once
Member Access
Self-serve
Tens of thousands of members could interact with the system directly

Some systems have to exist before the moment they serve. A job action cannot wait for a procurement cycle. By building the coordination system on a platform and keeping it available between actions, the union turned a future emergency into something it could activate rather than assemble, a model, build once, keep ready, restart on demand, that applies to any organization facing intermittent, high-stakes events it cannot schedule.

The platform behind the story.

WorkAxle is a compliance-first enterprise workforce management platform, purpose-built for regulated organizations with multi-jurisdiction, multi-union workforces. From demand forecasting to payroll integration, it provides the operational layer for enterprises where labor rules are too complex for generic tools. WorkAxle is a Workday Innovation Partner (Silver), Design Approved and listed on the Workday Marketplace, and an SAP partner (SAP PartnerEdge) with a SAP SuccessFactors integration.

About this case study.

What industry is this customer in?

Public education and organized labor. One of Canada's largest education-sector unions, representing tens of thousands of members across Ontario.

What did WorkAxle build for them?

A custom job-action coordination system with member self-service, built on WorkAxle's configurable workforce platform rather than coded from scratch.

Why was the deadline the hard part?

A job action is set by events, not a project plan. The system had to be standing, tested, and trusted for the full membership before a fixed external date that could not slip, with no soft launch.

Can the system be reused?

Yes. It was kept available to restart for subsequent actions, on a build-once, keep-ready, activate-on-demand model.

Ready to see results like these in your operation?

See more customer stories.

Browse case studies by industry, module, or challenge to find the one closest to your operation.

Explore the platform for your industry.

See how WorkAxle's configurable platform handles complex, unionized public-sector workforces.

See how WorkAxle can deliver similar results.

Bring your hardest scenario to a 30-minute demo. We'll show you the math on your own numbers.