A certified translator's time should go to the wording — not to counting whether the file is complete.
Machine translation didn't replace certified work — immigration and credential files still need a real translator to sign and stand behind them. But the hours before that signature — checking the file is complete and formatted for IRCC — don't need your certification at all.
01 The pain
A certified translation of immigration or credential documents has to be signed off by a licensed translator who takes responsibility for it — that's the whole point, and no machine can carry it.
But before you get to the wording, there's the sorting: is every document here, is it in the format IRCC expects, is anything missing? That's careful clerical checking eating time you should spend on the language itself.
02 Where your software stops
Google Translate and DeepL handle rough meaning — they don't produce a certified, signed translation, and they don't check that a client's file is complete and compliant. The responsibility and the prep both stay with you.
So the front-end review — counting pages, confirming requirements, chasing the one missing document — lands on the same person whose real value is the translation.
The machine can rough out the words. It can't sign for them — or check the file is complete first.
03 Why you can't just offshore it
An offshore team doesn't know Canadian immigration formatting — the IRCC rules for certified translations. I do: I'm bilingual EN/Mandarin and I know this path first-hand, working through the PGWP process myself — so the prep is checked by someone who understands both the language and the paperwork.
04 The gap I fill
I build the pre-translation layer: it checks each file against IRCC requirements, flags what's missing, and confirms formatting — so your certified time goes to the wording and the professional judgment, not to counting pages.
It never signs anything — the certification stays entirely yours. Every completeness check waits for you to review and approve it, and each requirement links to the IRCC rule it's based on — if it can't confirm something, it says "not found" instead of assuming the file is ready.