Two sources of requirements
The group standard describes what the plant is to do and report, while the local requirements concern Polish regulations, the workforce and the contractors. The first set is usually in the head office language, the second in Polish. The coordinator's task is to bring them together in one table: requirement, source, system function, status.
InnerWeb is an independent system that complements the client's existing systems, such as access control, time and attendance, HR and ERP. As a result, the conversation with the head office concerns only the OHS scope, not an exchange of global systems.
Stages of agreement
Below is the sequence that works best at the pre-rollout stage.
- Collect the group requirements in the original language and in a working translation
- Compare them with the local requirements in one table
- Assign a system function to each requirement
- Mark the gaps: what has no equivalent in the system
- Decide what goes into the pilot and what is an option for later
- Approval of the table by the OHS manager, the IT department and the head office
Gaps are not a failure
A missing system function should be recorded explicitly, together with a decision: a workaround, an option on request, or dropping the requirement. A silent gap comes out at the group's audit.
Sample status of requirements in the compliance table
Implementation pitfalls
The first pitfall is the assumption that everything written in English in the standard works in English in the system. The interface and documents work in six languages, and every interface change in the project is released only with translations in all six. However, the dictionaries have an English column in only four cases, so local names in the others must be entered deliberately.
The second pitfall is label overrides that cover translations. The third is the lack of an owner of changes: who approves a new name after launch if the head office changes the standard.
The fourth is the contractors. The group standard rarely describes how a Polish plant should handle external companies with a foreign workforce, yet they are the ones who need documents in their language.
Role of the IT department and the head office
The IT department is responsible for access and accounts, the head office for accepting the standard, and the coordinator for the compliance table. If one of these roles is empty, the table does not close and the pilot drags on.
Record also who reports changes after launch. Without this, the first change to a permit template requires re-agreeing the whole scope.
Criterion for closing the pre-rollout stage
The stage can be considered closed when the compliance table has a status in every row and the gaps have decisions. Only then is the pilot scope stable and can it be priced.
Sample compliance table
The table can have five columns: requirement number, wording, source (group standard or local regulation), system function and status. Three status values are enough: covered, workaround, option for later. Simple statuses make the head office's acceptance easier.
For each requirement with a workaround, record who performs it and how it is documented. A workaround without an owner is the most frequent source of comments from the group auditor.
The table is a living document. After each change to the group standard, the coordinator updates the rows and informs the owners of the scope.
Video
Frequently asked questions
Must the group standard be implemented in full in the pilot?
No. The pilot covers the scope agreed in the compliance table, and the rest is an option for later.
Who approves the compliance table?
The OHS manager, the IT department and the group's head office, each within their own scope.
What about a requirement with no equivalent in the system?
Record it as a gap with a decision: a workaround, an option, or dropping it.
Build the compliance table
We will help you match the group requirements with the system functions before the pilot.
Let's talk