11 minutes

Writing the decision down

A decision that exists only as an outcome cannot be explained, challenged, applied consistently or revisited. This lesson builds the seven-line review that holds the reasoning, and hands you the tool to copy into your own work.

What you’ll be able to do

Complete a multi-perspective decision review for one real decision, naming the tension, the standpoints, the tests, what it costs whom, how people can challenge it, the revisit point and what repair would require.
Compare the responses to this question and explain your choice: What actually failed here?
Draft a multi-perspective decision review for your work, including the decision in one sentence, obligations in tension, who is affected, and who was in the room.

Why the record is the decision

Most decisions in a division are recorded as outcomes. Approved. Denied. Required. Effective from this date. The outcome is the only part that travels, and within a couple of cycles the people who made the decision have moved on and the reason has gone with them. What is left is a rule nobody can explain, applied by people who were not there, to people who cannot find out what standard they were held to.

Recording the reasoning fixes several problems at once. It lets the next person apply the same rule to the next similar case, which is what consistency actually is. It gives the people affected something specific to challenge, which is what accountability actually is. And it lets a decision be revisited when the facts change, instead of hardening into a permanent state because reopening it would look like criticism of whoever made it.

None of this needs a new process or a form somebody has to approve. Seven lines, in the document where the decision already lives — the memo, the change request, the meeting record, the note in the file — will carry it. The discipline is writing them before the decision is final, rather than reconstructing them afterwards, once the reasoning has quietly smoothed itself out.

A multi-perspective decision review

Seven lines that hold the reasoning behind a decision, so it can be explained, challenged, applied to the next case and revisited. The example below continues the grant scenario.

The decision in one sentence We will accept an equivalent financial record in place of the audited statement that some community organizations cannot produce, and we will say so in writing to every applicant.

Obligations in tension Careful stewardship of public money and a verifiable record, against equal access for smaller and culturally specific organizations that have never had an audit and cannot afford one. The current design favors the first, and nobody chose that; it arrived with the form.

Who is affected, and who was in the room Applicants, the communities they serve, grant staff, and the reviewer who will audit this cycle. In the room: grant staff and the program manager. Spoken for: applicants, through questions they asked in past cycles. Missing: the smaller organizations themselves, and the office that owns the requirement.

Tests applied, and what they changed Publicity: the original reason — “they did not meet the requirement” — could not be said to an applicant without embarrassment. Burden: the requirement costs a small organization money and months it does not have, and costs a large one a phone call. The rule: said aloud, we were writing “organizations without audits do not receive grants,” which nobody would sign.

What we chose, and what it costs whom Accept an equivalent record, listed in the application itself with examples. Cost: grant staff spend longer reviewing unfamiliar records, and the unit takes on the work of explaining the change to the office that owns the requirement.

How people will be told, and how they can challenge it The change goes into the application and into a plain-language note to every organization that applied in the last cycle, with a named contact and a route for proposing a different equivalent record.

Revisit point, and what repair would require Look again after two cycles at the approval pattern by organization size. If anyone was denied under the old reading for this reason alone, tell them, explain what changed, and invite a new application without making them ask first.

Copy the seven lines into the document where your decision already lives — the memo, the change request, the meeting record — and fill them in before the decision is final.

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

What makes a line usable rather than decorative

A decision sentence somebody outside the division could read once and understand.
Obligations named in pairs, so the trade is visible: this protects one thing and it costs another.
Standpoints marked honestly as at the table, spoken for, or missing. Writing “missing” is a legitimate and useful entry.
A cost line that names who pays, not only how much.
A challenge route with a person attached, not a general address and a hope.
A revisit point with a date and an owner, plus what would make you look sooner.

The seven lines

The decision

One sentence, in words the person affected would use. If it takes a paragraph of internal shorthand, the decision is not clear yet, even to you.

Obligations in tension

Name at least two, and say which one this design favors. “This protects safety and it costs people their own choices” is a complete entry.

Who is affected, and who was in the room

Three marks: at the table, spoken for by somebody else, missing. Writing “missing” is far more useful than leaving the line blank.

Tests applied

Which of the six you ran, and what changed because of them. If nothing changed, say that; it is information about the decision too.

What we chose, and what it costs whom

The line people skip, and the one that makes the record worth keeping. Money, time, travel, waiting, paperwork, risk, dignity.

How people will be told, and how they can challenge it

Plain language, the channels people actually use, a named contact, and a route that does not require knowing how the division is organized.

Revisit point, and repair

When you will look again, what would make you look sooner, and what you would owe somebody if this turns out to have caused harm.

Put the reasoning where the next person will find it

What you can change

You control whether the reasoning goes into the document that travels with the decision, or stays in your own notes.

What to watch for

Do not leave the reasoning in a meeting recollection, an email thread or your memory. All three leave when you do, and what remains is an unexplainable rule with your unit’s name on it.

Your next step

Before your next decision is final, put the seven lines into the record that will outlive you in this role, and tell the person who inherits the work where to find them.

Which decision record can the next staff member actually apply to a similar case?

“Request denied. Does not meet program requirements. Applicant notified.”

“Request denied because the required document asks for something this applicant’s clinic will not produce. We are treating an equivalent record as sufficient from now on, have told all current applicants, and will review the pattern after two cycles. Contact: the program lead.”

“Request denied after discussion. The team considered several factors and reached consensus.”

Try a situation

A DSD grant program accepted a community organization’s application two cycles ago even though it lacked one required financial document, because the requirement asked for something the organization could not produce and the gap did not affect the work. The discussion was careful. None of it was written down. A new staff member now has two similar applications and no record of why the first was accepted. One is approved and one is denied. A third organization asks what the standard is.

What actually failed here?

Nothing failed at the time. The original decision was sound, and the problem is the new staff member’s inconsistency, which a reminder about applying requirements consistently will fix.

The reasoning was never recorded, so a good decision became an unexplainable one. Reconstruct and write down the rule that was actually made, apply it to all three applications, tell the organizations plainly what the standard is, and keep the review with the program’s requirements so the next person inherits it.

Deny all three and refer the documentation requirement upward to the office that owns it for a formal change.

Carry this forward

A decision record is only paperwork if it holds nothing but the outcome. With the reasoning in it, it is what lets a decision be explained, challenged, applied consistently and changed.
Seven lines carry almost all of it: the decision, the obligations in tension, who is affected and who was in the room, the tests applied, what was chosen and what it costs whom, how people will be told and how they can challenge it, and what would make you look again.
Write it for the person it affects, not for the auditor. A record a person could read and recognize is also a record a reviewer can follow.
Put repair in before anything goes wrong. Deciding in advance what you would owe somebody if this caused harm is what separates a commitment from a sentiment.
A decision with no revisit point is not a decision. It is a permanent state that nobody owns and nobody can reopen without appearing to start a fight.

A scenario about a sound decision that was never written down, a completed seven-line decision review you can copy, and a knowledge check on what makes a record usable to the next person.

Choose one decision you can actually shape this month. Fill in the seven lines before it is final, put the page where the decision lives rather than in your own notes, and name the point at which you will look again.

Your next step

Which decision in front of you could you write down in seven lines this week?

Name the decision, and where the record will live so the next person finds it

Write the line about what it costs and whom, before anybody asks you

Name the revisit point and the colleague who will ask you about it

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.