Guide · Updated 2026-09-21

Best Way to Store CSCS Card Photos

Store CSCS card photos so they are readable, tied to the right person and requirement, and accessible only to people who need them for mobilisation or audit—not scattered across WhatsApp and personal phones.

Treat the image as controlled evidence

A CSCS (or affiliated) card image supports identity and expiry checks. Capture the full card face, avoid cropped corners, and confirm the name matches photo ID before filing. Prefer a system that attaches the file to the worker’s CSCS requirement rather than a generic shared folder named “cards”. When the card renews, replace the evidence and archive or clearly supersede the old image so assessors are not shown two conflicting faces.

Storage checklist

  • Readable image or PDF of the full card face
  • Filename including worker name (or ID) and document type
  • Link from the matrix CSCS requirement to that file
  • Card number and expiry typed as data, not only embedded in pixels
  • Access limited to training admins, relevant supervisors and audit roles
  • Retention aligned to your company policy and client contract needs
  • Process for deleting or restricting access when someone leaves

Workflow from capture to matrix

Stop evidence living only on the operative’s phone. Move it into the controlled store the same day.

  1. Capture or receive the card image at onboarding or renewal.
  2. Check legibility, name match and card type against the role assignment.
  3. Upload to the worker’s CSCS evidence field (or your controlled library with a deep link).
  4. Enter expiry and card type as structured fields.
  5. Restrict folder or system permissions to need-to-know roles.
  6. On leavers or card replacement, follow your retention and supersede process.

Privacy and operational caution (not legal advice)

Card photos are personal data. Minimise who can browse entire libraries, avoid posting images into open team chats, and do not email zip files of every operative’s cards to broad distribution lists when a named extract would do. Agree retention periods with whoever owns your privacy and information-security arrangements; this guide does not interpret UK GDPR or client data-processing terms. If a client portal requires uploads, use their controlled channel and keep your internal master copy consistent.

Sample-check storage monthly: open five random CSCS attachments and confirm they still match the matrix dates. Agency packs should be re-filed under named workers, not left as a single supplier PDF that cannot be filtered. Affiliated scheme cards need accurate scheme labels so a green “CSCS” cell does not misdescribe the evidence.

What FieldClear does with evidence

FieldClear lets you attach evidence to assigned requirements and track expiry. It does not grant site access, verify card authenticity with the scheme, or provide GDPR legal advice. Organising photos is not the same as guaranteeing compliance. This guide is operational information, not legal advice.

Already have a spreadsheet?

Upload your existing matrix and see who’s current, what’s expiring and what’s missing.

14-day free trial. No card required.