Subcontractor Onboarding
Prequalification decides whether you work with a sub. Onboarding is everything between "approved" and "on site", and it is where most of the avoidable friction on a job gets created or prevented.
Done well it takes a week and never comes up again. Done badly it produces a sub who invoices in the wrong format, has never seen your lien waiver forms, and shows up at the gate without a certificate.
Who owns it: the project manager for that job. The contract administrator supplies the paperwork; the PM owns whether the sub is actually ready.
If the sub is not yet approved, start at the prequalification process.
Phase 1 โ Contract executionโ
Nothing else in this workflow is worth doing until the subcontract exists.
Execute it before mobilization, not after. A sub working without a signed subcontract is working on your general conditions and their assumptions, and every dispute that follows starts from there.
The subcontract needs to carry, at minimum:
- The scope, by specification section and drawing reference, with exclusions stated
- The contract sum and how change orders get priced and approved
- The schedule, including their milestone dates and manpower commitment
- Payment terms, retainage, and the pay application cycle
- The insurance requirements exhibit
- Lien waiver forms as exhibits โ the actual forms they will be signing
- Safety requirements and the consequences of violating them
- Any conditions carried over from a conditional approval โ bonds, joint checks, funds control, increased retention
Use the subcontractor agreement generator as the base and keep your exhibits consistent across every sub on the job.
Conditions from a conditional approval have to be written into the subcontract itself. An increased retention percentage that lives only in the approval letter will not survive the first time accounting cuts a check from the standard template.
Phase 2 โ Documentsโ
Collect these once, centrally, and file them where the next person can find them.
| Document | What good looks like |
|---|---|
| W-9 | Entity name matches the subcontract signature block and the name they will invoice under |
| Banking / ACH details | Received on their letterhead, from a known contact, and verified by phone |
| Certificates of insurance | Checked line by line against the exhibit, with endorsements |
| Contractor's license | Current, correct state, correct classification for the scope |
| License bond, where required | Current |
| Written safety program | An actual document, not a statement that they have one |
| Emergency contacts | Two people, with mobile numbers, available outside business hours |
| Key personnel | Named foreman, named project manager, named safety contact, named person for invoicing |
| Subcontract bond, if required | Received before mobilization, not promised |
The banking fraud warningโ
Payment redirection fraud is the most common way construction companies lose money to fraud, and the mechanics are always the same. Someone emails from an address that looks like your sub's, says their banking details have changed, and attaches a form on convincing letterhead.
The rule, without exceptions:
Any change to banking details โ new account, new bank, new routing number โ is verified by calling the sub back on a number you already had on file, not a number in the email, and speaking to a person you have dealt with before. Do this for the first setup and for every change afterwards, including the ones that look routine.
Two supporting controls worth having:
- The person who changes banking details in your system is not the person who approves payments
- A first payment to changed details is confirmed with the sub by phone after it is sent
Write both into your accounting procedure. This is a fraud that succeeds because it happens during a busy week to a person acting alone.
Phase 3 โ Site orientation and safetyโ
Nobody works before orientation. That includes the sub's owner, their delivery drivers who enter the work area, and the crew they add in month four.
The orientation covers:
- Site-specific hazards โ what is on this job that is not on every job
- Site rules โ hours, parking, deliveries, laydown, hot work permits, PPE, drug and alcohol policy
- Hazard communication โ where the safety data sheets live and how to add theirs
- Emergency procedures โ muster point, first aid, who calls what, how an incident gets reported and how quickly
- The escalation path โ who they raise a safety concern with, and that stopping work is always allowed
Then two administrative pieces:
- Badging or sign-in, so you can produce who was on site on any given day
- A signed site rules acknowledgement from every worker, filed
Their foreman also needs to know how your daily reporting, manpower reporting and toolbox talk expectations work, because those are the things that get missed in week one and become an argument in week six.
Phase 4 โ Systems setupโ
The sub is joining your operating system. Show them how it runs before they are behind.
| Set them up on | What they need to know |
|---|---|
| Schedule | Where the current schedule lives, how updates are published, their milestone dates, and who to tell when a date is at risk |
| Submittals | The submittal register, their items, the format, the due dates, and the review turnaround they can expect |
| RFIs | Who may raise one, the form, where it goes, and the expected response time |
| Pay applications | The format, the schedule of values, the cut-off date, the approval path, and when payment actually lands |
| Lien waivers | Which form for conditional and unconditional, at which stage, and that lower-tier waivers are required too |
| Change orders | How a change gets authorized, and that work performed without authorization is at their risk |
| Document access | Current drawings and specs, and how revisions are issued |
The pay application piece deserves a real conversation, not an email. The most common cause of a late first payment is a first pay application in the wrong format against a schedule of values nobody approved.
Walk the sub's billing contact through one complete pay application cycle before the first one is due. Fifteen minutes there saves a month of cash flow argument, and cash flow arguments are how good subs become slow subs.
Also give them the who to call for what list. One name for scope and schedule, one for payment, one for safety, one for documents. Subs escalate to whoever answers, and that is usually the wrong person.
Phase 5 โ The pre-mobilization gateโ
One person confirms this list is complete before the sub is on site. Not "in progress" โ complete.
- Prequalification current and the award inside their single job and aggregate limits
- Subcontract fully executed by both parties
- Certificates of insurance on file, checked against the exhibit, all coverages current
- Additional insured, waiver of subrogation and primary and non-contributory endorsements received
- Contractor's license verified current for this state and classification
- W-9 on file, entity name matched
- Banking details verified by phone to a known number
- Subcontract bond received, if required
- Conditional approval conditions written into the subcontract and assigned to an owner
- Written safety program received
- Site-specific orientation scheduled or completed for every worker mobilizing
- Site rules acknowledgement signed
- Emergency contacts and key personnel on file
- Schedule of values approved
- Submittal items identified with due dates
- Lien waiver forms issued and acknowledged
- Systems access granted
The full printable version is the subcontractor onboarding checklist.
The gate is only real if somebody is willing to hold it on a Monday morning when the sub is already in the parking lot. Decide in advance who that person is, and back them when they do it.
What to hand them on day oneโ
Give this as one packet, on paper or as one shared folder, with a single index page. The onboarding packet template assembles it.
| Item | Why they need it |
|---|---|
| Executed subcontract with all exhibits | Their copy, with the exhibits attached โ not the unsigned draft |
| Site rules and safety requirements | The rules they just acknowledged, in writing |
| Site logistics plan | Access, parking, laydown, hoisting, deliveries, working hours |
| Emergency procedures card | Muster point, first aid, emergency numbers |
| Contact sheet | Who to call for scope, payment, safety, documents, and after hours |
| Current schedule extract | Their activities, their milestones, their float |
| Schedule of values, approved | What they may bill against |
| Pay application template and calendar | Format, cut-off dates, payment dates |
| Blank lien waiver forms | Conditional, unconditional, and lower-tier versions |
| Change order form and procedure | Including the sentence that unauthorized work is unpaid work |
| Submittal register extract | Their items and dates |
| RFI form and procedure | |
| Insurance requirements exhibit | So their broker has it for the renewal |
Handing over a complete packet on day one sets the standard for the rest of the job. Subs match the level of organization they are shown.
Related Resourcesโ
- Onboarding Packet โ day-one document set
- Onboarding Checklist โ mobilization gate
- COI Collection & Tracking โ certificates before site access
Next: keep them compliant through COI collection and tracking, and refresh the file each year at annual requalification.