Insights
A plan and French-speaking staff are not enough. See where active-offer duty breaks in Manitoba, and how an operations assessment fixes it end to end.
I grew up in Saint-Boniface, and I have watched this happen more times than I can count. A francophone resident calls a public body, asks a question in French, and within a minute is either switched to English or told someone will call back. The body is not hostile. It has a French-language services plan on file. It has staff who speak French. And still the resident cannot finish what they came to do in their own language.
That gap is the whole subject of this article. I am not a lawyer, and nothing here is legal advice. What I do is operations. When I look at a public body through that lens, French-language service is a process that either works end to end or breaks somewhere in the middle. Most of the time it breaks in a place nobody is looking at.
Manitoba's framework comes from The Francophone Community Enhancement and Support Act (C.C.S.M. c. F157), passed in 2016. The idea at the centre of it is active offer. French-language services are meant to be evident, readily available, and easily accessible to the public, and of a quality comparable to services offered in English. The resident should not have to ask twice, apologize, or prove they qualify.
Under the Act, departments and public bodies prepare multi-year French-language services plans that set out how they will meet this standard. The Secretariat of Francophone Affairs supports the framework and receives complaints about services in French. A wide range of organizations fall inside the scope over time, including municipalities in designated bilingual areas, Crown corporations, agencies, and health and community organizations that carry an active-offer duty.
Here is the part that matters for operations. The Act sets the standard and asks for a plan. It does not run your phone queue, write your intake form, or sit beside a front-line worker at four in the afternoon. Meeting the standard is an execution question, and execution lives in your day-to-day systems.
This is the insight I keep coming back to with public bodies. You can have a good plan and genuinely bilingual staff and still fail a francophone resident, because the procedures, templates, forms, scripts, and job aids those staff work from are all in English.
Think about what a front-line worker actually reaches for during a call. The knowledge-base article that tells them how to process a permit. The email template they paste from. The intake form on their screen. The escalation script for a complaint. The letter that goes out to confirm a decision. If every one of those tools exists only in English, a bilingual worker is not delivering French service. They are translating on the fly, under time pressure, without a safety net, and hoping the terminology is right.
So the plan says the body serves in French. The staff list says the capacity is there. And the resident still gets handed off, because the machinery behind the counter was never built to run in French. That is not a staffing failure or a goodwill failure. It is an operations failure, and it is fixable.
When I assess a public body, the breakdowns cluster in a few predictable places. Naming them plainly is usually the first useful thing I do.
Every one of these hides behind an organization chart that says the capacity exists. The chart is not lying. It is just measuring the wrong thing. It counts who speaks French, not whether a resident can get something done.
I use one test, and I hold every public body to it. Can a francophone resident complete a task from start to finish in French, on the phone, at the counter, or online, without being handed off?
Finish the task. Not be greeted in French. Not be promised a callback. Renew the licence, file the complaint, register for the program, get the letter that confirms it, and pay the fee, all in French, in one continuous flow. If the resident has to switch to English at any step to keep going, the body failed the test at that step, and now we know exactly where to work.
This test is powerful because it is concrete and it is honest. It moves the conversation off intentions and onto the actual journey a resident travels. It also maps cleanly to how operations people already think. A task that cannot be completed end to end has a broken step, and a broken step has an owner, a tool, and a fix.
An assessment is how I turn that test into something a public body can act on. I walk the service the way a resident would, then I walk it again from behind the counter, and I document what I find. The pieces fit together like this.
None of this requires new software or a reorganization. It requires walking the real service with clear eyes and writing down where it breaks. Most public bodies have never done exactly that, because everyone is too busy running the service to step outside and watch.
An assessment that only lists problems is not much help to a director who has a budget and a calendar. So the work ends in two things a leader can use.
The first is a rated readiness view. Each part of the service gets a plain rating for how ready it is to serve in French, so leadership can see at a glance where the body is strong and where a resident is likely to fall through. It gives you a shared picture instead of a stack of anecdotes.
The second is a prioritized roadmap. Not everything can be fixed at once, and not everything is worth fixing first. The roadmap sequences the work by two things: how much a gap hurts residents, and how quickly it can be closed. Translating the three most-used intake forms and building a French escalation script might move readiness more in a month than a year-long policy rewrite would. The roadmap makes that trade-off visible so the body spends its effort where it counts.
You can see how I structure this kind of review on the official-languages service readiness page, and the same discipline sits behind a broader operations health check.
It would be easy to read all of this as a call to translate more documents. It is not. Translation is one tool, and it matters, but a pile of translated forms nobody can find in the workflow changes nothing for the resident on the phone.
The work is operational because the fix lives in how the service runs. Which tool a worker reaches for at which step. Who is scheduled on the French-capable channel. How a complex file gets escalated without dropping the resident's language. Where the single point of failure is, and what the backup path is when that person is away. These are process and design questions, and process is what I do for a living as a Lean Six Sigma practitioner. Serve the resident by fixing the machine behind the counter, and the plan on file finally becomes true. If you want to walk your own service against the end-to-end test, get in touch and we can start with the tasks your residents use most.
Does an active-offer duty mean every employee has to speak French? No. It means a resident can access service in French of comparable quality without having to ask specially. That is a coverage and a systems question. You solve it by designing which channels, shifts, and roles carry French capacity and by making sure the tools behind them work in French, not by requiring French of everyone.
We already have a French-language services plan. Isn't that enough? The plan is the commitment. It is necessary and it is not the same as service. The test is whether a francophone resident can finish a task end to end in French today. A plan can be fully compliant on paper while the intake form, the confirmation letter, and the escalation script are English only. The assessment checks the execution, not just the document.
How long does an assessment take, and does it disrupt the service? It is designed to sit lightly on your team. Most of the work is observing the real service and reviewing the tools your staff already use, not pulling people into long interviews. The output is a rated readiness view and a prioritized roadmap your leadership can act on, scaled to the size of the body.
Is this legal advice or compliance certification? Neither. I am not a lawyer and I do not certify compliance. This is operations guidance rooted in francophone Manitoba. I help a public body see where its service breaks in French and give it a practical plan to fix it. For legal interpretation of the Act, work with counsel or the Secretariat of Francophone Affairs.
Provenance Advisory Group, bilingual training and fractional operations for owner-run businesses in Manitoba, Quebec and New Brunswick, and operations and Lean training for public-service teams and not-for-profits across Canada.
Curious where your own business stands? The free Operations Health Check takes five minutes.
Book a callBook a callSkip the form, you'll reach Kobe directly. No call centre, no script.
Call +1 (204) 399-3054