What should we be proving

We don't need to bin everything we've already got. We need all of it. The question is whether those things give us a proper answer when we need one.

We think there are three useful questions to ask.

Is the worker ready?

What are we basing that on?

And if somebody asks us later, can we prove it?

That changes the conversation from, ‘has Kris done the induction’? To ‘why are we happy for Kris to do this job today’?

His induction might be part of the answer. His cards might be another part. Maybe there's a knowledge check. Maybe somebody has seen him do the job. Maybe there's a supervisor sign-off. Maybe he needs a particular briefing because something changed on site this morning.

It depends on the person and the work.

And just to be clear, we aren't suggesting software should somehow remove judgement from this. You want good supervisors making judgements. What you don't want is good supervisors making those judgements without the evidence they need.

Wind the clock forward six months. Something's happened. It doesn't even have to be an accident. Perhaps a client asks a question. Maybe there's an audit. Maybe somebody simply wants to know why a particular person was allowed to do a particular piece of work, which now needs reworking.

And the question comes back: can you prove they were ready?

So you start digging. Someone gets the induction record. Someone else looks for the card. A certificate gets found somewhere. The subcontractor sends something over. Then eventually somebody asks the supervisor.

“Do you remember him?”

“Yeah, course I do. Good lad. Knew exactly what he was doing.”

And that might all be enough. But you've had to rebuild the picture after the event.

You've reconstructed readiness. You didn't necessarily know it at the point the person started work. The problem is that most of the systems we've had for years were built to record that things happened. They weren't necessarily built to answer whether that person was ready.

We've been asking an old set of records to do a different job.

If you're the person who needs to get a job moving, the answer you need in the end isn't particularly complicated. Can they work or can't they? We call it ‘Cleared or Not Cleared’.

What sits underneath that answer can be tricky. Skills, knowledge, experience and behaviours. Cards, training, site induction, briefings and practical sign-offs. Different roles will need different things and different sites will have different requirements.

No argument there.

But the person making the decision shouldn't have to log into five different systems, check a lever arch folder and ring a subcontractor before they can work it out.

The evidence can be complicated. The answer doesn't need to be.

If they're Cleared, you should be able to see why. That's what we mean by workforce readiness.

There's another obvious danger with all of this. We spot a problem around competence or readiness and immediately decide everybody needs more training.

Sometimes they do. Sometimes they absolutely don't.

Perhaps you've already trained them. Perhaps the evidence already exists. Perhaps one group of workers has a gap and everybody else is fine. Putting 500 people through another course because you can't tell which 40 need it isn't a particularly clever answer.

So instead of asking what training we can give them, perhaps the first question should be: what do we actually need to know before this person starts work?

Then you can work backwards. What evidence have we already got? What's missing? What needs checking? Who actually needs training?

That can save time as well as reduce risk. It can stop people repeating things they already know and help get people ready before they arrive on site.

And there's another side to it that's easy to forget. Good evidence can help win work.

Falco Construction uses regular digital safety learning to get toolbox talks and lessons from incidents out to small gangs working across a dispersed network. They can also show that people have understood what was sent. That proof became part of the story they could tell a client and helped them secure the biggest contract in the company's history.

So workforce readiness isn't only about protecting yourself if things go wrong. Being able to prove you've got a workforce that is genuinely ready can be valuable when you're trying to win the next job too.

Don't take our word for it. Try this on one of your own sites.

Pick one person who started work this morning. Anyone. Ask what they needed to know and be able to do before they started, then ask what evidence you actually had. What did you know? What had somebody checked? What did you take on trust?

Then imagine somebody comes back in six months and asks you to prove why that person was allowed to work.

How long would it take?

If the answer involves several systems, a couple of phone calls, a subcontractor and somebody eventually saying, “It's fine. I know him. He's good at his job,” then perhaps you don't have a training problem.

You've got a readiness gap.

That's the gap LUMA1's Workforce Readiness Dashboard (Atlas) is built to close. Instead of a completion count, it gives you Cleared or Not Cleared at a glance for the whole workforce. Who isn't cleared and exactly why, a breakdown by reason, readiness by trade, and credential expiry buckets, so the six-months-later question has an answer in seconds, not a morning of phone calls.