A first pass, yes. A version anyone signs, files or relies on still belongs to a qualified person who has read both texts.
Key takeaways
Machine translation is now good enough to produce a usable French first draft of most client documents. It is not good enough to produce a French version that will be signed, filed or relied on without a qualified person reading both texts and taking responsibility for the French one. That is not a comment on model quality. It is that a translated professional document carries the same duties as the original, and duties attach to people.
The useful framing is that AI changes the economics of translation, not the accountability. Work that was uneconomic to translate becomes economic; work that needed a qualified reviewer still needs one.
Two legal systems, one language. Quebec is a civil law jurisdiction and the rest of Canada is common law. A term with a settled English common-law meaning may have a French equivalent that belongs to a different conceptual system, and a translation that is linguistically correct can be legally wrong. This is the failure mode that costs the most and looks the least like an error.
Terms of art with statutory definitions. Where a term is defined in legislation, the correct French is the term the French version of that legislation uses, not the best-sounding equivalent. Models do not reliably know which words are load-bearing.
Register. Client correspondence, a formal opinion and a court document are three different registers, and a general-purpose model defaults to a flat middle one.
Numbers, names and negation. The same cluster that breaks transcription. A dropped “ne…pas” inverts a clause, and it reads perfectly well.
In Quebec, French is not only the sole official language but is treated as the common language of the province, and the Charter of the French language governs where and how other languages may be used. The Quebec government’s overview of the modernization of the Charter sets out that framework, including the exemplarity duty on the civil administration and the specific exceptions under which another language may be used.
For enterprises the obligations reach further than most out-of-province firms expect. An enterprise’s name must respect the Charter and therefore be in French, and a French enterprise name is a prerequisite for obtaining legal personality for a legal person constituted in Quebec — and where constituting documents contain no French version of the name, a French name must be declared in the enterprise register for use in Quebec. That is set out in the rules applicable to the name of an enterprise.
Firms advising clients who trade across the Ontario–Quebec line should settle the structural questions first: our sister firm covers French and English corporate names and an Ontario corporation carrying on business in Quebec. Those are legal questions, and no translation workflow resolves them.
A point worth being precise about, because it is often mangled. Under the Official Languages Act, English and French are the official languages of the federal courts, and either may be used by any person in, or in any pleading in or process issuing from, any federal court. The choice of either official language must not prejudice the person making it. Federal courts also have a duty to ensure a witness may be heard in the official language of their choice, and to provide simultaneous interpretation facilities at the request of a party.
So a French translation of a federal filing is a service to a client who reads French, not a filing requirement imposed on an English document. Knowing which it is stops firms from paying for translation they do not need and skipping translation a client actually does.
The reviewer has to be qualified in two senses: fluent in the professional French of the relevant jurisdiction, and competent in the subject matter. A bilingual staff member who is not qualified in the subject is proofreading, not reviewing, and the distinction shows up at exactly the wrong moment.
For legal work in Quebec, the professional order is the Barreau du Québec, whose stated mission is the protection of the public. A translated legal document remains legal work, and the person who puts it out is answerable for it in the ordinary way. The same logic applies to an engineering report, an audit communication or an insurance disclosure: translation does not create a category of professional output that nobody owns.
Pasting a client document into a translation tool sends personal and confidential information to a third party. The OPC’s guidelines for processing personal data across borders state that an organisation is responsible for personal information in its possession or custody, including information transferred to a third party for processing, and must use contractual or other means to provide a comparable level of protection. PIPEDA draws no distinction between domestic and international transfers.
The practical failure is not a considered decision to use a vendor. It is an individual pasting a draft agreement into a free consumer tool because it was there. Approve one route, make it convenient, and say plainly that everything else is off limits.
One: build a termbase. Fifty to two hundred terms your firm uses, with the agreed French for each and the jurisdiction it applies to. Feed it to the model with every job. This single step removes most of the recurring error.
Two: machine first pass, always into a working file. Never straight into the client-facing document, because a draft in the final template gets sent.
Three: bilingual review. The reviewer reads both texts side by side, and the instruction is to check meaning rather than to improve style. Style improvements introduce meaning changes.
Four: record the sign-off. Who reviewed the French, when, and against which source version. This is a two-line file entry and it is the entire audit trail.
Five: version control. When the English changes, the French is stale. Most translation problems in practice are version problems wearing a translation costume.
A mid-sized professional firm had a dozen Quebec clients and translated only what was demanded, late and expensively, because each translation was a project.
The change: a 140-term termbase, a machine first pass on standard correspondence and reports, and a named bilingual professional reviewing everything client-facing. Structural documents — anything constituting, contracting or filing — still go to an external legal translator, because that is where the civil-law vocabulary risk sits and the cost of being wrong is not comparable.
Measure what proportion of client-facing material now goes out in the client’s language, and how much reviewer time each document takes. If reviewer time per document is not falling as the termbase grows, the termbase is not being used.
Can AI translate a contract into French?
It can produce a draft. Whether that draft can be executed is a legal question, and for anything constituting, contracting or filing in Quebec the civil-law vocabulary risk means a qualified legal translator is the right cost.
Do we have to file in French in Federal Court?
No. Either official language may be used in pleadings and processes in a federal court, and choosing one must not prejudice you. Translation there is a service to the client, not a requirement.
Is a free translation tool acceptable for client documents?
Treat it as a transfer of confidential information to a third party, because it is. Approve one route with terms your firm has read, and make it the convenient one.
A 30-minute call is enough to tell you whether AI pays for itself here.
