Intercultural Practice and Equity · Internal leadership

Equitable Policy and Procedure Governance

Accessibility, plain language, cultural responsiveness and stakeholder impact are cheap to fix while a draft is still a draft. Four lessons on building the review stage that looks at them before the requirements lock.

40–45 minutes · 4 lessons · Voluntary learning

Start learning

Course outline

What a review stage decides, and when it is too late to add one
Governance is not a meeting. It is a written answer to what triggers a review, what gets examined, who decides, and what happens when the answer is not yet.
11 minutes
Four checks that find different things
Accessibility, plain language, cultural responsiveness and stakeholder impact overlap, and none of them substitutes for the others. Each becomes useful only when it is a question someone can answer with evidence.
11 minutes
Placement, authority, and the answer not yet
A stage with undefined authority becomes a comment box or a wall. Deciding in writing whether it advises, conditions or holds is most of the design.
11 minutes
Standing it up, and keeping it honest
One page, one document type, one workflow. Then the three ways this kind of stage fails, and the small number of things worth keeping track of.
11 minutes

Share this course

What you’ll be able to do

Explore and practice

Describe what an equity and access review stage decides, and find the point in your own workflow after which a requirement can no longer be changed without an amendment.
Turn accessibility, cultural responsiveness, stakeholder impact and plain language into four questions a reviewer can answer with evidence rather than with an impression.
Place the review where requirements are still open, and state in writing whether it advises, conditions or holds.
Set a service timeline and an emergency route with a named approver and a required back-check, so urgency does not quietly become the ordinary path.
Draft a one-page equity and access review stage for one real workflow, including what is recorded, who sees it, and how the stage itself will be examined.

What you can take into your work

Four worked scenarios drawn from bulletin publishing, form redesign, a review that has become a bottleneck, and a trial that produced no findings at all.
A knowledge check in every lesson with feedback that explains the usable answer.
Sorting practice that assigns real findings to the check that would catch them, and separates what the review decides from what other offices and affected people decide.
A completed one-page review stage for one workflow, with a trigger, a placement, decision rights, a timeline and a way out.

Choose one document type your team produces regularly. Draw its path from first draft to the day it reaches people, mark the last point at which a requirement could still change, and write the review stage that would sit immediately before that point.

Read the introduction

Almost everything a division decides reaches people as writing: a bulletin, a manual section, a form, a letter template, a contract clause, a work instruction. By the time most of that writing is reviewed for accessibility, plain language or cultural fit, the requirements inside it are already settled, and the only thing left to do is repair. This module is about the step before that. It covers what a review stage actually decides, four checks that find genuinely different problems, where the stage has to sit and what authority it needs, and how to keep it from turning into either a rubber stamp or a wall. It ends with a one-page review stage you can fill in for one workflow and take to the person who owns it.

Equitable policy and procedure governance

One page for adding an equity and access review to a policy workflow

A review that cannot hold anything is a comment box. A review nobody can plan around is a wall. Write down which one yours is.

Keep the four questions and the shape of the stage in view while you set up, run, defend or repair a review step in a bulletin, manual, form, letter or contract workflow.

Placement decides what a review can reach. Put it before the point where a change stops being an edit.
Four checks, because they find different things: accessibility, plain language, cultural responsiveness, stakeholder impact.
A criterion is a question with an answer and a piece of evidence, not a value the reviewer is asked to affirm.
Say in writing whether the review advises, conditions or holds, and name who can approve an exception.
Keep track of the work, not the people. Reflections are private and are never collected.

Write the review stage for one document type on one page, and take it to the person who owns the step it would sit before.

Place it before the lock

Draw the path from first draft to the day it reaches people, and mark where a change becomes an amendment.
Put the early look before clearance, while the requirements are still open.
Add a short confirmation before release: were the early findings resolved, or accepted in writing by a named person?
If the only available placement is after clearance, say plainly that the stage can improve documents and not requirements.

The four questions

Accessibility: can a person get through this document and this procedure, including the hours, channels, windows and formats?
Plain language: state the requirement in one sentence — do, find, prove or wait for, by when, counted from what.
Cultural responsiveness: what does this draft assume the reader already has?
Stakeholder impact: who is helped, burdened, excluded or misunderstood, in what numbers, and who read the draft from outside the drafting team?

Authority, timeline and the way out

Choose deliberately: advises, conditions, or holds. Write the sentence down where drafters can read it.
Publish a service timeline in working days, counted from receipt of a complete draft.
Name the exception approver, what they record, and the date of the back-check.
Define not yet as a real outcome: the finding, the owner, the date, and who is told.

Keep it honest

Compare drafts reviewed with drafts released; a gap is the finding.
Sort every finding into resolved before release, accepted in writing by a named person, or open.
Read one released document yourself against the four questions, at the agreed review point.
Pay outside reviewers, tell them what changed, and keep them as advisors and co-designers rather than an audience.

Who this helps

Policy and program staff, who decide what a requirement says and where it lives, and who carry most of the cost of a late finding.
Quality, compliance and performance staff, who already hold much of the evidence the stakeholder impact question needs.
Contracts, fiscal, grants and procurement staff, whose requirements decide who is able to apply at all, and whose clauses are hardest to change after release.
Executive and senior leaders, who decide the stage's authority, its timeline and whether the exception route stays exceptional — a useful place to start.
Communications, data and operations staff, whose work begins the moment a document is released and who see the consequences first.

Related modules

Leading a reflective DSD team
Quality, complaints, and incident learning
Responsible data and evaluation
Co-design and compensated partnership
Resource allocation and equity

Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.

Sources and further reading

Minnesota Department of Human Services, Content and writing guidelines
The department's own editorial guidance on first-read understanding, descriptive headings, familiar terms and writing suited to the reader — the standard a draft is reviewed against.
PlainLanguage.gov, Federal plain language guidelines
Detailed guidance on audience, organization, useful headings and the vague words that leave a requirement undecided until someone answers the phone.
Minnesota IT Services, Accessibility standard
The state's accessibility standard for digital documents, web content and procurement — the baseline the accessibility check is run against.
Section508.gov, Create accessible documents and content
Federal guidance and practical instruction on accessible documents, forms and digital content, including how accessibility is built in rather than repaired.
W3C Web Accessibility Initiative, Developing organizational policies on accessibility
How organizations write and maintain an accessibility policy, including scope, responsibility, timelines and review — directly relevant to designing a review stage.
ADA.gov, State and local governments (Title II)
U.S. Department of Justice guidance on what a state or local government program must provide, including effective communication and accessible programs, services and activities.
U.S. Department of Health and Human Services, National CLAS Standards
National standards for culturally and linguistically appropriate services, including the governance, leadership, workforce and written-communication standards used in this module.
Minnesota Framework for Universal Multicultural Instructional Design
The design reference for this curriculum: multiple ways to engage, culturally responsive materials and accessible instruction.

All research and sources across the program

Opening your page…

You can still use the navigation while it loads.

Course outline

What a review stage decides, and when it is too late to add one

Governance is not a meeting. It is a written answer to what triggers a review, what gets examined, who decides, and what happens when the answer is not yet.

11 minutes

Four checks that find different things

Accessibility, plain language, cultural responsiveness and stakeholder impact overlap, and none of them substitutes for the others. Each becomes useful only when it is a question someone can answer with evidence.

11 minutes

Placement, authority, and the answer not yet

A stage with undefined authority becomes a comment box or a wall. Deciding in writing whether it advises, conditions or holds is most of the design.

11 minutes

Standing it up, and keeping it honest

One page, one document type, one workflow. Then the three ways this kind of stage fails, and the small number of things worth keeping track of.

11 minutes

Sources and further reading

Minnesota Department of Human Services, Content and writing guidelines

The department's own editorial guidance on first-read understanding, descriptive headings, familiar terms and writing suited to the reader — the standard a draft is reviewed against.

PlainLanguage.gov, Federal plain language guidelines

Detailed guidance on audience, organization, useful headings and the vague words that leave a requirement undecided until someone answers the phone.

Minnesota IT Services, Accessibility standard

The state's accessibility standard for digital documents, web content and procurement — the baseline the accessibility check is run against.

Section508.gov, Create accessible documents and content

Federal guidance and practical instruction on accessible documents, forms and digital content, including how accessibility is built in rather than repaired.

W3C Web Accessibility Initiative, Developing organizational policies on accessibility

How organizations write and maintain an accessibility policy, including scope, responsibility, timelines and review — directly relevant to designing a review stage.

ADA.gov, State and local governments (Title II)

U.S. Department of Justice guidance on what a state or local government program must provide, including effective communication and accessible programs, services and activities.

U.S. Department of Health and Human Services, National CLAS Standards

National standards for culturally and linguistically appropriate services, including the governance, leadership, workforce and written-communication standards used in this module.

Minnesota Framework for Universal Multicultural Instructional Design

The design reference for this curriculum: multiple ways to engage, culturally responsive materials and accessible instruction.