| Timing | Activity | Lead Sponsor | Cosponsor | SCE |
|---|---|---|---|---|
| T-8 wks | Identify partner agency or government entity | ✓ | ○ | |
| T-8 wks | Define problem statements | ✓ | ○ | |
| T-8 wks | Define data requirements per problem statement | ✓ | ○ | |
| T-8 wks | Identify judges | ✓ | ○ | |
| T-8 wks | Define and fund food and drink | ✓ | ○ | |
| T-8 wks | Define and fund prizes | ○ | ○ | |
| T-8 wks | Source venue | ○ | ○ | ✓ |
| T-8 wks | Build event page | ✓ | ||
| T-6 wks | Run marketing push | ✓ | ||
| T-6 wks | Amplify through sponsor network | ○ | ○ | |
| T-4 wks | Nominate roaming experts | ○ | ○ | |
| T-4 wks | Recruit and train experts | ✓ | ||
| T-2 wks | Pre-match teams | ✓ | ||
| T-1 wk | Send judge and cohost briefing | ✓ | ||
| T-2 days – T-1 day | Pre-event logistics (venue walk, food and drink order, name tags, security list) | ✓ | ||
| Event day | Event run of show | ✓ | ||
| Event day | Kickoff statement | ✓ | ||
| Event day | Closing statement / winner announcement | ✓ | ○ | |
| T+1 wk | Run post-event survey | ✓ | ||
| T+1 wk | Send follow-up CTA (Substack, Slack, Connect) | ✓ | ||
| T+1–2 wks | Publish Substack recap | ○ | ✓ | |
| Ongoing | Route winning team's work to sponsoring agency | ✓ | ✓ |
Sponsor benefits
Lead Sponsor Benefits
- Logo and org credit on event page, image, and description
- Named in "Hosted By" line
- Kickoff statement (2–3 min)
- Closing statement / winner announcement
- Social amplification credit
- Early visibility into problem-statement pipeline and resulting prototypes
- Option to host at own space
Cosponsor Benefits
- Logo and org credit on event page, image, and description
- Named in "Hosted By" line
- Social amplification credit
Ready to sponsor a hackathon? Reach out at [email protected] and we will scope the event with you. Our first build night drew 80+ builders who shipped 20 working tools in one evening: see A Civic Tech Build Night.
Get in Touch →