• Home
  • Policy advisory
Policy advisory

Policy written by someone who has lived inside the authorities.


An explosive ordnance disposal career produces technical depth. Doctoral work in public policy produces an instrument-level understanding of how a rule is actually made to bind. The two together are rare, and the combination is the point of this line of work.

Why the combination matters

Most policy about this subject is written by people who have never executed under it.

That is not a criticism of policy professionals. It is a structural feature of how the two careers are arranged: the people who write the instrument and the people who live under it are almost never the same people, and almost never in the same room.

The consequence is familiar to anyone who has held the mission: a directive that is technically correct and operationally unusable, or an authority that stops exactly one step short of the decision someone has to make at two in the morning. Those failures are visible in advance, but only to a reader who has had to act under the instrument as written.

A senior technician who spent a career executing inside those authorities, and who is now doing doctoral work on how policy is constructed, can read a draft from both ends at once. That is the whole of the claim being made here, and it is deliberately no larger than that.

What the advisory work produces

  • Policy assessment. A written read of an existing policy, directive or plan against the mission it governs, including where it does not reach.
  • Authority mapping. Which authority applies, who holds it, where it stops, and which gap has to be closed by a decision rather than by effort.
  • Instrument drafting support. Drafting in the structure the system actually accepts, inside authorities and mechanisms that already exist rather than invented alongside them.
  • Claim review. Reading a capability claim against what policy and authority actually permit, before it is put in front of a customer.
  • Compliance path. Turning a mandate (which arrives as a deadline, not as a plan) into phased milestones with owners and evidence requirements.

The role in the federation

Blast Shield holds the policy advisory role within a federation of independent companies that share a delivery platform. In practice that means being the person who reads a capability claim, a teaming arrangement or a proposed offering against policy and authority before it goes anywhere, and says so plainly when it does not hold.

It is an advisory seat, not a supervisory one. It carries no direction over any other company in the group, and none of them carries any over Blast Shield.

How the federation is arranged

What this is not

Not legal advice, and not a substitute for counsel. Not a lobbying or government-relations practice. Not a compliance certification, and not an accreditation of anyone’s program. Where a question is a legal one it is named as a legal one and routed to a lawyer.

Commercial terms

Engagement and fee structure is agreed in writing per engagement. Nothing about commercial arrangements is published on this site.

On the doctorate

The PhD in public policy is in progress at Liberty University. It is described that way everywhere it appears on this site, and it will keep being described that way until it is conferred.

How a policy engagement runs

Four steps, and the third one is the one people skip.

  1. Frame the problem in writing

    What the risk is, who owns it, what current policy already covers, and where the gap genuinely sits, before anything is drafted.

  2. Work from primary sources

    Statute, directive, standard and agency source material, cited so a reviewer can follow the chain without taking anyone’s word for it. Not the trade-press summary of the controlling document.

  3. Circulate for correction before release

    A draft goes to the people who own the underlying mechanism, and to legal review, before it is presented as a position. Assumptions are labeled as assumptions and estimates are labeled as estimates.

  4. Deliver an artifact

    A document that can be signed, filed, briefed or submitted, not a deck describing a document that does not exist yet.

Have a draft that has to survive contact with an operator?

That is the read this practice is built to give.

Start a conversation