M2 Management · Lesson 4 of 4

Lesson 4 — Continuity, Policies, and Leadership Health

Reduce the organization's dependence on undocumented knowledge or any single person by identifying key-person risks and closing policy gaps.

Not started

M2 Lesson 3 Back to M2 Management M3 Lesson 1

Nine M curriculum version 1.0 · Nine M methodology, content, exercises and deliverables by Pastor Lee Jenkins.

Where this lesson sits

Curriculum version 1.0 · Pastor Lee Review

Module purpose: Build a healthy governance and operating structure with clear authority, accountable leadership, effective meetings, documented policies, and dependable execution.

Official outcome: Church Management and Accountability Plan

This lesson produces: Key-Person Dependency and Policy Gap Register

Anything you type is kept in this browser session only. This prototype does not save to a server.

Learn

Participant study reading — approximately 90 minutes of learning and shared work.

Learning objective: Reduce the organization's dependence on undocumented knowledge or any single person by identifying key-person risks and closing policy gaps.

Recommended participants: Pastor, board or elder body, senior staff

Estimated teaching time: 90 minutes

Success indicators

• The team has identified at least three key-person dependency risks by name and role
• A policy register lists existing, missing, and outdated policies across major ministry areas
• A 90-day improvement plan has been drafted with owners and due dates for the highest-priority gaps
• Leadership-team standards for communication and conflict have been documented or affirmed

Materials and evidence you will use

• Governance and Authority Map from lesson one
• Decision Rights Matrix from lesson two
• Any existing personnel, finance, or facility policies
• At least three key-person dependencies identified by name and role
• A policy register covering at least four major ministry or operational areas
• Top priorities assigned a named owner and due date

What you should be able to produce

• The team has identified at least three key-person dependency risks by name and role
• A policy register lists existing, missing, and outdated policies across major ministry areas
• A 90-day improvement plan has been drafted with owners and due dates for the highest-priority gaps
• Leadership-team standards for communication and conflict have been documented or affirmed

Foundational ministry principle

Deuteronomy 31:1-8

1 And Moses went and spake these words unto all Israel. 2 And he said unto them, I am an hundred and twenty years old this day; I can no more go out and come in: also the LORD hath said unto me, Thou shalt not go over this Jordan. 3 The LORD thy God, he will go over before thee, and he will destroy these nations from before thee, and thou shalt possess them: and Joshua, he shall go over before thee, as the LORD hath said. 4 And the LORD shall do unto them as he did to Sihon and to Og, kings of the Amorites, and unto the land of them, whom he destroyed. 5 And the LORD shall give them up before your face, that ye may do unto them according unto all the commandments which I have commanded you. 6 Be strong and of a good courage, fear not, nor be afraid of them: for the LORD thy God, he it is that doth go with thee; he will not fail thee, nor forsake thee. 7 And Moses called unto Joshua, and said unto him in the sight of all Israel, Be strong and of a good courage: for thou must go with this people unto the land which the LORD hath sworn unto their fathers to give them; and thou shalt cause them to inherit it. 8 And the LORD, he it is that doth go before thee; he will be with thee, he will not fail thee, neither forsake thee: fear not, neither be dismayed.

King James Version (KJV) · Public domain

Draft material proposed for Pastor Lee Jenkins' review: Moses, nearing the end of his leadership, publicly commissions Joshua before the whole community and reminds the people that the mission does not depend on Moses alone, since the same faithfulness that carried them will carry Joshua's leadership forward.

Proposed framing for facilitator use: this passage models intentional, public succession planning rather than leaving continuity to chance, which is the exact discipline this lesson asks leadership to practice around key roles and undocumented knowledge.

Understand the concept

Your work in this lesson focuses on this outcome: Reduce the organization's dependence on undocumented knowledge or any single person by identifying key-person risks and closing policy gaps.

Protecting the church's mission means making sure no single person's absence can bring critical operations to a stop; documentation and cross-training are acts of stewardship, not distrust.

Why it matters for your church

Undocumented financial processes create both fraud risk and continuity risk if the person handling them leaves.

Missing or outdated child protection policies expose the church to serious safety and liability risk.

A leadership team without agreed standards tends to handle conflict inconsistently, damaging trust over time.

Examine the evidence

Use Governance and Authority Map from lesson one, Decision Rights Matrix from lesson two, and Any existing personnel, finance, or facility policies to compare your church's present practice with its stated intentions. Look for documented patterns, missing information, and differences between what people assume and what the evidence supports.

Your completed work should be supported by At least three key-person dependencies identified by name and role, A policy register covering at least four major ministry or operational areas, and Top priorities assigned a named owner and due date. Record uncertainty honestly so your team knows what still needs to be verified.

Prepare for the shared exercise

Identify the church's highest-risk single points of failure and missing policies, and translate them into a prioritized 90-day improvement plan. The Key-Person Dependency and Policy Gap Register produces the Key-Person Dependency and Policy Gap Register, which contributes to the module's principal deliverable.

Before working with your team, consider this reflection: If you personally were unexpectedly unavailable for thirty days, what would be hardest for someone else to pick up in your absence, and what is one step you could take this month to make that easier?

Key terms

Key-person dependency: A situation where critical knowledge, access, or relationships exist with only one individual, creating organizational risk if that person is unavailable.
Policy register: A documented inventory of a church's policies by area, noting which exist, are missing, or are outdated.
Leadership-team standards: Written agreements about how a leadership team communicates, handles conflict, and holds one another accountable.

What this means for a church

• Undocumented financial processes create both fraud risk and continuity risk if the person handling them leaves
• Missing or outdated child protection policies expose the church to serious safety and liability risk
• A leadership team without agreed standards tends to handle conflict inconsistently, damaging trust over time

Common failure patterns

• Waiting until a key person actually leaves before attempting to document what they knew
• Writing a policy once and never revisiting whether it still matches actual practice
• Treating leadership health as a personality issue rather than a structure that can be intentionally built

Ministry case

The Password Only One Person Knew

A church's longtime volunteer treasurer managed all banking access personally for over a decade, a service given faithfully and without any complaint. When she was unexpectedly hospitalized for several weeks, the church could not access online banking, could not verify whether bills had been paid, and had no backup process in place.

The crisis passed once she recovered, but it prompted the board to build its first Key-Person Dependency and Policy Gap Register. They discovered four other similar risks across the church, each resolved not by replacing faithful volunteers but by documenting processes and adding a second authorized person to each critical system.

Lesson takeaway

Protecting the church's mission means making sure no single person's absence can bring critical operations to a stop; documentation and cross-training are acts of stewardship, not distrust.

Discuss

Guided discussion for the leadership table.

Let's name, as a group, the key-person risk we feel most exposed to right now, and talk honestly about what would need to happen in the next ninety days to reduce it.

Which key-person dependency in our church feels most urgent to address, and why?
What policy did we discover today is missing or badly outdated?
Have we ever written down how our leadership team handles disagreement, or has it always been assumed?
What would success look like in ninety days for the two or three priorities we are choosing to focus on first?

Discussion notes

Practice

Applied exercise — produces the Key-Person Dependency and Policy Gap Register.

Key-Person Dependency and Policy Gap Register

Identify the church's highest-risk single points of failure and missing policies, and translate them into a prioritized 90-day improvement plan.

Estimated time: 45 minutes

Participants: Pastor, board or elder body, senior staff

Artifact produced: Key-Person Dependency and Policy Gap Register

Required inputs

• List of roles and the knowledge or access each one uniquely holds
• Any existing policies, however informal, across finance, personnel, and ministry areas
• Prior lessons' Governance and Authority Map, Decision Rights Matrix, and Accountability Dashboard

Instructions

List each identified key-person dependency by role and name.
For each, describe what would break if that person were unavailable for thirty days.
Rate the risk level of each dependency as low, medium, or high.
List each major policy area and mark whether a policy exists, is missing, or is outdated.
Select the two or three highest-risk items across both dependencies and policies to prioritize.
Assign an owner and due date to each prioritized item for the 90-day improvement plan.
Record the completed register and plan for inclusion in the Church Management and Accountability Plan.

Complete it online

Key-Person Dependency and Policy Gap Register

Church name: ______________________
Date completed: ______________________
Facilitator: ______________________

Risk item (person or policy)	What breaks if unresolved	Risk level	Priority for 90-day plan?	Owner and due date

Your response — Key-Person Dependency and Policy Gap Register

Worked example

A fully completed sample using a fictional church. This is illustrative teaching material, not any church's actual data.

Northgate Community Church (illustrative example — not actual church data)

After the earlier check-signing and password concerns surfaced across the module, Northgate's leadership built its first full dependency and policy register.

Risk item (person or policy)	What breaks if unresolved	Risk level	Priority for 90-day plan?	Owner and due date
Office Administrator: sole holder of all online account logins	Church cannot access banking, email, or ministry software for an unknown period	High	Yes	Executive Pastor, credentials documented and stored securely within 30 days
Child protection policy	No documented background-check or two-adult rule currently exists in writing	High	Yes	Board Chair, policy drafted and adopted within 60 days
Worship Director: sole knowledge of sound system configuration	Sunday service audio could fail with no one able to troubleshoot	Medium	Yes	Facilities Team Lead, basic troubleshooting guide written within 90 days
Conflict-of-interest policy	No written process exists for board members with a financial interest in a vendor decision	Medium	No, addressed after top three	Elder Board, reviewed in next quarterly governance meeting

How this leadership team reasoned

• The credential dependency was rated highest priority because it echoes the exact scenario that caused a prior banking-access crisis at a similarly sized church.
• The missing child protection policy was rated high risk given its direct connection to child safety and legal exposure, even though no incident had yet occurred.
• The sound system dependency was rated medium since a failure would be disruptive but not safety-critical, making it appropriate for a 90-day rather than 30-day timeline.

Decisions recorded

• The Executive Pastor will document and securely store all account credentials with at least one backup authorized person within 30 days.
• The Board Chair will lead drafting of a formal child protection policy for adoption within 60 days.
• The conflict-of-interest policy will be addressed at the next quarterly governance meeting rather than within this immediate 90-day window, given the top three priorities.

Completed artifact extract — Key-Person Dependency and Policy Gap Register

Key-Person Dependency and Policy Gap Register Extract (Northgate Community Church, illustrative): The Office Administrator currently holds sole access to all online banking, email, and ministry software accounts, rated high risk given the church's inability to operate these systems if that access were lost. The Executive Pastor will document all credentials and establish a second authorized user within 30 days. The absence of a written child protection policy is rated high risk for its safety and legal implications, with the Board Chair leading the drafting and adoption of a formal policy within 60 days.

Illustrative exercise score: 18 of 20. The register is complete across both people and policy risks with specific ratings, draws on a real prior incident as evidence, directly serves the module's continuity purpose, and assigns clear owners and due dates for the top priorities identified.

Score

Transparent 20-point exercise rubric: four criteria rated 0 to 5 with observable anchors.

Criterion	0 — not evident	3 — acceptable	5 — exemplary	Sample
Completeness (0–5)	Fewer than three risk items are identified and risk levels are not rated.	At least five risk items are identified but risk levels or priority marking are missing for some.	At least eight risk items across both people and policy are identified with risk levels and priority marked for each.	5
Use of evidence (0–5)	Risk ratings are assigned without any reference to real church history or current practice.	Some items reference real practice but ratings otherwise appear arbitrary.	Risk ratings are directly tied to real past incidents or confirmed current gaps in practice.	5
Alignment to the module purpose (0–5)	The register does not address continuity or reduce dependence on any single person.	The register identifies some risks but does not clearly prioritize the highest-impact ones.	The register clearly prioritizes the highest-impact continuity risks and ties them to concrete mitigation steps.	4
Actionability and ownership (0–5)	No owners or due dates are assigned to any risk item.	Some items have owners but lack specific due dates.	All prioritized items have a named owner and a specific due date within the 90-day window.	4
Worked sample total				18 / 20

Completeness: Northgate's register covered both key-person and policy risks with a risk level and priority marking on every row.
Use of evidence: The credential risk was explicitly tied to a real prior access crisis, and the child protection gap was confirmed as genuinely absent in writing.
Alignment to the module purpose: The top three priorities were clearly ranked and tied to concrete mitigation, though the fourth item's deferral rationale could be documented more explicitly.
Actionability and ownership: The top three priorities each have a named owner and specific due date, though the deferred fourth item's future timing is only loosely set.

Lesson-exercise scores (20 points each) demonstrate learning and artifact quality. They do not automatically overwrite the official Nine M module assessment, which remains a separate 100-point rating of five module dimensions.

Submit evidence

What must be submitted for this lesson to count as complete.

Submit

• Completed Key-Person Dependency and Policy Gap Register
• 90-day improvement plan with owners and due dates for top priorities

Attach this evidence

At least three key-person dependencies identified by name and role
A policy register covering at least four major ministry or operational areas
Top priorities assigned a named owner and due date

File upload is not implemented in this prototype. Ticking a box records that the church can produce the document; it does not store a file.

Contribute to official outcome

How this lesson builds the Church Management and Accountability Plan.

Artifact produced: Key-Person Dependency and Policy Gap Register

Completes the policy register, succession-risk section, and 90-day improvement plan sections of the Church Management and Accountability Plan.

Open the module deliverable assembly

Participant reflection and notes

If you personally were unexpectedly unavailable for thirty days, what would be hardest for someone else to pick up in your absence, and what is one step you could take this month to make that easier?

M2 Lesson 3 Back to M2 Management M3 Lesson 1