TL;DR. The most effective regulatory submissions read like technical whitepapers, not advocacy. They translate engineering and operational reality into decision-grade policy options a regulator can adopt and defend. The skill is not arguing harder — it's making the regulator's decision easier and more defensible.

A regulatory submission has an unusual reader. It is written to a regulator who must reach a decision that can withstand technical challenge, legal challenge, and public scrutiny — often all three. That reader is not persuaded by conviction. They are persuaded by evidence they can stand behind.

This is why the strongest submissions don't read like advocacy. They read like analysis. They lay out the technical reality, the operational constraints, and the options — including the trade-offs of each — in terms the regulator can lift directly into a defensible decision. The submission does the regulator's hardest work for them: turning a complex, contested situation into a small set of clear, substantiated choices.

Two failure modes are common, and they pull in opposite directions.

  • The engineering submission. Technically rigorous, but written for engineers. It buries the decision the regulator actually has to make under detail the regulator can't act on, and assumes the policy implications are self-evident. They never are.
  • The advocacy submission. Polished and persuasive, but thin on the structured evidence a regulator needs to justify saying yes. It wins the argument and loses the decision, because the regulator can't defend a ruling built on assertion.

The work sits in the bridge between them: keeping the technical evidence intact while translating it into the regulator's frame. That means stating the problem in regulatory terms, presenting options rather than a single demand, quantifying the impact of each, and being honest about uncertainty — because a submission that acknowledges what it doesn't know is more credible than one that pretends to certainty it can't support.

It also means writing for the record. A regulatory submission is a document that may be cited, relied upon, and contested long after it's filed. Precision in how claims are framed and evidence is attributed isn't pedantry — it's what determines whether the submission helps the regulator build a ruling that holds.

Engineering and policy are usually treated as separate disciplines, handled by separate teams who hand work across a gap. The most effective regulatory submissions close that gap: they are written by people fluent enough in both to make the technical case in the regulator's language, to evidence-grade standards. That fluency is the difference between a submission that informs a decision and one that merely adds to the file.

Preparing a regulatory submission? Start a conversation.