Church Safety Team Policies and Procedures: A Planning Framework

Most congregations do not start a safety team because of a plan. They start one because something happened — a medical emergency during a service, an unsettling visitor, a news story about somewhere that felt a lot like here. A few capable people volunteer, they start standing near the doors, and everyone feels slightly better.

That is a reasonable place to begin and a bad place to stay. The gap is almost never willingness. It is that nothing is written down, so the plan lives in the heads of whoever happens to be serving that morning — and it changes depending on who that is.

This is a framework for the written part. It is deliberately about organization, not tactics: who does what, how they talk to each other, what gets recorded, and when it all gets reviewed.

Start with authorization, not with volunteers

Before roles or procedures, the policy needs to answer a governance question: who authorized this team to exist, and who does it answer to? In practice that means a written approval from the board, elders, council or whatever body governs your congregation, naming the team, its scope and its reporting line.

This matters for two reasons. It protects the volunteers, who are otherwise acting on their own initiative in a place full of other people's children. And it forces the leadership conversation to happen deliberately rather than by accumulation, which is the only way the team's limits get defined before they get tested.

• The governing body that approved the team, and the date
• Who the team leader reports to, and how often
• The team's scope — and explicitly, what is outside it
• Who can add or remove a team member, and on what grounds
• How the policy itself gets amended

Roles, written as responsibilities

A team of eight people who are all "on safety" is a team where nobody owns anything. Write roles as responsibilities rather than titles, so that on a given Sunday every function has exactly one name against it.

• Team lead for the service — the single decision-maker for that morning
• Greeter-side awareness — the people at the doors, who see everyone arrive
• Parking and exterior — often where a problem is first visible
• Medical response — who holds the first-aid role and where the kit is
• Children's ministry liaison — check-in, check-out, reunification
• Communications — who calls 911, who talks to leadership, who talks to nobody

The most useful thing about writing it this way is that it makes gaps obvious. If no name goes next to "medical response" this week, you have found something before it mattered rather than during.

A plan that depends on a particular person being there is not a plan. It is a habit that has not failed yet.

Communication is the part most plans skip

Almost every safety plan describes what to do. Far fewer describe how the people doing it will talk to each other while it happens. That is usually the thing that breaks first.

• The primary method — radios, a group text, a dedicated app — and who is on it
• The backup, for when the primary fails or the building's coverage is poor
• Plain language rather than codes. Codes fail under stress and confuse visitors
• Who is authorized to call 911, and the instruction that nobody waits for permission in a life-threatening emergency
• Who meets emergency services at the door and directs them
• Who informs the person leading the service, and how, without alarming the room
• Who does not speak — specifically, who handles press or social media, so nobody else does

Write down the physical address of every building and entrance, including any that differ from the mailing address. Under pressure, people forget the address of a place they have attended for twenty years. It belongs on a card in the kit, not in someone's memory.

Medical response is the emergency you will actually have

Congregations plan for the frightening scenario and under-plan for the likely one. Across a typical membership — with older members, small children and gatherings that run for hours — a medical event is the emergency a safety team is most likely to face, possibly repeatedly.

• Where the AED is, whether it is checked, and who has been shown how to use it
• Where first-aid supplies live, who restocks them, and on what schedule
• Which members hold current CPR or first-aid certification, and when it expires
• How someone summons help from inside a service without causing panic
• How emergency services get in — including which doors are locked mid-service
• Where an ambulance should stage, and who clears the route
• Any known medical needs among members, handled with real care for privacy

Children, families and reunification

Children's ministry is where a safety policy becomes most concrete, because it is the one area where a congregation already accepts a bit of friction. Parents will tolerate a check-in procedure that they would find strange anywhere else in the building.

• A check-in and check-out procedure that matches child to authorized adult, every time
• How custody arrangements and restricted-contact situations are handled discreetly
• Who may enter children's areas, and how volunteers are identified on sight
• Background-check requirements for anyone working with minors, and who tracks them
• A reunification plan — where parents go, who brings the children, how it is controlled
• A missing-child procedure with a defined first action and a defined escalation point
• Mandatory-reporting obligations, which vary by state and often name clergy specifically

Reunification deserves more attention than it usually gets. In any evacuation, the instinct of every parent in the building is to move toward their children, which is exactly the movement that makes an evacuation dangerous. A plan that does not answer "where do I find my child" will be overridden by people who love their children more than they respect your plan.

The procedures worth writing down

Keep each procedure to a single page. A plan nobody can hold in their head on a Sunday morning is decoration. For each one, write the first action, who decides, and how it ends.

1. 01Medical emergency — the most likely, and the one to rehearse most
2. 02Evacuation — fire, alarm, gas, structural. Include assembly points and headcount
3. 03Shelter in place — severe weather, and where the interior spaces are
4. 04Disruptive or distressed person — de-escalation, involving leadership, when to call for help
5. 05Missing child
6. 06Lockdown, and who can call it
7. 07Suspicious item or unattended package — do not touch, clear the area, call authorities
8. 08Threat received by phone, email or social media — record it, preserve it, report it
9. 09Severe weather during a service, including who monitors and who announces

Write these for the buildings you actually have. A procedure that references a fellowship hall you no longer use, or an exit that has been locked since the renovation, teaches your team that the document is not to be trusted.

If your team includes armed volunteers

Some congregations decide to include armed members on the team; many decide not to. Both are legitimate decisions for a congregation to make, and this framework does not argue for either. What is not optional is that the decision be explicit, documented and lawful.

The policy questions are governance questions, not tactical ones:

• Who authorized it — the governing body, in writing, with a date
• Who is permitted, how they are selected, and who can revoke that permission
• What training and what recurrency are required, and who verifies them
• Whether leadership, staff and the wider congregation are informed, and how
• What your insurer says, in writing, before the policy takes effect
• What your state's law actually says about carry in a house of worship

That last point catches congregations out, because the law is genuinely state-specific. In Michigan, for example, MCL 28.425o lists property owned or operated by a church, synagogue, mosque, temple or other place of worship among the premises where a CPL holder may not carry a concealed pistol — unless the presiding official or officials permit it. The permission of the presiding official is what makes the difference, which makes it a governance decision that belongs in writing in your policy. Other states handle this very differently. Verify your own.

Work with local authorities before you need them

The relationship you want with your local police and fire departments is one that exists before an emergency. Most agencies will walk a building with you, and many have a community liaison whose job includes exactly this.

• Invite local law enforcement and fire to walk the property and comment on the plan
• Give them current floor plans, and tell them when the buildings change
• Confirm which doors are locked during services, and how responders get through them
• Ask what they want your team to do — and not do — when they arrive
• Ask about existing programs, assessments or grant funding for houses of worship
• Record who your contacts are, so the relationship survives a change of volunteers

CISA publishes a security self-assessment for houses of worship that a team can work through together. It is a useful structure for a first meeting, and it produces a written record of where you actually are.

Training expectations, written as a standard

A policy that says members should be trained will produce a team that is not. Write the expectation as a standard with a frequency attached, and record who has met it.

• What every member must complete before serving, and within what window
• What is renewed annually — CPR and first aid are the usual baseline
• How often the team drills, and which procedures get rehearsed
• Who tracks certifications and expiry dates
• What happens when someone falls out of currency
• Additional requirements for specific roles, including armed members where applicable

Drills are worth more than they cost. A short walkthrough of an evacuation and a reunification, with the children's ministry involved, will find more problems in twenty minutes than a year of meetings.

Documentation, and why it protects you

Write down incidents — including the small ones. A pattern of minor events is often the only warning a congregation gets, and it is invisible unless someone is recording it.

• A simple incident report: what happened, when, who was involved, what was done
• Who reviews reports, and how quickly
• Where records are stored, who can access them, and how long they are kept
• How personal and medical details are protected
• Training and certification records
• Equipment checks — AED, first-aid kits, radios, lighting, locks
• Minutes from plan reviews and drills

Handle these records with the same care you would want applied to your own family's information. A safety team accumulates sensitive detail about members quickly, and losing control of that does its own damage.

Review the plan on a schedule

Set a review date and keep it. Annually is a reasonable default, with additional reviews triggered by specific events rather than by someone remembering.

• After any actual incident, however minor
• After a building change, renovation or new entrance
• After a significant change in team membership or leadership
• When a service time, format or attendance pattern changes materially
• When state law relevant to the plan changes

Put the review date, the version number and the approval date on the front page of the document. It sounds bureaucratic. It is the difference between a plan and a folder.

Where to start if you have nothing

If your congregation has no written plan at all, do not try to produce the complete document. Start with the three things that carry the most weight for the least effort:

1. 01A written authorization from your governing body that the team exists and who leads it
2. 02A one-page medical emergency procedure, with the AED location and the building address on it
3. 03A children's check-in, check-out and reunification procedure

Those three cover the most likely emergency and the most vulnerable people in the building. Everything else in this framework can be built on top of them over the following months.