From document-based approval to access control
When document compliance has a consequence for access control
Contractor document management does not have to stop at the approval of a document. Instead, it can also connect access control and compliance.
In fact, in certain industrial settings, the outcome of the document review is needed to make operational decisions. For example: is a company approved, does a worker meet the applicable requirements, and do they meet the conditions set for entering certain facilities?
With this principle in mind, AISP implemented a project in which the document management platform is integrated with the client’s physical access control system.
In other words, the goal was not only to digitalise contractor approval. It was also to ensure that the outcome of that process could be used by the system that controls workers entering and leaving the facilities.
The challenge
The client receives workers from several contractor companies.
Before they can enter the facilities, these companies and their workers must meet a set of predefined requirements.
As a result, several layers of information have to be managed:
- company documentation;
- worker documentation;
- applicable requirements;
- document expiry dates;
- review and approval status;
- worker identification;
- authorisation to access the facilities.
If document management and access control worked as separate processes, information would have to be passed manually between the two systems.
Besides the administrative effort, this separation would create a significant risk: the access system might not immediately reflect a change in document compliance status.
The project was therefore designed to connect the two processes.
A central platform for document-based approval
The document management platform acts as the central point for managing contractor information.
First, companies upload the required documentation, and the applicable requirements are reviewed during the approval process.
Next, the AISP document management team follows the process. It reviews the documentation against the client’s criteria and keeps the compliance status of each entity up to date.
In this way, the platform turns a scattered set of documents into structured information on the compliance status of companies and workers.
However, in this project, that information does not stay inside the platform.
From document compliance to the access control system
The document management platform communicates via API with the system the client uses to physically control entries to and exits from the facilities.
As a result, this integration gives the access control system the information it needs on each worker’s document compliance status.
In simple terms, the process has four steps:
1. Document submission
The contractor company uploads the required documentation to the platform.
2. Review and approval
The team reviews the documentation against the requirements set for the process.
3. Communication between systems
The integration then passes the resulting document management status to the access control system.
4. Entry control
When the worker presents their card at the reader, the system has the information it needs to apply the client’s entry rules.
In this way, the document decision becomes part of the operational process for accessing the facilities.
Document validity is no longer just a date
One of the most important consequences of this architecture is that expiry date control can be linked to operations.
For example, a document may be valid today and expire later.
Similarly, a worker’s compliance status can change when a requirement is no longer met.
When document information is integrated with other systems, these changes no longer matter only to the team that runs the platform.
On the contrary, they can have an operational consequence, according to the rules set by the organisation.
It is this link that turns document management into a tool for operational control.
Access control and compliance: Different systems, one process
The project did not require replacing the existing access control system.
Instead, the solution integrated technologies with different functions.
The document management platform handles documentation, requirements, review and approval.
Meanwhile, the access control system remains responsible for physically managing entries and exits.
In turn, the API provides the interoperability needed between the two.
This architecture keeps the organisation’s existing specialist systems in place and uses document information where it is needed.
It is also an example of how a document management platform can integrate with the client’s technology ecosystem, rather than work as an isolated application.
AISP’s role
In this type of project, AISP’s work goes beyond providing technology.
The service combines document management and HSE expertise with platform implementation, configuration and operation.
In this project, AISP runs the document review and approval process against the defined requirements. As a result, the information used by the integration matches the document status actually verified.
This is particularly important, because a technology integration is only as reliable as the information that feeds it.
Technology automates the flow of information. However, the quality of the document management process determines the quality of that information.
From document management to operational document management
This project shows an important shift in how document management platforms are used.
The goal is no longer just:
receive → review → approve → archive.
Instead, there is a broader chain:
requirement → document → review → compliance → integration → operational authorisation.
Documentation is still the evidence.
However, its value lies in the information it produces and in the ability to use that information in the processes that depend on it.
In this case, that information is used for access control, based on document compliance.
In other contexts, the same architecture can support accreditation, training, identification, Permit-to-Work, equipment management or other operational systems.
This link between documentation, compliance and operations is the basis of an operational document management approach.
Result
The integration created a process in which document-based approval and access control no longer work as two separate worlds.
The organisation now has a consistent chain that connects contractor requirements, the documentation submitted, its review and the use of that review in the facility access process.
In short, rather than simply digitalising documents, the project shows how document information can be built into operations.
Because document management gains value when compliance is not just recorded, but can actually be used.
See also: From document compliance to physical access and Access control based on document criteria.
Finally, for information on legal occupational health and safety obligations, visit the ACT, the Portuguese Working Conditions Authority.