At many join nights, families raise a hand, write down contact information, and leave with a good first impression. Then the sign-in sheet goes home in a tote bag. A week passes, the next meeting is not obvious, and a family that was interested now has to decide whether to ask again.
Families who express interest need a human welcome, one specific invitation, and a clear person who will be expecting them at the door. This sequence helps a pack, troop, or other Scout unit make that handoff without turning a recruitment event into a lead-management project.
Scouting America’s current Troop Open House guidance follows the same practical logic: personalize the invitation, call before the event, greet guests at the door, make the calendar available, and give new Scouts an activity soon after they join. Adapt the timing to your unit and local practice, but keep interest, an accepted visit, attendance, and completed registration as four separate states.
Make the next invitation the whole point
Give the first follow-up one job: help a family decide whether to attend one real next thing. Keep the invitation separate from a parent handbook or an implied promise that the family is already registered.
Name the exact meeting or activity, including date, time, location, and a person to look for. For a Cub Scout pack, that might be a Bear den meeting followed by the pack gathering. For a Scouts BSA troop, it might be a Tuesday troop meeting with a youth-led opening and a short parent conversation afterward. For a family that cannot make either, offer the next available visit rather than making them restart the conversation.
Answer these five questions before the family walks in:
- Where do we park and which door do we use?
- What time should we arrive, and how long will it run?
- What should the Scout wear or bring this first time?
- Should a parent or caregiver stay, check in, or arrange an observation with a leader?
- Who will greet us and answer questions afterward?
For Scouts BSA, do not assume that a parent will sit through a troop meeting. Scouting America describes the program as youth-led and asks parents or guardians who want to observe to coordinate with the Scoutmaster in advance. For Cub Scouts, family participation may look different. Say what your unit expects plainly instead of relying on program shorthand.
Keep only the fields that support a welcome
Use a paper sign-in sheet, a small spreadsheet, or a shared unit-approved tracker. Record only what lets one person follow through and see the next decision; follow current organizational, council, and unit expectations for collecting and retaining family information.
| Field | Why it belongs in the tracker |
|---|---|
| Parent or caregiver name and preferred contact method | Lets one known adult receive the invitation. |
| Youth first name and likely grade or program fit | Helps the unit offer the right den, patrol, or meeting contact without guessing. |
| Date and source of interest | Distinguishes a school open house, a friend referral, and a community event. |
| Next invitation and date sent | Prevents two leaders from sending competing messages. |
| Named follow-through person | Makes the welcome someone’s job, with a backup if needed. |
| Status: interested, invited, visit accepted, reschedule requested, visited, registered, or not now | Keeps a proposed visit from becoming a confirmed one by assumption. |
| Next step or respectful closeout date | Shows whether to invite, welcome after a visit, or stop repeated outreach. |
Leave out medical details, financial information, broad family notes, and anything that is not needed for this immediate handoff. The tracker is a short invitation log, not an official roster or registration record.
Use three messages with different jobs
Send each message from a real person who can answer a reply. The wording can be text, email, or a call script. This is a branching sequence, not an automatic drip: the family’s response determines what happens next.
| Current state | Next action |
|---|---|
| No reply after Message 1 | Send one tentative check-in. If there is still no reply, set a respectful future check-in or closeout date and stop. |
| Declines or says “not now” | Acknowledge the answer, record the family’s preference, and stop. |
| Accepts while the proposed visit is still upcoming | Send Message 2 and prepare the greeter. |
| Replies yes after the proposed visit has passed | Offer a new date; send Message 2 after that date is accepted. |
| Cancels or asks for another date before Message 3 | Confirm a new date and return to Message 2, or record “not now.” Do not send Message 3 for the old date. |
| Attends | Send the attended version of Message 3. |
| Accepts, does not arrive, and sends no update before follow-up | Send the unexplained-absence version of Message 3. |
Message 1: Send it while the event is still fresh
When: That evening or the following day.
Job: Say thank you and offer one specific visit.
Hi [caregiver name], it was great to meet you at [join night]. [Youth first name] is welcome to visit [meeting or activity] on [day, date] at [time] at [location]. Please use [entrance or parking note]. I’m [name], and I’ll be there to welcome your family. For this first visit, [simple clothing or bring-one-item guidance]. Would that date work for you?
Give the family something easy to accept, decline, or move. If a troop has a campout in two weeks but a regular meeting tomorrow, invite the family to the meeting first; the nearer, lower-pressure step is usually clearer.
If the family does not reply, send one tentative check-in before the proposed meeting: “Would [date] still work for a visit? If not, I can suggest another date.” If that also goes unanswered, set a future check-in or closeout date. Do not send arrival-confirmation or missed-visit messages unless the family accepts.
Message 2: Reduce the uncertainty before the visit
When: After the family accepts an upcoming visit. Send it by the day before when possible; if they accept on the meeting day, send it immediately. If the proposed time has passed, agree on a new date first.
Job: Answer the arrival questions before they become a reason not to come.
We’re looking forward to seeing you on [date]. Park by [landmark] and come through [door]. We start at [time] and finish around [time]. [Leader name] will meet you near the entrance. [Parent or caregiver expectation]. [Scout] only needs [simple item, if any]; uniforms and longer-term questions can wait. If the plan changes, reply here and we’ll help you choose the next visit.
A cancellation or reschedule request overrides the old acceptance, even if it arrives after the meeting but before Message 3. Confirm a new date and send arrival details for that visit, or record “not now.” Remove advance changes from the greeter’s expected-family list, and never send Message 3 for the old date.
For example, a pack can say, “Siblings are welcome at this pack meeting; your den leader will show you where the Wolf den gathers.” A troop can say, “Please check in with Ms. Rivera at the door; parents can ask questions after the opening while Scouts join the meeting.” Specificity is kinder than a long explanation of unit structure.
Message 3: Close the loop after the planned visit
When: The next morning after the family attended, or after an accepted visit passed with no arrival and no cancellation or reschedule message.
Job: Give one next step that matches what actually happened.
If the family attended:
Thanks for visiting [unit]. We were glad to meet [Scout]. If your family would like to continue, the next step is [registration conversation, next meeting, or specific activity] on [date]. [Contact name] can help with questions. We’ll send only the details you need for that next step.
If a family accepted, did not arrive, and sent no update before follow-up, do not send a guilt-tinged “we missed you” note followed by weekly generic reminders. Try one respectful branch instead: “It looks like tonight did not work out. Would [next date] or [alternative contact] work better?” If there is no response, mark a future check-in date or close the loop according to your unit’s practice. A quiet family may have a schedule conflict, not a lack of interest.
Give the door a named owner
The realistic failure mode is a polished first message with no arrival plan. A parent arrives at an unfamiliar school, sees several doors, and has no idea who knows they are coming. Meanwhile, the recruitment volunteer assumes a den leader is greeting them, and the den leader assumes the Cubmaster has it covered.
Before each first visit, assign three small jobs:
- Invitation owner: sends the appropriate message, updates the status when plans change, and keeps the expected-family list current.
- Door greeter: knows the family’s names, arrives early, and introduces them to the right leader.
- After-meeting contact: checks in briefly and confirms the next invitation or registration conversation.
One person can hold all three jobs, but naming them exposes the handoff. If the invitation owner cannot attend, the door greeter needs the arrival details and agreed introduction. Keep private contact information out of a broadly shared event post.
First-meeting readiness checklist
Use this ten minutes before the visit begins.
BEFORE THE DOORS OPEN
[ ] Every family on the expected list accepted this date; cancellations and reschedules are removed.
[ ] The family has a current date, start time, location, parking, and entrance note.
[ ] A named greeter and backup know who is expected.
[ ] The receiving den, patrol, or leader knows the family is visiting.
[ ] The parent or caregiver expectation is stated in plain language.
[ ] The next event or meeting is ready to name if the visit goes well.
AFTER THE VISIT
[ ] An attending family receives a personal thank-you and one next step.
[ ] A cancellation or reschedule is acknowledged when received; it never gets the absence message.
[ ] An unexplained absence receives one respectful alternative.
[ ] The tracker separates invited, accepted, rescheduled, visited, and registered status.
[ ] Registration, official records, fees, forms, and policy requirements stay in the appropriate approved process.
[ ] The follow-through person has one next date or a clear closeout note.Make a thoughtful visit easy, and keep an interested family from being lost between two well-meant messages.
Where Woggle fits after the decision to join
Once a family is ready to join and your unit has completed its normal registration process, Woggle can support the next coordination layer. An Invite can bring the adult into the unit; Household context, Groups or Channels, an upcoming Event, and one Announcement can make the first useful information easier to find. The Groups setup guide and first Event guide show those steps in more detail.
Keep official registration, Scoutbook, council requirements, forms, and unit policy in their approved systems. Woggle keeps the next meeting and its practical details connected once the family is part of the unit.
Start with the next join night: assign a door greeter, send Message 1 before the next day ends, and make one real meeting easy to say yes to.
