Platform capability
Included — not an add-on
Included as standard
Open development points that stay visible until they are closed
A competence development plan (CDP) is how Rail Intel records what still needs to improve after an assessment, incident or monitoring review, what was agreed, who owns it and whether it was completed. CDPs live on the Monitoring tab of the employee record, link back to the competence activity that raised them, and carry forward automatically when a continuous cycle renews.
Cycle carryover
Open CDPs move forward
Gated access
Permissions per company role
Full history
Closed plans retained
Competence development lifecycle
From finding to closure, with nothing lost at the cycle boundary
01
Employee record · Development view
The Monitoring tab
The Monitoring tab is the operational view of competence follow-up for one person: allocated incidents, open and closed development plans, and, where the Trainee Driver module is active, performance and support plans.
Managers and assessors with the right permissions see the full picture for people in their scope. Employees with own-record access see their own monitoring history without opening the company directory.
Incidents & CDPs together
Nothing logged in one system and chased in another.
Status at a glance
Open, in progress and completed plans on the record.
Tied to the person
Monitoring follows the employee, not a spreadsheet row.
02
Structure · Evidence · Closure
What a CDP contains
A CDP captures the gap that was found, the improvement agreed and the evidence that it was done. It is raised from competence activity, typically when assessment criteria are flagged, and stays on the record until formally closed.
Linked to the finding
the plan relates to the assessment or incident that triggered it.
Agreed actions
what the employee and manager or assessor committed to.
Completion tracked
closure is recorded on the record, not assumed.
03
Plan setup · Incident link · Validation
Raising a new CDP
When a competence gap is identified, assessors raise a CDP from the Monitoring tab. Plan type, start date, duration and linked incident are captured in one form, and the end date is calculated automatically from the duration you set.
Rail Intel enforces one CDP per incident. If a plan is already linked to the selected incident, the system blocks creation and explains why, preventing duplicate development plans on the same finding.
04
Continuous cycles · No re-keying
Automatic carryover
Competencies that renew on a continuous cycle do not wipe open development work at the boundary. When a new cycle period starts, scheduled assessment events and open CDP items carry over automatically.
Closed cycles remain in history. Carryover applies to live work that was not completed before the cycle turned over.
Continuous cycles supported
for competencies that renew rather than end.
Events carry over automatically
assessment schedule and open CDP items move with the cycle.
History retained
previous cycles and closed plans stay on the record for audit.
CDP monitoring events carry over when a continuous cycle renews.
05
Organisation settings · Granular control
Permissions by role
Monitoring and CDPs are core Rail Intel, not an add-on, but who can view or change them is controlled by company role permissions, the same model used across the rest of CMS.
Administrators configure roles in Organisation settings. Each role gets exactly the access your operation requires, no more, no less.
Assessor
Raise and update plans for people they assess.
Line manager
View monitoring for their team.
Driver
Own-record Monitoring tab — no company directory.
Company Admin
Configure roles and permissions for the operation.
Frequently asked questions
When do open CDPs carry over at cycle renewal?
Carryover applies only where continuous cycle rules are in place. Rail Intel runs automated checks against the nested continuous requirements and the parent cycle they sit within before renewal completes. If the record qualifies, outstanding CDP items and scheduled assessment events move forward automatically. Where continuous is not configured, or those checks are not met, the system prompts you, and outstanding work is not carried over by default.
Who can view and edit CDPs?
Access is controlled by company role permissions, assessors, line managers, drivers with own-record access and administrators each see what their role allows.
Can more than one CDP be linked to the same incident?
No. Rail Intel enforces one competence development plan per incident. If a plan is already linked to the incident you select, creation is blocked and the system explains why, preventing duplicate development plans on the same finding.
How is a CDP raised in Rail Intel?
Assessors raise a CDP from the Monitoring tab when a competence gap is identified, typically after assessment criteria are flagged or following an incident or monitoring review. Plan type, start date, duration and linked incident are captured in one form, and the end date is calculated automatically from the duration you set.
Are closed CDPs retained on the employee record?
Yes. Closed plans remain on the Monitoring tab and previous cycle periods stay in history for audit. Carryover applies only to outstanding live work at renewal; completed or closed items are preserved on the record either way.