Fit the pack, not the other way around
Packs differ in how they organize, communicate, and welcome families. Configuration and optional features should reflect that.
Built from the work of running a real pack.
ScoutKeep started with one pack, a new webmaster, and a desire to make things better for the families and volunteers who keep Scouting going.
It started with Lutz Pack 37.
I’m Alexander Kim. When I became the webmaster for Lutz Pack 37, I wanted to give the pack an awesome experience—not just a better-looking website, but tools that made life easier for its current members.
I wanted new leaders to have a clear starting point and current leaders to have the support to keep going. A pack’s knowledge should stay with the pack, so no one has to rebuild it from scratch or pass everything along from memory.
As we built and improved the experience, we received lots of comments about it. That made me realize this wasn’t something only our pack could benefit from. Other packs were doing the same work and facing many of the same challenges. That realization became ScoutKeep: taking what started with Lutz Pack 37 and making it useful to more packs.
What guides the product
Keep families and leaders in context
Show people the work relevant to them and give leaders permissions suited to their responsibilities.
Be clear about what’s ready
Upcoming features are labeled as upcoming, and optional features stay optional—your pack doesn’t need Slack or a website to get started.
Keep your pack on the same page.
Start with your pack’s details and choose the tools that make sense for you.