If you run a site, the CSCS problem is not checking one card. It is knowing, on any given morning, whether the ninety-odd operatives from fourteen subcontractors currently hold valid cards for the work they are doing — when the cards were issued by different schemes, expire on different dates, and belong to people whose employer never tells you when one lapses.
That is a tracking problem, and it is different from the check-at-the-gate problem most CSCS content addresses.
First, what a CSCS card actually is and is not
CSCS is clear about its own status. Per the scheme's own FAQs: "Holding a CSCS card is not a legal requirement but most principal contractors and major house builders in the UK require workers on their sites to hold a valid CSCS card."
So the card is an industry requirement, not a statutory one. No regulation says an operative must hold one.
What is statutory is the duty behind it. CDM 2015 Regulation 8(1) requires any contractor appointed to a project to "have the skills, knowledge and experience, and, if they are an organisation, the organisational capability, necessary to fulfil the role that they are appointed to undertake" — and Regulation 8(3) puts a duty on whoever appoints them to "take reasonable steps to satisfy themselves" that this is so.
The card is evidence toward that. It is not the duty itself, and treating it as the whole competence check is the most common mistake in this area. A valid card confirms the holder has passed the relevant health, safety and environment test and holds a recognised qualification for an occupation. It does not confirm they are competent for this task on your site.
A jurisdiction note. Regulation 3 applies CDM 2015 "in Great Britain". Northern Ireland has its own instrument — the Construction (Design and Management) Regulations (Northern Ireland) 2016, in operation since 1 August 2016 — so if you work there, check the NI position rather than assuming the regulation numbers cited here apply.
Why tracking is harder than checking
A gate check is a moment. Tracking is a state that decays, for four reasons:
Cards expire on individual dates. Not project dates, not renewal seasons. Every operative has their own.
The workforce churns. A subcontractor swaps two operatives mid-package and does not tell you. The people you checked in week one are not the people on site in week six.
Multiple schemes. The CSCS logo is not a single scheme. CSCS itself puts it this way: "CSCS Cards is one of the 37 CSCS Alliance card schemes that meet Construction Leadership Council (CLC) recommendations and are therefore permitted to display the CSCS logo" (CSCS Alliance). "Has a card" is not a sufficient record.
Nobody is incentivised to tell you. A subcontractor whose operative's card lapsed on Tuesday has no reason to raise it. The information only reaches you if you go looking.
Verifying a card properly
Visual inspection is not verification. Cards can be expired, altered or belong to someone else, and a laminated rectangle looks convincing at a site gate in poor light.
CSCS provides Smart Check for electronic verification, described on their site as a way to "verify our cards quickly and securely using CSCS Smart Check to help ensure compliance and prevent fraud on your site. Available as an API, mobile app and website." Per CSCS's Smart Check FAQs, a check confirms whether a card is genuine, valid and in date, along with the holder's name, photo, occupation and qualifications — which is the kind of record worth keeping, rather than "card seen."
The API matters if you are tracking at any scale: it is the difference between a person re-checking cards manually and a system that can re-check them.
What to record per operative
"Checked" is not a record. Store:
- Operative name and card registration number
- Which subcontractor they work for, and on which work package
- Card scheme and card type — not just "CSCS"
- The occupation the card covers
- Expiry date
- Date of the last electronic verification, and the result
- Date of site induction
The expiry date is what turns a filing system into a tracking system. Without it you cannot generate the only report that matters: which cards expire in the next 30, 60 and 90 days.
A workable process
1. Collect at onboarding, not at the gate. Ask for card details as part of the pre-mobilisation document set, alongside insurance and RAMS. An operative turning up at 7am with an expired card is a problem you now have to solve on the spot; the same fact discovered a fortnight earlier is an email.
2. Verify electronically and record the result. Visual checks leave no evidence and catch nothing sophisticated.
3. Check the card matches the work. The occupation and card type should correspond to what the person is actually doing. A card held for one trade does not evidence competence in another.
4. Set expiry alerts at 90, 60 and 30 days. Renewal is not instant. Thirty days' notice is the practical minimum for an operative to renew without losing site access.
5. Re-check when the workforce changes. Make it a subcontractor obligation to notify personnel changes, and treat a new name on a signing-in sheet as a trigger.
6. Keep the record after the project. If a competence question arises later, you need to show what you held at the time, not what is current now.
What this does not cover
Worth being explicit, because CSCS tracking is often over-relied on:
- It is not the CDM Regulation 8(3) check in full. That is a check on the contractor organisation — its systems, experience and capability — not only on individual cards.
- It does not replace trade-specific registration. Gas Safe, NICEIC and similar sit alongside CSCS, not underneath it.
- It does not evidence site-specific competence. That comes from RAMS review and induction.
- A card is not a substitute for supervision. Regulation 15(2) still requires the employing contractor to plan, manage and monitor the work.
The failure mode to design against
The one that actually bites is not a fake card. It is a genuine card that expired three months ago on an operative who has been on site throughout, discovered when a Tier 1 client audits the site register. At that point the question is not whether the operative was competent — it is why nobody noticed, which is a question about your system rather than about them.
Expiry tracking is unglamorous and it is the entire value of doing this properly.
For where card details sit in the wider onboarding set, see our subcontractor onboarding documents guide. For the competence framework the cards feed into, see our subcontractor compliance checklist and our contractor prequalification questionnaire guide. For the induction that should follow the card check, see our construction site induction guide.
SubComply is being built for exactly this tracking problem — card details, expiry dates, insurance and documents held per subcontractor with the renewal dates surfaced before they lapse. Join the waitlist to be notified when it launches.
Sources
- CSCS — Frequently Asked Questions
- CSCS — official website (Smart Check)
- CSCS — Smart Check FAQs
- CSCS — the CSCS Alliance
- The Construction (Design and Management) Regulations 2015 (SI 2015/51), Regulation 8
- The Construction (Design and Management) Regulations 2015 (SI 2015/51), Regulation 15
- The Construction (Design and Management) Regulations 2015 (SI 2015/51), Regulation 3 (application in Great Britain)
- The Construction (Design and Management) Regulations (Northern Ireland) 2016 (SR 2016/146)
This guide is for informational purposes and does not constitute legal advice. CSCS is an industry scheme, not a statutory requirement — check your client's and principal contractor's specific contractual requirements for the project you are working on.
Last reviewed: 28 October 2026