The Pre-Mobilisation File: Getting a Small Trade Team Through Site Induction Cleanly

Site induction is not the place to discover that the public liability certificate expired last month. For smaller UK trade firms, pre-start paperwork is often assembled in the van the night before mobilisation. Main contractors read the same paperwork differently. They treat it as evidence of management. A missing document suggests a missing system; a current, indexed pack suggests a firm that can be trusted with the programme.

The pre-mobilisation file is therefore not an administrative chore. It is a commercial instrument. It decides whether the team starts on the agreed date, whether the first day is productive, and whether the main contractor forms the view that this subcontractor will be easy to administer or a persistent exception.

The pack as a commercial instrument

A clean pack does three things. It proves that the firm is insured, competent and compliant. It gives the main contractor a single point of reference rather than a trail of email attachments. And it protects the trade firm's margin by removing the unbilled time that follows a failed induction: phone calls, reissued certificates, waiting for a supervisor to approve a late RAMS.

That is why the pack should be controlled before the first boots hit the ground. It should not be a folder of whatever happened to be on the desktop. It should be a short, indexed set of current documents with a named owner inside the business.

The core schedule

Most main contractors will ask for the same categories of evidence. The precise list varies by project, but the following schedule covers the common requirements for smaller trade firms.

Insurance certificates

Provide current public liability insurance and, where the firm employs anyone, employers' liability insurance. Professional indemnity may also be required for design or advisory elements. The certificate should show the policy number, the limits of indemnity, the insurer and the expiry date. Do not send a schedule that obscures the expiry date. If the policy renews mid-project, note the renewal date on the index page and diary the replacement certificate.

Risk assessments and method statements

RAMS should be project-specific. A generic method statement copied from another job is one of the quickest ways to lose credibility at induction. The document should identify the tasks, the significant hazards, the control measures, the PPE requirements and the emergency arrangements. It should be signed and dated. Where the work changes, the RAMS should change with it.

CIS details

For subcontract work under the Construction Industry Scheme, provide the firm's HMRC registration details, Unique Taxpayer Reference and verification status. If the firm is paid gross, the main contractor will want to see evidence. If it is paid net, that should be clear before the first invoice. Ambiguity here becomes a cashflow problem later.

Waste carrier registration

Where the firm removes waste from site, the main contractor will usually ask for waste carrier registration. In England and Wales this is administered by the Environment Agency; Scotland and Northern Ireland have separate regulators. Check whether the project requires upper tier registration and confirm the registration number and expiry date. Also confirm how waste transfer notes will be handled, because the licence alone does not discharge the duty of care.

Emergency contacts

A single emergency contact sheet should name the site supervisor, the first aider, the firm's responsible person and an out-of-hours number. These details are often wrong because they were copied from an old project. Check them before sending. The sheet should also state the escalation route for an accident, a near miss or a site emergency.

Supporting documents

Depending on the project, the pack may also need a health and safety policy, competence cards, plant inspection records, COSHH assessments or evidence of training. Include only what is required, but include it properly.

The index page

The most useful part of the pack is a one-page index. It should list each document, its version, its date, its expiry date and the person responsible for renewing it. The index turns a loose collection of attachments into a controlled file. It also gives the main contractor's document controller a clear route through the pack.

Use a consistent file name and issue the pack as a single PDF where possible. Avoid sending editable files unless they are specifically requested. An editable RAMS invites comments that may never be resolved; a controlled PDF with a clear version number is easier to administer.

Control before arrival

Agree a cut-off date with the main contractor and work backwards. Five working days before mobilisation is a sensible internal target for smaller firms, but the contract or pre-start meeting may require more. Send the pack through the agreed portal or named contact, and record that it was received. Do not assume that sending it is the same as it being accepted.

Keep a master copy in the office. When a certificate renews or a RAMS is revised, update the master and reissue the affected page with a new version number. Do not let the master and the site copy drift apart.

Common failure points

The same problems recur. Insurance certificates expire without anyone checking. RAMS are generic and unsigned. CIS status is assumed rather than verified. Waste carrier registration is lower tier when the project requires upper tier. Emergency contacts are out of date. The pack is sent as five separate emails with no index.

Each of these is avoidable. None requires a large administration system. It requires a named owner, a checklist and a diary.

A short sequence

Read the pre-start requirements and list every document the main contractor has asked for. Assign one person to own the pack. Assemble the master file and check every date. Write the index page. Send the pack as a controlled PDF and record receipt. Diary the renewals. Review the pack after induction and correct anything the main contractor queried.

The margin point

A delayed start is rarely recovered. The labour is still booked, the programme has moved, and the main contractor remembers which subcontractor caused the hold-up. A clean pre-mobilisation file is a small piece of work done at the right time. It gets the team onto site without scrambling, and it tells the client that the firm understands that paperwork is part of the job.

P.F. Lynch & Co. works with smaller UK trade firms on contracts, frameworks and the commercial controls that sit around them. A pre-mobilisation file is a simple place to start.