When is a job requirement only a proxy?
A requirement is a proxy when it stands in for a capability without explaining what the person must actually do. A degree may be used as shorthand for analytical work. Five years in one sector may be used as shorthand for handling its operating constraints. An exact job title may be used as shorthand for a set of responsibilities.
Those signals can be relevant, but they are not interchangeable with the capability itself. If the team cannot explain what a requirement is meant to demonstrate, reviewers cannot recognise equivalent evidence and candidates cannot judge whether their experience fits.
The OECD's skills-first hiring guidance describes an approach in which employers translate roles into skill requirements and use qualifications and experience as complementary information rather than the sole basis for hiring. The practical starting point is not to delete every credential. It is to make every important requirement explain its job-related purpose.
Which requirements should remain explicit?
Retain a requirement when the team has confirmed that it is a genuine entry condition. Examples may include a licence needed to perform regulated work, a certification required for a specific task, work permission, or a language capability needed for defined responsibilities. The applicable condition depends on the role and jurisdiction.
Do not remove a genuine condition merely to make a role look skills-based. Instead, record:
- the task or responsibility that creates the condition;
- the exact credential, permission, or capability required;
- when and how it will be verified; and
- whether it must exist at application, before start, or after training.
Everything else deserves a necessity check. “We have always asked for it” is not a job-related explanation.
How do you rewrite a proxy as a skills-based requirement?
Skilltage guidance: use six fields in this order:
- Work or outcome: what must the person do, decide, maintain, or deliver?
- Capability: what knowledge, skill, or judgement enables that work?
- Operating context: at what scale, complexity, independence, or constraint?
- Acceptable evidence: what examples could reasonably demonstrate the capability?
- Trainability: must the capability exist on entry, or can it be developed after joining?
- Priority: is it a hard entry condition, a standard review criterion, or a preference?
The European Commission Pact for Skills report identifies rewriting job descriptions around skills and adapting assessment as parts of a skills-first approach. Rewriting the advertisement alone is not enough: the evidence rule used during review must change with it.
Proxy audit: what is the requirement trying to prove?
| Proxy wording | Question to ask | More direct requirement direction |
|---|---|---|
| “Bachelor's degree required” | Which knowledge or work requires this qualification? | Name the relevant knowledge or retain the degree only where it is a confirmed condition |
| “Five years of experience” | What should the person be able to handle independently? | State the work, complexity, and evidence of responsibility |
| “Must have been a production planner” | Which responsibilities from that role matter? | Describe planning, constraint management, coordination, and decisions |
| “Experience in our exact sector” | Which sector conditions cannot be learned after entry? | Name the specific environment, rule, process, or risk knowledge |
| “Expert in system X” | Is the tool itself essential, or is the workflow transferable? | Describe the required task and whether equivalent tools count |
| “Natural leader” | Which observable behaviour is relevant? | Describe the decisions, coordination, feedback, or change work involved |
The CIPD employer guide recommends clear, specific, behaviour-based requirements and asks employers to keep requirements necessary for the role. Treat that as a disciplined authoring test, not as proof that any particular rewrite is legally sufficient or predictive of performance.
Worked example: a production-planning role
The inherited person specification says:
Bachelor's degree in supply chain management, five years in food manufacturing, and previous title of Senior Production Planner.
The hiring manager explains the actual need: the person must publish a feasible weekly plan, resolve material and capacity conflicts with production and procurement, and communicate the effect of changes.
A skills-based rewrite could be:
| Field | Reviewed requirement |
|---|---|
| Work or outcome | Produce and revise a weekly plan that accounts for demand, material availability, capacity, and changeovers |
| Capability | Interpret planning inputs, identify conflicts, compare options, and coordinate a documented decision |
| Operating context | Multiple product lines with changing priorities and dependencies across production and procurement |
| Acceptable evidence | Ownership of production, workforce, service, inventory, or project planning; examples of resolving competing constraints; equivalent terminology and sectors count |
| Trainability | The organisation's planning system and product rules can be learned after entry; independent constraint reasoning is expected on entry |
| Priority | Standard requirement; any genuinely required certification is listed separately as hard |
This rewrite does not assert that a degree or five years of experience has no value. It explains what those signals were being used to predict and gives reviewers a basis for recognising other credible evidence.
Can a skills taxonomy write the requirement for you?
No. ESCO is a multilingual classification that describes occupations and skills and links them through common terminology. It can help a team discover vocabulary, compare related occupations, or notice a missing capability.
It cannot know the actual work, constraints, priorities, training capacity, or evidence standard in your organisation. Use a taxonomy as a prompt and reference, not as a complete job analysis or an automatic list of must-haves.
Checklist before the requirement is confirmed
- The requirement starts with real work, an outcome, or a confirmed condition.
- The capability is described without relying on a title, sector, degree, or years alone.
- The operating context explains the level or complexity needed.
- More than one plausible form of evidence can count where appropriate.
- The team has decided what can be learned after entry.
- Hard, standard, and preferred requirements are visibly separate.
- Missing information has a treatment other than automatic failure unless a confirmed hard condition requires it.
- The public wording and the review rule describe the same role.
- A second reviewer can apply the requirement without inventing a hidden threshold.
How does Skilltage support this work?
Skilltage's Define workflow creates an editable job-brief draft from opening context. A recruiter can edit requirement text, assign hard, standard, or preferred priority, add notes, inspect available source wording, add or remove requirements, and explicitly confirm the set. Confirmed requirements gate job-ad generation and candidate intake. The job-ad draft remains editable and exportable.
These controls make human review visible; they do not determine whether a requirement is lawful, necessary, inclusive, or valid for predicting performance. Skilltage does not automatically remove proxy requirements or provide a universal skills taxonomy. The recruiter remains responsible for checking and confirming the role basis.
Limitations and decision boundaries
A skills-based requirement does not prove that a selection process is fair, lawful, or effective. Observable wording can still encode an irrelevant threshold, and candidates may omit relevant evidence from a CV. Local employment, equality, accessibility, qualification, and data-protection requirements still need appropriate review.
Do not convert every credential into a vague capability or assume every skill can be assessed from application documents. Interviews, work samples, references, accommodations, and professional judgement may be needed later in the process.
Start with a review-ready hiring intake brief, connect the rewritten requirements to explicit CV screening criteria, and check that the job ad and review rules stay aligned. During review, use the separate guide to recognise transferable experience.
Next step
Take the five most restrictive requirements in one current person specification. For each, write what it is meant to prove, the work it supports, acceptable evidence, and whether it can be learned after entry. Retain the original threshold only when the team can explain why it is genuinely necessary.