Tracking CISRS card expiry across a squad

Most firms record that an operative holds a card. Fewer record when it expires, and fewer still hold that date anywhere that will raise it before the day arrives. The result is a familiar pattern: expiry discovered late, a renewal that cannot be arranged in time, and an operative who cannot be allocated to the work they normally do.

The date has to sit where allocation happens

An expiry date in a personnel file protects nobody, because gang allocation is not made from the personnel file. It is made early in the morning by whoever is building the squads, from whatever information is in front of them — which is why card status needs to be visible at the point gangs are put together rather than filed correctly somewhere else.

Renewal takes longer than people plan for

Renewals are not instant, and they frequently require course availability rather than just an application. A firm that starts chasing at the expiry date has already lost. Starting far enough ahead to absorb a course being full is the practical difference between a renewal and a gap in availability.

Subcontract labour is the blind spot

Where labour comes through another firm, the tendency is to rely on an assurance rather than evidence. That assurance is a commercial protection, not a record about the named individual on site this week — and it is the individual a client or an inspector will ask about.

Common mistakes

• –Recording that a card is held without its type and expiry
• –Holding expiry where allocation decisions cannot see it
• –Starting the renewal chase too close to the date to absorb a delay
• –No record of whether a renewal has actually been booked or applied for
• –Relying on an assurance for subcontract labour instead of holding evidence
• –No prompt, so the date only works if somebody opens a file

In practice: a renewal that could not be arranged

An operative's card expiry was noticed four days before the date. The renewal required a course, the nearest available place was six weeks out, and the operative spent that period unable to be allocated to the work he normally did — on full pay, because the firm was not going to lose him.

The cost was entirely avoidable and had nothing to do with the operative. The expiry date had been captured correctly at recruitment, filed correctly, and never surfaced anywhere that would raise it in time. A prompt three months out would have cost nothing.

Build the prompt around the lead time, not the date

The useful notice period is not a round number; it is however long a renewal actually takes in the worst realistic case, plus a margin. Where that involves course availability, it is considerably longer than most firms assume and varies by season.

Worth establishing once, from experience rather than from the published process, and setting the prompt from that. A reminder that arrives after the last realistic booking date is decoration.

Worth knowing: expiry clusters

Cards obtained around the same time expire around the same time, which means a firm that recruited a squad together will face several renewals in the same few weeks — usually with the same course availability constraint. Looking at expiry as a distribution rather than a list of dates surfaces that months ahead.

• –Look at expiries as a calendar, not a list, to spot clusters
• –Stagger renewals deliberately where a cluster would strip a squad
• –Book course places before they are needed where availability is tight

Where this connects: expiries arrive in clusters

Cards obtained around the same time expire around the same time. A firm that recruited a squad together, or put four people through a course in one week, will face those renewals in the same few weeks — usually against the same course-availability constraint, and usually without having seen it coming.

Looking at expiry as a calendar rather than a list surfaces that months ahead, while it is still possible to stagger renewals or book places early. A cluster that strips a squad of three carded operatives in a fortnight is an operational problem long before it is a compliance one.

• –View expiries as a calendar to spot clusters, not as a list of dates
• –Stagger renewals deliberately where a cluster would strip a squad
• –Book course places ahead where availability is tight
• –Set the prompt from real lead time, including course availability
• –Record whether a renewal has actually been booked, not just that it is due
• –Include subcontract operatives in the same view