The problem it started from: drowning in admin
The pain points that shaped the design.
What the project works through
The moving parts of running a camp
Camp Registrations
- Per day, per night, or full camp
- Family & sibling pricing built in
- Complex attendance patterns
Simple Payments
- Online payments or pay later
- Transparent fees
- No ticketing hacks needed
Live Attendance
- Who's on site right now
- Arrivals and departures tracked
- Real-time headcount
Medical & Emergency
- Emergency contacts instantly
- Medical details when needed
- Always up to date
Leader Reports
- Printable attendance lists
- Summary dashboards
- Emergency-ready exports
Email & SMS
- Message everyone at once
- Or just today's attendees
- No manual list building
How a camp flows through it
Five steps, from creating a camp to running it.
Create a camp
Set pricing
Share link
Parents register
Run camp!
Built for camps, not concerts
Why generic ticketing was the wrong shape for the problem
| Feature | Scout Camp Log | Generic Ticketing |
|---|---|---|
| Purpose | Built for camps | Built for events |
| Pricing options | Family & day pricing | Flat tickets only |
| Live attendance | ||
| Medical information | ||
| Emergency contacts | ||
| Scout-specific reports |
That mismatch was the reason to explore something purpose-built.
Safety & Trust
How it was designed to treat sensitive data
About this project
A demonstration, not a product for sale
Scout Camp Log was built to explore how camp software could work — the interesting problems, not the business: modelling family & day pricing, live attendance, and medical/consent forms as data that validates itself.
It isn't a commercial service and isn't taking sign-ups — there's nothing to buy and nothing to launch. You're welcome to create an account and look around, but treat it as a sandbox: data is temporary and may be cleared at any time.
Curious how it fits together?
Have a look around the demo — no strings, nothing to buy.