The Scout Unit Communications Chair: A Job Description That Keeps Information Moving

A communications chair should make four things easier: families can find event details, leaders can publish a clear announcement, reminders arrive with a useful next step, and ordinary questions reach the right person. The role should not make one volunteer the unit’s human router for every decision, deadline, or family concern.

That boundary matters. A campout chair knows the food plan. A den leader knows the meeting change. Unit leadership decides what the unit is doing. The communications chair creates a dependable way for those decisions to reach the people who need them. The job description, intake checklist, responsibility table, and 30-minute rhythm below help a unit start without changing every tool at once.

Decide whether this role will solve a real problem

Many units already have someone doing this work under another name: a secretary, newsletter editor, committee volunteer, Cubmaster helper, or parent who turns scattered updates into one weekly message. A formal communications chair helps when event owners keep sending families competing versions of the plan.

Start the role when at least two of these are true:

• Families regularly ask where the current event information lives.
• Event owners send reminders in different places with different details.
• Leaders spend meetings forwarding messages instead of making decisions.
• A volunteer wants a bounded, repeatable job rather than a vague promise to “help with communication.”

Do not create the role as a substitute for an event owner, unit leader, safety lead, or policy decision-maker. It is a local operating function, not a universal Scouting America position. Girl Scout councils use their own vocabulary too; a current Girl Scouts Arizona troop-family guide lists a Communication Coordinator among possible family volunteer roles. Use the title that fits your unit and council practice, then define the work plainly.

Give the chair four outcomes and a short list of boundaries

The chair owns the communication system and rhythm. Other people remain responsible for the truth of their information.

This distinction keeps the chair from becoming the person who has to guess whether rain changes a meeting, approve an exception, interpret a policy, or chase every RSVP. The Scout communication channel guide is useful here: an announcement, reminder, conversation, RSVP, and urgent update have different jobs.

Use this practical job description

Copy and adapt this for a committee roster, family volunteer menu, or leader handoff.

SCOUT UNIT COMMUNICATIONS CHAIR

Purpose
Keep routine unit information consistent, findable, and connected to the
person who owns the underlying decision.

Core responsibilities
[ ] Maintain the unit's simple communication map: where current event details,
    official announcements, routine reminders, and casual conversation belong.
[ ] Run one 30-minute weekly review of the unit's upcoming events and message needs.
[ ] Turn approved updates into clear family-facing messages that name the action,
    deadline, audience, and current source of details.
[ ] Ask event owners for missing facts before publishing; do not fill gaps by guessing.
[ ] Keep one named owner for recurring family questions and surface patterns at
    the next leader or committee check-in.
[ ] Keep a reusable message template and a short handoff note for the next volunteer.

Does not own
[ ] Event, program, safety, transportation, financial, medical, or policy decisions.
[ ] Permission, registration, youth-protection, incident, or official-record processes.
[ ] Every reply in every group conversation.
[ ] Promising a notification, response, or follow-up that the responsible owner has not confirmed.

Time expectation
About 30 minutes most weeks, plus a defined handoff for unusual event changes.

Make every request pass through a small intake

Event owners often send a message request that sounds complete: “Can you remind everyone about Saturday?” A communications chair should ask for the missing planning facts before turning it into a family instruction.

COMMUNICATION REQUEST INTAKE

[ ] What changed or what action is needed?
[ ] Which event, decision, or current record is the source of truth?
[ ] Who needs this: the whole unit, a group, attendees, volunteers, or leaders?
[ ] What must the recipient do, and by when?
[ ] Who can answer a question or correct a detail?
[ ] Is this an announcement, a reminder, a conversation prompt, an RSVP/action request,
    or an urgent update under the unit's existing process?
[ ] Has the event owner confirmed the wording and the current detail before it is sent?

Here are three ordinary requests and the work the chair should do:

1. Pack picnic volunteer gap. The chair asks the lead for arrival time, job scope, sign-up home, deadline, and question owner. The reminder points families to that one location instead of collecting loose “I can help” replies.

2. Troop campout location correction. The event lead confirms the new entrance, updates the event record, and names the affected attendees. The chair sends one short pointer. The chair does not make the safety decision or send a speculative warning.

3. Den meeting question that keeps returning. Three families ask whether siblings attend. The chair routes the first question to the den leader, then adds one plain answer to the event description and weekly update. The useful measure is that the question stops recurring, not that a message gets more reactions.

Run the 30-minute weekly rhythm

Pick a consistent window, such as Sunday evening or Monday morning. Keep the work short enough that it survives busy seasons.

The rhythm is deliberately boring. A reliable Tuesday reminder is more useful than a perfect monthly newsletter that arrives after the RSVP deadline.

Measure whether the system is working

Views, likes, opens, and message volume do not prove that a family understood what to do. Look for operational evidence instead:

• Can a new family find the current answer without asking someone to resend it?
• Do event owners provide the complete facts before a reminder goes out?
• Are leaders correcting fewer duplicate or stale messages?
• Does each family question have a clear owner and a timely answer through the unit’s agreed path?
• After a changed plan, did the affected families get one current instruction rather than several competing ones?

The system can fail when the chair becomes too helpful. A leader forwards an incomplete note; the chair guesses at the location, answers a transport question, and promises follow-up. The event owner changes the plan. The polished message is now wrong because ownership was unclear.

Reset the boundary: the event owner confirms the information; the chair packages and routes it. For more on keeping durable details out of an endless chat thread, use How to Stop Important Scout Messages From Getting Buried in Chat. If the work itself needs to be distributed, How to Delegate Scout Unit Tasks Without Becoming the Bottleneck has a broader handoff pattern.

Scouting America says its youth-protection policies apply online and that one-on-one adult-youth contact is prohibited across in-person, online, phone, and text interactions. A communications role can support clear, appropriate routing; it does not replace current digital safety guidance, council direction, training, or a unit’s own approved process.

Where Woggle can support the rhythm

A unit using Woggle can keep the current plan in an Event, use a Group or Channel for the right ongoing audience, and use an Announcement when an important update needs to stay findable. Event owners can set a reminder at a selected time before an Event; the communications chair can then make sure the reminder points to complete, current details.

The tools support the communication rhythm, but the unit still needs a named decision owner, event owner, and response owner. Before the next committee meeting, try the intake checklist on one upcoming event. If one question exposes missing facts, fix that handoff before publishing another reminder.