Review a form, policy or message

Review what the person receives

Review the thing a person actually gets. Not the template in the style guide, not the screen a staff member sees, and not the policy that describes the form. The envelope, the first paragraph, the questions in order, the signature line, the way it arrives and the way it has to be returned.

Five lines are enough. What you are reviewing and who receives it. Every question it asks, with the reason for each one written beside it. Where a person could be exposed, burdened or left out. What the record can hold, and what it forces staff to bury in a note. Then the first fix, a named owner, and a point at which somebody will check.

Most reviews come back with three or four findings, one of which sits inside your own step. Make that one. It turns the review from an opinion about somebody else’s work into a piece of work with a result already in it, and it is the part that needs nobody’s permission.

A review sheet for one form, policy or message

Five lines that turn a document you inherited into a short list somebody can act on.

What you are reviewing, and who receives it The three-page program application, mailed to the home address on file, returned by mail or in person, and read aloud by phone when a person asks.

Every question it asks, and the reason for each one Legal name — needed to establish eligibility. Marital status — no reason anyone in the unit can state. Relationship to applicant — used to decide who may be contacted, which is not what the wording asks.

Where a person could be exposed, burdened or left out Mailed to a shared address with the program name on the envelope. “Legal representative” excludes a partner who is the person’s actual support. No place for the name the person uses, so notices print the other one.

What the record can hold, and what it forces into a note One name field, one address field, no contact preference, no field for a supporter the person chooses. Staff currently write all three into a free-text comment the next worker rarely reads.

First fix, named owner, next review point Mine this month: take the program name off the envelope and add a contact-preference question to the cover letter. System owner: add a used-name field and a chosen-supporter field; ask by the agreed review point and record the answer.

Copy the five lines, fill them in for one document you can actually change, make the fix inside your own step first, and send the rest to the owners you named with a date.

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

What a review usually finds

A question nobody can explain. It was inherited, and the reason left with whoever added it.
A definition of family that recognizes legal relationships and nothing else.
A record that holds a legal name and an address and nothing about how the person wants to be reached or who they want in the room.
A channel with no alternative: mail only, phone only, portal only.
A notice that names a program on the outside of the envelope.
A report small enough that one person in a category can be recognized.
A consent taken once, in general, and treated as permanent.

When the fix is not yours

Bring one finding, not the whole review

System and policy owners receive a great deal of general concern and very little they can act on. Bring the field, the wording, the effect on a person and the change you want. One specific ask travels further than a full report.

Bring the effect, not the frustration

“This form is bad” is a feeling. “This form has no field for the name a person uses, so every notice prints a name they do not use and staff are handling it in a comment field” is a defect with a cost attached.

Ask who else has to agree

Shared systems, legal review, data classification and public notices usually involve more than one office. Ask the owner who else signs off, and write that into the review so the next person does not start over.

Route the formal questions properly

Data classification and the wording of the notice given when the state collects private information go to the responsible authority and the department’s data practices office. Personnel questions go to human resources. Discrimination questions go to the department’s equal opportunity and legal offices and to the Minnesota Department of Human Rights. Anything involving Tribal Nations goes first to the Department of Human Services offices that handle tribal matters and to the Office of Indian Affairs.

Fix your own line first

What you can change

You control the wording, the envelope, the contact question, the example and the reply inside your own step.

What to watch for

Do not send the whole review upward and wait. A review with no completed fix in it reads as a complaint.

Your next step

Make one change in your own step before the review leaves your desk, and say in the review what you already did.

Which review finding is written so that somebody can act on it?

The application form is not inclusive and should be updated.

Question four asks marital status, and no one in the unit can state what the answer is used for. Owner: the program policy lead. First fix: remove the question or write the reason into the notice, by the agreed review point.

Staff should be more aware of privacy when they handle this form.

Try a situation

You inherit a three-page application form your unit sends out. It asks for legal name only, marital status, and “relationship to applicant” for anyone else listed. It requires a signature from the applicant or a legal representative, and the accompanying notice explains none of the questions. Nobody currently in the unit wrote it, and the system behind it is shared with two other program areas.

Where does your review start?

With the system owner, since most of the fields are shared and cannot be changed by your unit alone.

With a full rewrite of the form in plain language, which fixes the wording problems in one pass.

With the document as a person receives it: list every question and the reason for each, mark where somebody could be exposed or left out, note what the record cannot hold, and separate what you can change from what the system owner must.

Carry this forward

Review the document a person actually receives, in the channel they receive it, not the version in the style guide.
Three defects account for most of what a review finds: a question with no stated reason, a record that cannot hold something true about the person, and a definition that recognizes only some relationships.
A finding is only useful when it names an owner and a first fix. “This is a problem” goes nowhere. “This line, this change, this person, by this point” moves.
Fix the part inside your own step before the review goes anywhere. It needs nobody’s permission, and it is what makes the rest of the review credible.

A scenario about reviewing an inherited form, a completed five-line review sheet for one real document, and a knowledge check on what makes a finding actionable.

Run the five lines over one document you can change. Make the fix in your own step this month, and send the rest to the owners you named with a specific ask and a review point.

What you’ll be able to do

Review what the person receives

A review sheet for one form, policy or message

What a review usually finds

When the fix is not yours

Fix your own line first

What you can change

What to watch for

Your next step

Try a situation

Carry this forward

Your next step

Review a form, policy or message

What you’ll be able to do

Review what the person receives

A review sheet for one form, policy or message

What a review usually finds

When the fix is not yours

Fix your own line first

What you can change

What to watch for

Your next step

Try a situation

Carry this forward

Your next step