Onboarding a subtrade is a document-collection problem, and document collection is exactly what automation is good at. The checklist is short; the reason it takes three weeks is that nobody owns the chasing.
Key takeaways
Subcontractor onboarding is a document-collection problem wearing a compliance hat. There are perhaps eight things you need before a new subtrade sets foot on site, every one of them is a document somebody else holds, and the reason it takes three weeks is not difficulty — it is that nobody owns the chasing. Automate the chasing and the extraction, and the same set can be assembled in a sitting.
1. A WSIB clearance, before work starts. This one is not a nicety. The WSIB policy on clearance certificates in construction states that a principal who directly retains a contractor to perform construction work must obtain a clearance confirming the contractor is in good standing before the work begins, that the clearance must remain in effect for the entire time the contractor is performing the work, and that starting construction work without one is an offence for both the principal and the contractor.
2. Proof the sub is registered at all. Coverage in construction is broader than many small firms expect. The WSIB explains that under expanded compulsory coverage, independent operators, sole proprietors, some partners and some executive officers working in construction must have WSIB coverage, and that a business has 10 calendar days from the day it hires its first employee to register. A sub who “does not need WSIB” is worth a second question.
3. A current certificate of insurance, naming the right parties and covering the right dates. Collecting it is onboarding; keeping it current is a separate ongoing job.
4. Trade qualification where the trade is compulsory. Skilled Trades Ontario lists the compulsory trades in Ontario and the certificates a person must hold to work in one. This is a per-person check, not a per-company one, and no amount of paperwork at the company level substitutes for it.
5. A licence, where the work is licensed rather than merely certified. Electrical contracting in Ontario runs through the Electrical Safety Authority, which administers the Electrical Contractor Licence. New home building and selling runs through the Home Construction Regulatory Authority, which publishes the Ontario Builder Directory for checking a builder’s status. These are lookups, not documents to be requested — which makes them ideal to automate.
6. The tax details you will need at year end. The Income Tax Regulations require that a business whose income is derived primarily from construction activities and which pays or credits amounts for goods or services rendered in the course of those activities must file an information return for those payments, with the return due within six months after the end of the chosen reporting period. Collecting the sub’s legal name and business number at onboarding costs a field; collecting it in month eleven costs a week.
7. The subcontract itself, with scope, price, payment terms and holdback stated. For consumer-facing renovation work, Ontario guidance also requires the head contract to identify any sub-trades that will be contracted out, who the sub-contractors are, and who will pay for them — so the owner-facing paperwork and the sub onboarding are linked.
8. Site-specific safety documents — orientation completed, hazard assessments acknowledged, and whatever your own programme requires before a new crew mobilises.
Three places, in order of payback.
Intake. One form, sent once, that collects the company details and takes uploads for each document. This removes the email thread, which is where onboarding usually dies.
Extraction. Document-understanding services read the uploaded PDFs and pull out the fields you care about — names, policy numbers, expiry dates — instead of a coordinator retyping them. Azure Document Intelligence documents custom document models where the extraction fields are defined by your own labelled examples, and Google’s Document AI documents its Enterprise Document OCR processor for reading text and structure out of scanned files.
Chasing and expiry. The set is never complete on the first pass. The rule that earns its keep is simple and mechanical: a sub with a missing or expired document cannot be scheduled, and the reminder goes out on a schedule rather than when someone remembers.
Automate the collection, never the conclusion
Safe to automate: sending the request, reading the documents, extracting dates and numbers, checking a public register, flagging what is missing or expiring, and blocking scheduling until the file is complete.
Not safe to automate: deciding whether the coverage is adequate, whether a person is qualified for the task, or whether a worker is a contractor or an employee.
A useful test — if getting it wrong creates liability rather than an inconvenience, a named person signs off on it.
Whether the person you are onboarding is genuinely a subcontractor rather than an employee is a legal characterisation, and getting it wrong is expensive. Ontario’s guide to the Employment Standards Act is blunt about it: employers are not allowed to treat employees covered by the Act as if they are not employees, and an employment standards officer can issue a notice of contravention resulting in a penalty, a prosecution, or both. The same guidance lists the common misconceptions — that charging HST, submitting invoices, using their own vehicle, or the absence of statutory deductions makes someone a contractor. None of those is decisive, and neither is a signed document saying so.
A model can assemble the facts about the relationship. It cannot make the call. Our sister firm covers how the classification test works in Ontario, and separately what happens when a misclassified contractor is injured on the job.
Illustrative — a composite workflow rather than a specific firm’s results.
A general contractor adds a new drywall sub. The coordinator sends one intake link. The sub uploads a certificate of insurance, a WSIB clearance and a business registration, and types in a business number and two site contacts. Extraction pulls the insurer, the policy number, the limits and both expiry dates off the certificate, and the clearance number and its expiry off the WSIB document; each extracted field is shown to the coordinator next to a thumbnail of where it came from, for a five-second confirmation rather than a retype.
Two checks are still manual because they should be: the coordinator opens the public register to confirm the trade certificate of the person named as the lead installer, and the project manager confirms the scope and price on the subcontract. The file closes the same afternoon, with the clearance expiry and the insurance expiry both written into the calendar that blocks scheduling.
The subcontract and the trade certificates, often. The clearance, no — WSIB clearances have a defined validity period and must be in effect for the whole time the work is performed. Treat a returning sub as a refresh of the dated items, not a skip.
Ask anyway. In construction, coverage obligations extend to independent operators and sole proprietors, and the WSIB notes that independent operators outside of construction might not be obligated to register — so the answer to “do they need to be registered?” depends on facts, not on headcount alone.
All of it, if the checklist is a form and a calendar rather than a habit. The failure mode in small firms is not that the checks are hard, it is that they live in one person’s head. Writing them down as fields with expiry dates is most of the benefit; the extraction is what makes it fast enough that nobody skips it under pressure.
A 30-minute call is enough to tell you whether AI pays for itself here.
