Submitting your Project

Everything you need to know before you submit.

Built something cool? Awesome. Here's what you need to do before we ship you anything.

We ship real projects. Not vibes, not half-finished ideas. Real, working things.

There are two submission stages:

  1. Design Submission: before we ship you the kit
  2. Build Submission: required after you receive and build it

Both are required. You don't get to skip the build submission. That's the whole point.

95% of rejections are fixable in under 5 minutes. Read this carefully.

Stuck? Ask in #breadboard before DMing us. Odds are someone else had the same question.

A shipped design means all three of these:

  • 1 A complete CAD assembly with a polished enclosure. Not a bare breadboard sitting loose. Your circuit needs to live inside a real, designed case with proper mounting. Screws, clips, or press fits. Something you'd actually hand to someone.
  • 2 Firmware, if your project has a microcontroller. Even if it's untested, it needs to exist and be in your repo. A microcontroller with no code is just a paperweight.
  • 3 A working physical build with a demo. You built it, you proved it works. A video showing it doing its thing is required at the build stage.

Stage 1: Design Submission

This is what you submit before we send you anything. It should prove that you've thought your project through and that someone else could understand and replicate it.

Your README

Imagine someone stumbles onto your repo with zero context. Can they figure out what your project is without opening a single file?

If not, your README needs work. At minimum, cover:

  • What your project is and what makes it interesting
  • How it works and how you use it
  • Why you made it. Get personal! What problem were you solving? What did you want to learn?
  • A clear wiring diagram or schematic
  • Renders or images of your planned enclosure

Your Design

Your project must:

  • Be your own original work. No AI-generated designs, no copied tutorials.
  • Use several components from the kit (think shift registers, optocouplers, rotary encoders, etc.)
  • Have a complete wiring diagram or schematic
  • Have firmware. Even untested is fine, but it needs to exist.
  • Have a designed enclosure with a real attachment method. Not tape and hope. Screws, clips, something solid.
  • Have been looked over by someone else before you submit. Fresh eyes catch things yours won't.

Your repo must include:

  • A BOM (Bill of Materials) as a CSV, with links to every part
  • Your wiring diagram or schematic file
  • Firmware source code, if applicable
  • CAD files for your enclosure (.step, .f3d, .FCStd, or an Onshape link)
  • Any libraries or references your project depends on
  • Folders and files with clear, logical names

Stage 2: Build Submission

Once you receive your kit and build your project, you are required to submit your build. This is not optional. Receiving the kit and going silent is not okay.

Your build submission must include:

  • Photos of the finished breadboard circuit, fully assembled
  • Photos of your completed enclosure with everything housed inside
  • A demo video showing it actually working
  • A build log covering what you made, the decisions you made along the way, and what went wrong

Things That Will Get You Rejected

  • AI-generated code, designs, or writeups
  • Copying someone else's project without credit
  • Missing files from the checklist above
  • Not submitting your build after receiving the kit
Warning: Submitting stolen or AI-generated work can result in a permanent ban from this program and other Hack Club programs. Don't do it.

Build with ❤️ by teenagers, for teenagers at Hack Club

Hack Club is a 501(c)(3) nonprofit and network of 60k+ technical high schoolers. We believe you learn best by building so we're creating community and providing grants so you can make awesome projects. In the past few years, we've partnered with GitHub to run Summer of Making, hosted the world's longest hackathon on land, and ran Canada's largest high school hackathon.

enes