A secondment firm places an engineer at a client in Germany. His CV says “German: fluent” and the intake went well in English. In the first week it turns out that he follows meetings without trouble but cannot write the technical reports the client expects in German. The client is disappointed, the consultant has to explain what went wrong and the assignment is at risk. Nobody had checked, because the language was a single line on the CV and the vacancy only said “German required”. Languages decide whether a candidate can work with colleagues, customers and documents, yet they are often stored as a loose word without a level. This article explains why every candidate in your Applicant Tracking System needs recorded languages and proficiency levels: what goes wrong without them, which details to record, how to describe the requirement per vacancy, when to check the level in the pipeline, how to keep the approach fair, how it differs per segment and how to check with your own data whether it works.
Languages matter in every segment. Recruitment agencies submit candidates for customer service, sales and technical roles where a second language is part of the job. Staffing desks schedule international workers for sites where safety instructions are given in one specific language. Secondment firms place specialists at clients abroad or in international teams. Executive search firms present senior candidates who must negotiate, present and lead in more than one language. In-house recruitment teams hire for roles that work with colleagues or customers in other countries. In every case the question is the same: can you see in one place which languages a candidate speaks, at what level, and how you know?
What goes wrong without recorded languages
- A CV says fluent, good or basic, and every recruiter reads it differently
- A candidate is submitted for a role and turns out not to reach the level the client expects for speaking, reading or writing
- The vacancy only names a language, not the level or the skill that matters for the work
- Languages are typed as free text in different ways, so searches miss suitable candidates
- A level assessed years ago is treated as current, while the candidate has not used the language since
The result is rejected submissions, difficult first weeks, unhappy clients and candidates who are placed in a role that does not suit them.
What to record for each language
Keep the record short and the same for every candidate:
- Language — chosen from the shared skills and tag list, not typed as free text
- Level per skill — for example understanding, speaking and writing, on one shared scale such as the six levels of the Common European Framework of Reference (A1 to C2)
- Source of the level — self-assessed by the candidate, observed by a recruiter in a conversation in that language, or shown by a language certificate
- Date and assessor — when the level was assessed and by whom, so you know how current it is
- Note — a short remark where it helps, for example a specialist vocabulary or a language the candidate is currently learning
With these details on the candidate record, a recruiter can search for candidates who reach a given level in a given skill, instead of reading through CVs. If a candidate holds a language certificate with an expiry date, record it like any other certificate with an expiry date.
Describe the requirement per vacancy
A language requirement only helps if it is specific. Record in the structured brief which languages the role needs, the minimum level per skill and whether the requirement is a must or a preference. “Spoken Dutch at B1 to follow safety instructions” is a requirement a recruiter can check; “good Dutch” is not. Ask the client or hiring manager what the candidate will actually do in the language: talk to customers, read instructions, write reports or lead meetings. That answer determines which skill and level matter, and it often turns out lower or more specific than the first request.
Check the level at the right moments in the pipeline
Ask for languages and a self-assessed level through short screening questions at application, so you can sort early without a test. Check the level that matters for the role during the first conversation: hold part of it in the required language and record what you observed on the shared scorecard. Make a confirmed level one of the written entry criteria before a candidate is submitted to a client for roles where the language is a must. Tell the client in the submission how the level was assessed, so expectations match. Record a candidate’s preferred contact channel and the language in which they prefer to be contacted separately; that is a communication preference, not a job requirement.
Keep it fair and job-related
Record languages only where they are relevant to the work, and describe the requirement as a level, not as an origin. A requirement such as “native speaker” excludes candidates who reach the level that the role actually needs and can conflict with equal treatment rules; ask for the skill and level instead. Assess every candidate for the same role in the same way, and do not record nationality or place of birth as a stand-in for language ability. Tell candidates which details you record and why, in line with your own privacy statement.
Differences per segment
Agencies focus on the languages a client names as a must and confirm the level before the first submission. Staffing desks often need one practical level for many workers, for example enough to follow safety instructions, and benefit most from searching by language and level on short notice. Secondment firms compare the level with the client’s working language for the full assignment and record whether reports or meetings require a higher level. Executive search firms assess negotiation and presentation in each language discreetly in the interview, and record what was observed. In-house teams align with the hiring manager on which skill really matters and avoid copying a language requirement from an old vacancy text.
Let the system help
Much of the work repeats and suits automation: a screening question that fills the language fields, a search on language, skill and minimum level, a warning when a candidate without a confirmed level is moved to a stage where the language is a must and a reminder to reassess a level that is several years old. An artificial intelligence helper can suggest languages mentioned in a CV and propose a draft entry, so the recruiter does not have to read every line. The recruiter checks the suggestion and assesses the level; artificial intelligence does not replace recruiters and does not decide on its own whether a candidate is good enough in a language.
Common mistakes to avoid
- One word for the level — fluent or good means something different to every reader
- One level for all skills — many candidates speak better than they write, or the other way round
- No source — a self-assessed level is treated the same as a level observed in a conversation
- Vague vacancy requirements — a language is named, but nobody knows which level the work needs
- Using origin as a proxy — asking for native speakers instead of a level excludes suitable candidates
Questions teams ask
- Which scale should we use? — One shared scale for every language; the six levels A1 to C2 are widely known by candidates and clients in Europe
- Do we need to test every candidate? — No; use self-assessment to sort, and check the level in a conversation only for roles where the language is a must
- What if the client asks for a language certificate? — Record the certificate, its date and who checked it, and keep a copy only if an agreement or your policy requires it
- How long is a level valid? — There is no fixed rule; record the date of the assessment and reassess when it is several years old or the candidate has not used the language
- Where do we record the language for contacting the candidate? — Separately, as a communication preference, so it is not confused with a requirement of the role
Check it with your own data
Count from your own records, per team and per segment: how many active candidates have at least one language without a level, how many vacancies name a language without a level per skill, how many submissions were rejected or placements ended early because of a language mismatch and how many levels were confirmed in a conversation before submission. Discuss these figures in your weekly pipeline review and report the number of candidates behind each figure. Do not compare with industry averages; your own trend is the number that matters.
A practical start
- Agree on one shared list of languages and one scale for levels
- Record language, level per skill, source, date and assessor on every candidate record
- Describe language requirements per vacancy as a skill and a minimum level
- Check the level in a conversation before submission where the language is a must
- Ask for levels, never for origin, and assess every candidate for a role in the same way
A clear language level is part of a good match
Candidates, clients and recruiters all benefit when everyone means the same thing by a language level. Record every language with a level per skill and a source, describe what each vacancy really needs, check the level at the stages where it matters and keep the approach fair and job-related. Explore the product or book a demo — we show how candidate records, vacancy requirements and the pipeline work together in BoldATS for your segment.