The rule: accept the result, not the description of work
The most common acceptance mistake is signing the protocol on the basis of a list of completed activities. A good practice is to accept a result that the OHS manager can check personally: a working module, an issued permit, a PDF printout, a passed test.
In the three-stage variant each month ends with such a result: a working training module and an instance with the map, then an issued and accepted test permit with documentation, and finally tests on the live traffic of external contractors and production go-live.
Practice 1: accept stage one by walking through the user path
In stage one of the shortened variant a separate server, accounts and permissions are created, teams responsible for areas are set up, and about 500 locations are named according to the plant's convention. Acceptance consists of logging in with several roles and checking that each person sees their own scope.
Walk the path from the end: randomly select 10 locations from the list and check whether their names match the naming used on the shop floor. A mistake in a location name later returns in permits and printouts.
Scope of stages in the 6-week variant
Practice 2: accept stage two through a test permit and test training
Acceptance of stage two of the 6-week variant is a passed test training and an issued test permit with a PDF printout. In this stage up to 80 risks and hazards with protective measures are prepared, together with 2 printout templates.
Issue a permit from start to finish: the application, approvals along the path, the printout, closing. Assess the printout through the eyes of the person who will keep it at the workstation: does it clearly show the hazards, the protective measures and the people responsible.
Practice 3: final acceptance through the first contractors at the gatehouse
The final acceptance of the 6-week variant is production go-live and the first external contractors admitted through the system at the gatehouses, after training of administrators, managers and employees.
Good practice: choose two or three companies with different profiles for the first day, for example a service company and a transport company, and observe their passage through the gate together with the guards.
What to record in the protocol
Record in the protocol the result, the way it was checked, the date and the people accepting it. This way the protocol is evidence for the auditor, not only a signature.
Practice 4: record remarks during the rollout, not after acceptance
Collect remarks on the stage during the weekly huddles and add them to the remarks register. At acceptance you close only those that have been fixed, and the others receive a deadline in the next stage.
This approach reduces the risk that the final acceptance turns into a list of objections that the team does not have time to close before go-live.
Checklist
Video
Frequently asked questions
What is the result of stage two?
A passed test training and an issued test permit with a PDF printout, with up to 80 risks and hazards with protective measures and 2 printout templates.
Who should accept a stage?
The person responsible for the process on the plant side, usually the OHS manager, together with the system administrator of the given site.
How do you avoid corrections after go-live?
Collect remarks on an ongoing basis and accept results checked on screen and on the printout.
Let us agree the stage results
Before the start we will write down with you the result of each stage and the way it is checked.
Let's talk