assess.one – AI-powered business operations platform

Workflow Template

Contractor Onboarding Workflow

Coordinator submits contractor company, worker, services, licence, insurance and safety document details. Compliance runs due diligence on the documents; if any are missing or deficient, they are requested from the contractor and rechecked until complete. The contractor then completes a site induction acknowledgement, site access is routed for approval, granted and recorded with a due date for expiring documents, and the coordinator is notified when onboarding completes or access is declined.

Organisations engaging third-party contractors face significant governance exposure around licence validity, insurance adequacy, and safety compliance before site access is ever granted. The Contractor Onboarding & Compliance Workflow provides a structured, auditable process spanning coordinators, compliance teams, and approvers, ensuring every contractor is vetted, inducted, and granted access only once documentation and safety requirements are demonstrably satisfied. Expiring document due dates and decision routing are captured throughout, giving organisations a defensible record for audit and regulatory review.

Business Outcomes

  • Reduced risk of unlicensed or uninsured contractors accessing sites
  • Faster onboarding cycle time through automated document rechecking
  • Complete audit trail of compliance decisions and access approvals
  • Fewer compliance breaches via automated expiring document tracking
  • Consistent induction and access sign-off across all contractor engagements

Workflow Steps

Steps

  1. 1
    Create Contractor Onboarding Recordcreate record

    Registers the submitted contractor onboarding request as a record.

  2. 2
    Set Status to Receivedupdate record

    Marks the onboarding record as received.

  3. 3
    Compliance Due Diligence Reviewcreate task

    Compliance officer reviews submitted licences, insurance and safety documents for completeness and validity.

  4. 4
    Set Status to Under Reviewupdate record

    Persists compliance review notes and marks record as under review.

  5. 5
    Route on Document Completeness

    Branches based on whether compliance review found all documents complete.

    documents_complete: "Yes"Set Status to Awaiting Induction
    documents_complete: "No"Set Status to Awaiting Documents
    DefaultSet Status to Awaiting Documents
  6. 6
    Set Status to Awaiting Documentsupdate record

    Marks the record as awaiting missing documents from the contractor.

  7. 7
    Request Missing Documents from Contractorrequest external input

    Sends the contractor a form link to resubmit missing or deficient licence, insurance or safety documents.

  8. 8
    Recheck Resubmitted Documentscreate task

    Compliance officer rechecks the resubmitted documents for completeness and validity.

  9. 9
    Route on Recheck Outcome

    Branches on whether the resubmitted documents are now complete.

    documents_complete: "Yes"Set Status to Awaiting Induction
    DefaultRestart Document Request Loop
  10. 10
    Restart Document Request Looprestart from step

    Documents are still incomplete; loop back to request missing documents again from the contractor.

  11. 11
    Set Status to Awaiting Inductionupdate record

    Marks the record as awaiting site induction acknowledgement.

  12. 12
    Request Site Induction Acknowledgementrequest external input

    Sends the contractor a link to complete and acknowledge the site induction.

  13. 13
    Record Induction Acknowledgementupdate record

    Persists the contractor's induction acknowledgement to the record.

  14. 14
    Request Site Access Approvalrequest approval

    Requests approval from the site manager to grant the contractor site access.

  15. 15
    Route on Access Approval Outcome

    Branches based on whether site access was approved or declined.

    approval_status: "approved"Grant and Record Site Access
    approval_status: "rejected"Set Status to Declined
    DefaultSet Status to Declined
  16. 16
    Grant and Record Site Accessupdate record

    Grants site access and records the access level on the record.

  17. 17
    Set Due Date for Expiring Documentsset due date

    Sets the record's due date to track when submitted documents expire and need renewal.

  18. 18
    Notify Coordinator Onboarding Completesend email

    Emails the coordinator confirming onboarding is complete and access has been granted.

  19. 19
    Set Status to Declinedupdate record

    Marks the record as declined when site access approval is rejected.

  20. 20
    Notify Coordinator of Declinesend email

    Emails the coordinator that site access was declined for this contractor.

Fields

  • Coordinator Name*
  • Coordinator Email*
  • Contractor Company Name*
  • Primary Worker Name*
  • Contractor Email*
  • Contractor Phone*
  • +14 more fields

Forms

Contractor Onboarding Request

11 fields

Data Views

Contractor Onboarding Records

company_name, worker_name, onboarding_status, access_level +1 more

Dashboard Widgets

Onboarding Status BreakdownOnboarding PipelineOnboarding Summary

Recommended integrations

Setup the following integrations to extend workflow capability.

  • Send email in the workflow

    AWS SES logoAWS SES
contractor onboardingcontractor managementvendor contractorsite inductioncontractor compliance

Similar Workflows

Similar Categories

FAQs

How is this workflow audited for compliance purposes?

Every status change, document review outcome, induction acknowledgement, and approval decision is timestamped and retained within the assess.one record for that contractor. This creates a complete, chronological audit trail that compliance and risk teams can review at any time without reconstructing history from email threads or spreadsheets. Records including due dates for expiring documents remain accessible for ongoing regulatory or internal audit purposes.

Who has access to contractor compliance and induction records?

Access is configured by role directly within assess.one, typically limited to coordinators, compliance reviewers, and designated site access approvers. Organisations can restrict visibility of sensitive licence and insurance documents to compliance personnel only, while coordinators retain visibility of status and outcome notifications. Permissions can be adjusted at any time as organisational structure or contractor volume changes.

How does this workflow integrate with existing enterprise systems?

Notifications to coordinators, contractors, and approvers via email or Slack are configured directly inside assess.one, with no third-party development required. This means integration is a configuration task completed within the platform itself, not a separate IT project. Additional connections can be added or adjusted as the organisation's tooling evolves.

How long does implementation take?

The template is ready to use and can be published in minutes, after which the coordinator, compliance, and approval teams can begin running live contractor onboarding immediately. There is no lengthy implementation project or software installation involved. Customisation of steps, roles, or notifications can be completed before or after publishing without delaying go-live.

What happens if a contractor's documents are missing or deficient?

The Route on Document Completeness step directs the case to the Request Missing Documents from Contractor step, notifying the contractor of exactly what is required. Resubmitted documents are then automatically rechecked, and the Route on Recheck Outcome step either progresses the case forward or restarts the document request loop until all requirements are satisfied. This ensures no contractor proceeds to induction or access approval with outstanding compliance gaps.

What happens if site access is declined?

The Route on Access Approval Outcome step directs declined cases to the Set Status to Declined step, and the coordinator is automatically notified via the Notify Coordinator of Decline step. This ensures decisions are communicated promptly and the record reflects a clear final status for audit purposes. No further access-related actions proceed once a decline outcome is recorded.

Can the workflow be customised for different contractor types or risk levels?

Yes, coordinators and administrators can adjust steps, approval logic, notification recipients, and required document types directly within assess.one to reflect different contractor categories or risk tiers. This allows, for example, higher-risk contractors to require additional approval layers without building a separate process. Changes take effect immediately upon publishing.

How are expiring documents such as licences and insurance managed?

Once site access is granted, the Set Due Date for Expiring Documents step records the relevant expiry dates against the contractor's record. This enables proactive tracking and follow-up ahead of expiry, reducing the risk of contractors operating on-site with lapsed licences or insurance. Organisations can configure notifications ahead of these due dates as part of their compliance monitoring practice.

Who is responsible for approving site access?

Site access approval is routed to designated approvers configured within the workflow, typically site managers or safety officers depending on organisational structure. The Route on Access Approval Outcome step ensures the case only proceeds to Grant and Record Site Access once formal approval has been recorded. This maintains a clear separation between compliance review and final access authorisation.

Ready to use this workflow?

Create a free account and customise this workflow for your business.

Contractor Onboarding & Compliance Workflow | assess.one