I.M.P.A.C.T. Church Empowerment Program

A partnership with Pastor Lee Jenkins, the Stewardship Coach, and Allan Bell - CPA, CMA, MBA, Nsites founder and creator

M6 Membership · Lesson 2 of 4

Lesson 2 — Follow-Up that is Timely and Pastoral

Establish follow-up standards by guest type and expressed need.

Not started

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: Create a clear, relational pathway from first visit to belonging, covenant, retention, and active participation.

Official outcome: Visitor-to-Member Pathway

This lesson produces: Follow-Up Sequence Standards with owners, timing and consent language

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

Learn

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

Learning objective: Establish follow-up standards by guest type and expressed need.

Recommended participants: Connections coordinator, care ministry leader, and front-line volunteer leads

Estimated teaching time: 75 minutes

Success indicators

  • • Follow-up timing windows are defined for each guest type
  • • Each follow-up step has a named owner and method
  • • Consent and confidentiality language is written for pastoral follow-up
  • • A process exists for guests who express a specific need or crisis

Materials and evidence you will use

  • • Lesson One's Belonging Journey Map
  • • Stewardship Nsites Connect follow-up pipeline data
  • • Each guest type has a distinct timing window and owner
  • • Consent language exists for at least sensitive guest types

What you should be able to produce

  • • Follow-up timing windows are defined for each guest type
  • • Each follow-up step has a named owner and method
  • • Consent and confidentiality language is written for pastoral follow-up
  • • A process exists for guests who express a specific need or crisis

Foundational ministry principle

Hebrews 13:2

2 Be not forgetful to entertain strangers: for thereby some have entertained angels unawares.

King James Version (KJV) · Public domain

this verse's call to show hospitality to strangers suggests urgency and attentiveness, not delay, in how the church reaches out to newcomers.

Draft framing for review: leadership may want to consider that timely, personal follow-up is not a customer-service metric but a pastoral practice consistent with the church's call to hospitality.

Understand the concept

Your work in this lesson focuses on this outcome: Establish follow-up standards by guest type and expressed need.

Follow-up that is both timely and pastoral requires differentiated standards, not just good intentions; consistency comes from writing down who does what, by when, and with what care for consent.

Why it matters for your church

Differentiated follow-up prevents both under-care of urgent needs and over-contact of casual visitors.

Written timing windows turn good intentions into a system that survives staff and volunteer turnover.

Consent language protects guest dignity and builds trust that personal information will be handled with care.

Examine the evidence

Use Lesson One's Belonging Journey Map, and Stewardship Nsites Connect follow-up pipeline data 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 Each guest type has a distinct timing window and owner, and Consent language exists for at least sensitive guest types. Record uncertainty honestly so your team knows what still needs to be verified.

Prepare for the shared exercise

Produce a written, differentiated follow-up standard that leadership can hand to every ministry team. The Follow-Up Standards Design Session produces the Follow-Up Sequence Standards with owners, timing and consent language, which contributes to the module's principal deliverable.

Before working with your team, consider this reflection: If a guest shared something painful with us this week, can we honestly say they would trust how that information was handled?

Key terms

Guest type
A category of visitor defined by how they arrived or what need they expressed, used to determine the appropriate follow-up path.
Timing window
The maximum number of days allowed before a follow-up contact must occur for a given guest type.
Consent language
Plain-language wording that tells a guest what will be done with information they share and confirms their ability to decline further contact.

What this means for a church

  • • Differentiated follow-up prevents both under-care of urgent needs and over-contact of casual visitors.
  • • Written timing windows turn good intentions into a system that survives staff and volunteer turnover.
  • • Consent language protects guest dignity and builds trust that personal information will be handled with care.

Common failure patterns

  • • Treating every guest identically regardless of what they expressed or needed.
  • • Setting timing windows with no way to track whether they are actually being met.
  • • Collecting sensitive information without any consent language, damaging trust when guests learn it was shared further.

Ministry case

The Prayer Request That Waited Three Weeks

A guest at a growing church checked a box on a connection card requesting prayer for a serious medical diagnosis. The card sat in a stack with dozens of general visitor cards and was not reviewed for three weeks. By the time a pastor called, the family had already found support elsewhere and did not return.

When leadership reviewed the incident, they realized the failure was not a lack of care but a lack of a differentiated process. General guests and urgent pastoral needs had been funneled through the identical, slow channel. Building separate timing windows and owners, as this lesson describes, was the direct fix.

Lesson takeaway

Follow-up that is both timely and pastoral requires differentiated standards, not just good intentions; consistency comes from writing down who does what, by when, and with what care for consent.

Discuss

Guided discussion for the leadership table.

With our guest types, timing windows and consent language drafted, let us test them against a real recent example from our own church before finalizing the standards in the exercise.

  1. Which guest type in our church most often falls through the cracks, and why?
  2. What would a 48-hour follow-up standard require us to change about our current volunteer schedule?
  3. How comfortable are we that guests currently understand what happens to information they share?
  4. Who should be the named owner for guests expressing an urgent pastoral need?

Practice

Applied exercise — produces the Follow-Up Sequence Standards with owners, timing and consent language.

Follow-Up Standards Design Session

Produce a written, differentiated follow-up standard that leadership can hand to every ministry team.

Estimated time: 40 minutes

Participants: Connections coordinator, care leader and volunteer leads in small groups

Artifact produced: Follow-Up Sequence Standards with owners, timing and consent language

Required inputs

  • • List of guest types encountered in the past year
  • • Current connection card or intake form
  • • Stewardship Nsites Connect follow-up pipeline view

Instructions

  1. List each guest type your church typically encounters.
  2. For each type, define the maximum acceptable timing window for first contact.
  3. Name the specific role responsible for that contact.
  4. Specify the method of contact, such as phone call, visit or written note.
  5. Draft consent and confidentiality language appropriate to each guest type.
  6. Identify how the team will track whether the timing window was met.
  7. Flag any guest type currently missing a defined owner.
Complete it online

Follow-Up Sequence Standards

  • Church name: ______________________
  • Date completed: ______________________
  • Facilitator: ______________________
Guest typeTiming windowOwnerContact methodConsent languageTracking method
      
      
      
      
      
      
      
      

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)

Continuing with the same illustrative congregation, this worked example shows Northgate's completed follow-up standards after identifying the ten-day delay in Lesson One.

Guest typeTiming windowOwnerContact methodConsent languageTracking method
First-time general guest48 hoursConnections coordinatorText message and handwritten note"We may follow up briefly to say hello; you're welcome to let us know if you'd rather not be contacted."Nsites Connect follow-up pipeline flag
Guest with prayer requestSame dayOn-call pastorPhone call"What you share is kept confidential between our pastoral team and used only to pray with and support you."Pastoral care log, reviewed daily
Guest in visible crisisSame day, before leaving campus if possibleCare ministry leaderIn-person conversation"We will only share this with the specific person helping you, and only with your permission."Care ministry direct handoff
Returning guest, second visit72 hoursConnections coordinatorPhone call inviting to newcomer coffee"We'd love to invite you to coffee; no pressure at all if now isn't the right time."Nsites Connect stage update
Guest invited by a member72 hoursInviting member plus connections coordinatorPersonal text from the inviting member"Feel free to loop us in only if you'd like more information."Manual check-in with inviting member

How this leadership team reasoned

  • • The team recognized that lumping all guests into one follow-up queue was the direct cause of the earlier three-week delay.
  • • They agreed urgent pastoral needs required same-day contact from a pastor, not a volunteer, to ensure appropriate care.
  • • They wrote consent language for every guest type so no one would feel surprised or exposed by follow-up contact.

Decisions recorded

  • • Route all prayer requests and visible crisis situations directly to pastoral staff same day, bypassing the general queue entirely.
  • • Use the Stewardship Nsites Connect follow-up pipeline as the single tracking point for the 48-and-72-hour windows.
  • • Review missed timing windows every Monday morning as a standing agenda item for the connections team.

Completed artifact extract — Follow-Up Sequence Standards with owners, timing and consent language

Northgate Community Church Follow-Up Sequence Standards: guests expressing a prayer request receive same-day contact from the on-call pastor by phone, with consent language read verbally confirming that information shared is kept confidential and used only for pastoral care and prayer...

Illustrative exercise score: 17 of 20. The standards clearly differentiated guest types with specific owners and timing, and consent language was thoughtfully written, though the tracking method for member-invited guests still relies on a manual step that could be made more consistent.

Score

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

Criterion0 — not evident3 — acceptable5 — exemplarySample
Completeness (0–5)No guest types, timing windows or owners are defined.Some guest types are covered but timing, owner or method is missing for others.Every guest type has a timing window, owner, contact method and consent language.4
Use of evidence (0–5)Standards are invented with no reference to prior follow-up experience or data.Some reference to past experience is made but timing choices are not justified.Standards are directly built from the specific delay and case identified in the church's own history.5
Alignment to the module purpose (0–5)The follow-up standards do not connect to the broader visitor-to-member pathway.Standards address initial contact but do not connect to later membership stages.Standards clearly build on the journey map from Lesson One and prepare guests for the orientation stage ahead.5
Actionability and ownership (0–5)No specific person or role is assigned to any follow-up step.Most steps have an owner but tracking or escalation is unclear.Every step has a named owner, a tracking method, and a clear escalation path for missed windows.4
Worked sample total18 / 20
  • Completeness: Nearly every guest type had a full standard, though the tracking method for member-invited guests was left partially manual.
  • Use of evidence: The standards were built explicitly around the three-week prayer-request delay that had actually occurred.
  • Alignment to the module purpose: Standards directly extended the journey map stages and pointed toward the newcomer coffee and orientation invitation.
  • Actionability and ownership: Owners and a weekly review rhythm were clearly assigned, though the escalation path for a missed window was not fully specified.

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 Follow-Up Sequence Standards worksheet
  • • Draft consent language reviewed by pastoral leadership

Attach this evidence

  • Each guest type has a distinct timing window and owner
  • Consent language exists for at least sensitive guest types

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 Visitor-to-Member Pathway.

Artifact produced: Follow-Up Sequence Standards with owners, timing and consent language

Supplies the follow-up standards and consent language sections of the Visitor-to-Member Pathway.

Open the module deliverable assembly

Participant reflection and notes

If a guest shared something painful with us this week, can we honestly say they would trust how that information was handled?