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.

What you’ll be able to do

Draft a one-page equity and access review stage for one real workflow, and name the three ways such a stage fails along with the check that would catch each one.
Compare the responses to this question and explain your choice: What should the leadership team make of a completely clean record?
Draft a one-page equity and access review stage for your work, including trigger and scope, where it sits in the workflow, the four questions and the evidence each needs.

Start narrow, and write it down

The most common way this work fails is not resistance. It is scope. A division decides that every public-facing document will go through an equity and access review, announces it, and then discovers that nobody has the hours, the criteria are unanswerable, and the release calendar does not move. Within two months the stage exists on paper and drafts go around it, and the next attempt has to overcome the memory of the first.

One document type. One workflow. One named owner for the step, one service timeline, one exception route. A page that a drafter can read in three minutes and a reviewer can work from. Once it runs for a season and produces findings that actually changed documents, extending it is an easy conversation, because you will have examples rather than a principle.

Write it down because unwritten stages drift. Everything below is the minimum that has to be on the page: what triggers it, where it sits, what gets examined and with what evidence, what authority it carries, how long it takes, how an exception works, what is recorded, and how the stage itself gets looked at.

A one-page equity and access review stage

Six lines that turn four questions into a step someone owns, with a timeline and a way out.

Trigger and scope Every revision to the provider bulletin series and to the manual sections those bulletins reference. Not internal scheduling notices, which continue through the standard communications review.

Where it sits in the workflow Early look: after the drafting team has a working draft and before legal and communications clearance, while the requirements can still change. Confirmation: a short check before release that the early findings were resolved or accepted in writing.

The four questions and the evidence each needs Accessibility: the draft in a working format, plus what a person must do, find, prove or wait for. Plain language: the requirement in one sentence, with days and a start date. Cultural responsiveness: what the draft assumes the reader already has. Stakeholder impact: what the division knows about who completes this step, and who read the draft from outside the drafting team.

Authority, timeline and exception route Conditional. Findings must be resolved before release or accepted in writing by the named document owner. Five working days from receipt of a complete draft. Exception: the division director may release with findings open, recorded with a name and a date for the back-check.

What is recorded and who sees it Drafts reviewed, findings by question, findings resolved before release, findings accepted and by whom, days in the stage, and what changed after outside review. Recorded about documents and steps, never as a rating of a person or a team.

How the stage itself is examined At the agreed point: ask reviewers what they lacked, ask two drafters what changed, read one released document against the four questions, and ask the compensated outside reviewers whether they were told what happened to their input.

Copy these six lines, fill them in for one workflow you own or influence, and take the page to the person who owns the step you named in line two.

Browse and download only. Staff notes are not typed or saved on this page.

Three ways this stage fails, and what catches each one

The rubber stamp

Everything passes. The record is clean, the stage costs almost nothing, and it reports beautifully. Usually the cause is one of three things: criteria that cannot produce a finding, reviewers who receive a document and nothing else, or findings handled in a hallway conversation and never written down. What catches it: read one released document yourself against the four questions, and ask a drafter what actually changed after their last review. If the answer is nothing, you have the stage's real result.

The wall

No service timeline, no exception route, broad and undefined authority. Drafting staff cannot plan around it, so they stop trying. Work moves to document types the stage does not cover, effective dates get described as immovable when they are not, and the stage hears about drafts late or not at all. What catches it: compare the number of drafts the stage sees with the number the division actually released in the same period. A gap is the whole finding.

The parallel record

Findings are careful, well written, filed, and unconnected to what goes out the door. This is the most demoralizing of the three, because everyone involved is working hard. It is almost always an authority problem rather than an effort problem. What catches it: for each finding, record resolved before release, accepted in writing by a named person, or open. If the third category is large, the authority line on your page is not being used.

Worth keeping track of, and worth leaving alone

Keep track of: drafts reviewed, and how that compares with drafts released.
Keep track of: findings by question, so you can see which check is doing the work and which one is never used.
Keep track of: findings resolved before release, findings accepted in writing and by whom, and findings still open.
Keep track of: working days in the stage, so the timeline you published stays honest.
Keep track of: what compensated outside reviewers said, what changed because of it, and whether they were told.
Leave alone: any count that becomes a rating of a person, a supervisor or a unit. It will not improve drafts; it will reduce the number of drafts the stage is shown.
Leave alone: anything a staff member wrote in a private reflection. Reflections in this program are not collected and are nobody else's business.

Protect the stage from your own calendar

What you can change

You control whether the exception route is used for genuine statutory deadlines or for ordinary schedule pressure, and you control whether the back-check actually happens.

What to watch for

Do not approve the first few exceptions quietly. The first three uses of an exception route set its meaning for everyone watching, and a back-check that is skipped once is a back-check that has been retired.

Your next step

Before the next exception is requested, write down what counts as one and who approves it, and put the back-check on a date rather than on a good intention.

Which record tells you the most about whether an equity and access review stage is real?

The number of drafts that passed the review with no findings, since a high number shows the drafting practice is strong.

The number of drafts reviewed compared with the number released, together with how many findings were resolved before release, accepted in writing by a named person, or left open.

The average time a draft spends in the stage, since a short average shows the stage is not creating delay.

Try a situation

A DSD leadership team approved a limited trial: every revision to one manual section goes through the new equity and access review before clearance. Three months in, the record shows twelve drafts reviewed and no findings on any of them. The trial is now up for a decision about whether to extend it to other document types.

What should the leadership team make of a completely clean record?

Treat it as evidence that the division's drafting practice is already sound, and extend the stage to other document types on that basis.

Conclude that the stage is not finding enough to justify the time it takes, and retire it.

Treat the clean record as the first thing to examine: whether reviewers received enough to answer the four questions, whether anyone outside the drafting team read the drafts, whether findings were handled in conversation and never recorded, and whether the criteria can produce a finding at all.

Carry this forward

Start with one document type and one workflow. A stage that covers everything on paper and nothing in practice teaches people that the stage is decorative, and that lesson is hard to unteach.
Three failure modes account for most of it: the rubber stamp, where nothing is ever found; the wall, where there is no timeline and no way out; and the parallel record, where findings are written down carefully and the document goes out unchanged.
Keep track of the work, not the people. Drafts reviewed, findings by question, findings resolved before release, findings accepted and by whom, and days in the stage will tell you whether the stage is real. Ranking teams will only tell you who stopped sending drafts.
Community reviewers are compensated advisors and co-designers, told what happened to their input. They are partners in this work and never learners in it.

A one-page review stage you can copy and fill in, a scenario about a trial that produced no findings at all, and a knowledge check on what a clean record actually tells you.

Fill in the review stage for one workflow, take it to the person who owns the step it would sit before, and agree on a start date, a service timeline in working days, and the point at which you will look at how the stage is working.

Your next step

What is the smallest version of this stage you could actually start?

Pick one document type your team produces regularly, and only that one.

Name the step it would sit before, and the person who owns that step.

Write the four questions and the single piece of evidence each one needs.

Set a service timeline in working days, an exception route, and a date to look at how the stage is working.

Browse and download only. Course notes are not typed or saved on this page.

Mark this lesson complete

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.