The problem
As contractor compliance becomes digital, it is tempting to let the system decide. If all requirements are met, the contractor is "approved". If a person's training is valid, they are "authorised". If something is missing, a manager overrides the status and the contractor becomes "compliant".
Each of these shortcuts blurs a distinction that matters: the difference between what a calculation shows and what a responsible person decides.
Why it matters
Readiness and eligibility are calculated from records: requirements, evidence, verification and expiry dates. They answer the question "according to our records, does this contractor or person meet the defined requirements?"
Mobilisation and access are decisions. They answer a different question: "given everything we know, including what the records do not show, should this contractor start work, and should these people enter this site?"
When the two are merged, several problems follow:
A calculated "ready" is treated as permission, even when a manager knows of a concern the system does not.
An override replaces the underlying status, so the record no longer shows that a requirement was unmet at the time.
Nobody can later tell whether a decision was made by a person or simply inherited from a calculation.
Eligibility to enter a site is confused with being authorised to enter it.
A practical approach
Keep facts and decisions separate, and record both.
Calculate readiness transparently. Readiness should be derived from requirements and show the specific blockers. Statuses such as Ready, Conditionally Ready and Not Ready are more useful than a percentage, because they make the remaining issues explicit.
Make mobilisation a recorded human decision. A named person decides whether to mobilise, with the calculated readiness in front of them. The decision, the person and the time are recorded.
Allow justified overrides without erasing facts. Sometimes work must proceed with a condition outstanding, under agreed controls. That can be legitimate. But the override should be recorded as a decision alongside the non-compliance, not as a change to it. The record should still show that a requirement was not met.
Keep history append-only. Decisions should be added, not overwritten. If a decision is reversed, the reversal is a new entry.
Separate eligibility from authorisation. A person may be eligible to enter a site because their requirements are satisfied. Authorisation to enter is a separate decision, made by someone with the authority to make it.
The principle can be summarised simply: calculation supports the decision; a person makes the decision.
What a good system should provide
A good contractor management system should:
Calculate readiness from defined requirements, with clear statuses and listed blockers.
Record mobilisation decisions separately from calculated readiness, including who decided and when.
Keep non-compliance visible after an override.
Store decisions as append-only history.
Distinguish calculated access eligibility from human access authorisation.
How those requirements are defined in the first place is covered in Why a Document Folder Is Not Contractor Compliance.
How Contractor Management addresses it
Contractor Management, a module of the Sospita HSE Platform that is currently coming soon, keeps calculation and human decision separate throughout.
Mobilisation readiness is calculated from requirement instances and shown as Ready, Conditionally Ready or Not Ready, with the blockers listed. The mobilisation decision is recorded separately as a human decision, and decisions are append-only. When a decision is made despite unmet requirements, the underlying non-compliance remains recorded alongside it.
Site access follows the same pattern. Calculated access eligibility is kept separate from site access authorisation, which is a human decision recorded with its own events. Contractor standing is also set by human decisions, rather than changing silently in response to other records.
Limitations and human responsibility
Separating calculation from decision only works if people take the decision seriously. A system can require that a decision is recorded; it cannot ensure that the person considered the information in front of them.
Readiness reflects the records. If evidence was verified carelessly or requirements were poorly defined, a "Ready" status can still be misleading.
Contractor Management records access authorisation decisions. It does not operate physical access control hardware such as gates, turnstiles or badge readers.
Responsibility for mobilising contractors and allowing people onto site remains with the organisation and its authorised personnel.