The Robotics Competition Checklist You Wish Someone Gave You Before Day One

You've been building for three months. The chassis works. The code mostly works. And two days before the competition, one of the following happens: a motor driver burns, a Bluetooth module stops responding, a battery swells, or a wheel encoder starts giving garbage data.

Competition prep is as much about spares management and risk mitigation as it is about building the robot. Here's what experienced teams do.

Hardware Checklist — One Week Before

• Run the full competition sequence 10 times in a row — not just the happy path
• Check every mechanical joint and fastener — Loctite anything that vibrated loose
• Test all batteries at competition charge level, not freshly topped off
• Verify sensor readings across the full range the competition environment might produce
• Test power-on to operational time — how long before it's ready to run?

The Spares Box — Non-Negotiable Items

• 2x of every motor driver (L298N, DRV8833, L293D — whatever you're using)
• Extra microcontroller (a fried Arduino at 11pm the night before is a crisis)
• Extra batteries (and a charger that works from venue power)
• Replacement wheels and axles if your drive system is weight-bearing
• Heat-shrink tubing in multiple sizes
• A full solder kit with iron, solder, flux, desoldering braid
• Spare servo (if you're using any)
• Extra jumper wires — both DuPont and breadboard

Software and Firmware

Tag a known-good commit before you leave. Label it 'COMPETITION_BUILD'. Any last-minute changes go on a branch. If they break something, you have 30 seconds to revert instead of 30 minutes debugging. Bring a laptop with all SDKs, drivers, and IDE installed offline.

Day-of Checklist

• Arrive with fully charged batteries — don't plan to charge at venue
• Do a practice run on or near the actual surface (carpet vs hardwood vs foam matters for wheels)
• Watch other teams' runs to spot edge cases you haven't considered
• Don't make code changes after the practice round unless something is broken
• Assign roles: one person drives/operates, one person handles tools and spares

Sourcing Last-Minute Spares in Bangalore

SP Road works, but it's slow when you need one specific component. For competition teams with deadlines, RoboDIB's component map lets you find specific parts from other makers in Bangalore — often available for immediate pickup, no shipping wait.