To check subcontractor technicians before mobilisation, compare every person the subcontractor proposes against the project's own training matrix — role by role, including onshore or offshore items — using certificates that have been verified, not just listed. Check expiry against the project end date, not just today. CertCase gives you that check per person and per project, with the reasons anyone is not ready.
This guide covers what to ask for, where checks usually fail, and how CertCase helps main contractors and their subcontractors see the same answer.
What to check for each subcontractor technician
Before a technician goes to site, you need to know:
- They hold every mandatory item for their role on this project: GWO BST modules, BTT where required, medicals and any electrical authorisations.
- Offshore items are covered when the work is offshore: GWO Sea Survival and an offshore medical.
- Certificates have been verified against evidence, not just typed into a list.
- Nothing expires during the deployment window.
- Client-specific items, such as a site induction, are confirmed separately where they cannot be proven by a certificate.
Where subcontractor checks go wrong
Subcontractor compliance is usually handled by email: a spreadsheet of names arrives, followed by a folder of PDFs. Someone has to open each file, compare it with the training matrix and chase what is missing — often days before mobilisation. Lists go out of date as soon as they are sent, and it is hard to show an auditor later what was checked and when.
How CertCase handles it
In CertCase, each technician keeps their own profile and shares it with the organisations they work for. A main contractor can see the subcontractor workforce allocated to its projects through contractor oversight, without anyone emailing certificate copies.
Each project has its own requirements. You can import the client's HSE training matrix; CertCase suggests the matching certificates and a person confirms uncertain matches before they count. Each person is then shown as ready, awaiting verification or not ready, with every missing or expiring item listed. "Workforce by company" groups the result by supplying company, so you can see which subcontractor carries the most risk.
Where something is missing, you can send an evidence request to the technician. It only closes when new, verified evidence arrives — older or unproven evidence does not close it.
Access is controlled. Some client users can be given summary-only access: they see readiness, but cannot open or download certificate files.
Before mobilisation: a short checklist
- Confirm the project environment (onshore or offshore) and dates.
- Load or confirm the project's requirements for each position.
- Add the proposed technicians, including subcontractors.
- Work through the "not ready" and "awaiting verification" items first.
- Export the requirements matrix to Excel for the mobilisation pack if your client asks for one.
Frequently asked questions
Can I see a subcontractor's technicians without them emailing certificates?
Yes, where the technicians are on CertCase and allocated to your project. Technicians control what they share.
Does CertCase check expiry against the project dates?
Yes. Readiness considers whether certificates remain valid through the project, not only today.
What happens with requirements that are not certificates, like a site induction?
They are shown as client-specific items to confirm on site, and never counted as met automatically.
Can I limit what some client users see?
Yes. Summary-only users see readiness but cannot open or download certificate files.
See how CertCase handles your own crews and projects.
Book a demo