Giving credits and codes to builders
Send your codes to the organizer. They upload them once, choose which tracks get them and when builders see them, and every builder or team claims their own code under Resources in their event dashboard.

Step by step
- 01
Make one code per builder or per team, and a short redemption guide.
- 02
Send them to the organizer as a list or CSV.
- 03
The organizer uploads them and picks the timing: immediately, at event start, or after check-in.
- 04
Builders reveal their code and follow your redemption steps.
What to agree with the organizer
| Question | A good default |
|---|---|
| One per person or one per team? | Per person for credits, per team for big prizes |
| When do builders see them? | At event start, or after check-in to reward people who show up |
| How many codes? | Number of accepted builders or teams, plus a buffer |
| Expiry | Long enough for builders to finish after the event |
If something goes wrong
- Builders say the code is invalid
- Check the codes are active, then send the organizer a new batch.
- Builders can't redeem without a link
- Add your redemption link and steps to the guide.
- You ran out of codes
- Send another batch. The organizer adds it to the same sponsor.
Questions
Can I see how many codes were claimed?
Yes. Every batch shows how many are assigned and claimed.
Can I upload the codes myself?
Today the organizer uploads them.
Can I send files, like a getting-started guide?
Yes. Builders open PDFs and images in Resources.
Related
Still stuck? Talk to a person.
