Guide · Updated 2026-09-10

How to Use a Rail Contractor Training Matrix

Use a rail matrix as an internal planning view of assigned records, then verify access, competence, medical and sponsor status through the required authoritative rail process.

Define the internal copy’s purpose

A contractor may need early visibility while bidding, rostering or preparing assurance packs. Make clear which data is an internal copy, when it was last checked and which system or sponsor process is authoritative. Do not imply that a spreadsheet or FieldClear replaces Sentinel or permits a person to work on railway infrastructure.

Keep dependencies separate

  • Sentinel card or profile reference
  • PTS and task competence labels
  • ICI or DCCR where assigned
  • Rail medical status and date
  • Drug and alcohol screening record
  • Sponsor or primary-sponsor status reference
  • Company learning and project briefing records
  • Last authoritative verification date

Plan possessions without stale assumptions

Use the internal view to identify potential gaps early, especially scarce roles such as COSS, ES or machine-control functions. Before confirming the team, complete required checks in the official process. Re-check after roster changes and at the point required by rail rules; exports become stale immediately when source status changes.

  1. Name an owner for internal rail data.
  2. Record the authoritative source.
  3. Import only the fields needed for planning.
  4. Flag records by last verification date.
  5. Perform formal checks before work.
  6. Correct internal copies promptly after source changes.

Control freshness and sensitive data

Set an internal freshness rule appropriate to each planning stage and show “last checked” prominently. Do not create invented future expiry dates for status that must be checked live. Rail medical and D&A information is sensitive: record only the minimum status and dates needed, restrict access and follow the employer’s retention policy rather than uploading detailed clinical information. When a sponsor or competence change is reported, update the planning view quickly and notify affected rostering teams. Periodically sample the copy against the authoritative source to measure data lag and correct the process, without claiming the sample guarantees all records.

Separate tender-stage candidate lists from confirmed possession rosters. A person may appear suitable in the internal view but become unavailable, de-sponsored or subject to another change before work. Give roster exports an as-at timestamp and prohibit their reuse as a live authority. Where a client asks for an assurance pack, explain the source and freshness of each field. Remove detailed medical documents if a simple verified status is sufficient for the stated purpose.

Never use the matrix as access authority

FieldClear cannot sponsor workers, read Sentinel status, issue competencies or determine fitness and access. It tracks assigned internal records only. Follow Network Rail, scheme, sponsor and employer processes and obtain competent advice; this guide is not rail-safety or legal advice.

Already have a spreadsheet?

Upload your existing matrix and see who’s current, what’s expiring and what’s missing.

14-day free trial. No card required.