Prequalification and onboarding side by side
| Dimension | Prequalification | Onboarding |
|---|---|---|
| Primary decision | Should this firm advance or be eligible for the work? | What must be completed before this selected firm starts? |
| Typical timing | Before bid invitation, selection, or award | After selection or award, before mobilization |
| Common inputs | Company profile, experience, capacity, safety, insurance, licensing, references | Executed contract, accounting setup, project evidence, orientations, plans, site logistics |
| Output | Documented evaluation or eligibility decision | Documented project-readiness decision and handoff |
| Owners | Estimating, procurement, risk, safety, operations, leadership | Project team, accounting, risk, safety, field leadership |
| Repeat cycle | Periodic company-level refresh and scope-specific review | Every project, contract, and mobilization |
Where prequalification should end
Prequalification should end with a recorded human decision, any conditions, the decision date, and the people responsible for it. It should not quietly remain open while project teams assume award means every requirement has been accepted.
- Capture company-level information once when policy allows, then confirm that it is current.
- Add scope-specific questions for value, capacity, hazard, trade, and location.
- Record exceptions instead of hiding them inside free-form notes.
- Pass approved conditions into onboarding so the project team knows what still matters.
Where onboarding should begin
Onboarding starts from the actual award and project requirements. The workflow should translate obligations into named tasks, evidence, reviewers, due dates, and a clear final handoff to the superintendent or other field authority.
- Confirm the executed commercial documents and current scope.
- Open accounting and tax setup through approved secure channels.
- Request project-specific insurance and licensing evidence for qualified review.
- Coordinate safety, orientation, access, logistics, schedule, and field contacts.
- Record readiness by area before an authorized person releases mobilization.
Why combining the workflows creates blind spots
A single long questionnaire often mixes company evaluation, sensitive document collection, contract administration, and project mobilization. That makes ownership unclear and encourages teams to treat receipt as approval. Two linked workflows create a deliberate decision boundary while still reusing information that remains current and applicable.
- The estimator can see the evaluation result without owning project onboarding.
- The coordinator can request evidence without interpreting coverage or legal sufficiency.
- The field team can see unresolved mobilization items without reading an entire prequalification file.
- Leadership can measure cycle time separately for selection and readiness.
BUILD BOTH WORKFLOWS
Start with a prequalification form, then hand selected firms into a project checklist.
Explore the free toolsCommon questions
Is subcontractor onboarding the same as prequalification?
No. Prequalification supports a decision before selection or award. Onboarding coordinates a selected subcontractor’s contract, evidence, internal reviews, project setup, and mobilization.
Should prequalification data be reused during onboarding?
Reuse information only when it remains current, applicable, permitted by policy, and available through the approved system. Project-specific requirements and decisions still need their own onboarding record.
Who decides when onboarding is complete?
Use the person or group authorized by company policy. The workflow can show that required areas are complete or unresolved, but the tool should not make the final authorization automatically.
Primary references
OSHA construction safety program guidance · SBA licenses and permits guidance
This guide describes a general coordination model. Your company should define the decision rights, requirements, and evidence appropriate to its contracts, projects, trades, and jurisdictions.