After crossover or summer camp, a longtime leader can leave the next volunteer a calendar, a few passwords, and a list of things that “usually work.” The new leader still does not know which deadline is real, who calls the chartered organization, or why the committee stopped doing a practice that now looks obvious.
Copying a shared drive leaves that gap in place. A leadership handoff needs context, a period of shared work, and permission to change what no longer serves the unit. This playbook gives an outgoing and incoming leader a practical way to transfer the work without treating the old way as untouchable.
Scouting America’s succession-planning material describes succession as an ongoing process: identify future leaders early, give them small jobs and time to observe, then set a transition date. Its troop committee self-assessment also asks whether key responsibilities are assigned, whether leadership depth prevents any volunteer from becoming indispensable, and whether there is a succession plan for key roles. Those are useful questions for any unit, even though roles and local practices vary.
Start before the departure announcement
Begin when a leader knows a transition may happen. A likely future Cubmaster may emerge months before a child bridges to a troop. A committee chair may know that a work move will change their availability after recharter. A Scoutmaster may need to reduce hours before they leave the role entirely.
Name a likely handoff window and a small transition team: outgoing leader, incoming leader, and one person who can keep the inventory moving. For a troop, that might include the committee chair and Scoutmaster; for a pack, the Cubmaster and committee chair. The unit’s formal appointments, registrations, required training, and permission changes stay with the appropriate Scouting America, council, chartered-organization, and unit processes.
The transition team’s first job is to make the role visible enough that a candidate can decide whether they can do it.
Separate official records from working knowledge
Put each item in one of three lanes before you transfer anything.
| Lane | Examples | Handoff rule |
|---|---|---|
| Official or sensitive | registration, advancement, financial records, health information, background checks, credentials, required forms | Use the system and access process required by the organization. Do not email copies or share personal passwords. |
| Shared unit working knowledge | annual calendar, vendor history, meeting outline, contact roles, recurring deadlines, event debriefs | Give the incoming leader a named location, owner, and explanation of how current it is. |
| Personal convenience notes | a leader’s private reminders, preferred script, old text thread, personal contacts | Extract only what is useful and appropriate; do not make the successor inherit a private archive. |
For example, the outgoing treasurer can explain the rhythm around a fundraiser and point to the unit-approved financial process, but should not hand over a personal bank login. The incoming advancement coordinator needs the annual rhythm and the name of the proper record owner. A pile of old screenshots will not provide either one. The outgoing den leader can introduce the school contact and explain the fall meeting routine, while the new leader decides whether that routine still fits the den.
Access deserves a separate check. Current Scoutbook Plus guidance says each volunteer uses their own my.Scouting credentials and that position-based permissions are managed through its designated tools. Review the current role and permission path with the people authorized to make changes; never solve an access gap by passing along someone else’s account.
Use this handoff inventory
Copy this into a shared planning note. A blank cell shows what the incoming leader still needs to discover.
ROLE AND PURPOSERole being handed off:What this role is responsible for:What it is explicitly not responsible for:
PEOPLE AND RELATIONSHIPSKey partner roles and why they matter:Who needs an introduction before the transition:Families or groups that need a clear leadership-change message:
RECURRING WORKMonth or trigger | Task | Current owner | Next deadline | Where the current information lives
CURRENT DECISIONSDecision | Why it was made | Revisit by | Who should be consulted
ACCESS AND RECORD BOUNDARIESSystem or location | What it holds | Authorized transfer path | Incoming leader action
KEEP, RETIRE, OR REVISITPractice | Keep / retire / revisit | Reason | First review dateThe last section prevents a common failure mode: the incoming leader inherits every workaround because nobody remembers its original purpose. A pack may keep its simple monthly family update, retire a duplicate text reminder, and revisit whether each den needs a separate signup sheet. A troop may keep a patrol leaders’ council planning rhythm, retire an unofficial attendance spreadsheet, and revisit the committee’s meeting agenda after the first quarter.
Put recurring work on a calendar
“In the fall, we get ready for everything” leaves an incoming leader guessing. List the jobs that return, the trigger that starts them, and the deadline that makes delay costly.
| Trigger | Work to transfer | Example of a useful note |
|---|---|---|
| Six weeks before a campout | Confirm leader-side coverage, open roles, and family details | “Event lead reviews open adult roles Tuesday; the official form process is managed separately.” |
| Before the program year | Publish the family-facing calendar and name working dates | “Committee chair checks school and council conflicts; youth planning remains with the troop’s normal process.” |
| Before recharter or annual registration work | Review official instructions and assigned owners | “Use current council and Scouting America guidance; do not reuse last year’s checklist without checking it.” |
| After a major event | Capture two or three decisions for next time | “Keep the earlier pickup window; revisit the snack plan after the fall campout.” |
This is also where a new leader can see the difference between a real requirement and a tradition. The annual-plan publishing guide can help turn the family-facing part of that rhythm into dates and actions people can trust.
Make the first 30 days shared work
A shadow period should include both observation and real decisions. Scouting America’s succession material explicitly recommends giving future leaders time to observe and, where possible, to shadow the current leader. Use four weeks to make that concrete.
| Week | Outgoing leader | Incoming leader | Shared outcome |
|---|---|---|---|
| 1 | Walk through the inventory and name unknowns | Ask what is optional, outdated, or unclear | A short list of gaps and a transition date |
| 2 | Introduce partner roles and show one recurring workflow | Lead one bounded task, such as the next family update | A first task completed with feedback |
| 3 | Stay available but do not take over | Make one routine decision and document why | A reusable example of judgment |
| 4 | Review what should change after the handoff | Lead the first check-in and name support needed | A 60-day follow-up date and clear ownership |
Imagine an incoming committee chair who runs the next agenda while the outgoing chair only fills in missing context. Or an incoming Cubmaster who leads the first leader huddle, then asks the outgoing Cubmaster to explain one recurring family question. Or an incoming Scoutmaster who meets the committee chair before a campout and agrees which adult-side details need visibility while youth leadership retains its program role. These are small but real tests of the handoff.
Hold one first conversation that changes the relationship
Use this agenda before the incoming leader starts acting alone:
- What does this role need to protect for Scouts and families?
- Which three recurring jobs are hardest to see from the outside?
- What decision is currently open, and who has the authority to make it?
- Which relationships need a personal introduction?
- What should the incoming leader feel free to stop, simplify, or revisit?
- When will we meet once more to see what the inventory missed?
The outgoing leader should answer without turning every answer into an instruction. The incoming leader should leave with a next action and the freedom to ask why. The aim is to preserve useful context while giving the incoming leader room to change a volunteer-run unit.
Where Woggle can support the day-to-day layer
Woggle can support a handoff after the official access and records work is handled elsewhere. Accurate Woggle roles and permissions can keep coordination access tied to the job; Groups and Channels can preserve the current context for committees or recurring audiences; Events can hold the practical details for an activity; and Announcements can keep a leadership-change notice or deadline easier to find than an old chat thread.
Keep official records, credentials, and the unit’s document archive in their proper systems. A useful first step is to make sure the incoming leader has the right Woggle access, knows which Groups are active, and can update one real Event and one durable Announcement with the outgoing leader nearby. For the ownership side of that work, use How to Delegate Scout Unit Tasks Without Becoming the Human Router.
Start the inventory before the next departure becomes urgent. Pick one key role, put its recurring work on a calendar, and schedule the first shared task this month.
