Freeze criteria that manufacturing can actually check

Firmware teams often declare a freeze in language only they understand: “boot stable,” “Wi-Fi mostly good,” “flash script works on my desk.” Contract manufacturers need different nouns — fixture version, image hash, expected LED sequence, fail-bin rules.

Write for two audiences

Keep a short internal note for engineers and a one-page freeze sheet for manufacturing. The sheet should name the exact binary artifact, the programming tool revision, and the observable pass condition on the line. If a condition requires a laptop and a developer console, it is not a factory check.

Tie criteria to the board revision

Every freeze sheet should state the PCB version and BOM date code it applies to. When hardware changes a pull-up, the sheet either updates or it lies. Advisory work spends surprising amounts of time simply aligning those version strings.

Practice the handoff once

Before the real freeze, walk the checklist with the person who will stand at the station. Ambiguous steps surface immediately. That rehearsal is cheaper than discovering ambiguity after boards are already in the queue.