Accreditation evidence pack template for UK contractors

An accreditation evidence pack should let an assessor find the specific current document, record or real job example that answers each question for the applicant's work and dutyholder role. It is more useful than a folder named “health and safety” containing hundreds of unrelated PDFs. Use the copyable index and gap sheet below to show what exists, what it proves, who reviewed it and what must be fixed before submission.

This is a supplier-side health and safety prequalification pack framework, especially for SSIP member schemes and construction work. It is not a scheme's official application form and does not promise approval. SSIP's Core Criteria were updated on 4 September 2026 and describe evidence areas and role-specific additions. A chosen scheme can ask its own questions or additional categories, and an individual buyer can still need project-specific scrutiny. Check the current scheme portal and applicant role before filling this pack. The existing Complys compliance document register article owns the general all-document inventory; this page is the evidence-to-assessor-question submission workflow.

Pack cover sheet — copy and complete

Avoid choosing a role merely because it looks attractive to buyers. Principal contractor and principal designer evidence requirements differ from those for an ordinary contractor. SSIP's criteria contain specific additional checks for those CDM roles. A new business that has not completed a project should not fabricate a past site example; ask the assessor how it accepts a proportionate demonstration of capability. The core criteria expressly discuss a sensible approach for start-ups.

Table A: question-to-evidence index

Copy one row for each *actual scheme question*, not just the suggested categories below.

The “page/section” column matters: a generic link to a 70-page policy makes assessors hunt. The “work type” column prevents a roofing applicant from submitting only an office-fire assessment. If one file answers several questions, reference its relevant section each time; do not duplicate the file under different names and risk submitting inconsistent versions. Use a stable file ID rather than a personal desktop path.

Table B: evidence categories to map

The current SSIP Core Criteria provide a useful starting map. The exact evidence needed depends on organisation size, work category, role and scheme.

The table is a mapping aid, not a claim that every document is mandatory for every applicant. SSIP asks for examples of site or project-specific risk assessments and safe systems for selected work categories, often within the previous 12 months, and notes a proportionate approach for very small firms and start-ups. It also distinguishes advisory questions from mandatory criteria; do not mislabel a wellbeing or fleet-scheme item as universally required. Confirm the live criteria on submission day.

Table C: file and gap control

Use gap for a missing real practice, not merely a missing PDF. If training was never provided, an empty matrix does not solve the gap. If a risk assessment exists only as a generic template, get a competent person to assess the actual work and produce a real example. Do not create retroactive signatures or pretend a policy was in force when it was not. If an accident history or enforcement question is uncomfortable, answer accurately and show corrective action. SSIP's criteria ask for specific accident and enforcement lookback information; confirm the current application wording and reporting period rather than relying on a generic checklist.

Build and check the submission

1. Confirm scope. Record scheme, current question set, work categories, business size and role. Ask whether mutual recognition or a current SSIP assessment can avoid duplicate stage-one work. SSIP explains its mutual-recognition approach, but the client may still need project-specific checks.
2. Import only current evidence. Choose the latest approved policy and real work examples. Compare company names, dates, job type and expiry; resolve contradictions across files.
3. Map evidence to questions. Fill Table A with exact file sections and Table C with version and shareability. Test the link as an assessor with only the intended permissions.
4. Close operational gaps. Assign an owner, resource and deadline; implement the underlying control before calling a document complete. Use the scheme's “not applicable” option only with a reason that matches the work.
5. Check personal and commercial information. Redact or restrict worker medical data, identifiers, client details and trade secrets where appropriate without making evidence unusable. Obtain client permission where required.
6. Quality-review and submit. A competent reviewer checks the responses against the current scheme questions. Record what was actually sent, when, to whom, and the scheme's receipt/reference.
7. Track assessor queries. Record the precise query, owner, evidence revision and response date. Keep the submitted version; do not silently overwrite it after a question arrives.

Assessor-query tracker

For a step-by-step response to assessor queries, the separate Complys SSIP query guide may be relevant if its route is verified at integration. Keep this template focused on the pack and its evidence trail.

Example: small electrical contractor

A six-person electrical firm applies for an SSIP assessment as a contractor, not a principal designer. It has a current signed policy, training records for actual workers and recent electrical job risk assessments. The first pack check finds that its sample method statement is a generic file with no site conditions and that the training matrix lists a worker whose card expired. The pack owner does not hide those gaps or upload a blank replacement. The supervisor completes a competent task-specific assessment for a real upcoming job, checks the worker's qualification and temporarily changes assignment until the competence gap is resolved. Table A points to the final approved example and the training evidence. The pack is now a map to real controls. It still needs the chosen assessor's current rules and may need other evidence.

What an accreditation can and cannot prove

An assessed health and safety standard supports organisational capability at the prequalification stage. It is not a licence to start every job regardless of its hazards. SSIP's HSE-view page says a client still needs project-specific scrutiny of a supplier's skills, track record and organisational capability before construction work starts, and that third-party prequalification is not itself a universal legal requirement. Do not present a badge as a guarantee of safety or contract award.

The contractor also needs to maintain the underlying practices after approval. Keep policy review, training, RAMS, inspections, incidents and subcontractor evidence current. If a scheme asks for renewal evidence, reuse the controlled index but review each answer afresh. A previously accepted PDF can become stale when the company changes trade, people, equipment or role.

Next step

Take the first five questions in your actual application and complete Table A with a file that a reviewer can open and understand. If any answer points to a generic or contradictory document, record the gap and fix the real process. For an implementation discussion, use the verified Complys home and ask to see the current prequalification workflow. The manifest's proposed /contractor-prequalification-software route and features require verification. This template does not claim Complys creates an accreditation, guarantees an assessment outcome or verifies every scheme criterion automatically.

Source, owner, link, product and writer-side QA

Terminal writer-side disposition: READY.