When Does a Machine Retrofit Need a Safety Assessment?
Involve a qualified assessor early when a machine retrofit changes, or could change, hazards, operating modes or protective functions. Before approving the design, agree what equipment and activities the assessment covers, what existing evidence is usable and who will validate the finished change. Establish machine retrofit safety assessment requirements for the installation with that assessor, including the applicable local requirements.
Last reviewed: October 2026
What changes should prompt an early safety assessment?
Use the following as planning triggers. They help decide what to discuss with an assessor; they are not a legal classification of the modification.
| Proposed change | Questions to resolve with the assessor |
|---|---|
| Replace a controller or rewrite its program | Which protective functions, permissives and restart conditions depend on the existing logic? |
| Change a drive, motor or transmission | What needs reviewing about motion, stopping behaviour and stored energy? |
| Add automatic loading or connect another machine | Where could people enter, and how should connected equipment stop and restart? |
| Add setup, cleaning or maintenance modes | What access is needed, what movement is permitted and which protections apply? |
| Alter guards, interlocks or emergency stops | What function must each device perform, and how will that function be validated? |
| Add remote commands or automatic recovery | Who can initiate movement, from where and under what conditions? |
Describe the intended behaviour before choosing replacement hardware. “Replace the obsolete controller” is a purchasing description. It does not define the machine's required protective behaviour.
Ask operators and maintenance staff to explain normal work, fault recovery, cleaning and difficult interventions. Include reported workarounds as conditions to investigate.
Where should the modification boundary sit?
Draw a boundary around the proposed work, then review its interfaces with a qualified assessor. Start with the machine, but explicitly consider connected conveyors, shared access, upstream and downstream commands, and common energy supplies.
Record:
- The equipment, software, wiring and mechanical parts being changed.
- The equipment being retained and the evidence supporting its continued use.
- The interfaces that cross the boundary, including stop, start, reset and mode signals.
- The people and activities included, from production to maintenance.
- The assumptions and exclusions that still need confirmation.
The boundary is a review decision, not simply the edge of the purchase order. Ask the assessor whether the proposed scope includes everything needed to evaluate the changed behaviour.
For an illustrative example, consider adding automatic discharge to a standalone machine. Review the discharge mechanism together with access between the machines, transfer commands, blockage clearing and restart after interruption. Record who owns each interface.
Which existing documents should you collect?
Request the available records before design starts. Give the assessor a document register that distinguishes current records, superseded records and missing information.
Useful inputs to request include:
- Previous risk assessments and records of earlier modifications.
- Electrical, mechanical and pneumatic or hydraulic drawings.
- Descriptions of protective functions and their intended behaviour.
- Controller programs, drive settings and configuration records.
- Operating, cleaning, isolation and maintenance instructions.
- Previous test reports, validation records and unresolved findings.
- Manufacturer instructions for retained and replacement equipment.
Treat the installed machine and its records as separate things to check. Ask the project team to confirm which drawings and configurations describe the equipment actually present.
Where evidence is missing, agree how to establish it through inspection, tracing, measurement or testing. Label assumptions clearly and assign someone to resolve them. Do not convert an undocumented assumption into an accepted design input.
How should protective functions be specified?
With the qualified assessor, write down what each affected protective function must achieve. Keep descriptions specific enough to support design review and testing.
For each function, ask:
- What event or condition demands a response?
- Which hazardous movement or energy must be addressed?
- What state should the equipment reach?
- What conditions must be met before reset or restart?
- How should faults, loss of power and communication interruptions be handled?
- What evidence will demonstrate the required behaviour?
Agree any necessary performance criteria and acceptance limits before implementation. Have the assessor identify the assessment methods and technical references appropriate to the machine and its location.
Keep these requirements in the functional design specification, with clear references to the assessment and test plan. Avoid relying on informal instructions such as “keep the existing safety logic”.
Who should own design, validation and release?
Name the responsibilities before work begins. Ask the assessor to identify the competence and independence needed for the assessment and validation activities under the applicable requirements.
| Activity | Responsibility to agree |
|---|---|
| Define machine use and operating conditions | Who supplies and confirms the plant's intended use, access needs and maintenance activities? |
| Assess the proposed modification | Who evaluates hazards, reviews protective measures and records unresolved issues? |
| Design and implement the change | Who owns the drawings, program, settings and interface requirements? |
| Validate affected protective functions | Who plans the tests, performs them and reviews the evidence? |
| Authorise return to production | Who checks the agreed release conditions and accepts the handover? |
Specify deliverables as well as names. A purchase order saying “safety included” leaves too much undefined.
Separate routine commissioning checks from the evidence agreed for validation. Ask what each test proves, which requirement it addresses and what result would fail it. Define how failed tests and subsequent changes will be handled.
What should happen before the shutdown?
Set a design review point before installation. Bring together the plant representative, integrator, relevant equipment suppliers and qualified assessor to review the scope and open decisions.
Use this readiness checklist:
- The modification boundary and intended operating modes are documented.
- Existing records have been reviewed, with gaps assigned for resolution.
- Affected protective functions have written requirements.
- Design review actions have clear owners.
- Validation procedures and acceptance criteria are agreed.
- Test access, equipment and competent personnel are scheduled.
- Failed tests, incomplete work and restart decisions have an agreed process.
- Handover documents and operating instructions have named owners.
Build this work into the shutdown retrofit plan. Reserve time for resolving findings and repeating affected tests. Agree what happens if the machine cannot meet the release conditions within the shutdown window.
Which local requirements need checking?
Ask the qualified assessor to identify the applicable local requirements for the machine, workplace and proposed modification. Request the current official sources and a written explanation of how they apply.
Questions to resolve include whether the work changes any responsibilities for the machine, whether particular assessments or inspections are required, and what records must be retained. Also identify any requirements attached to the site's operating permissions or contractual arrangements.
Do not use this article to determine a legal classification or declare conformity. Confirm the current position with the relevant authority or appropriately qualified local adviser. A completed retrofit, assessment report or successful test should not be described as certification without a specific, supported basis.
What common mistakes should you avoid?
Starting the assessment after the design is fixed. Schedule assessor involvement while layout, access and operating-mode decisions are still open.
Assuming unchanged hardware means unchanged behaviour. Include software, parameters and interfaces in the scope review.
Treating old paperwork as current evidence. Verify its relationship to the installed machine and record discrepancies.
Leaving validation to “the commissioning team”. Name the responsible people, required evidence and acceptance criteria.
Testing only normal production. Agree tests for the affected setup, recovery, cleaning and maintenance conditions, together with relevant fault conditions.
Releasing the machine with unresolved findings. Define release conditions in advance and record how each is satisfied.
Does every replacement need the same assessment scope?
Start with a documented review of the proposed replacement and its effects. Ask a qualified assessor to determine the appropriate scope; do not infer it from the component's appearance or purchasing description.
For a proposed like-for-like replacement, check the exact specification, configuration, installation conditions and effect on protective functions. Record the basis for any decision to limit further assessment.
Can an integrator handle the safety work?
Ask what work the integrator will perform, who the qualified assessor is and who will validate the result. Include those responsibilities and deliverables in the agreed scope.
Discuss the assessment boundary and documentation available when making the initial project enquiry.
What should the handover contain?
Agree a handover pack covering the modification boundary, assessment findings, updated drawings and configurations, validation evidence, operating instructions and maintenance information.
Record the basis for release, any conditions of use and who accepted the handover. Keep the evidence traceable to the machine and configuration being returned to service.
For how safety controllers differ from standard ones, see safety PLC vs standard PLC.