Physical rehearsals at full scale when the environment allowed. Reduced-scale mockups when it didn’t. Sand tables when those weren’t available. The rehearsal wasn’t about memorizing a script or walking through a sequence of events. It was about building a mental model detailed enough that decision points felt familiar when they arrived under pressure.
By the time we executed, we’d already lived through the operation multiple times. The unexpected became less disorienting because we’d stress-tested our assumptions in a controlled environment first. That discipline is directly applicable to UAS platform evaluation, and most procurement processes skip it entirely.
How Most UAS Evaluations Actually Work
The standard UAS procurement evaluation looks like this: the vendor conducts a demonstration flight at a location of their choosing, with conditions that favor the platform, operated by their most experienced pilot, with the payload configuration that shows the best performance numbers. The platform performs well. The numbers look good. The procurement team writes a favorable evaluation.
And then the platform arrives in the operational environment and the numbers don’t match the demo. This isn’t necessarily vendor deception. Vendors demonstrate their platforms under favorable conditions because that’s rational. The problem is that procurement processes accept the demonstration as operationally representative when it isn’t.
Evaluating Against Your Mission Profile
The operational equivalent of rehearsal in procurement is evaluation against your actual mission profile — not the vendor’s demonstration profile.
That means: your operators flying the platform, not the vendor’s demo pilot. Your payload configuration, not the configuration that shows best endurance numbers. Your operating environment — wind, temperature, altitude, terrain — not the vendor’s preferred demo site. Your maintenance personnel performing field repairs, not vendor technicians. Your communication architecture, not the vendor’s ground station.
The value of rehearsal — in operations and in procurement — is what you learn about the gap between assumptions and reality. In platform evaluation done right, you discover payload integration issues that weren’t visible in the demo, maintenance requirements that affect operational tempo, operator training curves that affect deployment timelines, battery performance curves in your actual thermal environment, and actual range characteristics under your communication constraints.
The Cost Comparison That Matters
None of these are necessarily disqualifying. Most of them are manageable if you discover them during evaluation rather than during an operational deployment. The ones that are disqualifying are far better identified before contract award than after.
The challenge is that thorough operational evaluation costs more time and resources than accepting a vendor demonstration. In procurement environments with timeline pressure, that cost feels prohibitive. The comparison to make is not “evaluation cost vs. zero.” The comparison is “evaluation cost vs. the cost of a fleet of platforms that underperforms its procurement justification.”
That second number is always larger. The agencies that have learned this lesson are building evaluation frameworks before they engage the market, not after they’ve seen a compelling demo.