Insight · Medical devices
Creating the FDA documentation for a Healthcare Hardware Product
We've become fans of the FDA review process, once we understood the purpose behind it. The structure it asks for, and the regulations and procedures that come with it, have changed how we build software for regulated products.
January 22, 2026 · 7 min read

We worked on a healthcare hardware product, a device that pairs with an app on the user's phone. Our work covered the device's firmware, the iOS and Android apps and the connection between them, and when the product moved toward FDA submission we also prepared the software documentation that goes with it. This article shares what that process taught us, and how it has changed the way we run projects.
What the FDA Looks For
The FDA reviews the evidence behind a product as well as the product itself. Each requirement needs to be documented, linked to the risks it addresses, reflected in the design and verified by testing.
The level of rigor depends on how much harm a software failure could cause. Software whose failure could seriously hurt a patient is held to a higher standard, with more documentation and more testing expected behind every part of it.
Working through the process, we came to see the intention behind all of this paperwork. The FDA wants to know that the people who use a device are protected, and that the team who designed and built it kept their safety in mind at every step. Seen that way, the documentation became a record of the care that went into the product, and we started giving it the same attention as the code itself.
What the Submission Taught Us
The biggest lesson was the importance of writing the specifications before any code. On a regulated product every requirement has to be traced through design, risk and testing, and that only works when the requirements are settled first. We now give this stage the time it needs, debating the possible approaches as a team, weighing their risks and recording why each decision was made, so the reasoning is on paper long before anyone asks for it.
Development starts once the specifications are outlined and agreed, and from then on the team builds what was planned. When something needs to change along the way, the change goes back through the specifications first, so the documents and the product stay in step. Our development plans, maintenance plans and support policies work the same way, set up when a project begins and kept current as it evolves.
Consistency mattered just as much, because a submission has to read as one coherent body of work, even when several teams contributed to it. We use shared templates, consistent naming and clear version control, so every document fits with the rest and requirements can be traced through design, risk and testing.
None of this helps unless the process is actually followed, so we keep ours practical, with ready-made templates, checklists at key milestones and reviews built into the normal workflow. We collect information from each specialist while the work is happening, rather than reconstructing it months later, and one person owns the process from start to finish.
Cybersecurity and Life After Launch
For a connected device, cybersecurity is no longer a side topic. The FDA expects manufacturers to show how the device is protected, how vulnerabilities will be found and fixed, and exactly which third-party software it contains, in the form of a software bill of materials (SBOM).
That is far easier when security is designed in from the start. We threat-model the firmware, the apps and the connection between them early, and keep the SBOM up to date with every release rather than assembling it just before submission.
The work continues after approval, because vulnerabilities have to be monitored, third-party software tracked and updated, and the product supported until the end of its life. We plan for this from the start, so the commitments made in the submission are ones the team can keep, and the same ongoing care we describe in our article on maintenance applies to a medical device just as much as to any other product.
Conclusion
Preparing a connected medical device for FDA submission is a big undertaking, and much of the work happens long before the submission itself. Teams that build documentation, risk management and security into the project from the beginning will find the process far smoother than those who try to assemble it at the end.
ActiveColor can help with both the product and the documentation that supports it. We've been through the process, we know where the gaps tend to appear, and we build projects so the evidence is in place when it's needed. If you're planning a device or a submission, talk to us about where you are and what's ahead.