11 minutes

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.

What you’ll be able to do

Describe what an equity and access review stage decides, and identify the point in your own division's workflow after which a requirement becomes expensive to change.
Compare the responses to this question and explain your choice: What is the most useful thing to do with that observation?
Document a next step for What a review stage decides, and when it is too late to add one: Draw your own division's path for one kind of document, from first draft to the day it reaches people, and mark the last point at which a requirement could still be changed without a formal amendment.

Governance is the part nobody sees

Almost everything the Disability Services Division decides reaches people as writing. A manual section, a bulletin, a form, a letter template, a web page, a contract clause, a work instruction a lead agency follows. None of it is neutral. Every requirement inside it quietly decides who will find the process straightforward and who will spend a month on it.

Governance is the set of rules about what happens to that writing before it goes out: which drafts get reviewed, at what point, against what criteria, by whom, and with what authority to say not yet. Divisions almost always have some of this already. Legal review, communications review, a clearance step, an accessibility fix near the end, translation for the documents someone flagged as vital. The question this module asks is narrower and more useful. Are accessibility, plain language, cultural responsiveness and stakeholder impact examined while the requirements are still open, or only after they are settled?

The difference is not a matter of how much anyone cares. Reviewers who arrive after clearance are handed a finished document and a release date. They can catch a missing heading structure, an unlabeled table, an image with no text alternative. They cannot ask why the process requires an in-person visit, because that question is no longer in front of them. Late review turns design questions into repair work, and repair work is what a busy calendar defers first.

Where access work usually sits, and what that placement costs

Accessibility arrives as remediation

A document is written, cleared, and then sent for an accessibility fix. Headings get tagged, contrast gets corrected, a text alternative is added. All of that is real work and worth doing. None of it touches the procedure: the ten-day clock, the in-person signature, the phone line open only on weekday mornings. Those are access questions too, and by the time the remediation step sees the file, they are decisions rather than options.

Translation is scheduled after the decision

Translation placed at the end has two effects. The first is timing: people who read in another language receive the requirement later than everyone else, and the clock usually started for them on the same day. The second is harder to see. A sentence written without translation in mind is often built out of idioms, program shorthand and long conditional clauses, and the translator inherits all of it. Writing with the translated version in view changes the original sentence, and that only happens if translation is present while the sentence is still being written.

Outside input is collected after the choice is made

Asking people what they think of a finished draft is a different activity from asking them what the requirement should be. The first produces reactions the division can acknowledge; the second produces design. When people with disabilities, families, interpreters and culturally specific organizations are brought in as compensated advisors and co-designers, the value comes almost entirely from the timing. After clearance, the only honest thing to offer them is a chance to comment on something that is not going to change.

Plain language is treated as copy editing

Plain language is often handled as a final pass over the wording: shorter sentences, simpler words, fewer acronyms. Useful, and not the same thing. The plain language question that matters in governance is what the reader has to do, find, prove or wait for, stated in one sentence. Answering that question frequently reveals that the requirement itself is unclear, not just the sentence describing it, and that discovery is worth much more before clearance than after.

One revision, four desks

She has a policy change to implement, an effective date she did not choose, and three other assignments. The draft is technically correct and cleared. The access items are real and she has queued them; the bulletin has to go out on Friday because the change takes effect the following month.

Put the stage before the lock, not after it

What you can change

You control where a review sits in a workflow you own, and whether its criteria are written down anywhere a drafter can read them.

What to watch for

Do not add reviewers to the end of a process and call it governance. A reviewer who receives a cleared document and a release date can only recommend repairs, and will be blamed for the delay when they do.

Your next step

Find the last point in one of your workflows where a requirement can still change, and move the access and equity questions to the step before it.

We did everything right on that bulletin. Legal cleared it, communications cleared it, the format fix went in two weeks later. And then a county worker told me she had spent the whole month explaining that the ten-day clock started on the date printed on the letter, not the day it landed in the mailbox. She could have told us that in five minutes. Nobody asked her, because by the time anyone thought to, the letter was already out.
Composite DSD staff perspective, illustrative

A division adds an accessibility reviewer to the final step of its publishing workflow, immediately before a document is released. What is the most accurate description of what that change accomplishes?

It closes the gap, because every document now receives an accessibility review before it reaches the public.

It will catch document-level problems such as heading structure, contrast and text alternatives, and it will rarely change a requirement, because by the final step the requirements are already settled.

It adds delay without benefit, since accessibility work is handled more efficiently as a correction after release.

Try a situation

A DSD program analyst has finished a revised procedure for a waiver service change. Legal and communications clearance are done and the bulletin posts Friday. Alternate formats and translations are queued for after posting. A quality analyst reads the draft and notices two things: the new step requires a document most people have to request in person from a county office, and the response window is ten days counted from the date printed on the letter.

What is the most useful thing to do with that observation?

Post on schedule and open a follow-up item covering the alternate formats, the translations and the ten-day window.

Post on schedule, and add a line inviting anyone who needs the bulletin in another format or language to contact the division.

Ask the owner of the bulletin to hold it one cycle and route it through a named review that examines accessibility, plain language, cultural responsiveness and stakeholder impact, with the decision recorded either way.

Carry this forward

Governance is the set of rules about which drafts get reviewed, at what point, against what criteria, by whom, and with what authority to say not yet. Most divisions already have some of it; the question is where accessibility and equity sit inside it.
Accessibility, translation, plain language and outside input usually arrive after the requirements are settled. At that point they can only be repair work, and repair work is the first thing a publication calendar defers.
A policy that reads the same for everyone can still cost different people very different amounts of time, travel, money and proof. Uniform wording is not the same as an even effect.
Placement decides what a review is able to reach. A reviewer handed a cleared document and a release date can improve the document and almost never the requirement inside it.

A scenario about a bulletin already cleared for release, a walk through the same revision as four different desks see it, and a knowledge check on what a final-step review can actually accomplish.

Draw your own division's path for one kind of document, from first draft to the day it reaches people, and mark the last point at which a requirement could still be changed without a formal amendment.

Your next step

Where does the last real chance to change a requirement sit in your own work?

Name one kind of document your team produces regularly: a bulletin, a manual section, a form, a letter template, a contract clause or a work instruction.

Write down each step it passes through and who has to agree at each one.

Mark the step after which a change stops being an edit and becomes an amendment, a reissue or a correction notice.

Note where accessibility, translation, plain language and outside review currently sit relative to that mark.

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.