Request a firmware review
Menu
Startups taking firmware in-house from a contractor or consultancy

Firmware handover checklist for your own team

Handover is finished when your own engineer can build, sign and release a version without help. Fifteen checks to get there.

Key characteristics

Items
15 in four groups
Groups
Code and builds, documents, keys and accounts, people
Output
Ticks on screen, CSV download, print
Runs
In your browser with nothing sent

Checklist: Firmware handover checklist for your own team

Tick items as you confirm them. Ticks stay on this page only; download the list when you are done.

Code and builds
Documents
Keys and accounts
People

0 of 15 items confirmed

Every outside firmware engagement should end with your team able to carry on without it, and that includes ours. A handover made of a repository link and a goodbye email leaves a startup owning code it cannot build, keys it cannot find and a release process nobody on staff has run. This checklist defines handover by what your team can do afterwards, in four groups: code and builds, documents, keys and accounts, and people.

How to use it

Agree on the list at the start of the engagement, not at the end, so documents and access build up as the work goes on. Review it together a few weeks before the planned handover date, and sign off only when every item is ticked or explicitly waived. Download the CSV as the record. Ticks are not saved if you leave the page.

The four groups

Code and builds

The repository is transferred or access granted with its full history; a clean build works from a fresh checkout using the written instructions; the CI pipeline runs under your account; and toolchain versions are pinned and documented. The fresh-checkout build is the real test. It catches the file that only ever existed on a contractor’s machine. If your builds are reproducible (the same source, environment and instructions give bit-by-bit identical output), you can also prove that the binary in the field came from the code you now hold.

Documents

An architecture overview (tasks, drivers, memory map and boot flow); the release procedure from tag to signed image to rollout; hardware notes (pin map, clock tree, known board issues); and a ranked list of open issues and planned work. Documents belong in your repository next to the code they describe, where they get updated with it.

Keys and accounts

Signing keys and update server accounts owned by you; contractor access removed from every system after handover; the recovery procedure for a lost signing key reviewed; and cloud and device provisioning credentials rotated. This is the group that matters most and the one most often skipped. The simplest version is a production signing key created in your own signing service from the start, so no contractor ever holds it. MCUboot’s tooling supports that way of working: the bootloader build needs only the public key, which can be exported without the private key.

People

Walkthrough sessions recorded for your team; your engineer has built, flashed and released one version unaided; and a named contact for questions during the agreed follow-up period. The unaided release is the item that proves all the others.

Reading the example

Example (fictional). Loamwick’s engagement ends with a team handover. Near the end, the startup hires its first firmware engineer, who builds the firmware from a fresh checkout, works through the recorded walkthroughs and the release procedure, and then ships a release through the same staged waves used for 1.1.0, with the outside team watching rather than doing. The checklist is signed only after that release is out.

The order in the example matters. Reading documents and watching recordings feels like progress, but the first unaided release is where the gaps show: a missing environment variable, a signing step that needed someone’s personal login, a dashboard nobody shared. Finding them while the outside team is still available costs an afternoon. Finding them six months later can cost a release.

Limits

  • Ownership is set by the agreement. This checklist covers what is handed over, not who owns what. Ownership and licensing terms are set out in each agreement.
  • It assumes a microcontroller product. Embedded Linux products add image build systems, package feeds and update servers to the code and accounts groups.
  • Recordings age. Keep the written documents current as the code changes; treat the recordings as an introduction, not the reference.

What to do next

Our documentation and onboarding service is built around this checklist, and a team handover is one of our engagements. The security page explains how we handle signing keys and access to your repositories. Before your team’s first release on its own, run the firmware release checklist and the secure boot checklist. More in the firmware architecture 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.