Build a BOM from clues, not from wishful part numbers

Custom builds are full of parts that do not have a clean catalog home: a salvaged connector, a motor with an abbreviated label, a board made for an earlier prototype, or a fastener that fits only one enclosure. The build can work perfectly and still be difficult to reproduce.

The remedy is to treat identification as part of the build system. Every unusual component gets an evidence packet before it becomes a line in the BOM.

Give each part an identity before it gets a quantity

A useful BOM row has more than a name and a quantity. It has a stable identity, a role in the assembly, and enough evidence for another builder to find the same part or approve a substitute.

For each unusual item, capture:

• The working name used in the design.
• The manufacturer marking, if any, without correcting its spelling.
• The mechanical envelope and interfaces that cannot change.
• The electrical, thermal, or material constraints.
• The source of the identification and its confidence level.
• The approved alternative, if the design allows one.

Photograph the part before it disappears into the prototype. Start an identification workspace when you want the images, markings, and candidate notes attached to the same record instead of scattered across a build chat.

That record becomes more valuable after the prototype works. The next revision can distinguish a part that was selected intentionally from one that was simply available on the day.

Measure the interfaces that define the design

Custom hardware often fails at interfaces, not at the headline specification. Two connectors can share a contact count and still disagree on pitch, keying, latch clearance, or wire exit. Two bearings can share a bore and still differ in width, seal, or load rating.

Use a constraint-first worksheet:

1. Mechanical: envelope, hole pattern, datum surfaces, threads, insertion depth, and keep-outs.
2. Interface: contact count, pitch, pin order, mating direction, voltage, current, and protocol.
3. Environment: temperature, vibration, moisture, chemicals, duty cycle, and service access.
4. Supply: minimum order, lead time, lifecycle, region, and whether a second source exists.

Mark each constraint as hard, preferred, or unknown. This prevents a candidate with a perfect label but the wrong mounting geometry from winning the comparison.

Use a manual to resolve the hidden dimension

When a drawing or service document exists, check the manual references before you redraw a part from a photograph. Look for the view that exposes the datum, not just the picture that resembles your prototype.

For a custom build, record the document revision and the exact figure used. If the document lists multiple suffixes, copy the differences into the BOM note. A suffix can change connector orientation, coating, keying, or a hole diameter while leaving the family name unchanged.

When no authoritative drawing exists, state that plainly. A measured sketch with tolerances is more reproducible than an unqualified “looks like” description.

Create candidate tiers instead of one fragile answer

Do not force every row to have a single perfect part number. Use tiers that match the design reality:

• Selected: the identity and interfaces are verified against the build.
• Qualified alternative: the substitute satisfies the hard constraints and has a documented difference.
• Lead: the family is plausible, but a measurement or source still needs confirmation.

This is especially useful when sourcing. The parts index is a practical starting point for hard-to-find component families, while your BOM remains the authority for what the current build accepts.

Add a reason to every rejection. “Wrong” is not enough; “same pitch, wrong keying” tells the next builder what to avoid and protects against accidentally reintroducing the candidate after a vendor change.

Make revision changes legible

When a part changes, update the evidence packet and the BOM row together. A revision note should say what changed and why:

REV C — replaced connector variant A with variant B.
Reason: latch clearance at the rear panel.
Unchanged: pitch, contact count, pin order.
Recheck: cable bend radius and enclosure cutout.

This format is deliberately plain. It gives a fabricator, firmware engineer, and future maintainer the same starting point without requiring them to reconstruct a conversation.

Build for the next person at the bench

The best custom-build BOM is not the one with the most rows. It is the one that makes uncertainty visible and keeps the evidence close to the decision. Put the photo, measurement, drawing reference, and sourcing status where a new builder can find them.

If the prototype only works with one unmarked part, treat that as a design risk. Measure it, label it, and record the interface before ordering more. A one-off build becomes maintainable when its clues become part of the artifact—not tribal knowledge around it.