Testing bilingual business email and office suites, a Canadian checklist

What to take away

What a bilingual test script must cover

A bilingual test script is a fixed set of tasks you run on any business email or office suite before you buy. It has one job: show whether a French-speaking employee can work at the same speed as an English-speaking colleague. Feature lists do not answer that. Tasks do.

Each part needs a pass or fail mark, and a note on what broke. A menu that stays English after you switch the profile is a fail. A date that flips from 13/09/2026 to 09/13/2026 between two machines is a fail. Write the script once, then reuse it at every renewal.

Keep the script short enough to run in an afternoon. Ten to fifteen tasks is enough. Long scripts get skipped, and a skipped script tells you nothing when a vendor asks for evidence.

Run these ten tasks on every candidate. They cover the script's four parts: interface, mail and calendar, dates, and documents.

Set the test bench before you start

Use two accounts on the same tenant, one set to English and one to French. Use a mailbox with real French email, not machine-translated samples. Test on the same devices your staff use, including at least one phone.

Record the build number of the app and the date. Vendors ship updates often, and a bug you saw in September may be gone in November. Your notes are only useful if they say which version failed.

Menus, spell check, and date formats in business email

Menus are visible, so people report them. Spell check and dates are quiet, so people work around them for months.

Start with the menus. Switch the interface to French and walk the whole client: compose, reply, search, settings and calendar. Look for strings that stay English, labels that get cut off because French runs longer, and error messages that appear in the wrong language. A half-translated settings panel is common.

Then test spell check. Type a French message with a few real errors and see what gets flagged. Check whether the French dictionary is installed by default or a separate download. Check whether autocorrect mangles French accents, and whether the client keeps the language per message or per mailbox.

Date formats need their own pass. French Canadian convention writes 2026-09-13 or 13 septembre 2026, not 09/13/2026. Test the date in a message header, in a calendar invite, in a task due date and in a file name. A single wrong format in a meeting invite causes missed appointments.

What three common clients do

Microsoft 365 with Outlook, Google Workspace with Gmail and LibreOffice cover most Canadian shortlists, and each one fails in a pattern you can test for.

Microsoft 365 with Outlook. Menus pass once the Microsoft 365 Language Pack is installed and French is the display language. Dates fail while the Windows region stays English (United States), so an invite renders 09/13/2026.

Google Workspace with Gmail. Menus pass, because the interface follows the account language. Dates are partial, because a header and an invite can disagree when the calendar keeps a locale of its own.

LibreOffice. Menus pass in the French build from the Document Foundation. Spell check is partial, because French dictionaries come from the Dicollecte project and sometimes need a separate install.

Worked example: a Montreal mailbox scored

A Montreal team switches a mailbox to French. The menus translate, but the calendar invite still shows 09/13/2026 and the spell checker flags "courriel" as an error. Two fails, both quiet, both easy to miss in a demo.

The team then runs all ten tasks on Microsoft 365 with Outlook. Daily tasks count x3, weekly x2, monthly x1.

Those six tasks carry 15 of the 21 weight points and score 4.5. The four passes add 6. The mailbox scores 10.5 of 21, or 50 per cent.

Both fails reached other people: a wrong invite date sent to a client, and a normal Quebec word flagged as an error. Both have fixes you can demand in writing. Set the region to French (Canada), and install the French proofing dictionary.

Judge any client on language kept per message or per mailbox, the French dictionary in the install, accents under autocorrect, and dates in headers and invites. Our notes on email client software cover desktop clients outside the browser.

Testing office suites for French interface gaps

Office suites hide their language gaps better than email clients, because most users only touch a few menus. Test the suite the way your staff actually use it: documents, spreadsheets, slides and PDF export.

Install the French language pack and check what it actually changes. Some suites translate the ribbon but leave dialogs, tooltips and templates in English. Some ship French templates that still carry English styles and headings. Open each app and walk the menus you use daily.

Name the packs. Microsoft 365 installs the Microsoft 365 Language Pack, which carries the French interface and French proofing tools. LibreOffice ships French in its localized build and lists a French dictionary extension from Dicollecte on its extensions site.

Google Workspace needs no pack, because French is one of its interface languages. On cost, Microsoft 365 lists its Business tiers at about $6, $12.50 and $22 per user per month in the United States, on an annual commitment. Language packs carry no separate charge.

Spell check and grammar need separate tests in each app. A suite may check French in the word processor but not in the spreadsheet or the presentation tool. Test comments, notes and speaker notes too, since those are where bilingual teams write quickly.

Check the file formats. Open a French document with accented characters, then save it and open it on a second machine. Look for broken accents, changed fonts and shifted page breaks. When you compare suites, you are testing the seams, not the feature list.

Suite gaps that survive a sales demo

The most common gaps are translated ribbons with English dialogs, French dictionaries that need a manual install, and templates that ignore French typography rules such as spacing before a colon. None of these show up in a sales demo.

If your team writes long documents, pick tools on structure, not styling, because headings and styles survive language switches better than manual formatting.

Official Languages Act obligations for federally regulated buyers

The Official Languages Act sets duties for federal institutions and for organizations under federal regulation, including banks, telecoms, air and rail transport. If your organization falls in that group, language support in your tools is part of how you meet those duties.

You can read the consolidated text on the Justice Laws Website, and find the Act itself through the Justice Laws index. The duties cover service to the public in both languages and the language of work for employees in designated regions.

In practice, that means an employee in a bilingual region must be able to work in French: email, documents, calendars and internal forms. A suite that only translates its menus does not meet that test if the employee cannot write and send French work without friction.

Privacy duties sit alongside language duties. Federal institutions have specific obligations, summarized by the Office of the Privacy Commissioner in its guidance for federal institutions. For French-language privacy material, the OPC publishes Sujets liés à la protection de la vie privée.

Buyers outside federal regulation still face provincial rules. Quebec's Law 25, the Ontario and British Columbia privacy commissioners, and the federal PIPEDA all shape what you may store and where. For general regulatory context, see the Government of Canada's Business and industry hub.

Language evidence for the procurement file

Put the scored run in the procurement file, with the build numbers and screenshots. It gives your bilingual staff a way to report gaps without arguing about preferences.

Scoring results and documenting failures

Score every task as pass, partial or fail, then weight the failures by how often staff hit them. A wrong date in a calendar invite is worse than a mistranslated tooltip, because it causes missed meetings.

Use a small scale and keep it consistent across vendors. This is the one we use.

Filter the results by how often staff hit the task: daily x3, weekly x2, monthly x1. A daily calendar invite fail costs three times a monthly tooltip fail.

Document each failure with four things: what you did, what you expected, what happened, and the app build number. A screenshot plus a short screen recording is enough. Vendors act faster on reproducible steps than on complaints.

Some failures disappear on their own. New ones appear when a vendor redesigns a menu. A log you never reopen is a wasted afternoon.

When you compare vendors, weigh format fidelity as heavily as price, because a cheap suite that corrupts French documents costs more in rework.

Numbered steps to log a failure

A repeatable checklist for Canadian teams

Run these seven items on every candidate suite and email client before a pilot starts, and keep the results with the contract.

When you choose an office suite, rank candidates by document type rather than feature count: contracts with numbered clauses, spreadsheets that carry dates, slide decks with French speaker notes, and PDF exports with accents. The same logic applies to email: pick the tool that fits the work your bilingual staff do every day.

Language support drifts with updates, and a suite that passed in September can fail after a winter release. The checklist is cheap. A missed French deadline is not.

Common questions