Tradecraft handover — when private firms support governmental clients

Governmental clients procuring private-sector tradecraft do so because they need capability they do not currently retain. Delivering the capability once is straightforward. Building it into the client organisation so it survives personnel rotation is the harder problem, and the only one that matters.

The retention problem

Personnel rotate. Operational priorities shift. The capability built into a governmental unit during a six-month engagement evaporates inside two rotation cycles unless the retention architecture is in place from the start.

The architecture has four pillars: documented procedures, embedded mentoring, structured exercises, and after-action discipline.

Pillar 1 — documented procedures

Tradecraft delivered without documentation lives in operator memory. Operator memory rotates out. Documentation is the first survival mechanism.

The documentation is operationally useful: standing procedures for the capability, decision trees for the situations the capability addresses, equipment and consumable specifications, and the training architecture for refreshers. It is written for the operator who will inherit the capability, not for the procurement file.

Pillar 2 — embedded mentoring

Documents do not transfer judgement. Embedded mentoring is the period when the private-firm operators run alongside the governmental operators in real conditions. Errors are corrected in flight; nuance transfers; the governmental operators build the cadence.

The mentoring period is a specific, scoped phase of the engagement, not an open-ended commitment. Its duration is a function of the capability's complexity and the receiving unit's baseline.

Pillar 3 — structured exercises

Exercises after handover are how the receiving unit owns the capability. The exercise architecture is designed during the engagement, runs at handover, and continues on a documented cadence after the private firm has demobilised.

The exercises are structured: scenario design follows the threat picture, AAR feeds back into the procedures, and exercise outputs are visible to the receiving unit's command. The cadence is the diagnostic of whether the capability is being retained or eroded.

Pillar 4 — after-action discipline

AAR is the loop that closes the system. Every operational deployment, every exercise, every handover phase generates a documented AAR. The AAR feeds the next iteration of procedures, exercises, and mentoring.

Without AAR discipline, the procedures become stale, the exercises become rote, and the capability degrades while the documentation remains nominally in place. The governmental client procuring the capability inherits the AAR discipline as part of the deliverable.

What private firms must accept

The handover architecture works against the simplest commercial incentive — selling the capability repeatedly. Firms that build genuine handover accept that the engagement ends with the receiving unit owning the capability outright. The next engagement is procured on different terms.

Firms that resist that endpoint produce engagements that look like ongoing dependency. Governmental clients recognise the pattern and procure differently from those firms thereafter.