Good Practice #4 | One Note, Many Builds: the short guide that aligned embedded sensing across the consortium

Great collaboration can still fall short if each team interprets integration differently. Our solution was not a lengthy SOP, but a concise 2–3 page Requirements Note that everyone could build against. It immediately changed the pace of our work.

Why we needed a single compass 

With multiple partners working across materials, devices, and control systems, the HealingBat system involves many interacting variables at different levels. Even small deviations, such as sensor placement shifting by a few microns, a different feedthrough seal, or a slightly thicker stack, can make datasets difficult to compare. Our goal was innovation while avoiding inconsistency.

What’s inside the Note (and why it works) 

• Scope and intent, in plain terms: embed temperature, pressure and gas sensing, plus localized heating, inside pouch cells to enable early detection and controlled response. 
• Placement and protection: sensors placed near critical interfaces, with robust insulation and sealed routing paths to protect both device and cell. 
• Electronics and data: simple per-cell readout with a lightweight data schema covering IDs, units, and ranges, so that every log stream follows the same format from day one. 
• Non-negotiables: safe drive levels and defined environmental operating windows, ensuring that “works in the lab” also means “can be integrated into a pouch cell.”

This is a shared floor. Teams still innovate on materials and patterns; the Note simply ensures that when results land, they’re comparable and actionable.  

How it changed day-to-day work 

The Requirements Note now sits alongside our build sheets and test plans. Device teams use it to check layouts against the placement rules; the test team aligns cycling protocols and records the same baseline channels; and system integration receives clean, consistently labelled data. The immediate impact has been fewer reworks, faster handovers, and clearer evidence when a new design outperforms an earlier one.

A living document 

As we integrate the expanded array and more pouch variants, the Note is updated on a sprint cadence. New learning (e.g.  improved encapsulation or refined threshold) is folded in quickly, keeping everyone aligned without adding bureaucracy. 

Call to action 

Explore our Work Packages to see how this simple practice shortens the distance from materials insight to smart, self-healing battery prototypes.