Starting a Chaplaincy Program at Your Agency
A practitioner-led roadmap for police chiefs, sheriffs, and agency administrators building a chaplaincy program from policy to fielded operations.
Most chaplaincy programs that fail were never properly built. They were improvised — well-intentioned pastors invited in without policy, structure, or accountability — and the gap caught up with them. Here is how to do it right the first time.
Why a formal program matters
An informal chaplaincy is one ride-along away from a liability incident. The chaplain is in the patrol car without an MOU. The chaplain is at the line-of-duty death scene without a documented scope of role. The chaplain is offering pastoral counsel that crosses into mandated reporting territory without knowing the legal standard. A formal program addresses each of these. Policy defines who the chaplain is, what they do, what they don't do. The MOU defines the relationship between the chaplain and the agency. Training establishes a baseline of competence. Documentation creates the paper trail that protects the agency, the chaplain, and the community. Formal does not mean bureaucratic. The best programs have documents you could read in twenty minutes — but they have those documents.
Phase A — Foundation (weeks 1–4)
Before any chaplain is appointed, the agency answers three questions in writing. What is the chaplaincy program for? Community engagement? Officer wellness? Critical incident response? Family support? Some combination? Be specific. A program that is for everything is for nothing. Where does the chaplain sit in the org chart? Reporting line, command relationship, who can task the chaplain, who reviews them annually. Most successful programs report through the chief's office or a designated coordinator. **What is the chaplain not for?** Equally important. Not counselors. Not pastoral employees. Not investigators. Not mandatory reporters of confessional disclosures (within the legal standard for clergy privilege in your jurisdiction).
Phase B — Documentation (weeks 5–8)
- Chaplaincy program policy — mission, scope, governance.
- Memorandum of Understanding (MOU) — agency-chaplain
- Code of ethics — confidentiality, impartiality,
- Recruitment & screening framework — sourcing, application,
- Training plan — onboarding, ongoing CEU requirements,
- Operational protocols — call-out procedures, on-call
- Documentation standards — what is recorded, what isn't,
Phase C — Recruitment and training (weeks 9–11)
Recruit chaplains through faith-leader networks, existing agency relationships, and the local interfaith council. Aim for diversity across denomination and tradition; demand consistency on training and ethics. Run candidates through the screening process you just documented. Background check, polygraph if your jurisdiction requires it, psychological evaluation, character references, committee interview. Onboard the appointed chaplains over two to three weeks. Cover agency culture, command structure, radio protocol, ride-along etiquette, scenes you will respond to, and the specific documentation standards. Pair each new chaplain with a peer mentor for the first 90 days.
Phase D — Launch (week 12)
The program goes live. Internal announcement to all sworn and civilian staff. Public-facing announcement (community, media, city council). Roll-call appearances by the chaplains across all shifts in the first 30 days. The first 90 days are about presence and trust-building, not dramatic call-outs. Even when major incidents happen during this window, lean on more experienced surrounding-agency chaplains for primary response and have your new chaplains shadow.
Common failure modes
- No MOU. The single most common cause of program collapse.
- Mission creep. The chaplain becomes the unofficial therapist,
- Single-faith staffing. A chaplaincy that only represents
- No succession plan. When the founding chaplain leaves, the
- Inadequate training. Untrained chaplains make mistakes
A maturity model for ongoing review
- Foundational documents — current, signed, accessible
- Training & development — ICPC progression, CEUs,
- Operational readiness — on-call rotation health, response
- Trust & relationships — officer feedback, family
- Risk & compliance — incident reports, documentation
When to bring in outside help
Bring in a consultant when you are starting from zero, when an existing program is struggling, or when leadership turnover has left the program without institutional memory. The Chaplaincy Program Design engagement is built around exactly this 90-day arc, with a fixed-fee scope and milestone deliverables.
Frequently asked
How long does it take to launch a police chaplaincy program?
A well-run launch takes approximately 90 days from foundation work to fielded operations. Compressed launches (30–60 days) are possible when leadership is decisive and templates are in hand, but tend to leave gaps that surface within the first year.
Should chaplains be paid or volunteer?
Approximately 90% of US police chaplains are unpaid volunteers. The right answer depends on agency size, scope of role, and budget. Most successful programs use a primarily volunteer model with a paid coordinator role for accountability and continuity.
What is the most important document to get right?
The Memorandum of Understanding (MOU) between the agency and each chaplain. It establishes the relationship, sets expectations, defines termination, and protects both sides. Programs without MOUs are the ones that fail liability tests.
Do we need an outside consultant to build a program?
Not strictly. A motivated chief or sheriff with strong administrative support can build a program from publicly available templates and ICPC guidance. A consultant accelerates the work and reduces failure risk; the value depends on agency capacity and timeline.