Case 55
Inclusive Language and Bias Check on a Job Description
Scenario
The new job description is ready to post. Your company has committed to widening its applicant pool and wants a check before anything is published.
Why this framework
Uses PIN. It is a focused review with a person making the final edits.
Example context
Job description to check, Planning Analyst, Fernway Logistics (draft for posting): "About the role: Join our young, dynamic planning team in a fast-paced environment. You will own the weekly labour capacity plan for two depots and build the peak-season shift model. What you will do: Build the weekly capacity plan; present forecasts to depot managers; challenge assumptions; maintain the shift-pattern model; produce a short weekly report. What you need: A recent graduate or someone with 2 to 4 years' experience; he or she will be a confident communicator who can handle pushy depot managers; strong Excel modelling; excellent written English; SQL; must be able to lift 15kg; a digital native comfortable with new tools. Nice to have: logistics or retail planning experience; dashboard tools. Practical: Daventry hub, 3 days on site. £32,000 to £37,000. 37.5 hours." Approved hiring brief, version 1: must-haves: builds spreadsheet models others rely on; explains numbers to non-specialists and handles challenge calmly; reliable weekly routine to fixed deadlines; clear written English. Nice-to-haves: SQL, planning experience, dashboard tools, warehouse systems knowledge. Non-criteria: degree, years of experience, driving licence, accent. The role is desk-based; no lifting. Inclusive hiring guidelines (extract): use "you" not "he or she"; avoid age-coded terms (young, recent graduate, digital native, energetic); avoid jargon and clichés (fast-paced, rockstar); list only requirements in the approved brief; state adjustments available; keep must-haves to what is needed on day one.
Prompt
Purpose: Check this job description for wording that could put off qualified people or exclude them unfairly, before we post it.
Context: Use the attached job description, the approved hiring brief it came from, and our inclusive hiring guidelines. The guidelines are the final word on house style.
Narrow the ask: A table with: the exact phrase, the concern (for example gendered or age-coded wording, an unnecessary requirement, jargon, a requirement not in the brief, a physical requirement the role may not need), and a suggested rewrite. Then list any must-have that is stricter than the brief. Do not rewrite the whole document. Explain concerns plainly and say where a concern is a judgement call rather than a clear problem.
Materials (pasted here in place of the attachments):
Job description to check, Planning Analyst, Fernway Logistics (draft for posting):
"About the role: Join our young, dynamic planning team in a fast-paced environment. You will own the weekly labour capacity plan for two depots and build the peak-season shift model.
What you will do: Build the weekly capacity plan; present forecasts to depot managers; challenge assumptions; maintain the shift-pattern model; produce a short weekly report.
What you need: A recent graduate or someone with 2 to 4 years' experience; he or she will be a confident communicator who can handle pushy depot managers; strong Excel modelling; excellent written English; SQL; must be able to lift 15kg; a digital native comfortable with new tools.
Nice to have: logistics or retail planning experience; dashboard tools.
Practical: Daventry hub, 3 days on site. £32,000 to £37,000. 37.5 hours."
Approved hiring brief, version 1: must-haves: builds spreadsheet models others rely on; explains numbers to non-specialists and handles challenge calmly; reliable weekly routine to fixed deadlines; clear written English. Nice-to-haves: SQL, planning experience, dashboard tools, warehouse systems knowledge. Non-criteria: degree, years of experience, driving licence, accent. The role is desk-based; no lifting.
Inclusive hiring guidelines (extract): use "you" not "he or she"; avoid age-coded terms (young, recent graduate, digital native, energetic); avoid jargon and clichés (fast-paced, rockstar); list only requirements in the approved brief; state adjustments available; keep must-haves to what is needed on day one.Example output from ChatGPT
Inclusive hiring review: Planning Analyst, Fernway Logistics
Overall assessment: The draft needs changes before posting. It contains several clear breaches of the approved hiring brief and inclusive hiring guidelines, particularly age-coded language, unnecessary experience requirements, and physical requirements unrelated to the role.
The review below uses only the three supplied documents. The approved brief determines job requirements, and the inclusive hiring guidelines determine wording.
1. Wording review
| Exact phrase | Concern | Suggested rewrite |
|---|---|---|
| "young, dynamic planning team" | Clear problem: age-coded. "Young" may discourage experienced candidates. "Dynamic" adds little useful information. | "Join our planning team supporting two depots." |
| "fast-paced environment" | Clear problem: cliché. Explicitly discouraged by the guidelines. It does not explain the actual work. | "You will deliver weekly plans to fixed deadlines." |
| "own the weekly labour capacity plan" | Judgement call: jargon. "Own" may be familiar internally but could be less clear to external applicants. | "Be responsible for producing the weekly labour capacity plan." |
| "challenge assumptions" | Judgement call: unclear expectation. Could sound confrontational without context. | "Review planning assumptions and explain where forecasts may need adjusting." |
| "A recent graduate or someone with 2 to 4 years' experience" | Clear problem: age-coded and unauthorised. Degrees and years of experience are explicitly non-criteria. | "You can build reliable spreadsheet models that others use to make decisions." |
| "he or she" | Clear problem: gendered wording. Directly contradicts the guidelines. | "You" |
| "confident communicator" | Judgement call: subjective. May discourage capable candidates who are less outgoing. The brief specifies observable communication abilities. | "You can explain numbers clearly to non-specialists and respond calmly to questions." |
| "handle pushy depot managers" | Clear problem: unnecessarily negative wording. "Pushy" describes colleagues negatively and makes the work sound adversarial. | "Respond calmly and constructively when depot managers question forecasts." |
| "strong Excel modelling" | Clear problem: stricter than the brief. The brief requires spreadsheet modelling, not proficiency in a particular application. | "You can build reliable spreadsheet models that others depend on." |
| "excellent written English" | Clear problem: higher standard than approved. The brief asks for clear written English, not an undefined level of excellence. | "You can communicate clearly in written English." |
| "SQL" | Clear problem: incorrect classification. SQL is explicitly nice-to-have, not essential. | Move to "Nice to have: SQL skills." |
| "must be able to lift 15kg" | Clear problem: unnecessary physical requirement. The approved brief confirms the role is desk-based with no lifting. | Remove entirely. |
| "a digital native" | Clear problem: age-coded. Explicitly prohibited by the guidelines. It can imply that younger applicants are preferred. | Remove. Do not replace with another technology requirement unless the brief supports it. |
| "comfortable with new tools" | Clear problem: unsupported requirement. Although potentially reasonable, it is not a must-have in the approved brief. | Remove from the essential criteria. |
| "Practical: Daventry hub, 3 days on site. £32,000 to £37,000. 37.5 hours." | Clear problem: missing adjustment statement. The guidelines require applicants to be told adjustments are available. | Keep the practical details and add: "You can request adjustments during the recruitment process." |
2. Must-haves stricter than the approved brief
| Draft requirement | Approved brief | Required action |
|---|---|---|
| Recent graduate | Degree is explicitly a non-criterion | Remove |
| 2 to 4 years' experience | Years of experience explicitly excluded | Remove |
| Strong Excel modelling | Ability to build reliable spreadsheet models | Remove the Excel-specific restriction |
| Excellent written English | Clear written English | Use the brief's wording |
| SQL | Nice-to-have | Move to optional criteria |
| Ability to lift 15kg | Desk-based role; no lifting | Remove |
| Digital native | Not required; age-coded term prohibited | Remove |
| Comfortable with new tools | Not listed as a must-have | Remove as a requirement |
Finding: Eight requirements or restrictions are stricter than, or unsupported by, the approved hiring brief.
3. Missing or underrepresented approved requirements
The draft also needs to represent the actual essential abilities more accurately.
| Approved must-have | Current coverage | Recommendation |
|---|---|---|
| Builds spreadsheet models others rely on | Partially covered by "strong Excel modelling" | Focus on reliability and practical modelling ability |
| Explains numbers to non-specialists and handles challenge calmly | Partially covered by "confident communicator" | State both abilities explicitly |
| Reliable weekly routine to fixed deadlines | Missing from the essential criteria | Add: "You can organise recurring work and meet fixed weekly deadlines." |
| Clear written English | Present, but overstated | Replace "excellent" with "clear" |
The existing nice-to-haves, logistics or retail planning experience and dashboard tools, are consistent with the brief. SQL should join them. Warehouse systems knowledge is another approved optional skill that could be added.
4. Recommendation before posting
Revise before publication
The eight unsupported or stricter requirements should be removed, corrected or reclassified before the advert is published.
Three actions matter most:
- Make the must-haves match the brief exactly in substance. Assess candidates on four abilities: spreadsheet modelling, explaining numbers and handling challenge calmly, reliable weekly delivery, and clear writing.
- Remove exclusionary wording. In particular, remove references to age, experience length, gender and unnecessary physical ability.
- Complete the practical information. Keep the Daventry location, three on-site days, 37.5-hour working week and salary range. Add the recruitment adjustment statement.
Judgement calls versus clear problems: "Own", "challenge assumptions", and "confident communicator" are not inherently discriminatory. Their concern is clarity and whether applicants can understand what success looks like. The other flagged requirements and wording conflicts are directly supported by the supplied guidelines or approved brief.
Final conclusion: The job description describes a role that could reasonably attract candidates from several backgrounds, but the current wording unnecessarily narrows that pool. Aligning it with the approved brief would make the advert clearer, fairer and more useful for self-selection, without lowering the standards required to do the job.
