How to Track the CITB HSE Test and CSCS Separately

Why one merged column causes trouble

Spreadsheets often carry a single “CSCS / HSE” cell because both appear on the same renewal journey. That shortcut fails when a worker has a card due this month but a test result already out of the window your process uses, or when a pass is booked while the card application is still pending. Separate fields make status honest: each requirement has its own date, evidence and owner. Assign either or both only where your organisation’s rules and the project arrangement require them—not because the labels sound interchangeable.

Checklist for a clean dual record

• Distinct requirement names: CITB HSE test and CSCS (or affiliated) card
• Exact card colour or type stored separately from the test category
• Pass date and card expiry date as independent fields
• Evidence files attached to the correct requirement
• Status values that distinguish missing, not required, expired and booked
• Renewal owner and next action date for each line
• Project programme dates used to judge whether cover lasts the full attendance period

Workflow that keeps both lines in step

Run the two requirements through the same planning cadence without treating them as one status. When either date moves, update only that line and re-check whether the other still supports the planned work.

1. Map which roles assign the test, the card, both, or neither under company policy.
2. Import genuine dates from result emails and card images.
3. Filter people with either requirement due in the next 90 days.
4. Sequence bookings so test centre slots and card processing both finish before mobilisation.
5. On receipt of new evidence, update the matching requirement first, then re-check the linked line.
6. Brief supervisors that a verbal “I’ve got CSCS” is not enough without both records where assigned.

Operational patterns that expose false confidence

Agency substitutions are the usual failure mode. A named operative arrives with a different card type, a test under another spelling of their name, or a screenshot that does not match your verification route. Require named-person extracts from labour suppliers and reject company-level claims that everyone is covered. When a principal contractor gate checks only the card, still maintain your internal HSE-test field if your process assigns it—external acceptance does not rewrite your employer records. If a worker holds an affiliated scheme card rather than a classic CSCS card, label the scheme accurately instead of forcing everything into one CSCS column.

Use paired filters: show people who are green on the card but amber or red on the test, and the reverse. That view is more useful than a blended RAG. Keep booking confirmations as planning notes, not as current credentials. When programmes extend, re-run the dual filter against the new end date so a mid-contract expiry is not discovered at the gate. Archive old tests and old cards with history so date changes are explainable during client audits.

Limits of the tracker

FieldClear shows the requirements you assign and the evidence you attach. It does not interpret CSCS or CITB scheme rules, approve site access, or guarantee that a card and test combination satisfies a client. Organising evidence is not the same as achieving accreditation. This guide is not legal advice.