Managing Sentinel cards as a small subcontractor

Sponsorship, swipes, expiries and what to do when a card goes wrong at the access point.

Sentinel is the rail industry's competence card scheme, and if you sponsor your own people it is also a weekly admin job: keeping sponsorship current, keeping competences on the card up to date, and making sure the card is swiped in and out on every shift so the hours and fatigue records are right.

The three things that go wrong

• Expiry nobody saw coming. A competence lapses on the card and a trained person is turned away at the access point. Fix: the card number drives your competence list, and the warnings come from that list, not from memory.
• Swipes missing. Someone forgets to swipe out, the hours look wrong, the fatigue return is wrong, and the client questions the timesheet. Fix: a daily check of swipes against the planned shift, with a nudge to the person the same day.
• Sponsorship paperwork drifting. New starters, leavers and transfers not reflected in Sentinel. Fix: one onboarding and offboarding checklist that includes the Sentinel steps and is signed off, not just remembered.

What to automate first

The daily swipe check and the expiry warnings. Both are rule-based, both are the ones that cost real money when missed, and neither needs a human decision; the human decides what to do when the warning arrives.

Want this done for you? That is what the free half-day audit is for.