Tool one
The chat app
A chat app that treats a Scout like any other user — built for everyone, which means it was built with no one’s youth-protection rules in mind.
Troop, pack, district, council, camp — every level of your program in one place, with safeguarding you can watch working.
Tool one
A chat app that treats a Scout like any other user — built for everyone, which means it was built with no one’s youth-protection rules in mind.
Tool two
A troop website from another decade — where announcements go to be posted a second time, and rosters quietly drift apart from the truth.
Tool three
The official record, and the right place for it — that was never built to be your group’s daily home. It should stay the record. It was never the home.
So announcements get posted twice, rosters drift apart, and every parent asks the same question: where is the thing?
TOTEM OS replaces the first two and respects the third.
A totem is the sign a group raises to say who it is. TOTEM OS is built the way the mark looks: five bars — Troop · Pack · District · Council · Camp — stacked into one identity, under one roof.
Tap a bar to see its workspace. The bars are the meaning — there are always five.
Level 1 · The unit
Patrols and committees at the unit — the daily home your troop actually lives in.
Each level gets its own workspace, shaped for the people who actually work there: patrols and committees at the unit, commissioners and Eagle boards at the district, camping and advancement at the council, and a full operations module at camp.
Data captured once — by families, at the unit — flows upward through named, bounded bridges. Nothing leaks sideways: a council sees rollups, never a troop’s raw roster; a camp sees its registered troops, never the district’s files. Least access isn’t a setting. It’s the architecture.
Every tool in this category says “youth protection” somewhere on its website. TOTEM OS is the one that shows you the rule working.
PROOF 1
A conversation that includes Scouts can only be posted in when its composition is valid: at least two registered adult leaders, or a registered leader plus a parent of a Scout in the conversation. An adult-to-Scout one-to-one chat cannot be created — not “is discouraged,” not “is off by default.” It does not exist.
PROOF 2
Create a chat with Scouts in it and the app stops you — politely, in plain language a 13-year-old understands — and tells you exactly who to add. The chat opens when the composition is complete, and not before. Safeguarding at the moment of the action, not in a settings page.
PROOF 3
Merit-badge class caps hold in the database, not on a whiteboard. Camp staff work from surfaces built for their role — a counselor’s gradebook, a check-in lane, a Trading Post that requires two adults to cash out.
This is the shipped creation flow, in miniature. Add people to a new Patrol Hub chat, then try to open it. The rule below is the same one the database enforces — watch what happens when the composition isn’t complete.
Choose who is in the chat
This chat can’t open yet
A chat with a Scout in it needs two registered adult leaders — or one registered leader and a parent of a Scout in the chat.
Not yet — here’s who to add
Add two registered adult leaders, or one registered leader and the Scout’s parent, and this chat can open. A chat between one adult and a Scout can’t be created in TOTEM OS — there is no setting that allows it.
Chat open — composition complete
Two-deep leadership is in the chat, so posting is enabled. If an adult is removed and the composition breaks, posting stops until it’s complete again.
Patrol Hub · Composition verified · Demo data only
Leader Rivera: Meeting moves to 6:30 on Monday — gym entrance.
Scout: Got it. Bringing the patrol flag.
Leader Okafor: I’ll bring the sign-in sheet.
Illustrative simulation with demo data only — no real people, rosters or chats. The pilot enforces this rule in the database and in the creation flow.
Registration was never the hard part of camp. The hard part is arrival day, the health lodge, the swim checks, the gradebooks, and the Scoutmaster who needs an answer at 9 p.m.
TOTEM OS Camp Management plugs into the platform your units already use: family data captured once flows to camp through the Bridge; class caps, waitlists and prerequisites hold themselves; counselors keep gradebooks that look like their clipboards because they were modeled on them; completions flow back to troops and into Scoutbook.
Camp pricing
$5–8 per camper per season, or a flat $5,000–12,000 a year per camp.
Sold camp by camp, because camps are run camp by camp.
Packs get dens, crossover-ready records, and a Pinewood run-sheet — the pack year, run from the same home the troop uses later.
Districts get an Eagle Board scheduler that respects the signature chain — the advancement chair signs, nobody else’s button even appears — plus commissioner tools and campaign tracking.
Councils get camping and advancement portfolios and a unit-health view built from aggregates: flags and counts, never another unit’s private data.
The roundel is the institutional mark — for council and district documents and formal correspondence, where the work above the unit carries the same roof.
Unit Core
Free
The daily home, at no cost — how units meet TOTEM OS.
Unit Full
$125 / unit / year
The complete toolkit, one flat price, no per-Scout fees.
Camp Management
$5–8 / camper / season
Or a flat $5,000–12,000 / year per camp.
No per-Scout fees. No price games. The free tier is how units meet us; camps and councils are how we keep the lights on.
No. TOTEM OS is an independent tool built by a Scout leader. It is not affiliated with or endorsed by Scouting America.
No — Scoutbook stays the official record. TOTEM OS is the daily home your unit actually lives in, with a two-way file bridge to Scoutbook: import its export files (you review everything before anything is written), and export back in Scoutbook’s own format. No re-keying, no shadow records.
Any conversation that includes Scouts must include at least two registered adult leaders, or a registered leader and a parent of a Scout in the conversation — and the rule is enforced by the software, in the database and in the creation flow, not by a policy document. One-to-one messaging between an adult and a Scout is not possible in TOTEM OS. See the Safeguarding section and try the demo.
Your troop does. TOTEM OS is designed so payments run through your unit’s own Stripe, Square, or PayPal account — we never hold your funds, and the ledger’s cash discipline (two-adult turn-ins, receipts, no self-approvals) works the same for cash and checks.
Payments arrive with the public launch; the pilot runs a demo ledger.
The welcome path is bilingual (EN/ES) — the same care, in the family’s language. The product itself is in English.
The Scoutbook bridge works today. Importers for legacy unit tools are on the launch roadmap, sequenced behind our privacy and consent model — when they land, migration help from a real person comes with them.
TOTEM OS is in closed pilot with a Fort Mill, SC troop while we finish the work a public launch deserves. Join the list and we’ll write when your level opens.
Interest list only — no sales before launch.
One stack. One roof. Every level of your program, home at last.
Where things stand: TOTEM OS is in closed pilot with a Fort Mill, SC troop. There are no sales before launch — the interest list is how you hear, in order, when your level opens.
Tell us which level you work at and what your unit runs on today. When your level opens, that’s the note we write from.