Avoid These 3 PCB Mistakes Before You Order

A PCB can look correct on the screen and still fail during assembly, testing, or field use. I often see the same three PCB mistakes: unclear design rules, weak component placement, and poor communication with the manufacturer.

Each issue can increase rework, delay testing, and raise production cost. A careful review before fabrication can prevent many of these problems.

1. Using the wrong design rules

A board may pass an electrical check in the design software while remaining difficult to manufacture. Trace width, spacing, drill size, copper weight, and layer structure all affect production.

For example, a designer may use narrow traces for a compact control board. The layout looks neat, but the selected fabricator may not support those trace sizes at the quoted price. The factory may ask for a layout change, or the board may require a different process.

I reduce this risk by checking the manufacturer’s PCB capabilities before routing the board. I confirm:

• Minimum trace width
• Minimum spacing
• Smallest finished hole
• Annular ring requirements
• Layer count
• Copper thickness
• Solder mask clearance
• Board edge tolerance
• Controlled impedance needs

I also create a design rule file based on the selected production process. This is more useful than relying on default settings in the CAD software.

A small spacing change can affect the whole layout, so I prefer to confirm production limits before placing components.

1. Placing components without considering assembly

Component placement affects more than the appearance of a PCB. It influences signal quality, heat flow, inspection, repair, and assembly time.

One common problem appears when connectors, large capacitors, and heat-producing parts are placed without checking the assembly direction. A connector may block access to a test point. A tall capacitor may prevent a nearby component from being placed by the assembly machine. A voltage regulator may sit close to a sensitive sensor and add unwanted heat.

I review the board from several angles:

• Can the assembly machine reach each part?
• Are polarized components easy to inspect?
• Do tall components block smaller parts?
• Are test points available for key signals?
• Are heat-producing parts separated from sensitive devices?
• Is there enough space around connectors and mounting holes?
• Can a technician replace a damaged part?

A practical example is a motor control board with a power transistor near a temperature sensor. The circuit may work during a short bench test, but heat from the transistor can affect sensor readings after longer operation. Moving the sensor away from the heat source and adding a clear thermal path can make the design more stable.

I also keep related components close to the device they support. Decoupling capacitors should sit near the power pins of the integrated circuit. Gate resistors should remain close to the transistor gates. This reduces unwanted loop area and makes the layout easier to check.

1. Sending incomplete production files

A manufacturer needs more than a single PCB layout file. Missing or inconsistent files can lead to questions, delays, or a board that does not match the intended design.

Before sending the order, I prepare and compare:

• Gerber files
• Drill files
• Pick-and-place data
• Bill of materials
• Assembly drawings
• Schematic PDF
• Fabrication notes
• Stack-up information
• Impedance details, when required
• Special instructions for connectors or sensitive parts

The file names should remain consistent. Part references on the assembly drawing should match the bill of materials and pick-and-place file. A capacitor listed as C15 in one file should not appear as C16 in another.

I also open the exported Gerber files in a separate viewer. This check can reveal missing solder mask openings, incorrect board outlines, reversed text, or a copper layer that was exported with the wrong settings.

A real production issue can come from a simple mismatch. A bill of materials may list one resistor package while the footprint uses another size. The part may fit poorly, or the assembly supplier may place a substitute without enough information. Clear package data and approved alternatives help reduce this risk.

My review process is simple:

• Compare the schematic with the PCB layout.
• Run electrical and design rule checks.
• Review the board outline and mounting holes.
• Check polarized and orientation-sensitive parts.
• Inspect the exported manufacturing files.
• Confirm the bill of materials and approved parts.
• Ask the manufacturer to review unusual requirements.

The three PCB mistakes are easy to describe, but they often appear together. A board with narrow traces may also use an unsuitable layer stack. Poor component placement may hide test points. Incomplete production files may make the factory guess which version is correct.

I treat PCB design as a shared process between the electrical designer, mechanical team, assembly partner, and manufacturer. When these groups review the same information early, the board has a better chance of moving from prototype to production with fewer changes.

A clean schematic is useful. A finished PCB also needs suitable manufacturing rules, practical placement, and complete production data. Checking these areas before fabrication can save time and reduce avoidable rework.

Before I place an order, I take a few minutes to check the details. A small mistake in size, quantity, delivery address, or return terms can lead to extra cost and wasted time.

This simple check works for clothing, electronics, home items, services, and many other products.

1. Check the product details

I read the product name, model, size, color, material, and listed features. Photos can help, but they may not show every detail.

For example, a desk may look large in a photo but measure only 80 cm wide. I check the measurements and compare them with the space at home before ordering.

For electronics, I look at:

• Model number
• Voltage and plug type
• Storage or memory
• Supported devices
• Included accessories
• Warranty information

For clothing, I check the size chart instead of relying only on S, M, L, or XL labels. Size standards can vary between brands.

2. Review the total price

The product price may not be the full amount I pay. I check shipping fees, taxes shown at checkout, service charges, installation costs, and optional extras.

A low-priced item may cost more after delivery and setup fees are added. I prefer to compare the final checkout amount rather than the item price alone.

I also check whether the listed price applies to one item, one set, or a smaller part of the product. A furniture listing may show a complete room in the image while the order includes only one table.

3. Confirm the seller and product source

I check the seller name, business details, customer support options, and product description. A clear seller profile makes it easier to ask questions or request help after purchase.

I look at customer reviews with care. I pay attention to comments about:

• Product quality
• Delivery condition
• Actual size
• Ease of use
• Customer service
• Differences between the photo and the received item

A review with specific details is often more useful than a short comment with only a star rating.

For example, a buyer may write that a phone case fits the listed model but blocks part of the camera. That kind of detail can help me avoid an unsuitable order.

4. Check delivery information

I confirm the delivery address, phone number, estimated delivery period, and available delivery methods. I also check whether the seller delivers to my area.

If I live in an apartment building, I make sure the address includes the building number, unit number, and access details where needed.

For larger products, I check:

• Package size
• Delivery location
• Door and stair access
• Assembly service
• Need for an adult to receive the order

A washing machine may fit inside the home, but the package may not pass through a narrow doorway. Checking these details before ordering can prevent a difficult delivery.

5. Read the return and refund terms

I look for the return period, product condition requirements, return shipping rules, refund method, and any excluded items.

Some products cannot be returned after opening, use, activation, or removal of a seal. Personalized goods and digital products may follow different rules.

I save a copy of the order page, product description, and return terms. If the listing changes later, these records can help me explain what I ordered.

6. Ask questions before paying

When a detail is missing, I contact the seller before placing the order. Useful questions include:

• Is the listed size the product size or package size?
• Are batteries, cables, or mounting parts included?
• Does the item support my device or system?
• Can the seller provide the material or care details?
• How will damaged items be handled during delivery?

A clear answer helps me make a better choice. If the seller avoids basic questions or gives answers that do not match the listing, I pause the order.

7. Check payment and account details

I make sure the website address is correct and that the payment page is secure. I avoid sending card numbers, passwords, or identity documents through informal messages.

I check the billing name, delivery address, selected payment method, and order quantity before confirming payment. If the quantity shows two instead of one, I correct it before placing the order.

After payment, I keep the order number and confirmation message. These details are useful when checking delivery status or contacting support.

8. Compare the product with my actual needs

I ask myself what problem the product needs to solve. A popular item may still be unsuitable for my home, work, budget, or daily routine.

For example, I once considered a compact printer for occasional home use. The device was small, but the replacement ink cost more than I expected. A quick check of ongoing costs helped me choose a different model.

I look at the full use experience:

• Will I use it often?
• Does it fit my available space?
• Can I find replacement parts?
• Is it easy to clean or maintain?
• Does it work with the devices I already own?
• Is the return process practical if the item does not fit my needs?

9. Pause when the information feels unclear

I do not place an order when the product description, price, seller details, or return terms are difficult to understand. Clear information supports a better decision.

A useful order check can take only a few minutes:

1. Read the product details.
2. Confirm the total price.
3. Review the seller and customer feedback.
4. Check delivery conditions.
5. Read return and refund terms.
6. Ask questions about missing information.
7. Confirm the final order details before payment.

I treat the checkout page as a confirmation step, not a quick button to press. This habit helps me choose products that match my needs and reduces avoidable order problems.

A small PCB error can create a long chain of problems.

A wrong footprint may prevent assembly. A missing via can break a power path. An unclear silkscreen mark can lead to reversed parts on the production line. When the board reaches testing, the cost may include rework, scrap, delayed delivery, and extra engineering hours.

I have seen teams spend more time fixing avoidable layout problems than improving the product itself. A clear review process helps reduce that risk before files reach the fabricator.

Check the schematic before layout

Many PCB problems begin before the board outline is created.

I review the schematic for:

• Unconnected pins
• Incorrect net names
• Missing power connections
• Unused pins that need a defined state
• Incorrect component values
• Connector pin assignments
• Voltage levels between devices

A simple example is a power regulator connected to the wrong voltage rail. The layout may look clean, but the board can still fail when power is applied.

I compare the schematic with the product requirements and the selected components. If a device needs 3.3 V but receives 5 V, no amount of visual inspection can repair that mistake later.

Match every footprint to the real part

A symbol represents an electrical function. A footprint must match the physical component.

I check:

• Pin numbering
• Pad size
• Pad spacing
• Package type
• Thermal pad size
• Pin-one marking
• Component height
• Land pattern guidance from the datasheet

A footprint can look correct in the CAD library and still be wrong for the part on the bill of materials. This often happens when two packages have similar names but different pad layouts.

I place the component drawing from the datasheet beside the PCB footprint during review. This takes little time and can prevent a board from being assembled with every pin shifted by one position.

Review power and ground paths

Signal routing receives much attention, while power paths are sometimes treated as an afterthought. That can lead to voltage drop, heat, noise, or unstable operation.

I check whether:

• High-current traces have enough width
• Return paths remain short
• Ground planes are connected as planned
• Thermal vias are placed under heat-producing parts
• Decoupling capacitors sit near the related power pins
• Sensitive signals are separated from switching nodes
• Connector grounds have a suitable return path

A narrow trace may pass a basic design rule check and still perform poorly under load. I use the expected current, copper thickness, trace length, and temperature needs to guide the layout.

Use design rule checks with care

Automated checks are useful, but they do not understand every product requirement.

A design rule check can find:

• Clearance violations
• Unrouted connections
• Overlapping shapes
• Missing board-edge spacing
• Hole and pad conflicts
• Trace width problems

It may not detect a connector facing the wrong direction. It may not know that a test point is blocked by a shield. It may not identify a silkscreen label hidden beneath a component.

I run the tool, review each warning, and confirm that approved exceptions are documented. A clean report is helpful, but it is not a substitute for looking at the board.

Inspect the board from the assembler’s view

I imagine the production operator holding the board.

Can the pin-one mark be seen?
Can the connector orientation be understood?
Can the test probe reach the required points?
Can polarized parts be installed without guessing?
Will a large component block a smaller part nearby?

A practical PCB review includes the assembly drawing, not only the copper layers. I check reference designators, polarity marks, fiducials, tooling holes, panel rails, and component spacing.

The Raspberry Pi 4 provides a useful lesson. Early boards had a USB-C power compatibility problem linked to the CC resistor arrangement. Some electronically marked USB-C cables and chargers did not power the board as expected. The board could function with many chargers, yet the connector design limited compatibility with others. This shows why a connector circuit deserves the same care as the mechanical shape.

Build a prototype test plan

Testing should begin before the prototype arrives.

I list:

• Power input checks
• Startup current
• Main voltage rails
• Reset behavior
• Clock signals
• Communication buses
• Protection parts
• Heat around power devices
• Mechanical fit
• Cable and connector behavior

I apply power with a current limit and measure each rail before connecting the full system. This gives me a safer way to find shorts, reversed parts, and unexpected current draw.

I record the expected result beside each test. “The board works” is too vague. “The 3.3 V rail remains within the agreed range at the selected load” gives the team something that can be measured.

Keep revision control simple

A PCB error can return when an old file reaches production.

I keep the schematic, layout, bill of materials, fabrication files, assembly files, and review notes under the same revision. I remove outdated files from shared production folders and use clear file names.

When a change affects a footprint, net, component value, or board outline, I repeat the related checks. A minor capacitor change may not need a full mechanical review, while a connector change may affect routing, assembly, enclosure fit, and testing.

The most useful PCB review is not the longest one. It is the review that checks the right risks before fabrication. I compare the electrical design with the physical parts, inspect power paths, test the production files, and record each decision. That process can reduce rework and give the manufacturing team a board they can build with fewer questions.

Ordering food online should make a busy day easier. Yet many people still face unclear menus, missing details, delivery surprises, and long waits for support. A smarter order starts before I click “pay.”

I use a simple process that helps me choose the right items, control the total cost, and reduce avoidable mistakes.

I check the menu before choosing

A good menu should show the item name, size, main ingredients, price, and available options. I read these details instead of relying only on photos.

When I order for one person, I look for a suitable portion. When I order for a group, I compare shared dishes with individual meals. This helps prevent paying for more food than we need.

Food preferences also need attention. I check for ingredients such as nuts, dairy, seafood, or spicy sauces. If the menu does not explain an ingredient clearly, I contact the business before placing the order.

I build the order around the occasion

My order changes based on the situation.

For a quick lunch, I may choose one balanced meal and a drink. For a family meal, I compare the number of servings and select dishes that different people can share. For a meeting, I check whether the food is easy to divide and whether the delivery time matches the schedule.

This small step reduces random choices. It also makes the final order easier to review.

I review the full price

The item price is only one part of the total. I check service fees, delivery charges, taxes, packaging costs, and optional extras before payment.

A meal listed at $12 may cost more after several additions. That does not mean the order is wrong. I just want to understand what I am paying for.

I also remove extras that I do not need. A second sauce, a larger drink, or an additional side can raise the total without adding much value to the meal.

I confirm custom requests

Special requests should be short and clear.

Instead of writing, “Please make it better,” I might write:

“Please leave out the peanuts.”

“Pack the sauce separately.”

“Please do not add onions.”

Clear wording gives the restaurant a better chance to prepare the order as expected. I avoid adding too many requests, since the kitchen may not be able to support every change.

I choose a delivery time that fits my schedule

I do not select a delivery window without checking my plans. If I have a call at 12:30, a delivery around that time may create a problem.

A short delivery note can help:

“Please call when you arrive.”

“Leave the order with the reception desk.”

“Use the side entrance.”

The note should match the location and follow the platform’s delivery rules. I avoid sharing private details that are not needed for the delivery.

I check the order before payment

Before I place the order, I review five details:

• The selected items
• The quantity of each item
• The meal size and options
• The delivery address
• The total price

This review takes less than a minute. It can prevent common errors, such as sending food to an old address or choosing the wrong size.

A customer named Daniel once ordered lunch for his office. He had selected six meals but only five drinks. The mistake was easy to miss because the order page showed the meals and drinks in separate sections. A quick review helped him correct the quantity before payment.

Small checks can make a clear difference to the ordering process.

I save useful information with care

If I often order from the same place, I may save a delivery address or repeat a previous order. I still review the details each time. Menus, prices, store hours, and availability can change.

I also keep receipts when I need them for work expenses or group orders. A digital receipt makes it easier to check the payment record and divide the cost among several people.

I give useful feedback

If something goes wrong, I describe the issue with specific details. I mention the order number, the missing item, the condition of the food, or the time of delivery.

“Something was wrong” gives the business little information.

“Two drinks were missing from order 1842” is easier to check and resolve.

I also share positive feedback when the menu was clear, the order matched the request, or the packaging worked well. Practical feedback helps businesses improve the parts customers actually use.

Ordering smarter does not require a complicated system. I read the menu, plan around the occasion, check the full price, confirm special requests, and review the order before payment.

The goal is not to spend more. It is to make a choice that fits my needs, budget, schedule, and preferences. A clear process gives both the customer and the business a better chance of getting the order right.

A PCB can look complete on the screen and still fail during testing. I have seen boards with correct schematics, clean layouts, and approved Gerber files develop noise, heat, weak solder joints, or unstable signals after assembly.

Most PCB problems start earlier than the lab bench. A missing return path, a narrow power trace, an unsuitable component package, or a late mechanical change can create trouble that is expensive to fix. I use a simple review process to reduce these risks before fabrication.

Start with the product requirements

Before placing any component, I write down the working conditions of the board:

• Input voltage and expected current
• Signal speed and interface type
• Board size and layer count
• Connector positions
• Operating temperature
• Enclosure limits
• Assembly method
• Test points and service needs

This list gives the layout a clear direction. A small sensor board and a motor-control board may use similar software tools, but they need very different power paths, grounding methods, and thermal plans.

I also check whether the board will be assembled by hand, through a standard pick-and-place line, or with mixed processes. A package that looks efficient on the layout may create inspection or soldering problems during production.

Do not treat the schematic as a complete design review

A schematic can show that two parts are connected. It does not always show whether those connections are suitable for the real current, voltage, noise level, or temperature.

When I review a schematic, I ask:

• Does each power pin have the required bypass capacitor?
• Are unused pins handled according to the component data sheet?
• Can the regulator support the expected load?
• Are pull-up and pull-down values suitable for the signal speed?
• Are protection parts placed on the correct side of the connector?
• Is there a clear path for high-current return flow?
• Do the selected parts have stable supply status?

A common example is a microcontroller board that resets when a relay or motor starts. The schematic may show a regulator with enough average current, but the layout may place the motor return path close to the controller ground. The voltage dip and noise can reach the controller through the shared path.

The fix may include a better power structure, separate return paths, local capacitors, and a suitable driver. Changing only the firmware may hide the symptom without solving the board problem.

Give the current a clear path

Every current loop needs a route out and a route back. Designers often focus on the forward trace and give less attention to the return path.

For low-speed signals, a solid reference plane usually helps. For faster interfaces, the return current tends to stay close to the signal trace. A gap, slot, or split in the reference plane can force that current to move around the break. The result may be extra noise, signal distortion, or unwanted radiation.

I check each high-speed route together with its reference layer. If a trace changes layers, I look for a nearby ground via that gives the return current a short transition path. If a connector crosses from one board area to another, I inspect the full path rather than only the visible top-layer trace.

This matters for USB, Ethernet, HDMI, LVDS, clock lines, and other fast signals. A short trace can still perform poorly if its reference path is broken.

Keep noisy and sensitive circuits apart

A switching regulator, motor driver, relay, or high-current LED circuit can create voltage changes and magnetic fields that affect nearby analog or communication circuits.

I usually separate the board into functional areas:

• Power entry and protection
• Power conversion
• Digital processing
• Analog measurement
• Wireless or high-speed communication
• Output drivers

This separation does not mean that every area needs a separate ground plane. It means the current flow should be predictable and the noisy loops should stay compact.

For example, a temperature sensor placed beside an inductor may report unstable readings even when the sensor wiring looks correct. Moving the sensor away from the switching node, reducing the hot-loop area, and improving the reference path may solve the issue without changing the sensor.

Place decoupling capacitors where they can work

A bypass capacitor only helps when the current path between the capacitor, the power pin, and ground is short and low impedance.

I place the capacitor close to the related power pin, then connect it to the reference plane with a short route or direct via arrangement. A capacitor located several centimeters away may still help with lower-frequency changes, but it may not control fast current demand at the device pin.

I also check the capacitor value, voltage rating, package, and dielectric type. The printed value alone does not describe the full behavior across frequency and operating voltage.

A common mistake appears on processor boards: the schematic includes every required capacitor, but the layout places several of them in a distant row to make routing easier. The board may pass basic startup tests and fail during communication or heavy processing.

Review trace width and copper temperature

Trace width should match the expected current, copper thickness, allowed temperature rise, and board construction. I do not use one width rule for every net.

Power traces may need wider copper or polygon areas. Short pulses and continuous loads also need different checks. Narrow necks near pads can limit the benefit of a wide trace, so I inspect the complete current path.

High-current vias deserve attention as well. A wide top-layer trace connected through one small via may create a bottleneck. Multiple vias, larger holes, or a different layer structure can provide a better route.

For boards that carry heat, I review the thermal path from the component to the copper area, vias, and enclosure. A thermal pad with no useful connection to the board may leave heat trapped under the part.

Do not ignore manufacturability

A layout can meet electrical rules and still be difficult to build.

I check:

• Minimum trace and space rules from the selected fabricator
• Via size and aspect ratio
• Solder mask openings
• Component spacing
• Silkscreen overlap
• Pad sizes
• Board edge clearance
• Panelization needs
• Test probe access

A practical example is a dense board with two small connectors placed too close together. The parts fit in the CAD file, but the assembly nozzle, inspection camera, or technician cannot access them well. A small spacing change can reduce assembly risk.

I also avoid placing vias inside pads unless the fabrication process supports it. Unfilled vias can pull solder away from the joint and cause weak or uneven connections.

Protect external connections

Connectors are common entry points for electrostatic discharge, surges, reverse voltage, and wiring mistakes.

Protection components should sit close to the connector so unwanted energy has a short path to ground or another safe route. Long traces between the connector and the protection device can allow noise to travel deeper into the board.

I check the following items for every external port:

• Expected voltage range
• Possible reverse connection
• ESD exposure
• Cable length
• Shield connection
• Protection device capacitance
• Connector pin order
• Chassis or signal ground plan

A USB port, a motor cable, and a battery connector do not need the same protection approach. The interface standard and the product environment should guide the choice.

Use design rules, but do not rely on them alone

Electrical rule checks and design rule checks can catch many errors:

• Unconnected nets
• Clearance violations
• Missing connections
• Wrong footprints
• Short circuits
• Copper near the board edge
• Incorrect hole sizes

These tools cannot judge every design decision. They may not know that a crystal is too far from a controller, that a current loop is too large, or that a sensor sits in a noisy airflow path.

I run automated checks and then perform a visual review. I inspect the board by function, by current path, and by layer. Looking at the entire board only as a collection of lines makes it easy to miss system-level problems.

Check footprints against the actual parts

A footprint can be electrically correct and still be physically wrong.

I compare the library footprint with the manufacturer drawing:

• Pad length and width
• Pin-one location
• Thermal pad size
• Courtyard area
• Exposed pins
• Package height
• Recommended land pattern

This check is especially useful for connectors, power modules, switches, crystals, and parts with several package versions. A wrong footprint may not be discovered until components arrive, which can delay assembly and force a board revision.

For parts with a long lead time or uncertain supply, I review possible alternatives before routing. An alternative part may use a different pin order or package, so the layout should not assume that every replacement is a direct match.

Prepare for testing before sending files

A board without test access can turn a small fault into a long search.

I add test points for:

• Main input power
• Regulated rails
• Ground
• Reset
• Programming signals
• Communication lines
• Key analog nodes

I also make sure the test points are reachable after assembly. A hidden pad under a connector may look acceptable in the layout and be useless during debugging.

Before release, I review the bring-up sequence. I want to know where to measure power, what current is expected before firmware starts, and which signals confirm that each section is working.

The most useful PCB review is not a search for one dramatic error. It is a steady check of current flow, signal reference, heat, assembly, protection, and testing. When I treat the board as a physical system rather than a drawing, many design traps become easier to see.

A clean schematic, a careful layout, and a suitable fabrication plan work together. None of them can replace the others.

A PCB can look correct on screen and still fail during assembly, testing, or field use. I have seen small oversights cause large delays: a missing test point, an unclear stackup, a footprint that does not match the part, or a BOM that lists a component with a long lead time.

I use a practical checklist before sending any PCB design to fabrication. It helps me review the electrical design, board layout, manufacturing data, and test plan as one connected process.

1. Confirm the project requirements

I start with a short project record:

• Board length, width, and thickness
• Number of layers
• Maximum input voltage and current
• Signal speed and key frequencies
• Operating temperature range
• Connector locations
• Mounting hole positions
• Enclosure limits
• Required production quantity
• Target assembly method, such as SMT, through-hole, or mixed assembly

A board for a battery-powered sensor has different needs from a motor controller. The sensor may focus on low power and small size. The motor controller may need wider copper, stronger terminals, better heat control, and protection from electrical noise.

I also mark which requirements are fixed and which can change. This gives me room to adjust the layout without affecting the product enclosure or main circuit function.

2. Review the schematic

Before checking the PCB layout, I review the schematic from the power input to the main outputs.

I check:

• Every component has a clear reference designator
• Power and ground symbols are connected correctly
• Unused pins are handled according to the component datasheet
• Decoupling capacitors are placed near the related power pins
• Pull-up and pull-down resistors use suitable values
• Protection parts are included where the circuit needs them
• Connectors use the correct pin order
• Test points are added for key power rails and signals
• Net names are clear and consistent
• No hidden power pins are left unconnected

Power labels deserve extra care. A net named “5V” may not be the same as a regulated 5 V rail if the design has several power domains. I prefer names such as “5V_IN,” “5V_REG,” and “3V3_DIG” when the circuit contains multiple sources.

I run the schematic electrical rules check, then inspect each warning. A warning may be harmless, but I do not ignore it without recording the reason.

3. Check the component library

A correct schematic can still create a faulty board if the footprint is wrong.

For each part, I compare:

• Pin numbering
• Pad size and spacing
• Package outline
• Thermal pad size
• Courtyard area
• Polarity marks
• Recommended land pattern
• Component height
• Assembly orientation

I pay close attention to diodes, LEDs, electrolytic capacitors, connectors, voltage regulators, and integrated circuits. These parts often have pin or polarity details that vary between package types.

A useful example is a regulator with the same package name but a different pin arrangement. If the footprint comes from another part family, the board may pass a basic layout review while the assembled circuit remains unusable.

I also check whether the selected part is available through the planned supply channel. A footprint should match the actual component, not only a similar part shown in the library.

4. Review the board outline and mechanical data

I import the enclosure drawing, mounting details, and connector positions before routing critical signals.

The review includes:

• Board outline
• Cutouts and slots
• Mounting holes
• Hole diameter and tolerance
• Keepout areas
• Connector access
• Switch and LED positions
• Component height limits
• Heat sink clearance
• Distance from the board edge

I leave enough space around mounting holes for washers, screws, and assembly tools. I also check whether a tall component could touch the enclosure lid.

A board may pass electrical checks and still fail to fit into the product housing. Mechanical review prevents that type of late change.

5. Set the layer stackup

I ask the fabricator to confirm the proposed stackup before I calculate controlled impedance or complete sensitive routing.

I record:

• Copper weight for each layer
• Dielectric thickness
• Core and prepreg materials
• Finished board thickness
• Controlled impedance values
• Via structure
• Surface finish
• Solder mask color, if the product requires a specific option

For a four-layer board, I often place a solid ground plane close to the signal layer. This can reduce return path problems and give high-speed signals a more predictable reference.

The stackup affects trace width, differential pair spacing, via design, and signal quality. A trace width calculated from an assumed stackup may not meet the target after the fabricator changes the layer structure.

6. Review placement before routing

Placement sets the path for power, heat, signals, and assembly.

I usually place the parts in functional groups:

• Power entry and protection
• Regulation
• Processing or control
• Memory
• Communication interfaces
• Sensors
• Drivers and loads
• Connectors
• Test points

I keep current loops short. A switching regulator works better when the input capacitor, switching device, inductor, and output capacitor stay close to the recommended path shown in the datasheet.

I also keep noisy sections away from sensitive analog or sensor sections. Separating them by placement is easier than trying to fix noise with long routing changes.

Component orientation affects inspection and assembly. Consistent orientation can help reduce mistakes, especially when several parts use the same package.

7. Route power and ground with care

I check the expected current for every major power path. Trace width should match the current, copper weight, allowed temperature rise, and available space.

My power review covers:

• Input current path
• Regulator paths
• Motor or actuator paths
• Ground return paths
• Protection device connections
• Connector pin current
• Via current capacity
• Copper pours and neck-down areas

A wide trace does not solve every power problem. If the return path is narrow, interrupted, or forced around a noisy area, the circuit may still show voltage drop or noise.

I use ground planes where the stackup supports them. I avoid splitting a return path without a clear reason, especially under high-speed or sensitive signals.

8. Review high-speed and sensitive signals

The required checks depend on the interface. USB, Ethernet, CAN, LVDS, DDR, RF, and fast clocks each have different layout needs.

I check:

• Differential pair width and spacing
• Pair length matching where required
• Reference plane continuity
• Via count
• Stubs
• Trace length
• Termination placement
• Distance from noisy power areas
• Connector escape routing
• ESD protection placement

For a USB connection, I keep the pair together, use a suitable reference plane, and place protection parts near the connector. I do not treat every signal as a high-speed pair just because it has a fast edge. I review the interface guidance and the device data before setting layout rules.

Sensitive analog traces need their own review. I keep them short, avoid switching nodes, and place filters near the circuit section they protect.

9. Check thermal performance

Heat problems often come from small areas that were missed during layout.

I review:

• Regulator dissipation
• MOSFET heating
• LED power
• Processor temperature
• Copper area around thermal pads
• Thermal vias
• Airflow direction
• Distance from heat-sensitive parts
• Enclosure heat paths

A thermal pad must connect to the intended copper area through the recommended via pattern. I also confirm that the fabrication process can produce the selected via and pad design.

If a component is expected to run warm, I record the estimated power loss and check whether the board and enclosure can release that heat.

10. Run design rule checks

I run electrical and physical checks before manufacturing release.

Typical rules include:

• Minimum trace width
• Minimum clearance
• Minimum via size
• Hole-to-copper clearance
• Copper-to-edge distance
• Solder mask clearance
• Silkscreen-to-pad spacing
• Unconnected nets
• Short circuits
• Acute copper angles
• Plane clearance
• Courtyard conflicts

The rule values should come from the fabricator’s capability table and the board’s design needs. I do not copy values from an old project without checking the current process.

Each remaining warning needs a clear decision. I either fix it or document why it is acceptable.

11. Inspect the silkscreen and markings

Silkscreen supports assembly, inspection, and service work.

I check:

• Reference designators are readable
• Polarity marks are visible
• Pin 1 markers are clear
• Connector labels match the schematic
• Test point names are easy to find
• No text sits on exposed pads
• No labels are hidden under components
• Board revision and identification marks are present when needed

I avoid placing important marks near crowded areas. A tiny label that cannot be read during inspection offers little value.

12. Prepare manufacturing files

Before release, I generate the required files and open them in an independent viewer.

The release package may include:

• Gerber files
• NC drill files
• Pick-and-place files
• Assembly drawings
• Fabrication drawing
• Schematic PDF
• Bill of materials
• Stackup information
• Impedance notes
• Special process instructions
• Test requirements

I compare the Gerber view with the PCB layout. I inspect copper layers, solder mask, paste layers, drill files, board outline, and silkscreen separately.

File names should be clear. I include the board name, revision, and file type so an old version is less likely to enter production.

13. Review the BOM

The BOM connects the design to purchasing and assembly.

I check:

• Manufacturer part number
• Supplier part number, when used
• Quantity per board
• Reference designators
• Package
• Value
• Tolerance
• Voltage rating
• Temperature rating
• Approved alternatives
• Assembly notes
• Current supply status

I do not replace a part based on package similarity alone. Electrical ratings, pin function, thermal behavior, and firmware support may also change.

For a small prototype, I may list an approved substitute. For a larger build, I ask for confirmation before changing a component that affects performance or compliance testing.

14. Plan inspection and testing

A board is easier to test when test access is designed from the start.

I identify test points for:

• Main input power
• Regulated rails
• Ground
• Reset
• Programming interfaces
• Communication lines
• Critical analog outputs
• Fault signals

I define what the assembler or technician should measure, the expected range, and the condition of the board during the test.

For a controller board, a basic test may include power resistance, current draw, firmware programming, connector checks, communication, and load operation. The exact steps depend on the product.

I also consider whether a test fixture can reach the selected points. A test point hidden under a connector may exist in the layout but remain difficult to use.

15. Complete a final release review

At the release stage, I compare the final PCB, schematic, BOM, and manufacturing files.

I ask:

• Do all files show the same revision?
• Does the BOM match the placed components?
• Does the schematic match the netlist?
• Does the board outline match the mechanical drawing?
• Are all critical nets connected?
• Are polarity and pin 1 marks visible?
• Have all rule warnings been reviewed?
• Can the fabricator and assembler understand the notes?
• Has the test plan been approved?

I keep a short change record. It shows what changed, why it changed, and which files were updated. This helps when the prototype needs a second revision.

A practical PCB checklist is not only a list of rules. It is a way to connect design decisions with fabrication, assembly, testing, and product use.

When I review a board, I look beyond the screen. I picture the fabricator drilling it, the assembler placing parts, the technician probing test points, and the user installing the finished product. That view catches problems that a single software check may miss.

Interested in learning more about industry trends and solutions? Contact lingchao: mr.xu@lingchaopcb.com/WhatsApp +8613780181891.

1. IPC 2022 IPC-2221B Generic Standard on Printed Board Design

2. IPC 2020 IPC-A-610H Acceptability of Electronic Assemblies

3. Howard Johnson and Martin Graham 2003 High-Speed Signal Propagation Advanced Black Magic

4. Henry W Ott 2009 Electromagnetic Compatibility Engineering

5. Paul Horowitz and Winfield Hill 2015 The Art of Electronics

6. Eric Bogatin 2018 Signal and Power Integrity Simplified