Fourteen capabilities that separate a real contractor management system from a visitor system wearing a contractor label — and the one demo test that proves it.
Most facilities discover they need contractor management the hard way: an incident occurs, and the investigation reveals that the injured worker's safety certificate expired two months earlier — and that nothing in the entry process would have caught it.
A visitor system will not catch it either, because a visitor and a contractor are structurally different. This guide explains what a contractor management system actually does, and the fourteen capabilities that separate a real one from a visitor system wearing a contractor label.
| Dimension | Visitor | Contractor |
|---|---|---|
| Entry frequency | Once or occasionally | Daily for weeks or months |
| Basis of authorisation | Appointment with a host | Valid contract + valid documents |
| Documents required | Usually ID only | ID, insurance, safety training, permits |
| Access scope | Reception or meeting area | Defined operational zones, often hazardous |
| Accompanying elements | Rarely | Workforce, equipment, vehicles |
| What ends authorisation | End of the visit | Contract end or any document expiry |
| Legal exposure | Limited | Safety liability sits with the facility |
The final row is the commercial argument. When an incident involves a contractor's worker on your site, the first question is not whether the contractor tracked their documents — it is whether your facility admitted an unqualified worker. You control the gate, so you carry the operational responsibility.
Ask for one scenario in the demo: upload a safety training certificate that expires tomorrow, advance the date by one day, then attempt to admit the worker.
Acceptable outcome: entry is refused, the reason is displayed clearly to the guard, and the event is logged. Unacceptable outcome: a warning is recorded and entry proceeds — which makes the system a documenter of the violation rather than a control against it.
In Saudi industrial facilities, planned maintenance shutdowns can multiply contractor headcount tenfold for three weeks. A system sized for the ordinary state fails during the shutdown; one sized for the shutdown looks oversized the rest of the year.
Ask specifically how the contract handles peaks. Three models exist: pricing on the peak year-round, pricing on the average with an agreed ceiling, or a base package plus seasonal add-on bundles. The third is usually right for sites with scheduled shutdowns — provided the add-on price is fixed in the original contract. Detail in the Arabic guide on contractor system pricing.
In Haseen, contractor management is a native module rather than an add-on. Each contracting company has a file holding its contracts and authorised zones, with individual worker files beneath each contract carrying IDs, insurance and training certificates — each tracked to its own expiry date. Alerts fire ahead of expiry, and access is suspended automatically when a document lapses.
Work permits route through the area owner, adding the safety officer as a mandatory step for hazardous work, and lapse automatically when any condition fails. Vehicles are registered with their drivers and plates read automatically at vehicle gates. See Haseen contractor management and the visitor system buyer's guide.
A platform that ties every contractor entry to three live conditions: a valid company contract, valid individual documents, and a work permit scoped to an area and period. Unlike a visitor system, it tracks validity continuously because a contractor's documents expire during an ongoing engagement.
By tying entry eligibility to document validity inside the system rather than a separate spreadsheet. When a date passes, eligibility lapses automatically and the attempt is refused at the gate with the reason shown to the guard. A tracking spreadsheet, however current, blocks nobody.
It must. Subcontractors are where the documentation chain breaks in most projects — the main contractor is documented, but the subcontractor's workforce enters under the main contract with no files. Correct handling registers the subcontractor as a separate entity linked to the main contract, with its own worker documents.
Work permits should be part of the same system, not a separate one. Separation is the root cause of the most common gap: a worker enters because their badge is valid while their permit expired yesterday, and nobody at the gate knows.
Operationally the facility, because it controls the gate. A contract clause requiring the contractor to track its workers' documents does not transfer that responsibility, and the only defensible evidence is a record showing the system checked and refused those who did not qualify.
On a variable unit — active contractors, registered workers, monthly active workers, or issued permits — plus sites, gates and functional modules. Ask which unit is used and how seasonal peaks are handled before comparing quotes, because those two answers move the figure more than anything else.
Prepare four numbers before requesting a quote: active contractors in an ordinary month, the number you reach at peak, sites and gates, and whether you need hazardous work permits.
Upload a certificate that expires tomorrow, advance the date, then try to admit the worker — and watch what the system does.