Why Copying Your Old Safety File Could Put Your Next Project at Risk
You've completed a project.
The client approved your safety file.
Everything worked.
So when the next project starts, it makes sense to use the previous file as a starting point.
There's nothing inherently wrong with that.
The problem starts when a previous safety file is copied and submitted without properly reviewing whether the information still applies.
A safety file should reflect the project it belongs to.
If the project changes, the documentation may need to change too.
Why copying an old safety file is so tempting
Creating and maintaining safety documentation takes time.
Contractors often have standard policies, procedures, forms, risk assessments and supporting documents that they use across multiple projects.
Reusing appropriate documentation can make sense.
It avoids unnecessarily recreating documents that genuinely remain applicable.
But there is a critical distinction between:
Reusing appropriate documents
and
copying an old safety file without reassessing it.
The first can improve efficiency.
The second can leave important project-specific risks and requirements overlooked.
Every project has its own risk profile
Even when the same contractor is performing similar work, projects are rarely identical.
Consider the differences between two construction projects.
The first might involve basic interior maintenance in an occupied building.
The second might involve:
- Working at height.
- Excavation.
- Heavy equipment.
- Multiple subcontractors.
- Public access near the work area.
- Different environmental conditions.
- Different emergency arrangements.
The hazards and controls may be substantially different.
A risk assessment created for the first project should therefore not simply be copied into the second project without reviewing whether it remains suitable.
South Africa's Occupational Health and Safety framework requires employers to identify and evaluate workplace hazards and take appropriate steps to protect people from those hazards. The specific project circumstances therefore matter when determining what controls and documentation are appropriate. (saflii.org)
A safety file can look complete and still be wrong
This is one of the biggest problems with copied safety files.
A document can contain dozens or hundreds of pages and still fail to properly address the actual project.
For example, the file might contain:
- Company policies.
- Training certificates.
- Appointment letters.
- Risk assessments.
- Method statements.
- Registers.
- Inspection records.
- Emergency procedures.
But what if the risk assessment doesn't cover one of the project's major activities?
What if the emergency procedure refers to the previous site?
What if the method statement describes work that isn't being performed?
What if the client has additional contractor requirements that aren't included?
The file may look impressive.
But documentation isn't effective simply because it is extensive.
Relevance matters.
Risk assessments should reflect the actual work
A risk assessment should help identify hazards and establish controls for the work being performed.
That means changes in the project should trigger a review.
Examples include changes to:
- Work activities.
- Equipment.
- Materials.
- Site conditions.
- Work environment.
- Number of workers.
- Subcontractors.
- Access arrangements.
- Working hours.
- Interfaces with other contractors.
If any of these change significantly, simply carrying over the old assessment may not be enough.
Client requirements can change from project to project
Another common mistake is assuming that because one client accepted a particular safety file, every client will accept the same structure.
Clients can have their own contractor management requirements.
They may specify particular documentation, forms, registers, appointments, procedures, submission formats or approval processes.
Some may also have project-specific requirements based on the nature of the work and the risks involved.
This means your safety file should be checked against the current client's requirements, not simply the requirements of the previous project.
Don't forget the small details
Copied documents often contain outdated information that is easy to miss.
Before submitting a file, check for:
Project details
- Site address.
- Project name.
- Client name.
- Project number.
- Contractor information.
- Dates.
People
- Responsible persons.
- Supervisors.
- Safety representatives.
- Emergency contacts.
- Subcontractors.
Documents
- Expired certificates.
- Old medical records where applicable.
- Previous project references.
- Outdated appointments.
- Superseded procedures.
One old project name buried in a document might seem minor.
But it can signal that the file wasn't properly reviewed.
What can you reuse?
You don't necessarily need to start from scratch for every project.
Some documents may be organisation-wide and remain relevant across projects.
Examples can include:
- Company OHS policies.
- General procedures.
- Standard forms.
- Company information.
- Competency documentation.
- Standard appointment templates.
- Lessons learned from previous projects.
The key is to determine whether each document remains current, appropriate and applicable.
A useful way to think about it is:
Your previous safety file is a resource, not a finished safety file for the next project.
A practical safety file review before submission
Before submitting your next file, work through these questions.
1. What exactly are we doing?
List the activities that will actually take place on the project.
2. What are the significant hazards?
Identify the hazards associated with those activities and the site environment.
3. Are the controls appropriate?
Check that the risk assessments and procedures address the actual hazards.
4. Who is involved?
Make sure employees, supervisors, subcontractors and other relevant parties are properly accounted for.
5. What does the client require?
Review the current client's specifications and contractor requirements.
6. What has changed since the previous project?
This is the question most likely to expose copied information.
If the answer is "nothing," take another look.
There is usually something that has changed.
What about generic safety files?
A generic safety file can have a legitimate place in a company's safety management system, particularly as a structured foundation containing company-level information and standard documentation.
The issue is when a generic or previous-project file is treated as though it automatically covers the circumstances of a specific project.
The more project-specific the hazards and requirements are, the more important it becomes to ensure the documentation reflects those circumstances.
The objective should not simply be to move from "generic" to "site-specific" as a box-ticking exercise.
The objective is to have documentation that accurately supports the way the work will actually be managed.
The real value of your previous safety file
Your previous safety file shouldn't be thrown away.
It can be extremely useful.
It can show:
- What worked previously.
- What documents were required.
- What problems were encountered.
- What controls were effective.
- What lessons were learned.
- What could be improved.
That information can make your next project safer and more efficient.
But the new project still needs its own review.
Learn from the old file. Don't let the old file define the new project.
Before you submit, ask one final question
Take your completed safety file and imagine that the client knows nothing about your previous project.
Then ask:
"Does this file clearly demonstrate how we intend to manage the health and safety risks of this project?"
If the answer is yes, you're looking at the file in the right way.
If the answer is:
"Well, most of it is from our previous project..."
that's probably a sign that it needs another review.
A good safety file isn't the one with the most pages.
It is the one that is current, relevant, properly maintained and aligned with the work actually being performed.