Contractor prequalification is usually built as an intake form. A contractor fills it in, a coordinator reviews it, the record is filed, and the crew starts work. Two years later nobody can say which safety statistics were reviewed, whether the insurance is still in force, or which sites the crew was cleared for. The form was completed. The control was never operated.
Operators and mining companies carry hundreds of contractor relationships across drilling, construction, maintenance, logistics and specialist services. Each arrives with a different safety record, insurance profile and set of competency requirements. Treating that population with one questionnaire and one approval step produces a file rather than a qualification. It also produces a slow onboarding cycle, because every exception is settled by email.
This datasheet sets out what a prequalification and onboarding system has to capture, who owns each item, what re-opens it, and what evidence it produces. Prequalification is a recurring control with a cadence, not a gate a contractor passes once and then leaves behind.
What prequalification has to establish
A qualification decision rests on four judgments. Can this contractor perform the scope safely, is it financially able to carry the work, is it permissible to transact with the entity, and do the crews hold the competencies the site requires. Each judgment needs its own evidence, refresh cycle and owner. Bundling them into a single pass or fail flag destroys what a work order approver needs later.
- Qualification questionnaire and scoring, structured by work type so a scaffolding contractor answers scaffolding questions, with weighted scoring that produces a band rather than a binary result and a documented threshold per band.
- HSE performance evidence, safety statistics, incident history and training records captured as dated fields with defined units, so numbers can be compared across contractors and trended across reporting periods.
- Insurance certificate capture, policy type, carrier, limits, named insured and expiry recorded as data, with the certificate stored on the record and the expiry date driving re-verification on its own.
- Financial and screening checks, financial standing review alongside sanctions and denied party screening, run as a repeatable step with a stored result, a date and a named reviewer rather than a search.
- Site and competency requirements, the permits, inductions and individual certifications each work type demands at each location, held per site so a crew cleared for one facility is not assumed cleared everywhere.
Those five items behave differently over time. A questionnaire answer is stable until the contractor changes. Safety statistics refresh on a reporting cycle. An insurance certificate expires on a fixed date. A screening result decays because the underlying lists move. Competency records expire per person. A system that stores all five the same way lets the shortest-lived item go stale while the record still reads qualified.
Treat qualification as a state that must be maintained, not a status that was granted. Every element supporting it carries a valid-through date, and the earliest of those governs the record. When that date passes without new evidence, the contractor moves to conditional or suspended, and work order approval reads the change immediately.
What the platform does
The capability set below separates a prequalification system from a document library. Each item removes a manual step that otherwise depends on somebody remembering. The test is the same for all of them. When the underlying fact changes, does the record change on its own, and does the person about to award work see it.
- Work type questionnaires with weighted scoring. The scope selected at intake determines which sections a contractor sees. Scores roll up to a band, and the band drives approval routing, so a high-risk scope cannot be cleared by a general reviewer.
- HSE evidence held as structured data. Safety statistics, incident history and training records land in typed fields with reporting periods attached, rather than as attachments nobody opens. Comparison across the population becomes a query, not a reading exercise.
- Expiry driven re-verification. Insurance certificates, site permits and individual competencies each carry an expiry. The system opens a re-verification task ahead of the date, notifies the contractor, and escalates when evidence does not arrive in time.
- Screening as a scheduled, repeatable step. Financial review and sanctions or denied party screening run on a defined cadence and on triggers such as a change of ownership. Each run stores its result, date and reviewer, which is what an auditor asks for.
- Handoff into the agreement and the work order. A qualified record passes its scope, tier and conditions into the master service agreement, and the work order inherits the site clearances and competency requirements the qualification established.
A five-step rollout for contractor qualification
Step 1, Define The Work Type Catalog
Start with the scopes you actually award, not an abstract vendor taxonomy. Each work type gets its own question set, competency list and risk tier. Keep the catalog short enough that a coordinator can pick the right entry without guessing, and revisit it as service lines change.
Step 2, Fix The Scoring Model And Bands
Agree the weighting before configuration and write down what each band permits. A band should map to something operational, such as which sites the contractor may enter and which approver releases the work. Have safety and procurement sign off jointly, because a model owned by one function gets argued with.
Step 3, Convert Evidence To Fields
Take the documents you collect today and decide which values inside them the business actually uses. Those become fields with units and reporting periods. The document stays attached for reference, but the decision runs on structured values, which is what makes comparison possible.
Step 4, Attach Expiry And Cadence To Every Item
Give each evidence type a validity period and a re-verification lead time. Insurance and individual competencies drive the calendar because their dates are fixed. Safety statistics and screening follow the reporting cycle and the tier. The cadence belongs on the item, not in a spreadsheet.
Step 5, Wire The Handoff To Contracting
Connect the qualified record to agreement creation and work order release. The tier selects the template and insurance requirements, and the release check reads live qualification state. Until that link exists the qualification is advisory, and someone will award work to a lapsed contractor.
See contractor qualification run as a control
Walk through work type questionnaires, structured HSE evidence, expiry driven re-verification and the handoff into the agreement, using your own contractor population and site requirements.
Requalification cadence tied to risk tier
Uniform requalification is the most common design mistake. An annual refresh for everyone treats a catering supplier and a well intervention crew as the same exposure, and it generates enough noise that responses stop being read. Tie the cadence to the tier instead. High-risk scopes refresh safety statistics and competency evidence on a short cycle and re-screen on a change of ownership. Low-risk scopes confirm insurance and basic details on a longer one. Event triggers sit on top of the calendar, so an incident, a change of control or a new site assignment re-opens the record whenever it happens. Teams that already track post-signature obligations usually find the same scheduling engine handles requalification without a second tool.
The capability table, what is captured and what it proves
The table below is the deliverable. Each row names what the platform captures, who owns it, the trigger that re-opens it, and the evidence it produces on request. Qualification feeds the agreement layer covered in the guide to JOA and EPC contract automation, and its safety evidence lines up with an HSE and environmental compliance audit checklist.
| What is captured | Owner | Trigger that re-opens it | Evidence produced |
|---|---|---|---|
| Qualification questionnaire and score | Contractor management lead | Scope change or tier cycle | Scored response with reviewer, date |
| Safety statistics and incident history | HSE function | Reporting period close or incident | Dated performance record |
| Training and competency records | Site supervisor | Individual certification expiry | Per person certification register |
| Insurance certificates and limits | Risk or procurement owner | Policy expiry or limit change | Certificate with limits and dates |
| Financial and sanctions screening | Compliance reviewer | Cadence or change of ownership | Screening result with source, date |
A contractor file proves that a form was completed. A contractor record proves that a qualification is current, that the evidence behind it carries a date, and that the work order released last week was cleared against live state rather than a memory of an old review. The difference is not extra process. It is the same information held so that it expires on its own, reaches the person who needs it, and can be produced without a search.
For related guidance, see Contractor prequalification and MSA control for operators, ServiceNow supplier onboarding: closing the contract gap and The operator’s guide to oilfield MSA indemnity control.
