Writing a decision someone can defend

Trust & Safety teams protect people from harm online, and a lot of that comes down to applying a rule to a case. The basic unit of the work is one decision: this post, this rule, this outcome.

Months later, someone may look at that decision again. A person handling the user's appeal, a quality checker, sometimes a government regulator or a journalist. By then the only version of your decision that exists is the one you wrote down. Whether you can defend a call rarely comes down to your judgment. It comes down to your notes.

What your notes need to say

• What was actually in front of you: the reported post and the context you really saw. Describe it. Don't assume.
• The rule, quoted. The actual words, not your summary. Summaries are how a rule slowly drifts away from what it says.
• The outcome, plainly: removed, limited, warned, or left up.
• Why this outcome and not the next closest one. One sentence on why you removed it instead of limiting who could see it, or the other way round.
• What would have changed your mind: the one fact that would have flipped the call if it had been there.

The same decision, twice

Before
  Removed. Violates community guidelines.

After
  Reported video uses recruiting language
  and a join link for a named group. Removed
  under Violent Organizations 3.2, "recruiting
  on behalf of a designated entity". Didn't
  just limit it: 3.2 requires removal when
  there's a join link. Would have changed the
  call: news or reporting context, not present.

Deciding the close ones

Hard cases sit between two outcomes. The trick is to decide using the rule as it's written today, then flag the rule separately if it gave you a bad answer.

In your notes, name the option you turned down. "Considered limiting it, removed instead because..." is one short phrase, and it turns what looks like a coin flip into a reasoned choice. Keep the two jobs apart: your decision applies today's rule, and your feedback to the people who write the rules improves tomorrow's.

Who reads it later

You write the note once, but four kinds of people may read it:

• A quality checker needs the rule and your reasoning, so they can check it against the standard.
• An appeals reviewer needs what would have changed the call, so they can see whether it's there now.
• The user needs the reason, in words plain enough to put in a message to them.
• A government regulator or auditor needs proof that a written process was followed, case after case.

One rule covers all four: describe what was posted and what was done, and say nothing more about who the person is than the decision needs. A note that quotes what someone said doesn't need guesses about who they are. The leaner note is the safer one, for them and for you.

Why it's worth the two minutes

A decision you can't rebuild six months later is a decision you can't defend. That's the defensive case. There's a career case too, and it pays off quietly.

Reviewers who write notes like this get asked to help keep everyone's decisions consistent, and then to help shape the rules themselves, because their notes show where the rules really break down. That's how a reviewing job turns into a rule-writing one. It starts with writing down what you were already thinking, which is about as low-effort as career advice gets.