How Ottawa public servants should choose bilingual email software

What to take away

What the Official Languages Act requires of an email tool

The Official Languages Act gives English and French equal status in federal institutions. That duty covers the tools employees use, not only the documents they publish. An email system with a half-French interface creates a language-of-work problem for Ottawa staff.

Read the consolidated statute on the Justice Laws index, then map the two parts that apply onto your email tool: Part IV, communications with and services to the public, and Part V, language of work. Interface, notifications, templates, and support all fall inside that map.

Duties apply in both languages in regions with significant demand. In Ottawa that demand is constant. A francophone employee in Gatineau should not need a workaround to read a calendar invite.

Cite the Justice Laws Website when you write the requirement, so the clause points at a consolidated act rather than a summary.

Some departments keep an internal language of work plan. If yours has one, attach it. It tells vendors what your institution has already promised employees in writing.

Shared Services Canada procurement, in sequence

Shared Services Canada is the route most federal departments use for enterprise email. Treat these steps as a sequence. Skipping to demos wastes vendor time and yours.

Vendors often answer the language question with a checkbox. Ask for screenshots, a live sandbox, and a named francophone reviewer. A vendor who cannot show a French admin console has answered the question.

Put three questions in writing: which interface components ship in French, how the French build updates when the English one changes, and who handles French support tickets. Vague answers now become escalations later.

Timing follows the fiscal year, which ends in March. An Ottawa pilot started in autumn has room to finish before the next planning round. Compare cost in your own units, because a lower licence price can hide translation work, an integration project, or a training bill.

Testing the French interface before a pilot

A French interface test checks what employees touch, not what the marketing site says. Run it in a sandbox with real accounts and real mail flow.

Use a five-person panel: two anglophones who work in French, two francophones, one IT administrator. Give each the same five tasks. Record where they hesitate. Hesitation is a finding.

Set the gate before the test starts. A workable bar is 90 percent of task attempts completed in French without switching to English, and no more than two blocking defects left open. Count a menu, dialog, or error message that appears only in English as blocking. Fail the vendor if either bar is missed.

Compare candidates on those tasks rather than on feature lists. The method in testing the seams applies directly: failures show up at the edges, where languages, formats, and defaults meet.

Import a week of representative messages, including attachments with accented filenames. Everything works in an empty sandbox, where nobody is replying to anything.

If email sits inside a wider suite decision, read how to choose an office suite by document type before you commit.

Spell check, menus, and date formats

Spell check is where bilingual email quietly fails. A French dictionary that flags every accented word trains users to ignore the tool. Test both dictionaries on one message, and check that language detection does not flip mid-paragraph.

Menus and dialogs need a full French build. A French inbox with an English settings page is the common defect. Check the admin console too, because IT staff work in one language while employees work in another.

Date formats cause real errors. Canadian federal writing uses a year-month-day convention, while many tools default to month-day-year. A request read as 03/04 can mean two different days.

French Canadian number conventions use a space as a thousands separator and a comma for decimals. Confirm the tool honours locale settings instead of forcing a US default.

Sit with the IT team that administers the tenant. They see policy pages, retention labels, and role names that employees never open. If those are English only, the translation is incomplete.

The argument in storage shape and defaults is that defaults drive daily behaviour, and language settings are defaults like any other.

Documenting the pilot for the procurement file

An Ottawa pilot needs a paper trail a procurement officer can defend. Write the test plan before the pilot starts: participants, tasks, pass criteria, review date.

Keep a findings log with screenshots and version numbers. When a vendor ships a fix, note the build. Undated bug reports do not survive an audit.

A usable entry names the build and the date. For example: build 4.1.9, 2027-02-03, admin console retention label page renders in English when the tenant locale is fr-CA (screenshot 12). Vendor acknowledged; fix promised in build 4.2.0. Retest due 2027-02-17. Status: open.

Add a privacy review before go-live if the pilot covers personal information in mailboxes. The guidance for For Federal institutions explains what federal bodies must do under the Privacy Act, and it belongs in the pilot file.

Keep the pilot short. Six weeks with a clear end date produces a decision. An open-ended pilot produces drift and competing accounts of what was tested.

Where privacy duties land

Email holds personal information about employees and about members of the public. That brings the Office of the Privacy Commissioner of Canada into the decision. Federal institutions must limit collection, set retention periods, and dispose of records on schedule.

Read the Federal government privacy material before you accept a retention setting. Default retention of forever is not neutral. It creates cost and legal exposure.

Ask where backups sit, who can access them, and how deletion works. Get the answer in writing.

Retention schedules vary by record type. Ask your records manager which mailbox content is a government record and which is transitory before you set one default for the whole tenant.

French-language privacy material exists for francophone staff and for published notices. The OPC's Sujets liés à la protection de la vie privée pages help when you draft bilingual privacy text for the pilot.

Check the tool against the wider market before you shortlist. A disciplined shortlist, as described in business email software, starts by ruling out tools that cannot meet the language and records duties at all.

For desktop clients rather than webmail, the same test applies to email client software: confirm the French build exists before the trial, not after.

Common questions

Does the Official Languages Act apply to the software interface?

Yes. Language of work duties cover the tools employees use, so French interface elements are part of compliance rather than a nicety. Check the act on the Justice Laws Website and confirm scope with your department's official languages coordinator.

Do I always need Shared Services Canada procurement?

Not always. Many departments must use it for enterprise email services, so confirm the vehicle with your procurement team before contacting vendors. That one call prevents a process that has to be restarted.

How long should a French interface test take?

A focused test with five tasks and a five-person panel can finish in one to two weeks, depending on sandbox access and vendor responsiveness. The pilot around it should still close inside six weeks.

What is the most common bilingual defect?

Partial translation. The inbox is French while settings, error messages, or the admin console stay English. It surfaces in the admin console first, which is why the IT administrator belongs on the panel.