Most of the people on an infrastructure site do not work for the operator. Contractor management is where a site access platform earns its keep, or quietly stops being true.
| Contractor | Trade | Status | Inductions | Insurance |
|---|---|---|---|---|
| D. OkaforNorthline Electrical | Electrical | Active | Compliant | 14 Mar 2027 |
| S. BaptisteRedgum Scaffold | Scaffolding | Pending | Compliant | 02 Aug 2027 |
| L. MoreauKestrel Mechanical | Mechanical | Pending | 1 outstanding | 19 Jan 2027 |
| P. AdeyemiArdent Traffic | Traffic control | Suspended | Locked out | Expired |
Status is derived from the evidence on file and an administrator’s approval. Nobody types it in, which is what stops a register drifting away from what is actually verified.
Each stage writes to the contractor's record. Nothing here lives in a spreadsheet that somebody has to remember to update.
An administrator invites a company or an individual. The wizard resolves what that trade at that site actually needs and sends one link carrying the whole journey.
Licences, insurances and certificates are uploaded to the same link. OCR reads the fields off the upload and puts them in front of a reviewer; it never approves anything on its own.
A reviewer approves or declines with a reason. A decline is the message that tells the contractor what to upload again. Expiry dates are captured and monitored from then on.
An administrator approves the contractor on the register. Until then no pass can be issued. The status is derived from the evidence and the decision, never typed in.
A credential is issued, scoped to the sites they are cleared for. Policy acknowledgement and a current induction can each hold it.
Shifts scheduled and accepted, hours submitted and approved, documents watched as they approach expiry, and the live roster showing who is on site right now.
Work orders close, credentials are revoked, and archiving the contractor revokes what they still hold. The record and the audit trail remain.
Every company and every individual working on your sites, with their current status.
Request the right documents, assign the right inductions, in one action.
Schedule the work, record the hours, approve or reject them.
Attach the job to the people, the site and the documents it needs.
These are the ones that come up in evaluation, and the ones that are hardest to change later.
A contractor with every document verified is still "pending" until an administrator approves them. An automatic path that writes the value a permissioned path is gated on is how an approval gate gets bypassed by accident.
A crew submission creates an invitation, a contractor record and an approval for each individual. The company is the shared context they arrive under, not the thing that gets cleared.
Site requirements union with what the contractor already has verified. A depot can demand its own extra certificate without sending somebody back to upload again the insurance another site checked last month.
The company with four trades, three sites and an insurance certificate that expired last week. That is the walkthrough worth having.
