Organization requirements
The records your organization requires across the contractor relationship.
Move from collection to readiness
Onboard Contractors Efficiently
Replace scattered email threads and one-off checklists with an onboarding path that shows what has been received, what has been reviewed, and what still blocks an assignment.
Add the contractor to your subscription before any invitation, Portal access, profile or document collection, upload, message, or compliance review.
Profile Who is being engaged
Requirements What must be provided
Review What has been approved
Ready For the applicable assignment
Onboarding should answer one question: ready for what?
General onboarding can establish a foundation, but the final readiness decision may depend on the client, location, role, or assignment.
Client requirements
Approved requirements that apply to work for a particular client.
Location requirements
Access, insurance, qualification, or documentation needs tied to a location.
Assignment requirements
The evidence or qualifications needed for the specific work being considered.
A readiness path with clear gates
- 1
Add and define
Add the contractor to your subscription, then use reusable document-requirement sets to define what the Active contractor must provide.
- 2
Collect
Receive profile, company, agreement, tax, insurance, and qualification records.
- 3
Review
Resolve missing, rejected, or unclear information before the first assignment.
- 4
Release
Carry the approved record into the assignment decision.
Company documents and individual qualifications are not the same thing
Contractor company
- Business information
- Company agreements
- Company insurance
- Service coverage
People performing the work
- Individual qualifications
- Approved training records
- Role-specific documents
- Assignment readiness
Spot exceptions before they become delays
The onboarding view should make these conditions distinguishable.
- Not received
- Received but not reviewed
- Approved
- Rejected or needs correction
- Current but expiring
- Required only for a particular assignment
Example
One company, several people, three client locations
A contractor company can submit company-level records once while the people expected to perform the work provide their individual qualifications. The final readiness check can then account for the requirements of each location.
Questions
What teams usually ask
Does onboarding make a contractor eligible for every assignment?
No. General onboarding and assignment-specific readiness are separate decisions.
Can requirements vary by client or assignment?
Yes. Organization-wide requirements can be supplemented by client, location, role, or assignment requirements.
Does onboarding count separately from later work in our subscription?
No. Each contractor counts once toward your purchased capacity throughout onboarding and later work. Add the contractor to your subscription before onboarding starts. The contractor then has access to the later work features included in your plan.
Can we reuse onboarding requirements and messages?
Yes. All plans include reusable document-requirement sets and onboarding message templates. Templates do not require AI.
Explore Mezline
Connect the outcome to the rest of your contractor operation.
See how Mezline brings contractor records, clients, assignments, approvals, invoicing, payables, and reporting into one operating system.