Contractor safety file checklist before site induction
Use a checklist to find the missing conversation before the deadline. The required documents depend on the project, but the preparation sequence is consistent: define the scope, assign owners, connect controls to the work, and preserve evidence.
Confirm the project boundary first
Record the client, site address, work description, start and end dates, principal contractor, responsible supervisor, subcontractors, equipment, interfaces, and known hazards. Ask for the client or principal-contractor index, submission deadline, induction requirements, and document naming convention.
A generic safety-file list is only a starting point. The project requirements control what must be prepared, and the work sequence controls which risk assessments, method statements, appointments, inspections, and records are relevant. If the scope changes, record the change and review the file.
Assign ownership for every document
Create a register with the document name, project, owner, version, issue date, review date, expiry date where relevant, and storage location. Include company records, appointments, competency and training evidence, medical or fitness records where required, insurance, equipment records, and site-specific controls.
A document without an owner becomes stale quickly. Name the person who obtains it, the person who reviews it, and the person who approves or submits it. Keep the responsibility clear when a subcontractor supplies part of the evidence.
Prepare company and people records carefully
Check which registrations, insurance documents, appointments, competency records, training, induction, identification, and health records the project requires. Use the client list and current legal requirements as the controlling sources, not a copied online checklist.
Minimise the sharing of personal information. Medical, identity, contact, and incident records should go only to an identified recipient through an approved process. Do not upload sensitive records to an unverified referral service because a form says they are needed.
Connect documents to the actual work
Prepare risk assessments, method statements, safe-work procedures, emergency arrangements, permits, inspection registers, equipment records, and toolbox or briefing records for the work package. The document should describe the location, task sequence, people, materials, tools, interfaces, and conditions that can change risk.
A copied procedure may contain the correct headings while describing a different job. Review the controls with the people doing the work and make sure the induction, supervision, inspection, and corrective-action records show how the controls are implemented.
Check dates, signatures, and versions
Before submission, verify the project name and address, contractor names, dates, signatures, approval fields, version numbers, certificates, expiry dates, document links, and index. Open a sample of the files; an index can look complete while a PDF contains a blank template or a different site address.
If a document is not applicable, record the reason and the person who made that decision. A visible explanation is more useful than an unexplained gap that leaves the reviewer guessing.
Record the submission and feedback
Keep the submitted package, transfer record, request for changes, approval, rejection, and resubmission. Name the version that was sent and record the date and recipient. Do not overwrite the only copy of a prior submission.
When the client or principal contractor asks for a change, identify the affected document, assess whether the work or risk changed, obtain the required approval, and communicate the change to the crew. The file should show a chain from request to action.
Do not buy a file as a guarantee
A template or digital product can help with structure, document control, and reminders. It cannot know the site, replace competent review, satisfy every client requirement, or prove that a worker understood and followed a control.
A MySafetyFile product link is separate from any promise of legal, client, or inspector acceptance. Read the current product scope and terms, then have the responsible project person review the result.
Use the checklist as a conversation tool
Before the induction, ask four questions: What work is actually being done? Which hazards and controls apply? Who owns each document and decision? What evidence will show that the control was implemented? If an answer is unclear, the file is not finished just because the folder has many documents.
The strongest file is understandable to the team using it. It lets a project identify the current instruction, find the evidence, explain a change, and hand the record to the next responsible person without relying on memory.
Prepare for the handover
Agree who receives the final controlled package, which records remain with the contractor or principal contractor, how long records are retained, and how a later reviewer can identify the current version. Keep a recovery copy and restrict editing access.
A handover record closes the loop between preparation and use. It should show what was submitted, what was accepted or changed, and who is responsible for keeping the live file current during the work.