How to Build Training Evidence Packs for Principal Contractors

Make the pack answer a defined request

Ask for the project, work package, named roles, expected file format and submission date. Requirements differ between principal contractors and sites, so last month’s pack may contain too much, too little or stale evidence. Record an as-at date and version so recipients know what they are reviewing.

A practical pack structure

1. Cover sheet with subcontractor, project, package and contact.
2. Crew list showing role and employer.
3. Matrix extract limited to assigned project requirements.
4. Certificate index matching each file to worker and requirement.
5. Clearly named evidence files.
6. Exceptions log for missing, booked or under-review items.
7. Submission record and later revision history.

Quality and privacy checks

• Every date traces to readable evidence
• Names and card categories agree across files
• Expired items are not presented as current
• No fake dates are used for non-expiring records
• Unrelated medical, identity or address data is removed where appropriate
• Share through an approved secure route
• Retain according to your data policy

Freeze the submitted export rather than allowing a live link to change silently. If the crew changes, issue a clear revision. The live matrix remains the operating source, while the pack records what was represented at a point in time.

Manage revisions during mobilisation

Crew lists change after submission, particularly where agencies and specialist subcontractors are involved. Set a cut-off and revision convention, for example replacing the entire named-worker extract with a clearly numbered issue rather than emailing loose certificates. State what changed and withdraw superseded files from the active shared location. Confirm that the site team received the revision before the substitute travels. After mobilisation, reconcile who actually attended with the submitted pack; this catches undocumented substitutions and creates a better starting point for future works. Do not retain duplicate identity documents merely because they arrived with a certificate bundle.

Agree whether the principal contractor wants card numbers, certificate copies or verified status, and provide no more personal information than necessary. Use a consistent filename such as surname, requirement and expiry, avoiding special categories of data in names. If a portal creates its own record, note the upload timestamp and receipt. At project close, move the final accepted issue into the contract record and remove temporary sharing links according to policy.

Acceptance remains with the recipient

FieldClear can organise assigned requirements and evidence, but it cannot guarantee that a principal contractor will accept a worker or pack. It does not verify competence or determine legal requirements. Follow the project process and obtain data-protection or legal advice where needed.