Collect the worker file
Worker identity, employer, assignment, country, site, and role context attached before checks begin.
01That is chain liability. And from 2026, Belgian law makes it explicit.
02Most main contractors on complex infrastructure projects have verified less than 10% of their active workforce at any given time. The rest rely on subcontractor assurances, email confirmations, and the assumption that someone further down the chain checked.
03When an auditor arrives or an incident occurs, that assumption becomes your exposure.

Every worker across every contractor tier has a verified file before they reach your site. You see compliance status across your full project, live. When a document expires, the system flags it. When a worker is blocked, you see why. When an audit comes, the evidence is already there, timestamped, exportable, complete.
You don't need to trust the chain. You can see it.
The mechanism is the same for every team around the access decision. The context, evidence, risk, and reason stay attached to one worker file.
Worker identity, employer, assignment, country, site, and role context attached before checks begin.
Dockt checks what evidence is needed for the project, role, dates, and access decision.
Teams see what's ready, what needs review, and what blocks access until corrected.
Source documents, timestamps, reviewer actions, and status changes stay connected to the decision.
Walk us through your current project setup. We'll show you what Dockt sees that you currently don't.