How long should a charity EDI policy be?

For most small and medium charities, four to six pages of plain English, plus appendices. Policies that run to 30 pages are almost never read in full. Length signals seriousness, but it does not produce behaviour.

Should the EDI policy and the safeguarding policy be combined?

Keep them separate but cross-referenced. EDI is about how the organisation treats people in relation to identity and access; safeguarding is about preventing harm. They overlap, but conflating them weakens both.

How often should the EDI policy be reviewed?

At least every two years at trustee level, with an annual lighter touch operational review. Major changes (new service, new workforce model, external incident) should also trigger a review out of cycle.

An EDI Policy That Staff Actually Use: A Practical Guide

Most charity equality, diversity and inclusion policies sit in a folder and shape almost nothing. A pragmatic approach to writing an EDI policy that staff actually use, with the structural decisions that turn paper commitments into operational behaviour.

Most charity EDI (equality, diversity and inclusion) policies are written for a regulator that does not read them. They run to 30 pages, cite the Equality Act in full, and are filed in a folder on the shared drive that nobody opens between annual reviews. Staff have not read them. Trustees signed them off without amendment. Practice across the organisation is unchanged.

An EDI policy that actually shapes behaviour is short, structured for the situations staff face, and tied to operational hooks that bring it into daily practice. What follows is a guide to writing such a policy for a UK charity in 2026.

What an EDI policy is for

It is not the same as the Equality Act

The Equality Act sets the legal floor: protected characteristics, prohibited conduct, the public sector equality duty for some charities. The EDI policy is the organisation's commitments and practice on top of the legal floor. Confusing the two produces policies that recite law rather than commit to action.

Its purpose is decision support

A useful EDI policy helps staff make better decisions in situations they actually face: recruitment, service design, supplier choice, event planning, internal conflict, beneficiary feedback. If the policy does not help with those decisions, the policy is not useful.

A structure that holds up

Section 1: Plain-language statement of intent (half a page)

What the charity commits to, in language any staff member could repeat from memory. Avoid recitations of every protected characteristic; one or two sentences that name commitment, accountability and scope.

Section 2: Legal context (half a page)

Brief reference to the Equality Act and any sector-specific duties, with links to the full text. Not the place to reproduce the statute.

Section 3: Recruitment and employment (1 page)

Specific practices: job advert language, anonymous shortlisting, interview panel composition, accessibility of recruitment process, reasonable adjustments, fair pay practices. This is where most of the operational impact sits.

Section 4: Service design and delivery (1 page)

How EDI shapes the design and delivery of services: who is involved in design, how feedback is gathered, how access barriers are reviewed, how language and translation are handled.

Section 5: Suppliers, partners and events (half a page)

Standards for suppliers, partner expectations, event accessibility and inclusion. Specific commitments here close common gaps (e.g., venues that are not wheelchair-accessible, panels with no diversity of voice).

Section 6: Raising concerns and accountability (1 page)

How staff, volunteers, beneficiaries and partners raise EDI concerns, who handles them, what happens next, and how confidentiality is managed. Cross-reference whistleblowing and grievance policies.

Section 7: Governance, review and reporting (half a page)

Who in the senior team owns EDI, which trustee or committee provides oversight, how often the policy is reviewed, and what data is reported to trustees and (where appropriate) publicly.

Four to five pages in total, plus appendices for definitions and detailed processes. Long enough to be substantive; short enough to be read.

Operational hooks that bring the policy alive

Recruitment templates that embed the policy

If the policy says job adverts should avoid jargon and unnecessary qualifications, the job advert template should enforce it. The most reliable way to make a policy operational is to embed it in the templates and workflows staff already use.

Service design checklists

A short checklist used at the design stage of any new service or campaign: who has been involved, what access considerations apply, how feedback will be gathered. Practical, lightweight, and impossible to skip if the workflow requires it.

Supplier onboarding questions

When onboarding new suppliers above a defined value threshold, ask a small number of EDI-relevant questions and record the answers. Avoids the policy being aspirational while procurement decisions stay unchanged.

Annual EDI conversation in performance reviews

One question in the annual review: what have you observed or done this year in relation to EDI, and what would help you do more. Light touch, but it surfaces issues and builds shared responsibility.

Governance that keeps it honest

A named senior owner and a named trustee

A member of the senior management team owns EDI operationally; a named trustee or committee provides oversight. Without these, EDI becomes an ambient responsibility nobody specifically holds.

Annual reporting to trustees

An annual report covering workforce data, recruitment data, service access data, concerns raised and progress against any commitments. Disaggregated where data is sufficient, anonymised where not. Trustees should expect to see this, and challenge it.

Honest acknowledgement of limits

Where the charity has not made progress, the report should say so. EDI reports that read uniformly positive across every dimension lose credibility quickly. Trustees and staff should be able to see where work remains.

Mistakes that quietly hollow out an EDI policy

Cutting and pasting from another charity

EDI policies cut and pasted from another organisation rarely fit the context. The legal sections might survive; the practice sections almost never do. Write your own, even if shorter.

Equating EDI with annual training

Mandatory annual EDI e-learning has limited evidence of changing behaviour. It can be part of the picture, but should not be the bulk of the response.

Conflating representation with inclusion

A diverse workforce that does not feel included produces high turnover and low candour. Inclusion practice (who speaks in meetings, who shapes decisions, who feels heard) sits alongside representation, not below it.

Letting beneficiary EDI slide

Workforce EDI gets most of the policy attention. Beneficiary EDI (who is and is not accessing services, who shapes design, whose voice is missing) is often where the biggest mission-aligned issues sit.

A four-page EDI policy that staff use beats a thirty-page policy nobody reads, every time. Length is not seriousness; usage is.

A six-month implementation plan

Month 1: name the senior owner and the trustee/committee owner. Audit the current policy honestly.
Month 2: redraft the policy in plain English, four to six pages, structured as above.
Month 3: build the operational hooks (recruitment templates, service-design checklist, supplier onboarding questions).
Month 4: socialise across the team with one all-staff session and one trustee briefing.
Months 5 to 6: gather the first reporting data (workforce, recruitment, concerns) and bring it to trustees.

Five steps, six months. The point is not perfection; it is moving from a policy that exists to a policy that is used.

An EDI Policy That Staff Actually Use