PCB Design Process: From Schematic to Manufacturing; Step by Step

By Altrobyte Lab | altrobytelab.com | Learn. Build. Innovate.

Introduction

Every great electronic product, from your smartphone to an industrial motor controller, started life as a hand-drawn circuit on paper. Then someone translated that circuit into a PCB. That translation process is one of the most valuable skills in all of embedded engineering, and almost no college teaches it properly.

Think of PCB design like architecture. An architect does not just dream up a beautiful building, they produce precise blueprints, get them reviewed by inspectors, and hand detailed construction documents to a builder who turns the drawings into a real structure. PCB design works exactly the same way. Your schematic is the blueprint. Your layout is the floor plan. Your Gerber files are the construction documents. And the PCB manufacturer is the construction company that turns your digital design into a physical board.

This blog covers the complete PCB design process from defining your requirements and capturing your schematic all the way to manufacturing your first real board in India. Every step is explained practically, with real examples, real tools, and real costs.

Whether you are designing your first development board or preparing for a role at an embedded product company, this guide covers everything you need to know.

What Is a PCB and Why Should Every Embedded Engineer Know How to Design One?

A Printed Circuit Board is a flat board that mechanically supports and electrically connects electronic components using conductive copper traces etched into its surface, instead of the tangle of loose wires you would otherwise need. The substrate is typically FR4 fibreglass, the traces are copper, and the surface is coated with green solder mask (though red, blue, and black are common too).

PCBs matter because breadboards do not scale. A breadboard prototype that works perfectly on your desk will fail within days in a real environment — vibration loosens connections, wires fall out, and signal integrity collapses at higher frequencies. A well-designed PCB is reliable, reproducible, compact, and professional. It is the difference between a science fair project and a real product.

Here is why every embedded engineer, not just hardware designers, needs to understand the PCB design process:

• Firmware engineers who understand PCB layout debug hardware problems faster. When your I2C bus is behaving erratically, a firmware engineer who understands trace length and decoupling capacitors finds the root cause in minutes. One who doesn't spends days chasing software bugs that don't exist.

  
  

• Hardware-firmware co-design is a premium skill in India's embedded job market. Engineers who can contribute to both the schematic and the firmware are consistently paid more and promoted faster.

  
  

• Companies like Bosch, Tata Elxsi, and Mistral Solutions expect embedded engineers to read, understand, and comment on schematics — even if they are not the primary hardware designer.

• For freelancers and startups: PCB design is the single skill that separates a working prototype from a product you can manufacture, sell, and scale.

The most widely used PCB design tools today are KiCad (free, open-source, recommended for students and professionals alike), EasyEDA (free, browser-based, beginner-friendly), Altium Designer (industry standard at large companies, expensive), and Eagle (used at many mid-size companies, now owned by Autodesk).

Learning the PCB design process is not optional for serious embedded engineers. It is a career multiplier.

Overview, The Complete PCB Design Process at a Glance

Before going deep into each step, here is the full sequence so you always know where you are in the process:

1. Define requirements and draw a block diagram

2. Select components and build a Bill of Materials (BOM)

3. Schematic capture, draw the circuit

4. Assign footprints and generate the netlist

5. PCB layout, place components and route traces

6. Design Rule Check (DRC) and design review

7. Generate Gerber files, the manufacturing documents

8. PCB manufacturing and assembly

   
   

Think of Steps 1–3 as the architectural brief and blueprint phase — you are defining what you are building and drawing the logical design. Steps 4–6 are the engineering review, translating the logical design into a physical layout and verifying it meets manufacturing standards. Steps 7–8 are handing the completed construction documents to the builder and watching your design become a real physical board.

Step 1: Define Your Requirements and Draw a Block Diagram

The most common PCB design mistake has nothing to do with KiCad or Gerber files. It is opening design software before you have clarity about what the board actually needs to do. Step 1 happens entirely on paper — and it saves you from hours of rework later.

This is the architect sitting down with the client before touching a drawing board: "How many bedrooms? Single storey or double? What is the budget? Does it need a garage?" Get the brief right before a single line is drawn.

Answer these questions before opening any software:

• What does this PCB need to do? (Define the function clearly in one sentence)

• What microcontroller or processor will it use? (ESP32, STM32, NXP, Microchip?)

• What input/output interfaces are needed? (UART, SPI, I2C, USB, CAN, analog inputs, digital outputs?)

• What is the power supply architecture? (3.3V, 5V, 12V, battery-powered, USB-powered?)

• What are the physical size constraints? (Does it need to fit in an existing enclosure?)

• Does this product need to meet regulatory standards? (CE marking for Europe, FCC for the USA, or BIS certification for sale in India — BIS is mandatory for many electronic products sold in the Indian market)

  
  

Once you have answers, draw a block diagram: boxes representing each major subsystem connected by lines showing data flow and power distribution. For a temperature monitoring IoT node, your block diagram would show an MCU block (ESP32), a sensor block (DHT22), a display block (SSD1306 OLED), a power block (USB 5V to 3.3V regulator), and a connectivity block (Wi-Fi/MQTT). Every block gets a box. Every connection between blocks gets a labelled arrow.

Pro Tip: A 30-minute block diagram session prevents a 3-hour schematic redesign. The block diagram forces you to make architectural decisions, which interfaces, which power rails, which communication protocols, before you are buried inside a schematic editor. Never skip this step.

Step 2: Select Your Components and Build a BOM

Your Bill of Materials (BOM) is the complete list of every component that will appear on your PCB, with part numbers, values, package types, quantities, suppliers, and unit prices. Building a thorough BOM before schematic capture is the professional approach that separates product engineers from hobbyists.

Why does package type matter so much? The same 10k ohm resistor comes in 0402 (tiny, for machine assembly only), 0603 (small, manageable with practice), 0805 (comfortable for hand soldering), and through-hole (easiest to solder, takes more board space). Your choice affects layout density, soldering difficulty, assembly cost, and whether a manufacturer in India can assemble it affordably.

For each component, evaluate these criteria before committing:

• Availability in India: Check Robu.in, Mouser India, DigiKey India, Evelta Electronics, and Element14 India before finalising your BOM. A component that looks perfect on a datasheet but is not available in India with reasonable lead time will stall your project.

  
  

• Datasheet availability: Always design from the official manufacturer datasheet — not from tutorial code or random forum posts. The datasheet gives you pin functions, voltage ratings, timing requirements, recommended circuits, and package dimensions.

  
  

• Package type: Choose a package appropriate for your assembly method. If you are hand-soldering prototypes, avoid anything smaller than 0603 passives and QFN ICs without proper tools.

  
  

• Minimum Order Quantity (MOQ): Many ICs from Indian distributors have MOQs of 5 or 10 units. Factor this into your BOM cost calculation.

  
  

Format your BOM as a spreadsheet with these columns: Reference Designator (R1, C3, U2), Component Value (10k, 100nF, ESP32-WROOM), Package (0805, 0603, SMD-38), Manufacturer Part Number, Supplier, Unit Price (INR), and Quantity.

Pro Tip: Cross-check every single component's availability in India before committing to your BOM. A single unavailable IC especially a custom voltage regulator or a specific communication transceiver can halt your entire production run and force a board redesign. Discover this at the BOM stage, not after 50 boards are manufactured.

Step 3: Schematic Capture Drawing the Circuit

Schematic capture is the blueprint phase of the PCB design process. The schematic shows what connects where the complete logical circuit without any consideration for physical position on the board. It answers the question: "How does this circuit work?" The layout answers a different question: "Where does everything physically sit?"

Using the architect analogy: your schematic is the architectural drawing that shows which rooms connect to which, how many windows each room has, and where the plumbing runs logically — not yet where the furniture sits, how thick the walls are, or what the building looks like from the street.

Open KiCad (free, available on Windows, Mac, and Linux) or EasyEDA (browser-based, no installation required) and follow these schematic best practices:

• Use proper schematic symbols from the tool's standard library — never create your own symbols for standard components. Custom symbols for non-standard ICs are acceptable, but standard resistors, capacitors, and common ICs must use standard symbols for readability.

  
  

• Label every net clearly with descriptive names: VCC_3V3, GND, UART_TX, UART_RX, SPI_MOSI, SPI_MISO, SPI_CLK. Never leave unnamed nets on a professional schematic.

  
  

• Add decoupling capacitors (100nF ceramic) near every IC power pin. This is the single most important schematic practice beginners skip — and it causes 80% of "my schematic looks correct but the board doesn't work" failures. Decoupling capacitors filter the high-frequency switching noise that digital ICs inject into the power supply, preventing it from causing erratic behaviour in neighbouring components.

  
  

• Organise logically: power connections at the top, signal flow left to right, ground at the bottom. Group related subcircuits together with a clear boundary.

  
  

• Add a title block with the project name, revision number (start at Rev A), date, and designer name. This seems trivial but becomes essential when you have multiple board revisions.

  
  

• Label every connector pin with its function and direction (Input, Output, Bidirectional, Power).

  
  

Once the schematic is complete, run the Electrical Rules Check (ERC) — this automated tool catches unconnected pins, duplicate component references, missing power flags, and electrical conflicts in the schematic before you proceed. Fix every ERC error before touching the layout.

Pro Tip: Sketch your schematic on paper first. Even a rough hand-drawn version of the major connections MCU to sensor, MCU to power, MCU to connector before opening KiCad saves enormous time and prevents fundamental architecture mistakes. The paper sketch takes 15 minutes. The mistakes it prevents take hours to undo.

Step 4: Assign Footprints and Generate the Netlist

A footprint is the physical land pattern on the PCB the copper pads, silkscreen outline, and courtyard boundary that corresponds to the physical package of your component. Every schematic symbol must be linked to a footprint before layout begins. This step is the bridge between the logical world of the schematic and the physical world of the PCB.

To make this concrete: an 0805 resistor footprint has two rectangular copper pads spaced approximately 2mm apart. A SOT-23 transistor footprint has three pads arranged in a specific triangle matching the physical transistor package. An ESP32-WROOM module footprint has 38 castellated pads matching the exact pad pitch of the physical module. If your footprint does not match your physical component exactly, the component will not solder correctly or at all.

In KiCad, assign footprints using the Symbol Properties editor or the dedicated footprint assignment tool. For standard components (resistors, capacitors, common ICs), KiCad's built-in footprint library covers most cases. For unusual ICs, custom connectors, or any component not in the standard library, you must create the footprint manually from the package dimensions in the datasheet. This is a critical skill — every embedded PCB engineer needs to be able to read a datasheet mechanical drawing and translate it into a KiCad footprint accurately.

Once all footprints are assigned, export the netlist a structured file that lists every component and every electrical connection between them. This netlist is what you import into the PCB layout editor to begin the physical design.

Pro Tip: Before beginning layout, verify your footprints against the actual physical components using digital calipers. Print the footprint at 1:1 scale from KiCad and physically place the component on the paper if it fits, the footprint is correct. A wrong footprint discovered after manufacturing means boards that cannot be assembled. A wrong footprint discovered during this step costs you five minutes.

Step 5: PCB Layout Placing Components and Routing Traces

PCB layout is the most creative and technically demanding step in the entire PCB design process. This is where your logical circuit becomes a real physical board and where design decisions have direct consequences for electrical performance, manufacturing yield, and long-term reliability.

Returning to the architect analogy: you now have approved blueprints. Now you must decide where every room goes, how wide the corridors are, where the electrical conduits run inside the walls, and how to make the whole floor plan functional, safe, and efficient. A beautiful schematic implemented in a poor layout produces a board that misbehaves. Good layout turns a correct schematic into a board that works first time.

Import your netlist into KiCad's PCB editor (PCBnew). All your components appear as footprints on the board, connected by thin "ratsnest" lines showing every connection that still needs to be physically routed. Your job is to place every component and route every connection.

Component placement — do this before routing a single trace:

• Place the MCU first. It is the hub that everything connects to, and its position determines the optimal position of everything else.

  
  

• Place decoupling capacitors immediately adjacent to the IC power pins they serve within 1mm ideally. This is where the majority of beginner PCB layouts fail. A decoupling cap placed 10mm from the IC power pin is nearly useless.

  
  

• Group related components together — all SPI peripheral components near the SPI pins, all power supply components in one area, all connectors at board edges for accessibility.

  
  

• Consider signal flow direction: inputs typically enter from one side, outputs leave from the other, power supply occupies a corner or edge.

  
  

• Keep analog signal components physically separated from high-speed digital switching components — digital noise radiates and corrupts sensitive analog measurements.

  
  

Trace routing guidelines:

• Power traces carry significant current and must be wider — minimum 0.5mm for low-current power rails, 1mm or more for rails carrying 1A or above.

  
  

• Signal traces between components are typically 0.2–0.3mm wide for standard digital signals.

  
  

• Use a copper pour (copper fill) on the bottom layer as a ground plane — this single practice dramatically improves signal integrity, reduces noise, and simplifies routing by giving you a ground reference everywhere on the board.

  
  

• Route traces at 45-degree angles at corners, never 90 degrees — 90-degree corners create acid traps during chemical etching that can cause manufacturing defects.

  
  

• For differential pairs (USB D+/D-, CAN H/L): keep both traces equal length and tightly coupled side by side — length mismatch causes signal skew that destroys high-speed communication.

  
  

• Use vias to move traces between layers when routing becomes congested on one layer.

Layer stackup for beginners:

A 2-layer board (top and bottom copper layers) is the correct starting point. Use the top layer for component placement and signal routing, the bottom layer primarily as a ground plane with power traces where needed. A 4-layer board adds inner power and ground planes for better performance appropriate once you are working with high-speed signals or sensitive analog circuits.

Define your board outline using KiCad's Edge.Cuts layer this tells the manufacturer exactly where to cut the board.

Pro Tip: Spend 30 minutes on component placement before routing a single trace. Excellent placement makes routing almost automatic traces flow naturally between well-placed components. Poor placement turns routing into a puzzle that gets worse with every trace. Placement is where PCB layout skill lives.

Step 6: Design Rule Check (DRC) and Design Review

The Design Rule Check is the automated building inspector of PCB design. Before your layout goes anywhere near a manufacturer, the DRC verifies that every measurement in your layout meets the minimum manufacturing specifications — trace widths, trace clearances, drill hole sizes, courtyard boundaries, and net connectivity.

The architect analogy is exact here: the building inspector reviews your completed floor plan before construction begins, checking that walls meet minimum thickness requirements, that electrical wiring is safely spaced from plumbing, that fire exits meet code. Problems found at this stage cost nothing to fix. Problems found after the house is built cost enormously.

Run DRC in KiCad via Inspect → Design Rules Checker. The DRC checks:

• Minimum trace width (0.1mm is the physical minimum for most manufacturers, but 0.2mm is recommended for reliability)

  
  

• Minimum trace-to-trace clearance (typically 0.2mm — violations cause short circuits in manufacturing)

• Minimum drill hole size (0.2mm for standard manufacturers, 0.15mm for advanced processes)

  
  

• Courtyard violations — components whose physical footprints overlap

  
  

• Unrouted connections — any ratsnest line that was not converted to a physical trace

  
  

The goal is zero DRC errors and zero DRC warnings before proceeding. Every error represents a manufacturing problem or a design defect that will cause the board to fail.

Beyond automated DRC, perform a manual visual review:

• Verify decoupling capacitor placement visually — are they actually adjacent to the IC power pins?

  
  

• Confirm all high-current traces are wide enough

  
  

• Check every connector has its Pin 1 orientation marked correctly on the silkscreen

  
  

• Verify the board outline is a single closed polygon with no gaps

  
  

• Confirm all text labels (component values, reference designators) are on the silkscreen layer, readable, and not obscured by copper pads

  
  

• Look for isolated copper islands — copper areas with no connection to any net are manufacturing waste and potential antenna problems

  
  

If possible, send your layout to a second engineer for peer review before generating Gerbers. A fresh pair of eyes catches what yours has become blind to after hours of staring at the same layout.

Pro Tip: Print your PCB layout at exact 1:1 scale and physically place your actual components on the paper printout. This takes five minutes and catches footprint errors that look perfectly correct on screen mismatched pad spacing, wrong package size, incorrect connector orientation before they become expensive manufacturing mistakes.

Step 7: Generate Gerber Files Your Manufacturing Documents

Gerber files are the universal language of PCB manufacturing. Every PCB manufacturer in India and worldwide JLCPCB, PCBWay, Seeed Studio, as well as Indian manufacturers like Outputs Technologies, PCBPower, and CircuitAnt accepts Gerber files as the standard input format for fabrication.

A complete Gerber package contains one file for each layer and manufacturing operation:

• F.Cu / B.Cu — top and bottom copper layers (the actual circuit traces)

  
  

• F.Mask / B.Mask — solder mask layers (the green coating with openings at each pad)

  
  

• F.Silkscreen / B.Silkscreen — the white text and component outlines printed on the board surface

  
  

• Edge.Cuts — the board outline (where to cut)

  
  

• Drill file (.drl or .xln) — the drill file specifying every hole's position and diameter

  
  

• B.Paste / F.Paste — solder paste stencil layers (required for SMT assembly)

  
  

In KiCad, generate Gerbers via File → Plot. Select Gerber as the format, select all required layers, and click Plot. Then generate the drill file separately using Generate Drill Files. Package all output files into a single ZIP archive — this is what you upload to the manufacturer.

Before uploading to a manufacturer, use a free Gerber viewer — such as gerbv (open source) or the built-in viewer on JLCPCB's order page — to visually inspect every layer. Verify the copper traces match your layout, the board outline is correct, and the drill holes are positioned accurately. This is your final quality check before real money is spent.

Pro Tip: Always keep a copy of the Gerber files alongside your KiCad project files, labelled with the revision number and date. When you order boards again six months later or need to modify a specific revision, you will know exactly which Gerbers correspond to which board version. Version control for hardware saves the same headaches that Git saves for firmware.

Step 8: PCB Manufacturing and Assembly India Options and Real Costs

Your Gerber files are complete. Now the construction company builds the house.

For PCB design and manufacturing in India and internationally, these are the most commonly used options by Indian embedded engineers and startups:

International Manufacturers (shipped to India):

Manufacturer	Min. Order	2-Layer 10x10cm Price	Lead Time
JLCPCB (China)	5 boards	~₹400–₹600 for 5 pcs	7–14 days
PCBWay (China)	5 boards	~₹600–₹900 for 5 pcs	7–14 days
Seeed Studio (China)	10 boards	~₹700–₹1,000 for 10 pcs	10–15 days

Indian Manufacturers:

Manufacturer	Min. Order	2-Layer Board Price	Lead Time
PCBPower India	1 board	~₹800–₹1,500 per board	5–7 days
Outputs Technologies	5 boards	~₹600–₹1,200 for 5 pcs	5–10 days
CircuitAnt	5 boards	~₹500–₹1,000 for 5 pcs	5–8 days

For prototypes (1–10 boards), JLCPCB and PCBWay offer the lowest cost globally and ship to India reliably. For production volumes or when lead time is critical, Indian manufacturers offer faster turnaround and avoid customs complications.

PCB Specifications to specify when ordering:

• Number of layers (2 or 4)

• Board dimensions (length x width in mm)

• Board thickness (standard is 1.6mm)

• Copper weight (1oz standard, 2oz for high-current boards)

• Surface finish (HASL standard, ENIG for fine-pitch components)

• Solder mask colour (green standard, other colours typically same price)

• Minimum trace/space (0.1/0.1mm standard, 0.2/0.2mm for easier manufacturing)

• Silkscreen colour (white standard)

  
  

Assembly options:

For prototypes, hand soldering is practical for 0603 and larger components. For 0402 and below, or for QFN/BGA packages, use a hot air station or reflow oven. For production quantities, most Indian PCB manufacturers offer SMT assembly services — JLCPCB's PCBA service is widely used by Indian startups for cost-effective assembled boards delivered to India.

Pro Tip: Order a small first batch 5 boards to verify your design before committing to larger quantities. Even a well-reviewed design sometimes has a mistake that only becomes apparent on real hardware. The cost of 5 prototype boards to catch an error is far less than the cost of 100 boards with the same error.

PCB Design Software Comparison

Tool	Cost	Platform	Best For	Learning Curve
KiCad	Free	Win/Mac/Linux	Students, professionals, open-source projects	Moderate
EasyEDA	Free	Browser-based	Absolute beginners, quick prototypes	Low
Altium Designer	₹1.5L+/year	Windows	Enterprise, large teams	High
Eagle (Autodesk)	Free (limited) / Paid	Win/Mac	Mid-size companies	Moderate
OrCAD	Paid	Windows	Automotive, defence industry	High

For students and engineers starting with PCB design and manufacturing in India, KiCad is the clear recommendation — it is completely free, professionally capable, has excellent documentation, and the skills transfer directly to professional workflows.

Common PCB Design Mistakes and How to Avoid Them

These mistakes appear in nearly every first PCB design. Knowing them in advance saves you a board spin:

Missing or misplaced decoupling capacitors are the number one cause of boards that look correct on the schematic but misbehave on the bench. Every IC power pin needs a 100nF ceramic capacitor within 1mm. No exceptions.

Wrong footprint for the physical component causes boards where components either don't fit or solder unreliably. Always verify footprints against physical parts with calipers before manufacturing.

Traces too thin for the current they carry causes copper traces to act as resistors — voltage drops, heat is generated, and in severe cases traces fail permanently. Use a trace width calculator and add margin.

No ground plane results in a noisy board where digital signals interfere with analog measurements and communication protocols behave erratically. Always flood the bottom layer with a ground pour.

Connector polarity not marked on silkscreen means the assembled board can be connected backwards during testing, immediately destroying components. Always mark Pin 1 clearly.

Skipping the DRC before generating Gerbers sends manufacturing defects directly to the fabrication house and you pay for boards that cannot be assembled correctly.

Not checking component availability in India before finalising the BOM means discovering mid-project that a critical component has a 12-week lead time or is not distributed in India at all.

How Altrobyte Lab Teaches PCB Design

Understanding the PCB design process as a concept is valuable. Actually doing it — under the guidance of an experienced engineer who has debugged real board failures is what makes the skill stick.

Altrobyte Lab's Advanced Embedded System program covers PCB design as part of a complete embedded engineering curriculum that also includes FreeRTOS, STM32, power optimization, and OTA firmware updates. Students do not learn PCB design in isolation they learn it in the context of designing boards for real embedded systems they have already written firmware for.

This context is what separates Altrobyte Lab's approach from a standalone PCB tutorial. When you design a board for a sensor node you have already programmed in C, your design decisions — where to put decoupling caps, how wide to make the power trace, how to route the UART lines — are grounded in real understanding of what the firmware expects from the hardware.

"Practical Embedded IoT + RTOS training, real STM32/ESP32 projects, personal lab, and strong mentorship — Altrobyte Lab made me job-ready fast." — Hrishabh Jaiswal, Altrobyte Lab Student

Ready to go from breadboard to PCB with expert guidance? Explore the Advanced Embedded System program

Conclusion

The PCB design process follows a clear, logical sequence define requirements, select components, capture the schematic, assign footprints, layout the board, run DRC, generate Gerbers, and manufacture. Each step builds on the previous one, and each step has specific skills that can be learned, practised, and mastered.

The architect builds the house from brief to blueprint to building never skipping a phase, never handing incomplete documents to the construction company. You now have the complete map for doing the same with your PCB.

PCB design and manufacturing in India has never been more accessible with free tools like KiCad, affordable fabrication from both international and Indian manufacturers, and component supply chains that reach Indore, Pune, Bangalore, and every engineering city in between. The barrier is not cost or tooling. It is knowing the process.

Now you know the process. Build something with it.

Book a free consultation with Altrobyte Lab → altrobytelab.com/book-online