Most of what happens in a regulatory conference session is fair game the moment it's said — you can write it down, quote the speaker by name, and put it straight into a trip report. A workshop, a study group, or a smaller working session sometimes runs under a different agreement: the Chatham House Rule, or a plainer version of the same ask — use what you hear, don't say who said it, or in the strictest version, don't repeat it outside the room at all. The organizer usually says so once, at the start, in a single sentence easy to miss if you walked in a minute late. Getting it wrong afterward isn't a matter of taste. It's the one way to make sure you're never invited back to that particular room.

The rule is doing real work, not just decoration

A session that runs on the record produces careful, hedged, defensible statements — useful, but rarely candid. A session that runs under a non-attribution agreement is built to get something more honest out of people who would otherwise stay guarded: a regulator thinking out loud about a policy still in draft, an industry colleague naming a problem their own communications team would never clear for a podium. The rule exists because that candor is worth protecting, and it only survives as long as everyone in the room actually honors it. One trip report that quotes someone by name closes that particular room to everyone who comes after you, not just to you.

Two different rules, easy to conflate

The classic Chatham House Rule is narrower than most people assume: you may use the information you heard and describe what was discussed, but you may not reveal who said it or, often, who else was in the room. That's a real permission, not a gag order — a trip report can say "one regulator suggested the guidance would likely narrow the current definition" without naming which one. A stricter, more informal version some workshops use goes further: nothing discussed leaves the room at all, in any form, attributed or not. The two get treated as interchangeable in casual conversation and they are not. If the organizer's opening statement is vague, ask directly which version applies before the session starts — it's a normal question, not an awkward one, and asking it after the fact because you're not sure what you can write is a much worse conversation to have.

The trip report and readout meeting are the actual test

The rule doesn't get tested in the room. It gets tested afterward, in exactly the two places a trip report and a readout meeting already ask you to be specific: what did you learn, and from whom. Under a non-attribution session, the honest version of that report describes the substance in full and handles attribution the way the room agreed to — "several participants," "a regulator present," "one perspective in the room" — never a name, a title specific enough to identify one person, or a detail so narrow that anyone who was there could work out who said it. A live readout is the riskier of the two, because a direct question from a colleague who wasn't in the room ("okay, but who actually said that?") invites an answer you agreed not to give. Deciding in advance how you'll deflect that question, politely and without pretending it wasn't asked, is worth doing before the meeting, not during it.

When someone else breaks the rule in the room

You will occasionally sit in a session where another attendee violates the agreement in real time — posting to social media mid-session, or naming a speaker in a question addressed to the whole room. That isn't your rule to enforce, and it doesn't retroactively release you from your own agreement; two wrongs don't make attribution permissible. It's worth quietly flagging to the organizer afterward if it was serious, the same instinct behind noticing where a hallway conversation's boundaries actually sit — but your own trip report and your own answer in the readout meeting stay exactly as careful as the rule required, regardless of what anyone else in the room did with theirs.

Worth a look in the directory

  1. PDA Annex 1 Implementation Workshop 2026 — a working-session format where non-attribution ground rules are common
  2. HMA/EMA Multistakeholder AI and Data Forum 2026 — a multistakeholder forum built for candid, not-for-attribution discussion

More from Save the Date

  1. The trip report that actually gets read
  2. The readout meeting after the trip
  3. Talking to the regulator standing next to you

Essays are editorial: they describe how we plan and attend events, not rules. Event listings on this site are verified against the organizer’s own pages — but confirm dates and pricing with the organizer before booking anything.