Time to proficiency is useful only when the start, finish and permitted level of support are clear. Define the milestones between joining and independent work, then record where learners spend time so that a shorter course does not obscure a longer period of supervised work.
Define the finish for a specific role
Describe the work someone must perform, the conditions under which they must perform it and the help they may receive. A representative might handle routine billing questions independently while still escalating a disputed transaction. Record that boundary rather than labeling the person fully proficient across every responsibility.
Distinguish classroom completion, readiness for supervised work, independent performance and formal accreditation. If a client contract has a separate competency or billability gate, record that too. These milestones may occur on different dates, and combining them into one undefined ramp measure makes comparisons hard to interpret.
Choose a clock and keep it consistent
Select a start event such as the first scheduled training day, and define whether the measure uses calendar days or scheduled working days. Record training hours separately from elapsed time. A learner waiting for system access may accumulate elapsed days without receiving instruction or practice; that delay still matters to operations, but it is a different problem.
For each milestone, capture the first date the learner meets the agreed standard, who confirms it and the supporting evidence. Record pauses, absence, reassessment and changes to the expected work. Keep the original dates when criteria change, and label the new definition so historical comparisons remain understandable.
Complete a proficiency definition sheet
Use one sheet per role or workflow. The training and operations owners should agree these fields before the cohort starts.
| Field | Definition to agree |
|---|---|
| Scope | Tasks included, exceptions excluded and normal working conditions. |
| Start event | The event and date that start the clock; calendar or working days. |
| Milestones | Instruction complete, supervised readiness, independent performance and any accreditation or contract gate. |
| Evidence and support | Required observations, critical errors, permitted help and decision owner for each milestone. |
| Reporting cutoff | Date of review, learners still progressing and reasons for pauses or exits. |
A fictional example: billing support readiness
A fictional billing team finishes classroom instruction on day 10. One learner passes the supervised-work gate on day 12, then meets the independent-work criteria on day 24. A separate accreditation review finishes on day 28. The team reports those dates separately and counts instruction and coaching hours alongside them.
Another learner is still working toward independence at the reporting cutoff. Their elapsed time remains visible as an unfinished journey; the team does not silently remove them or count the cutoff as a completion date. The first learner's day-24 result also does not imply readiness for specialist disputes excluded from the assessment.
Report progress without hiding unfinished journeys
For each cohort, show how many learners have reached each milestone by a fixed review point and how many are still progressing. If you report the median time among completers, label that denominator explicitly and show the unfinished group alongside it. Break out stage durations to identify whether the delay sits in instruction, practice, observation or approval.
Compare groups with similar roles, prior experience and assessment standards. Record changes in staffing, policy or access that could affect the journey. Use early independent-work reviews to check whether the readiness threshold holds up, and investigate any deterioration before treating a shorter timeline as an improvement.
