Home
/
Blog
/
What Progress Should HR Expect After Three, Six and Twelve Months?

HR and L&D Guides

What Progress Should HR Expect After Three, Six and Twelve Months?

Author: Stanislav Kirillov
Last updated: September 2026

Corporate English review timeline at three, six and twelve months with task-based evidence

What progress can HR expect after three, six and twelve months?

After three months, HR can reasonably look for early changes in a small number of practised tasks: clearer structure, better use of clarification or more consistent written follow-ups. After six months, employees may handle a wider range of those situations with less preparation and recover more effectively when the conversation changes. After twelve months, a sustained programme may produce greater independence across connected tasks and, where the learning volume and breadth support it, measurable development in the wider language profile. These are review horizons, not promises. Compare similar tasks, report attendance and workplace opportunity, and avoid treating elapsed time as evidence of progress.

The calendar is attractive because it is easy to present. “Three months, confidence; six months, fluency; twelve months, transformation” would also be meaningless. HR needs observable expectations and the conditions behind them.

The milestones below are planning examples, not guaranteed outcomes. Results depend on the starting point, programme intensity, attendance, practice, role demands and opportunities to use English at work.

Start with the baseline and programme dose

Two employees can attend for six months and receive very different learning exposure. One joins two sessions a week and uses English daily. Another attends intermittently and rarely needs the target skill at work.

Record:

starting CEFR profile where relevant;
performance on two or three workplace tasks;
planned and attended guided learning time;
practice outside sessions;
opportunities to use the skill at work;
major changes in role, workload or programme design.

The baseline should include the conditions. A prepared presentation and an unplanned response to a client question are different tasks. Later evidence must be comparable enough to support the conclusion.

Cambridge English gives a rough estimate of about 200 guided learning hours for moving from one CEFR level to the next and notes that individual circumstances affect the time. A typical corporate programme may deliver far fewer guided hours within three or six months. That does not make it ineffective. It means HR should distinguish focused workplace progress from a broad level change.

What to look for after three months

The first review should ask whether the programme is relevant, accessible and beginning to change the practised behaviour.

Early progress is often narrow. A software engineer who previously gave a long update may now use a consistent sequence: completed work, current blocker, impact and request. The employee may still need notes and may lose the structure when several people interrupt.

HR can look for:

clearer organisation in one or two recurring tasks;
use of specific clarification or checking strategies;
fewer avoidable omissions in practised writing;
greater willingness to take a defined speaking role;
teacher evidence that the same problem is becoming less frequent;
early workplace use reported through a suitable, narrow observation.

Also review the programme itself. Are employees attending? Does the group fit? Do the tasks resemble their work? Are managers protecting the time? Three months is early enough to fix a timetable or role mismatch before another cycle is lost.

Do not expect every change to be independent. The participant may perform well after preparation and still struggle under pressure. Record the support used.

What to look for after six months

At six months, the question moves from first use to range and consistency.

An employee may now apply the same communication method across several related situations. A product manager who learnt to state assumptions clearly in discovery calls may use that skill during planning and scope discussions. A QA engineer may write a clearer bug report and answer follow-up questions without repeating the whole history.

Possible evidence includes:

comparable task performance across more than one scenario;
less reliance on a script or teacher prompt;
better recovery after interruption or misunderstanding;
more appropriate adaptation for technical and non-technical audiences;
repeated workplace examples rather than one successful event;
a clearer account of the remaining gap.

Six months can also reveal that the original goal was wrong. Perhaps engineers improved in class but receive no opportunity to speak on client calls. Perhaps the team needs writing more than meetings after a project change. Adjusting the programme is a useful result of evaluation, not a failure to preserve the original syllabus.

What to look for after twelve months

A year allows several cycles of practice, application and review. HR can examine whether employees handle connected tasks with greater independence and whether the programme still serves the organisation’s needs.

Depending on the starting point and total exposure, evidence may include:

sustained performance across recurring work situations;
more spontaneous handling of questions, disagreement and uncertainty;
clearer audience adaptation without extensive preparation;
successful use of the skill in a broader role or project;
development across several CEFR activities, supported by an appropriate reassessment;
reduced need for the original learning support and a defined next goal.

Do not assume that twelve months produces a CEFR jump. A participant attending one short weekly session has a different learning volume from someone in an intensive programme with daily workplace use. Reassess broadly only when the programme and evidence justify a broad conclusion.

The programme should not continue unchanged simply because a year has passed. Some employees may leave after reaching the target. Others may move into a new role that requires a different track.

Use milestones that match the role

The following examples show how the same time horizon can look different across technology roles. They are illustrative and should be adjusted to the baseline.

The table does not set a standard for every participant. It gives HR a way to replace broad words such as “confidence” and “fluency” with behaviour that can be reviewed.

Measure the same construct at each review

If the baseline assesses a two-minute incident update, the next task should test a comparable update. A final presentation with two weeks of preparation measures something else.

Use a stable rubric for:

task completion;
structure and clarity;
interaction and response;
audience fit;
language control where it affects meaning.

Change the scenario so the employee cannot repeat a memorised answer. Keep task difficulty, preparation time and support similar enough for a fair comparison.

The CEFR Companion Volume provides descriptors across language activities, including interaction and mediation. Use it as a reference where appropriate, then add the role and workplace purpose through the task.

Report more than the best sample

One strong performance can be encouraging. HR needs to know whether it represents a pattern.

Combine evidence from:

a comparable assessment task;
teacher observations across sessions;
attendance and access context;
employee reflection;
an approved work sample or narrow manager observation where available.

Each source answers a different question. A teacher sees learning behaviour. A manager sees selected work situations. The employee knows how much preparation and effort the task required. None should be presented as complete on its own.

The CIPD guidance on learning evaluation recommends aligning evaluation with organisational objectives and considering transfer. That means the report should state what changed in learning and whether the work gave employees a chance to apply it.

Explain when progress is uneven

Speaking, listening, reading and writing do not develop at the same rate. Neither do prepared and spontaneous performance.

An engineer may produce much clearer written updates and still hesitate during conflict. A manager may lead routine meetings comfortably and struggle to explain a sensitive decision. Report the profile rather than averaging the differences into one reassuring number.

Uneven progress can point to:

the amount of practice given to each skill;
a mismatch between the assessment and target work;
limited exposure to a particular situation;
a group or level problem;
attendance changes;
a new role requirement;
a language feature that needs focused support.

The next cycle should follow the evidence. It does not need to repeat the original content evenly.

Diagnose a flat result before adding more lessons

No visible progress after a review does not immediately prove that the employee failed or the provider is ineffective.

Check the chain:

Was the baseline comparable with the review task?
Did the employee attend enough of the relevant practice?
Was the target present in the lessons?
Did the employee receive understandable feedback and another attempt?
Was there any opportunity to use the skill at work?
Did the role, manager or project change?
Is the remaining problem mainly linguistic?

Then decide whether to adjust the goal, format, group, teacher, schedule or workplace support. More hours in the same design may reproduce the same result.

Create a 3, 6 and 12-month reporting rhythm

The same employee does not need an identical formal test at every point. Use enough evidence for the decision and avoid assessment that consumes the learning time.

HR reports should remain clear about individual and group data. Aggregate reporting may support programme decisions, while detailed personal feedback goes to the employee under the agreed policy.

Keep one live programme view between reviews

Formal assessment points may be three or six months apart. HR still needs a light operational view in between. It can contain:

active learners and groups;
completed and target academic hours;
recent pace over a clearly stated period;
midpoint assessment completion;
current CEFR distribution where reassessment has taken place;
a projected finish date based on recent pace;
groups that need a scheduling, relevance or placement review.

This view explains the conditions around later progress. If a group has received much less practice than planned, the review should say so. If an employee has completed the planned hours, that fact belongs in the report but does not replace the comparable task or language assessment.

The individual report can add a short monthly observation between formal assessment points. Use the same four prompts each time:

strengths demonstrated in a defined task;
areas to work on;
the next focus for lessons or self-study;
a summary and next action.

If there has been no reassessment, keep the original starting level and say that the current CEFR level has not been reassessed. Midpoint and final test fields should show both status and result. Comments should describe what the learner did in a lesson, assessment or agreed work sample. Avoid personality judgments such as “unmotivated” or “not confident” unless the report defines the evidence behind them.

Use group-level summaries for routine programme management. Detailed individual findings need a defined audience, purpose and access policy. A public case or sample progress report should be rebuilt with synthetic or fully anonymised data rather than copied from the live delivery system.

Set expectations with employees and managers

At launch, explain what each horizon means. A three-month review checks early task change and programme fit. It is not a deadline for fluency. A six-month review looks for range and consistency. A twelve-month review considers sustained use and the next development need.

Managers should know which behaviour to observe and how often. Employees should know what evidence is shared. This reduces the pressure to perform improvement in every meeting and keeps feedback connected to the stated purpose.

If the company publicly promises a fixed result before seeing baselines, the reporting process will be pushed towards proving the promise. Use conditional, task-based expectations instead.

Frequently asked questions

Should employees move up a CEFR level every year?

No fixed annual progression applies to every employee. A level change depends on starting point, learning volume, breadth, practice and assessment. Many corporate programmes focus on selected workplace tasks rather than the full profile required for a new level.

Can confidence be reported as progress?

Yes, if the method is clear and confidence is kept separate from demonstrated performance. Ask about specific situations and compare the response over time. Pair it with task or workplace evidence.

What if an employee improves in class but not at work?

Check whether the work provides a suitable opportunity, whether the manager supports use and whether the class task matches the real situation. The employee may need a more gradual transfer plan.

Should HR expect the same progress from everyone in a group?

No. Participants differ in starting profile, attendance, practice and workplace exposure. Use a shared rubric where the task is shared, then report individual conditions and group patterns without forcing identical outcomes.

When should training stop?

Stop or change the current programme when the target has been reached, the need has changed, the design cannot address the confirmed barrier or further training has no clear decision attached. Ending one track may lead to another development goal.

Use the calendar as a review schedule

UnifyHub's corporate English programmes for IT teams set role-specific communication goals and review evidence during delivery. A team English assessment can establish the baseline needed for realistic expectations. For planning the initial commitment, see how much corporate English training employees need.

Define one task-level expectation for three months, one question about range for six months and one decision for twelve months. Then attach the evidence and conditions to each. The dates become useful because they trigger action, not because time itself proves learning.

Book a team assessment