Platform

Prequalification that checks the document, not just that one exists

Insurances, licences, SWMS and inductions in one place, with expiry dates the system watches - so a crew turning up on Monday is a question you have already answered.

Join waitlist

Replaces: CM3, spreadsheets, email chains
Tiering: Strategic and occasional, checked differently
Hierarchy: Head contractor, sub, sub-sub
Used by: Procurement, HSEQ, site managers

What does contractor prequalification need to do beyond collecting documents?

Collecting documents is the easy half, and the half that fails quietly. A certificate of currency that expired in March is still a file in the folder. Prequalification works when every document has an expiry the system watches, when the depth of the check matches how much work the contractor actually does for you, and when what a contractor was approved for is the same record the site gate reads. Frontline holds the company, its workers, their competencies and its documents as one linked record, so 'can this crew start Monday' has an answer rather than an email thread.

Every document carries an expiry, so lapsing is a state and not a surprise
Tiered checks - a strategic contractor is not vetted like a one-day trade
Head contractor, subcontractor and their subcontractors in one hierarchy
Approval, induction and competency resolve to the person at the gate

924
competency rules from one customer's training matrix31 roles by 70 requirements: 3
tiers of contractor hierarchyHead contractor, sub, sub-sub: 24h
from your contractor list to a live register: 0
documents that expire without anyone noticing

The problem

The folder is full and nobody is sure

Prequalification usually means a shared inbox, a folder per contractor and a spreadsheet saying who is approved.

It holds up right until someone asks a question with a date in it. Is that public liability policy still current. Did the ticket for the operator on site last week actually cover the plant he was on. The documents exist, so the answer feels like yes, and checking properly takes an afternoon nobody has.

The other failure is uniform effort. The contractor doing forty percent of your work and the one doing a day of ceiling repairs go through the same forms, so the important one gets the same shallow check as the trivial one.

Expiry dates the system watches, on every document
Depth of check set by what the contractor actually does for you
The gate reads the same record procurement approved

What it does

Companies, people and proof on one record

Companies and workers linked

A contractor company holds its people, its insurances and its licences on one record. Approving the company and approving the crew stop being two disconnected exercises.

Expiry is a state

Certificates of currency, licences, tickets and SWMS all carry dates. Approaching and lapsed are states on the register, and the people who need to know are told before it matters.

Tiered verification

Set the depth of the check by tier. Strategic contractors get the full pack and a real review, occasional trades get a proportionate one, and your effort goes where the exposure is.

Multi-tier hierarchy

Head contractor, subcontractor, and their subcontractors, with the chain visible. You can see who is on your site and whose approval they came through.

Competency rules that resolve

Requirements come from the person's role rather than a checklist someone remembers. One customer's training matrix became 924 rules the system resolves and joins evidence against.

One record at the gate

Induction, approval and competency resolve at sign-on, so the site enforces the same decision procurement made rather than a printout of it.

How it works

From your contractor list to a live register

Send the list you keep now
A spreadsheet, a CM3 export, or the folder structure. We take what exists rather than asking you to fill in a template first.
We set the tiers and the requirements
What a strategic contractor must hold, what an occasional one must, and what expires when.
The gaps show up immediately
Expired insurances, missing tickets, contractors approved four years ago and never re-checked. That list is the point of the exercise.
Renewals stop being someone's memory
Every document has a date, so chasing is a list the system produces rather than a thing your coordinator remembers to do on a good week.

Included

What you get on day one

Your contractor companies and their workers, imported
Document requirements set per tier
Expiry tracking on insurances, licences and tickets
A live list of what has lapsed or is about to
Multi-tier contractor hierarchy
Competency rules resolved from role
Site induction and sign-on against the same record
Approval history - who approved what, and when

Questions we get asked

We use CM3. Does this replace it?

That is usually the intent. Send the export and we import the companies, the documents and the approval states you already have, so you are not starting the register again from nothing.

Can contractors maintain their own documents?

That is the direction and it is on the build rather than finished. Today your team works from a live list of what has lapsed instead of chasing by memory, and the document requirements per tier are already configured.

How do you handle subcontractors of subcontractors?

As a hierarchy. Each company sits under the one that engaged it, so you can see the whole chain that ends up on your site and whose approval it came through.

Does the site gate know about any of this?

Yes. Sign-on resolves against the same record - the approval, the induction and the competencies for that person's role. A crew that is short of something is short at the gate, not after an incident.

Where teams take it next

See it on your own contractor list.

Send the spreadsheet or the CM3 export. When your spot comes up we show you what has already lapsed.