There’s a familiar moment in a lot of rail businesses. A buyer or prime sends over onboarding requirements and, buried in the detail, is the line that matters: you need RISQS accreditation.
That’s usually when someone says, “Can’t we just get a consultant to sort it?”
You can bring in help, and it often makes sense. But RISQS isn’t a paperwork project. In the rail supply chain it’s a test of whether your controls hold up on real jobs, under time pressure, with multiple interfaces, and with a clear expectation of traceable evidence.
So what do RISQS consultants actually do that’s worth paying for?
They stop you picking the wrong scope
Rail punishes over-claiming. If you include an activity in scope, you’re expected to evidence competence, supervision, and control around it, even if you only do it occasionally.
Good consultants push hard on scope early because it dictates how heavy the work becomes, what evidence you need, and whether you’re building something maintainable or setting yourself up for a scramble.
They translate “how you work” into “what rail assurance expects”
A useful gap assessment isn’t “do you have a procedure?” It’s “how do you do this on a live rail job, and what proof exists?”
That’s where common weaknesses show up:
- briefings happen, but records are inconsistent
- competence is assumed, but role requirements aren’t defined
- change happens mid-shift, but approvals aren’t clearly captured
- job files exist, but traceability is patchy
- nonconformances get “closed” without showing learning
In rail, buyers care about evidence because it’s how they manage supplier risk at scale.
They build a competence approach that stands up in a rail context
Lots of firms have capable people. The issue is showing a disciplined approach that fits safety-critical expectations.
RISQS consultants typically help put structure around:
- role profiles and what “competent” means for your scope
- a matrix linking people, roles, and required evidence
- sensible refresh and supervision arrangements
- consistent recording of briefings and checks
It’s less about bureaucracy and more about being able to show you’re in control.
They make sure the system survives possessions and pressure
Many systems look fine in an office. Then they meet rail delivery: possessions, tight access windows, night shifts, and multiple parties working in the same space.
A good consultant sanity-checks whether your processes still work when:
- the plan changes at 01:00
- you need to adjust resources or method quickly
- documents must be available on site, not just “somewhere in SharePoint”
- subcontractors or agency labour are brought in at short notice
If a process only works when everyone has time, it won’t work in rail.
They focus on evidence you can maintain, not an “audit pack” you rebuild every time
The aim is to generate evidence as part of normal delivery, so you’re not doing heroics before an audit.
That usually means simple, repeatable routines: standard briefings, consistent job file structure, clear version control, and a workable way to record deviations and approvals.
What they can’t do for you
It’s worth being blunt. Consultants can’t:
- create competence that doesn’t exist
- make people follow processes leadership won’t enforce
- do it without internal time and ownership
They can bring structure and momentum. The business still has to live the system.
A quick reality check
Pick one recent rail job. Can you show, end-to-end, who was competent, what briefings happened, what approvals were needed, what changed during delivery, and what records prove it?
If yes, you’re refining. If no, you’re collecting documents. That’s the line RISQS accreditation tends to expose.
