How to track PCB prototypes: a practical system

Published 15 September 2026

Every hardware team eventually hits the same wall. The first spin of a board produces five prototypes and everyone knows where they are. By the third spin there are forty, half of them reworked, a few at a test house, one on a customer’s desk, and a spreadsheet nobody quite trusts.

This guide describes a tracking system that scales from your first build to pilot production. It works in a spreadsheet, in Proto Tracker, or anywhere else. The principles matter more than the tool.

1. Give every physical unit its own identity

The unit of tracking is one physical board, not a design and not a batch. Each board gets a serial number that is:

• Unique within the design. MC4-007 should only ever mean one board.
• Physically on the board. A silkscreen field, a sticker or a QR label. If you can’t read it with the board in your hand, it isn’t a serial.
• Never reused. When a board is scrapped its serial retires with it.

We cover schemes in detail in serial numbering for prototypes, but the short version is prefix + zero-padded counter, for example MC4-001.

2. Separate designs, revisions and units

Most tracking systems go wrong by flattening three different things into one list:

Level	Example	Changes when
Design	MC-4 motor controller	You start a new product
Revision	Rev B	The layout or BOM changes and new boards are fabricated
Unit	MC4-014	Never. It’s a physical object

A unit belongs to exactly one revision of one design. Keeping these apart lets you ask questions like “how many rev B boards passed thermal test?” without counting cells by hand.

3. Treat rework as data, not notes

Between revisions, boards get modified: bodge wires, swapped resistors, cut traces. These mods are where tracking usually breaks down, because they’re done quickly, often late, and recorded (if at all) in a free-text notes column.

Instead, define each mod once against the revision it applies to (“Rev A: bodge R12 to 10k”), then record per unit whether it has been applied, by whom and when. Now “which boards still need the fix?” is a filter, not an investigation. We go deeper in tracking rework and bodge wires.

4. Track status and location separately

Status answers what state is it in? Location answers where is it? Teams often merge them (“At EMC lab” as a status), which falls apart as soon as a board fails a test while it’s at the EMC lab.

Keep a short, ordered list of statuses that match your process, for example:

1. Assembled
2. In bring-up
3. In test
4. Passed / Failed
5. Scrapped

And a list of locations, flagging the ones outside your building (test houses, customers, contract manufacturers) so off-site boards are easy to review.

5. Keep a change log you don’t have to remember to write

The most valuable question in hardware debugging is “what changed?”. A board that passed last week and fails today has a history, and you want it.

Whatever tool you use, every change to a unit’s status, location, revision or mods should be logged automatically with the time, the person, and the before and after values. If the log depends on people remembering to write it, it will have gaps precisely when you need it.

In a spreadsheet, turn on version history and restrict who can edit. In Proto Tracker the history is automatic and append-only: it’s written in the same database transaction as the change itself and can’t be edited afterwards.

6. Make the record reachable from the bench

Tracking only works if updating it is faster than not updating it. Two things help most:

• QR labels that open the unit’s record on a phone.
• Inline editing of the two things that change most, status and location, without opening a form.

7. Review it weekly

Ten minutes a week keeps the data honest: filter for units at external locations, units stuck in the same status for a long time, and failed units without notes. Fix what’s wrong, and your tracker stays trusted, which is the whole point.

---

Want this without building it yourself? Proto Tracker implements everything above, free for individual engineers. Start at app.proto-tracker.com.