A competency register can show that every certificate is in date and still leave management unable to answer a basic question: is this person suitable for this assignment, on this railway, today? The answer depends on more than the expiry date printed on a record.

Separate qualification from authority to deploy

Training completion, formal assessment, route or traction knowledge, local authorization and recent practical experience serve different purposes. A locomotive engineer may hold a valid professional qualification but lack the required route knowledge, rolling-stock familiarization or local operating-rule endorsement. A maintainer may be competent on one equipment configuration but not on a modified fleet.

A deployment decision should therefore connect the individual to a defined role and task, the railway’s requirements and the evidence accepted by the responsible manager. Restrictions and supervision requirements must remain visible rather than being buried in a document folder.

Verify the evidence, not just the entry

A database entry stating ‘competent’ is not evidence by itself. The record should identify the assessment or authorization, who issued or verified it, the applicable scope, its validity and any outstanding conditions. Where a requirement changes, the system should identify which people and assignments are affected.

Expiry alerts are useful, but they address only one failure mode. Other risks include an assessment that was never independently verified, a superseded standard, an unresolved competence gap, an induction not completed for a specific site or a person whose availability conflicts with another deployment.

Make exceptions explicit

Management sometimes needs to consider provisional suitability or a restricted assignment. Such decisions should be controlled, documented and made by an authorized person against defined rules. The system should distinguish suitable, suitable with restriction, provisionally suitable and not suitable, while recording what must change before restrictions can be lifted.

Software can bring information together and surface exceptions. It cannot replace the accountable manager, competent assessor or applicable railway authorization process.

A practical assurance question

Before assigning someone, ask what they will do, where they will do it, what evidence proves their suitability, which restrictions apply and who has accepted the deployment decision. If those answers cannot be found quickly, the weakness is operational, not merely administrative.

Axis is developing CDAS, a Competency & Deployment Assurance System, initially for its own operations. It is a development initiative, not a product currently available for purchase. The objective is to make evidence and assignment-specific requirements easier to review while keeping professional judgment and authorization with management.