In a regulatory consultation, the operator with the evidence wins
May 19, 2026 · Bayview Strategies
In a regulatory consultation, the strongest voice in the room is the operator who brought the evidence, in their own name. Not the firm that argued hardest, not the brief that was polished best — the one who put the technical reality on the table and made it checkable. I say this to every founder heading into a consultation, because it cuts against the instinct to come in loud: the submission that wins is the one that does the regulator's hardest work for them.
A regulatory submission has an unusual reader. You're writing to someone who has to reach a decision that can withstand technical challenge, legal challenge, and public scrutiny — often all three at once. That reader isn't moved by conviction. They're moved by evidence they can stand behind after you've left the room. So the job isn't arguing harder. It's making the regulator's decision easier and more defensible.
The strongest submissions I've seen don't read like advocacy. They read like analysis — closer to a technical whitepaper than a pitch. They lay out the technical reality, the operational constraints, and the options, including the trade-off on each one, in terms the regulator can lift straight into a ruling that holds. You're turning a contested, complicated situation into a small set of clear, substantiated choices. That's the gift. A reader under pressure to defend their call will take that gift every time.
Two ways I watch it go sideways, and they pull in opposite directions.
The first is the engineering submission — technically rigorous, but written for engineers. It buries the decision the regulator actually has to make under detail they can't act on, and quietly assumes the policy implications are self-evident. They never are. The second is the advocacy submission — polished, persuasive, and thin on the structured evidence a regulator needs to justify a yes. It wins the argument and loses the decision, because nobody can defend a ruling built on assertion.
The work lives in the bridge between those two. You keep the technical evidence intact while translating it into the regulator's frame: state the problem in regulatory terms, present options instead of a single demand, quantify the impact of each, and be honest about uncertainty. A submission that says plainly what it doesn't know is more credible than one pretending to a certainty it can't support — and the honest version is the one that survives cross-examination.
It also means writing for the record. A regulatory submission can be cited, relied on, and contested long after it's filed. Precision in how you frame a claim and attribute the evidence under it isn't pedantry — it's what decides whether your submission helps the regulator build something durable or just adds to the file.
Why does this have to be you and not a proxy? Engineering and policy usually get handed across a gap between separate teams, and the case arrives at the regulator translated twice and weaker for it. You're the one who lives the operational reality. When you make the technical case in the regulator's own language, to evidence-grade standards, in your name, you're the most credible source in that consultation — and no hired voice can be that for you.
My part sits one step back from yours. I help you read the regulator and the room, shape the options so they're decision-grade, pressure-test the evidence before it's filed, and build the materials — but the file is yours and the voice is yours. That's the policy research and regulatory strategy work, and if you want the fuller picture of running this yourself, I've written up how to do your own government relations.
If you've got a consultation on the horizon, start with a scoping call — send me a note and I'll tell you straight what your evidence has to do to make the regulator's yes defensible.