Remove exclusionary wording

Change the wording.
Keep the requirements.

Replace wording about age, gender, disability, origin, or family status with wording about the actual task. Facts, obligations, and figures stay put, precise legal and technical terms are preserved, and we never speak for any group.

Wording onlyRequirements holdNo voice borrowed

Review the rewrite

Your result will appear here

We find wording that describes people rather than capability, restate it as a concrete condition or drop it, and mark precise terms to keep and hard requirements you must confirm.

SAMPLE OUTPUT

Here is exactly what you receive.

This is the complete output for the source text in the demo above: an inclusivity score, itemised changes, why certain terms were kept, items to confirm, and the rewritten text. It is a demonstration, not a customer case.

SAMPLE

Rewrite result (sample)

Inclusivity score88/100

+50

Remove the age-based filter

“Young and energetic” turns age into a job condition, but the source gives no age-related capability requirement, so it is removed with the reason stated.

Remove the gender-based filter

“Suits men better; women may find it hard to cope” substitutes gender for a capability judgement and is unrelated to the work, so it is removed and replaced by a factual statement about workload.

Turn a trait into a behaviour and keep the fact

“Everyone is normal” becomes an expectation about communication, while overtime stays as a real part of the role, with a prompt to add frequency and compensation instead of softening it.

Rewritten text

# Role description (inclusive rewrite)

We are hiring an engineer and welcome candidates of any age, gender, and background.

**Workload**: this role has demanding periods around releases, including overtime.

TODO: add roughly how often overtime occurs and whether time off in lieu or overtime pay applies; candidates need this to judge the role.

**Teamwork**: you will need clear, timely communication with the rest of the team.

**What changed**
- “Young and energetic”: age is not a capability requirement for this role, so it was removed.
- “Suits men better”: gender is unrelated to the work, so it was removed.
- “Everyone is normal”: that phrasing excludes disabled colleagues, so it became a statement about communication.

**What stayed**: overtime is a real part of the role, so it stays rather than being softened.

TODO: if the role does have physical or other hard requirements, state them as concrete conditions instead of as traits of a type of person.

WHAT REWRITING DOES

Describe the work, not the kind of person.

Drop traits that carry no capability

Age, gender, family status, and origin say nothing about whether someone can do the job. Removing them is usually the safest edit.

State the behaviour instead

“Can handle a demanding release schedule” is more accurate than “young”. Write the standard and you can actually screen against it.

Write hard requirements as conditions

Physical tasks, licences, and language levels belong as concrete conditions: how much, which certificate, what level. Not as a preference for a type of person.

WHY IT IS WORTH DOING

One line makes half your readers close the page.

Wording decides who applies

Put “men preferred” in a post and qualified women may never apply. You never see the CV.

Bias hides inside praise

“Young and energetic” reads as a compliment and acts as an age filter, which is exactly why it survives review.

Rewording is not lowering the bar

Remove the trait, write the capability concretely, and your screening standard gets clearer and easier to defend.

Note: a common practice in inclusive-language guidance is to replace descriptions of people with descriptions of the task, an approach adopted by many writing and hiring guides. Industries and jurisdictions set their own compliance requirements for hiring, medical, and public-service text. This site rewrites at the wording level; it is not a compliance check, is not legal or HR advice, and does not represent the position of any group.

REWRITE DEMO

One job paragraph, rewritten.

Before

We are looking for a young, energetic programmer to join the team. This role requires frequent overtime, so it suits men better; women may find it hard to cope. Everyone on the team is normal, so communication is not a problem.

Rewritten

# Role description (inclusive rewrite)

We are hiring an engineer and welcome candidates of any age, gender, and background.

**Workload**: this role has demanding periods around releases, including overtime.

TODO: add roughly how often overtime occurs and whether time off in lieu or overtime pay applies; candidates need this to judge the role.

**Teamwork**: you will need clear, timely communication with the rest of the team.

**What changed**
- “Young and energetic”: age is not a capability requirement for this role, so it was removed.
- “Suits men better”: gender is unrelated to the work, so it was removed.
- “Everyone is normal”: that phrasing excludes disabled colleagues, so it became a statement about communication.

**What stayed**: overtime is a real part of the role, so it stays rather than being softened.

TODO: if the role does have physical or other hard requirements, state them as concrete conditions instead of as traits of a type of person.

Demo sample: age and gender filters removed, “normal” restated as a communication expectation, and the overtime fact kept with a prompt to add detail. Paste your text to get your version (sign-in required; one credit per run).

WHY YOU CAN TRUST IT

We put “do not change the requirements” into our product principles.

Facts and obligations stay

Duties, assessment criteria, and service scope are content. We change wording about people, never loosening or tightening a requirement.

Precise terms survive

Defined legal names, medical terms, and technical specifications stay as written instead of being generalised for tone.

We speak for nobody

We add no group's position, experience, or needs, and invent no representative opinion. Anything drawing on lived experience has to come from the person themselves.

Content is not stored

Submitted text is used for this single AI request and is not intentionally persisted. See the Privacy Policy.

FAQ

Ask these before you pay.

Will you change my role requirements?

No. Genuine capability, qualification, and schedule requirements stay. Only wording about people that carries no capability is changed, and real hard requirements are restated as concrete conditions rather than deleted.

Can you handle technical or legal text?

Yes, without giving up precision. Defined legal names, medical terms, and technical specifications stay verbatim with the reason stated, rather than being generalised to read more smoothly.

Will you add a group's perspective?

No. We invent no group's experience, needs, or views. If lived experience needs quoting, it has to come from the person or from source material you supply.

What does one rewrite cost?

One credit per run, usually done in seconds, returning the draft, the change notes, and items to confirm.

Do credits expire?

No. Credits never expire - whatever you do not use carries over to the next cycle instead of resetting.

Is there batch processing or an API?

Not yet. Each run processes one document and consumes one credit; there is no bulk upload or API today. Email us with your use case and we will assess it.

Is my content stored?

Not intentionally. Text is used for this single AI request only. See the Privacy Policy.

What text fits?

Job posts and role descriptions, internal policies and handbooks, public service notices, product and help documentation, training material - any text that has to read as addressed to everyone.

SIMPLE PRICING

Prove the value before you upgrade.

Starter

$9/ month

For an occasional publishing cadence, with a focused monthly credit allocation.

50 optimization credits per monthly renewal
Complete GEO analysis
Chinese and English output
Markdown export

Pro

Recommended$29/ month

For frequent publishers who iterate on content continuously.

250 optimization credits per monthly renewal
Complete GEO analysis
Chinese and English output
Markdown export

Advanced

$79/ month

Our largest monthly credit allocation, for the heaviest continuous usage.

1,000 optimization credits per monthly renewal
Complete GEO analysis
Chinese and English output
Markdown export

Credits never expire: unused credits carry over instead of resetting. Credits apply to this site only and are not shared with other sites.

Prices shown are USD baselines; final currency, taxes, and discounts are determined by Paddle for the checkout location.