Skip to content
Supervisor checking a contractor compliance record at a site boom gate.

Platform module

Every contractor compliant before they set foot on site.

A live register of every service provider, the documents they owe you and their compliance status across every site — so non-compliant entry is blocked at the gate, not discovered after an incident.

Contractor & vendor register · Required-document tracking · Site inductions · Expiry-driven status · s37(2)-aligned agreements · Block non-compliant entry

The problem

Contractor compliance fails quietly — until it doesn’t.

Expired documents, uninducted workers and unsigned agreements only surface when an inspector, or an injury, forces the question.

📁

Documents in filing cabinets

Insurance, medicals and safety files scattered across email and paper mean nobody can prove who was compliant on the day.

⏰

Nobody watches expiry dates

Certificates lapse silently. A contractor who was compliant last quarter walks on site today with cover that expired weeks ago.

🚧

No gate on non-compliance

Without a hard check at access, uninducted or unagreed contractors get to work — and the liability lands on you.

How it works

Onboard once, stay compliant continuously.

Register. Add each contractor and vendor to a central register, mapped to the sites where they work.

Require. Define the documents each provider owes — insurance, medicals, method statements, s37(2)-aligned agreements.

Induct. Run and record site inductions so every worker is briefed before their first shift.

Monitor. Expiry dates drive live compliance status across all sites, with alerts before anything lapses.

Enforce. Non-compliant providers are flagged and entry is blocked until the gap is closed.

Capabilities

Everything you need to keep the gate honest.

🗂️

Contractor & vendor register

A single source of truth for every service provider and where they operate.

📑

Required-document tracking

Define, collect and version the documents each provider must hold to work on your sites.

🎓

Site inductions

Deliver and record inductions so competence and briefing are proven, not assumed.

🔔

Expiry-driven status

Compliance status updates automatically as documents approach and pass their expiry.

✍️

s37(2)-aligned agreements

Capture and store mandatary agreements aligned to section 37(2) obligations.

⛔

Block non-compliant entry

Hard-stop access for any provider whose documents, induction or agreement are outstanding.

On the data spine

Compliance that talks to access, incidents and audits.

Service-provider compliance doesn’t sit in a silo. It reads inductions and documents, feeds a live status to your access control, and links straight to any incident or audit finding involving a contractor — so the same record answers “were they allowed on site?” every time.

What feeds it

  • Uploaded certificates and agreements
  • Site induction records
  • Audit & inspection findings
  • HR and access-control integrations

What it feeds

  • Access control (allow / block at the gate)
  • Incident management (contractor incidents)
  • Non-conformance & CAPA
  • Meetings & reviews reporting
“An expired certificate used to be a problem we found after the fact. Now a contractor simply can’t get through the gate until they’re compliant — and it holds across every site.”
Group Compliance ManagerLogistics · South Africa

Name and company withheld under NDA at the client’s request.

FAQ

Service-provider compliance, answered.

Can MiMs actually stop a non-compliant contractor entering?

Yes. Providers with outstanding documents, inductions or agreements are flagged non-compliant, and — where integrated with access control — entry is blocked until the gap is closed.

How do you handle document expiry?

Every required document carries an expiry date that drives compliance status automatically, with alerts raised before a certificate lapses so you can act ahead of time.

What are s37(2)-aligned agreements?

These are mandatary agreements aligned to section 37(2) of the OHS Act, capturing the shared safety obligations between you and your contractors. MiMs stores and versions them against each provider.

Does it work across multiple sites?

Yes. A contractor’s status is tracked per site on your data spine, so a provider compliant at one location isn’t assumed compliant everywhere.

Can it connect to our HR or access systems?

Yes. Through the MiMs API and integrations, compliance status can flow to access control and pull worker data from HR, so the gate always reads the current record.

Ready when you are

See how MiMs keeps every contractor compliant before entry.