Challenge Response

Someone questions a decision, in a meeting or by email or in front of a team, and you have about ten seconds. Answered under pressure, the reply tends to come out either defensive or vague, and both are worse than the decision itself. The wording you would be content to see quoted back is almost never the wording you produce on the spot.

What it does. You pick the closest situation from six — a trans person has asked you for something; someone has complained about shared spaces; a policy question; a formal request such as an FOI or subject access request; a legal or campaign challenge; or a colleague raising something about a colleague. You set your role, from frontline staff and line managers through HR, trustees and directors to champions and allies, and the script's register and authority flex with it. You set the severity, which decides whether the wording de-escalates, responds or escalates: behaviour rather than identity, a one-off incident, or a repeated and escalating pattern. You can anchor it to your sector, and paste a policy excerpt so the script can quote your own wording back.

What you get. A verbatim script you can say aloud — not an outline to work up. It comes with the tone to take, the follow-up, and the things to avoid saying. Nothing is stored unless you save it.

Who uses it. Line managers facing pushback in the room. HR and people leads preparing for a difficult conversation. Internal communications colleagues who have to say something today.

Where it fits. Prepare it in advance rather than in the moment; that is the whole point. Complaints Triage decides where something belongs, and this decides what to say about it. Defensibility tells you which parts of your position will be pressed hardest, which is what the response has to be ready for. It is drafting help, not legal advice.