How to measure English progress in a team
Six months into a training programme, someone senior asks whether it worked. The folder that comes back usually contains attendance percentages, a list of completed units and a satisfaction survey. All three are real numbers, and none of them answers the question that was asked.
Attendance is a cost, not a result
Companies count what the platform reports, and platforms report participation. That data answers a different question: whether the money was spent as planned. It says nothing about whether the engineer can now push back in a design review, which is the reason the budget existed.
| What usually gets counted | What it actually tells you |
|---|---|
| Attendance percentage | Whether the schedule survived the workload, nothing about language |
| Units or modules completed | The pace of the course book, not the pace of the learner |
| Satisfaction survey | How the lessons feel, which correlates with staying, not with speaking |
| Vocabulary count in an app | Recognition of words, tested outside any working situation |
| Recorded working task, repeated | Whether the job now happens in English, which is the thing being bought |
Three measurements that hold up
Everything useful comes from comparing a person with their own earlier self, not with the group.
- A task recorded twice. Five minutes of a real scenario at the start, the same scenario months later. Both recordings sit in the same folder, and the difference is audible to anyone, including the person themselves.
- Sub-skills, not one label. Speaking, writing, listening and reading move at different speeds, and in a working context the first two carry the money. A report that gives one letter hides the half that matters.
- Scenario completion. Whether a named situation now runs end to end in English: the call held without a follow-up in Ukrainian, the specification reviewed without translation, the complaint answered the same day.
How often, and what belongs in the report
Twice a year is the sensible rhythm for a formal check, with a short monthly note in between. Anything more frequent measures familiarity with the test rather than command of the language, and anything less leaves a failing group unnoticed for too long.
A monthly note that a director will actually read fits on half a page: who is in the group and at what level, which scenarios were practised, which of them are now handled unaided, what is blocking the ones that are not, and the attendance figure last rather than first. That is the format we keep for corporate English language courses, because a company that cannot see the movement stops paying for it, quite reasonably.
Signals that only look like progress
Three of them cost companies the most time.
- Confidence. A person who has stopped being afraid speaks more, which is genuine and worth having, but the range of what they can say may not have changed at all.
- Accent. It is the first thing a listener notices and the last thing that matters at work. Clarity, structure and precision are assessed on the CEFR scale; accent is not.
- Vocabulary size. Knowing more words shows up in reading long before it shows up in speech, and the working gap is almost always production rather than recognition.
The mirror image is just as common: a quiet participant who says little in the lesson but has started answering client emails without help. Progress at work does not always announce itself in the classroom, which is exactly why the manager's half of the measurement exists.
Questions HR asks about assessment
Start the measurement before the training, not after it. A baseline recorded in the week the group is formed costs an hour and settles every argument that follows; without it, six months later you are left comparing an impression with a memory. If you are still deciding which level each role needs, that decision comes first and is set out in what English level your team needs, and a quick online level test gives everyone a CEFR starting point on day one.