Request a firmware review
Menu
Founders and firmware leads preparing their first field updates

Write down who ships updates, when and how to undo them

Seven decisions every team shipping updates has to make, each with a rule, an owner and notes. Edit the fictional example and download it for your team.

Key characteristics

Columns
Decision, our rule, owner, notes
Output
Editable table, CSV download, print
Default example
A fictional policy for a small trial fleet
Runs
In your browser with nothing sent

Worksheet: Write down who ships updates, when and how to undo them

The rows are a fictional example. Edit any cell, add or remove rows, then download a CSV for your team. Nothing leaves your browser.

DecisionOur ruleOwnerNotesRemove

An update pipeline decides how a release reaches devices. An update policy decides who is allowed to send it: who can sign a release, which devices see it first, what makes you stop, and how long a board revision keeps getting fixes. Without one, those questions get answered under pressure, at the worst moment, by whoever is awake. This worksheet keeps the decisions in one table with an owner for each, so the answers exist before the first bad release.

How to use it

  1. Read each decision in the example and replace the rule with yours.
  2. Name a role as owner for every row. A row owned by everyone is owned by no one.
  3. Use the notes column for the reasoning and the signals you will watch.
  4. Add rows for decisions specific to your product, such as who may push an urgent security fix outside the normal waves.
  5. Download the CSV and keep it with your release procedure. Review it after every incident.

Reading the default example

Example (fictional). A policy written for Loamwick’s LW-1 trial fleet. Two named people can sign a production release, the key stays in the signing service and nobody signs from a laptop (owner: CTO). Wave 1 is the team’s own 4 bench probes, on the same hardware revisions as the fleet, then 12 trial probes, then the rest (firmware lead). Waves are 48 hours apart, longer if a weekend falls inside, while the team watches reconnects and battery voltage (firmware lead). The rollout halts if more than 1% of updated devices roll back or go silent: halt first, then investigate (firmware lead). Downgrades are allowed only to versions that are not missing a known security fix, and the security counter refuses images with a lower counter (CTO). Trial sites hear by email two days before wave 3, with a plain-language summary of the release notes (customer success). End of support for a hardware revision is announced 12 months ahead, and security fixes continue until that date (CEO).

Three rows deserve a closer look.

When we halt counts devices that go silent, not only rollbacks. MCUboot reverts an image that boots but is never confirmed, so a crash at start-up shows up as a rollback. A release that confirms itself and then stops reporting does not. On a 40-probe trial, 1% is less than one probe, so in practice any single rollback or silent probe halts the rollout.

Downgrades rests on a mechanism worth understanding. MCUboot offers two kinds of downgrade prevention: comparing image versions, which its documentation says works only with overwrite-based updates, and a security counter stored in a trusted, non-volatile part of the device. The counter does not have to rise with every release. Raise it only in releases that fix a vulnerability, and devices will accept a rollback to any version since the last such fix and refuse anything older. That is what this rule asks for.

End of support carries regulatory weight in some markets. The UK’s product security regime, in effect since April 29, 2024, requires makers of consumer connectable products to publish the minimum period for which security updates will be provided, with an end date. Under the EU Cyber Resilience Act, whose main obligations apply from December 11, 2027, the support period is generally at least five years, and products must be able to receive security updates, where applicable automatically by default with a clear way to opt out. This page is not legal advice; check what applies to your product and markets.

How the worksheet works

Four text columns and no calculation. You can add, edit and remove rows; Download CSV saves what is on screen, and Print gives a paper copy for a review meeting. Nothing is stored or sent.

Limits

  • A policy is only as good as the pipeline behind it. A two-person signing rule needs a signing service that enforces it. A halt rule needs a dashboard that shows rollbacks and silent devices within the soak time.
  • The example is for a small trial. A fleet of thousands needs wave sizes and a halt threshold that make sense per wave; the staged rollout planner turns a percentage into a device count.
  • Owners change. Review the owner column whenever someone joins or leaves, and after any handover.

What to do next

Set wave sizes and soak times with the staged rollout planner, and check each release against the firmware release checklist. Our over-the-air updates service writes this policy with you as part of the rollout plan, and the security page explains how we handle signing keys and access to your systems. More in the updates and releases section of Field Update.

Send us your board and your plan.

A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.