What Happens When Your CM Just Assembles What You Send Them
30 Apr, 2026There is a version of contract manufacturing that looks appealing on the surface. You send your files. They build your boards. No back-and-forth, no questions, no delays. You get boards back fast, and everything feels efficient.
Until the boards come back wrong.
Design for manufacturability PCB review is not a formality. It is the part of the manufacturing process where an engineering-capable contract manager reads your design and asks the question a passive assembler never asks: is this actually going to work? What you find out when that step is skipped is rarely cheap.
The Boards Come Back. The Problems Don’t.
A passive CM is not making a mistake by building what you send. They are doing exactly what the contract says. The problem is that electronic designs, especially at the prototype stage, routinely contain issues that are invisible on screen and obvious on a board.
Component placement that creates soldering access problems. Trace widths that sit right at the edge of fabrication tolerances. Test points buried under components. A BOM with part numbers that reference a discontinued alternative and an active one interchangeably. None of these will stop a passive assembler from running your job. They will just become your problem after the fact.
Rework is expensive. A re-spin is more expensive. And the timeline cost of going back to layout after you have already paid for a prototype run is the kind of setback that pushes a funding milestone or regulatory submission by weeks. The boards came back. The problems came with them.
What a Passive CM Never Flags
The issues that passive assembly lets through are not exotic. They are the same categories that appear in project after project when no one is doing design for manufacturability review before the job runs.
Trace widths and clearances are the most common. A design that looks clean in your layout tool may have traces that are technically fabricatable but sit so close to minimum spec that yield drops, especially across temperature cycling. A CM running your job without DFM review will build it anyway. You will see the failures in testing, not in a pre-run file check.
Component placement problems follow a similar pattern. Fine-pitch ICs placed too close to passives create bridging risk during reflow. Components near board edges can interfere with depaneling. Tall components in shadow zones create inspection problems for AOI. None of this stops production. It just makes the output less reliable and the inspection process less useful.
BOM hygiene is another category that passive assembly ignores by design. Inconsistent part numbers, alternates that are not actually electrically equivalent, references to obsolete parts without approved substitutes: a passive assembler will source what they can find and build. An engineering review surfaces the discrepancy before the job runs and before you receive a board built with a component that was never validated in your circuit.
The pattern behind all of these is the same. A passive CM’s job is throughput. Reviewing your design for problems is not throughput. It is engineering work, and most assembly operations are not set up to do it.
Why So Many CMs Default to Passive Assembly
This is not an indictment of the contract manufacturing industry. Passive assembly is a rational business model for a certain kind of operation. High volume, established designs, customers who have done their own DFM, known-good files: in that environment, a CM that builds what it receives can run efficiently and deliver consistent output.
The problem is that this model gets applied to prototypes and new product development work where it does not belong. Engineering teams bring early-stage designs to production-oriented shops because the price is right or the lead time is short. The shop assembles the job. Problems surface after the fact. The customer assumes manufacturing variation. The CM assumes the design was approved by someone. No one asks the question that would have caught the issue on day one.
An engineering-capable CM operates differently because it is staffed differently. DFM review requires someone who can read a schematic and a Gerber file and understand the relationship between them. It requires someone who knows what reflow profiles do to specific component geometries and what that means for placement rules. That capability is not universal, and shops that have it invest in using it on every job, not just on jobs where the customer asks.
What an Engineering-First Review Actually Catches
At Evertech, the process starts with file review before a single board runs. That means Gerbers, BOM, assembly drawings, and schematic. The goal is to identify anything in the design that will create a manufacturability, reliability, or yield problem and flag it before it becomes physical.
The categories that come up most often: trace widths and spacing at or near minimum spec for the intended fabrication process; component placement that creates inspection access issues for AOI; silkscreen markings that overlap pad areas and will be obscured after soldering; BOM inconsistencies where alternates are listed without confirmation that they are electrically equivalent; and missing or ambiguous callouts for controlled impedance layers or specific stackup requirements.
When issues are found, the conversation is direct. Here is what we found, here is the risk if we build it as-is, here is what we recommend. The customer decides how to proceed with complete information. That is different from a shop that builds what it receives and lets you discover the problem in testing.
This is what engineering services and PCB assembly working under the same roof actually enables. The people reviewing your files are the same people running your boards. There is no handoff between a sales team and a production floor where context gets lost. If your design has a question mark in it, the engineer who would have to work around it is the one who finds it.
Questions Worth Asking Before You Commit
If you are evaluating a CM and want to understand whether they are going to catch problems or just build what you send, a few direct questions will tell you quickly. The first is whether they perform a design for manufacturability review before every job runs, and specifically what that review covers. A shop with a real DFM process will give you a specific answer. A shop without one will tell you they look at the files.
Ask who performs the review. Is it an engineer who can engage on your design, or is it a pre-production check against a standard checklist? Ask whether they have caught specific issues during DFM review that would have caused production failures, and whether they can describe one. Ask what happens when they find a problem: do they flag it and wait for your input, or do they make a judgment call and build anyway?
The 5 questions every engineer should ask their PCB manufacturer before signing off covers this territory in more detail. The underlying principle is the same. A manufacturing partner who welcomes that conversation is showing you how they operate. One who deflects or gives you vague answers is telling you the same thing.
The 7 silent killers of PCB projects documents exactly what makes it through when these questions never get asked. Ignoring DFM and assuming the manufacturer will figure it out are two of the most expensive entries on that list.
The Cost Is Not Always Obvious Up Front
A passive CM often looks cheaper. The quote is lower. The lead time is shorter. There is less back-and-forth. What does not appear in that comparison is the cost of the problems that go undetected until you are testing boards, or the cost of a re-spin, or the timeline impact of discovering a layout issue that should have been caught at file review.
Design for manufacturability PCB review adds time at the front of the job. It is time well spent. The alternative is finding out what your CM missed after the boards are already built.
If you are working on a new product and you are not confident your current manufacturer is actually looking at your design before they run it, Evertech is always happy to take a look. Reach out at contact@evertechinc.com or through the contact form to start the conversation.
