NASA's JPL Just Untangled Its Spacecraft Checklist Chaos

NASA's Jet Propulsion Laboratory builds some of the most complicated machines humans have ever made — rovers, orbiters, space telescopes. Before anything launches, engineers must prove it works. That process is called verification and validation, or V&V for short: essentially, a formal, documented way of double-checking every requirement, from "this antenna must survive 200 degrees" to "this software must not crash when the signal drops."

The problem: over the past decade, each JPL mission drifted into its own way of doing those checks. Different teams used different names, formats, and paperwork for the same activities. That sounds like a filing annoyance, but it isn't. It means engineers re-solve problems other teams already solved, knowledge doesn't transfer between missions, and reviews take longer and cost more. Since NASA is funded by taxpayers, that overhead has a real price tag.

The fix, described in a new paper, came from 29 practitioners across multiple mission types and disciplines who worked together in human-centered design workshops. Rather than dictate one rigid process, they built a flexible framework. It separates the five classic ways of checking something — testing it, analyzing it, inspecting it, demonstrating it, and reviewing the design — while keeping a shared set of attributes so everything can be compared and searched. Crucially, the framework maps the two-way relationships between requirements, the checks performed, where they happen, and the evidence they produce. That means you can trace any piece of proof back to the exact requirement it satisfies — and spot requirements nobody is checking. The whole thing was formalized as a system model (a visual blueprint language for complex engineering) and then implemented inside Jama, the software JPL uses to track requirements.

The practical payoff is automation and reuse: teams can copy proven patterns instead of starting from scratch, and connect checks into a "digital thread" — one continuous record from design to launch. The catch? This is an internal process standard at one organization. It won't fix a flawed design, and adopting any new standard takes time and training before the savings show up. It's plumbing, not a breakthrough — but good plumbing is why missions come home.