Why You Actually Need a Spreadsheet Before Building a Mechanical Keyboard
I spent three weekends in 2019 completely botching a keyboard build because I never wrote anything down. I bought switches from three different vendors, forgot to check if the PCB matched the case mounting style, and ended up with forty leftover 5-pin switches that would have worked with a simple mod I'd seen recommended but never jotted down. That was the moment I started using a proper worksheet system. Most people in this hobby treat their first build like they can wing it. They watch a YouTube video, order parts, and hope everything fits. The parts arrive, nothing lines up, and they're left with a box of expensive components and a half-ordered PCB that doesn't support hot-swap sockets. A comprehensive keyboard build worksheet prevents this by forcing you to make every decision before money leaves your account.
Worksheet For Mechanical Keyboard Comprehensive: The Structure That Actually Works
The worksheets people find online tend to fall into two camps: overly simple one-pagers that miss critical compatibility checks, and bloated spreadsheets with thirty columns most of which go unused. The version I've been refining over four years and roughly eighteen builds sits somewhere in the middle. It has seven sections, each serving a specific purpose in the build flow. The first section is layout specification. This is where you lock in your key count, form factor, and any anomalies like rotary encoders or macro columns. I recommend writing the exact layout name you'd search for online rather than just the piece count. A "75 percent" keyboard and a "65 percent with knob" look similar until you're trying to find compatible cases and the part numbers don't match what you expected. Below that comes the case and mounting section. This is the part most people skip and then regret. You need to record the mounting style (top mount, bottom mount, or tray mount), the screw sizes your case uses, and whether your PCB is pre-modded for your chosen mounting method. I learned the hard way that a case listing might claim universal compatibility while actually requiring you to file down standoffs. Having that written down before purchase saves you from opening a package three weeks later and discovering you already paid for parts that won't assemble without additional tools and modification time.
The PCB and controller section follows. Here you note the manufacturer, revision number, whether it supports VIA/QMK customization, hot-swap socket type (Kailh, Gateron, Omron), and any onboard component like RGB controllers or voltage regulators that might affect your case clearance. The revision number matters more than you'd think. PCB manufacturers occasionally release v1.1 or v2.0 revisions that change trace routing or add support for different switch brands without changing the physical footprint. If you order a case designed for v1.0 and receive v1.2, the mounting holes might be in slightly different positions and nothing will line up.
Get the Full Details
Switches, Stabilizers, and the Compatibility Traps Most Builders Miss
The switch section of my worksheet tracks brand, model, linear or tactile or clicky, pin count (3-pin or 5-pin), spring weight in centinewtons, and whether you need stabilizer modifications. I also include a column for the vendor and the price per switch so I can calculate total cost as I go. This last point is actually the most important feature of the entire document. Without per-switch pricing, you'll underestimate your budget by a significant margin, especially when you start looking at boutique switch vendors where individual units run above two dollars. Stabilizers deserve their own dedicated section rather than being lumped in with switches. The common mistake is assuming all stabilizers work the same. They do not. Plate-mount, case-mount, and PCB-mount stabilizers are not interchangeable without adapters or modding. I once spent an evening trying to install Alps-style wire stabilizers into a keyboard case designed for barebones stabilizers. They physically wouldn't seat. The workaround was cutting the wire loops flush and using O-rings to secure them, which changed the feel entirely and required me to retest every large key. Put it in the worksheet and check it twice before ordering. The keycap section looks straightforward but has a hidden complexity. You need to record the keycap profile (Cherry, OEM, MT3, SA, XDA, etc.), the switch compatibility (MX-style cross stem versus something proprietary), the material (ABS, PBT, POM, PC), and the key count for your specific layout. I also add a column for the font and colorway because some profiles look dramatically different in various legends. The GMK sets for example come in multiple font styles and the readability varies noticeably depending on which one you choose.
Assembly Notes, Firmware, and the Parts You Keep Forgetting
After the main components, my worksheet includes an accessories and firmware section. This covers USB cables, case screws (counted individually because manufacturers sometimes ship fewer than needed), foam types and thicknesses for modding, and the firmware platform you plan to use. VIA and QMK are the standard choices but they require different flashing processes. QMK requires compiling a custom firmware file which means you need to understand how to use the QMK Toolbox or the web compiler. VIA is simpler but locks you into VIA's config system. This decision affects your workflow more than most builders realize. The foam and mod section is where I track everything from PCB foam and case foam to sound dampening materials like tape mod options or silicone inserts. Different foams have different densities and the acoustic result varies significantly. A 2mm PE foam under the PCB sounds different from a 3mm EVA foam between case halves. I keep a running log of what I've tried so I can compare results across builds rather than guessing next time. One edge case I ran into that the standard worksheets don't address involves rotary encoders and niche components. I built a board with a rotary encoder for volume control and assumed any encoder would work. It didn't. The encoder had a different shaft diameter than what the case cutout accommodated and the mounting holes didn't align with the PCB holes. I ended up sourcing a different encoder from the manufacturer's recommended list and going back to the worksheet format was exactly what helped me catch this after the fact. I added an encoder compatibility field to my template immediately after that build.
How to Use the Worksheet Without Turning It Into Another Chore
The biggest reason people abandon build worksheets is that they make them too complicated upfront. Start with the five mandatory columns: component category, specific product name, quantity, price, and vendor. Fill those in as you shop. Once that baseline exists, add the compatibility notes and firmware details. The process of building out the worksheet should take about twenty minutes for a standard 65 percent or 75 percent build and maybe forty-five minutes for a more complex custom PCB layout with encoders and specialty switches. I also keep a separate post-build results column in the same spreadsheet. After I finish assembling and testing, I go back and note which parts performed well and which ones I'd avoid. This turns your worksheet from a planning tool into a reference document that improves with every build. The information from your sixth keyboard will make your seventh build significantly faster because you're not relearning compatibility constraints you already figured out. The actual download template I use is available as a Google Sheets file. It has the seven-section structure described above with dropdown menus for common switch types and case mounting styles to speed up data entry. The cost calculation formulas are built in so the total updates automatically as you fill in prices. There are also validation rules that flag when your switch pin count doesn't match your PCB's hot-swap socket type, which catches the most common error I see in builder forums.
If you're doing a very simple off-the-shelf keyboard order where everything is pre-matched, the worksheet is overkill. But the moment you're sourcing components from different vendors or mixing plate-mount switches with case-mount stabilizers, having that single document tracking every decision cuts your return and exchange rate from something like twelve percent down to near zero. It also makes the actual assembly day faster because you already know which screw goes where and which foam layer belongs to the top mount versus the bottom mount. The upfront time investment pays for itself within the first build. The template link is embedded in the Google Sheets community spreadsheet I maintain. You can copy it directly without needing to request access. Some of the cells are protected to prevent accidental formula deletion but you can edit all the component data freely. If you run into a build scenario that isn't covered by the existing columns, adding a custom column takes about thirty seconds and the cost formulas adjust automatically.
