PCB Layout: 10 Rules That Prevent Failures

Your circuit works on breadboard but the PCB fails? These 10 layout rules prevent the most common student PCB failures: component placement, decoupling, crystal layout, trace sizing, ground planes, thermal relief, DRC, and mounting.

Written by Projectech7 min readPublished
For B.E./B.Tech Electronics and E&TC students designing their first custom PCB for a final-year project Topics: PCB Design, KiCad, Electronics
Illustration of a PCB layout showing component placement, ground plane, decoupling capacitors, and trace routing.
Illustration generated for this guide.
In this guide

Your circuit works on a breadboard. Now you need it on a PCB — smaller, reliable, and professional enough for a final-year project. But the jump from breadboard to PCB layout is where most student boards fail: the schematic was correct, but the layout introduced noise, the regulator overheats, or the board just doesn't work and nobody knows why.

PCB layout is a skill, not just a drawing exercise. These ten rules are the ones that prevent the most common student PCB failures. Follow them and your first board has a real chance of working.

1. Place components before routing a single trace

The biggest beginner mistake is starting to route traces immediately. Placement determines 80% of your board's success.

Group components by function: power supply section together, microcontroller with its crystal and decoupling caps, sensor circuitry near the sensor connector. Keep the signal flow logical — input on one side, processing in the middle, output on the other. A well-placed board almost routes itself; a badly-placed board can't be saved by clever routing.

Print the placement on paper at 1:1 scale and lay your physical components on it. You'll catch footprint errors (wrong pin spacing, components that collide) before spending money on fabrication.

2. Decouple every IC power pin — and place the caps correctly

Every digital IC needs a decoupling capacitor (typically 100nF ceramic) between its VCC and GND pins. This isn't optional folklore — when the IC switches, it draws sharp current spikes that the power supply can't deliver fast enough through the PCB traces. The capacitor acts as a local reservoir.

Placement is everything: the capacitor must be as close as possible to the power pin, with short traces to both VCC and GND. A 100nF cap placed 3cm away through thin traces is barely better than no cap at all. For the ESP32 or STM32, place one 100nF per power pin pair, plus a larger bulk capacitor (10µF) nearby for the whole chip.

3. Keep the crystal and its load capacitors tight

The crystal oscillator is the heartbeat of your microcontroller — and it's sensitive. Place the crystal as close as possible to the MCU's oscillator pins, keep the traces short and symmetric, and put the load capacitors right next to the crystal.

Don't route other signals under or near the crystal. Don't cut the ground plane under it. A crystal with long, wandering traces can fail to oscillate or oscillate at the wrong frequency — and the symptom (MCU doesn't boot, or boots intermittently) gives you no hint that the crystal layout is the cause.

4. Give power traces the width they deserve

Signal traces can be thin (0.25mm is fine for most signals). Power traces cannot. A trace that's too thin for its current heats up, drops voltage, and in extreme cases delaminates from the board.

As a rule of thumb for 1oz copper:

Current Minimum trace width
< 500mA 0.5mm
500mA – 1A 1.0mm
1A – 2A 2.0mm
> 2A Use a polygon pour or 3mm+

Your 5V rail feeding an ESP32 (peaks of 250mA on WiFi transmit) plus sensors should be at least 1mm. Motor power should be a polygon pour, not a trace. When in doubt, go wider — there's no penalty for a fat power trace.

5. Don't split the ground plane (unless you know exactly why)

On a two-layer board, make the bottom layer a solid ground plane. Don't route signals on it unless absolutely necessary, and never create isolated islands of copper that aren't connected to ground.

Beginners sometimes split the ground plane into "analog" and "digital" sections, having read that it reduces noise. On a simple student board, this almost always makes things worse — return currents can't flow directly under their signal traces anymore, creating loop antennas that radiate noise. A single solid ground plane is the right choice for 95% of student projects.

If you must route on the ground layer, keep those traces short and perpendicular to the top-layer traces to minimize crosstalk.

6. Keep high-current loops small

Every switching current forms a loop: out through the power trace, through the load, back through ground. That loop is an antenna — the larger its area, the more it radiates (causing EMI) and the more susceptible it is to picking up noise.

This matters most for:

  • Switching regulators — keep the input cap, inductor, and output cap in a tight cluster with minimal loop area. Follow the datasheet layout example exactly; it's not a suggestion.
  • Motor drivers — the motor current loop (driver → motor → ground → driver) should be as compact as possible.
  • Relay switching — keep the relay coil drive loop tight and away from sensitive analog signals.

The companion rule: never route sensitive analog signals (sensor readings, ADC inputs) parallel to high-current or switching traces. Cross them at 90 degrees if you must cross.

7. Thermal relief on pads, but not where it hurts

Copper pours connected directly to a component pad act as heatsinks during soldering — the pad won't heat up enough for the solder to flow properly. Thermal relief spokes (thin connections between pad and pour) solve this for hand-soldered boards.

Use thermal relief on all hand-soldered pads connected to copper pours. But don't use thermal relief on:

  • High-current connections (the thin spokes become fuses)
  • RF or high-frequency signal pads (the spokes add inductance)
  • Pads you'll solder with hot air (less critical, but still good practice)

If you're getting boards assembled professionally, direct connections are fine — but for student hand-soldering, thermal relief is the difference between a 10-second joint and a cold, cracked one.

8. Add test points and debugging aids

You will need to probe this board. Add test points (small exposed pads) for:

  • Power rails (3.3V, 5V, GND)
  • UART TX/RX (for serial debugging)
  • SWD or JTAG programming pins
  • Any signal you'll want to scope during bring-up

Also add: a power LED (with current-limiting resistor) so you know the board is alive, clearly labeled pin 1 markers on all ICs and connectors, and your name/date/version on the silkscreen. Future-you, debugging at 2 AM before the demo, will be grateful.

9. Respect the fab's design rules — check before ordering

Every PCB fabricator publishes design rules: minimum trace width, minimum clearance, minimum drill size, minimum annular ring. Your EDA tool has a Design Rule Check (DRC) — configure it with your fab's rules and run it before generating Gerbers.

Common student DRC failures:

  • Traces too close to board edge (keep 0.5mm+ clearance)
  • Silkscreen overlapping pads (the fab may just clip it, leaving unreadable labels)
  • Drill holes too small for the component leads
  • Missing solder mask clearance on test points

Run DRC, fix everything it flags, then run it again. A board that fails DRC at the fab gets delayed or manufactured wrong — both are worse than spending 20 minutes fixing violations.

10. Include mounting holes and think about the enclosure

A PCB that can't be mounted is a prototype, not a product. Add at least 3–4 mounting holes (M3 size, 3.2mm drill) at the corners, positioned so screws don't short against nearby traces (keep copper 2mm+ away from hole edges unless they're grounded mounting holes).

Think about the enclosure now, not after fabrication: where do connectors sit relative to the box walls? Can you reach the programming header with the board mounted? Is the USB port accessible? A board that works electrically but can't be mounted or accessed in its enclosure is a failed project.

Bonus: the pre-order checklist

Before you send Gerbers to the fab:

  • DRC passes with the fab's actual design rules
  • All footprints verified against physical components (1:1 print test)
  • Power traces sized for their current
  • Decoupling caps placed adjacent to every IC power pin
  • Crystal placed tight to MCU with short symmetric traces
  • Ground plane solid (no accidental splits or islands)
  • Test points on all power rails and debug interfaces
  • Silkscreen labels readable and not overlapping pads
  • Mounting holes present and clear of copper
  • Someone else has reviewed the schematic (fresh eyes catch what you miss)

The last item is the most valuable. Have a teammate or mentor review your schematic and layout before ordering — they'll spot the floating pin, the reversed connector, or the missing pull-up that you've stared at too long to see.

For the schematic-capture side of this workflow, the KiCad guide walks through the tool itself. For understanding why decoupling and grounding matter electrically, read the decoupling capacitors guide and the EMI/EMC basics guide. More electronics concepts live in the Electronics branch hub.

More project guides

More in Electronics / E&TC