Open development points that stay visible until they are closed

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.

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.

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.

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.