무료

수료증 무료 발급 — 2027년 3월 31일까지.

PT703E Church Planting: Theology and Practice

Lecture 9-4: Setting a Realistic Launch Date and Readiness Criteria

카드로 보기 (3분)
목차 53
PT703E Church Planting: Theology and Practice
제 0 장 · Introduction: The God Who Calls Things That Are Not
  1. Introduction: The God Who Calls Things That Are Not
제 1 장 · Chapter 1: Foundations — Missio Dei and the Theology of Church Planting
  1. Lecture 1-1: Missio Dei — Mission Belongs to the Sending God
  2. Lecture 1-2: Church Planting as the New Testament's Ordinary Pattern
  3. Lecture 1-3: Calling the Things That Are Not — A Theology of Apparent Nothing
  4. Lecture 1-4: What Makes a Plant a Church — Ecclesiology for Planters
제 2 장 · Chapter 2: Biblical Models — Antioch, Paul's Journeys, and the Apostolic Band
  1. Lecture 2-1: The Antioch Pattern — From Scattered to Sending
  2. Lecture 2-2: Did Paul Have a Strategy? Reading Acts Honestly
  3. Lecture 2-3: The Apostolic Band — A Team, Not a Solo Act
  4. Lecture 2-4: When Planting Partners Fall Out — Paul and Barnabas
  5. Lecture 2-5: What This Chapter's Evidence Does Not Settle
제 3 장 · Chapter 3: Discerning the Call and Assessing a Planter
  1. Lecture 3-1: The Theology of Calling
  2. Lecture 3-2: Assessment — What a Serious Process Actually Looks For
  3. Lecture 3-3: Named Failure Patterns
  4. Lecture 3-4: The Sending Church's and Assessor's Own Responsibility
제 4 장 · Chapter 4: Reading a Context — Exegeting a Community Before Planting
  1. Lecture 4-1: Demographic and Needs Analysis
  2. Lecture 4-2: Reading Receptivity and Existing Gospel Presence
  3. Lecture 4-3: Cultural and Spiritual Exegesis
  4. Lecture 4-4: Prayer-Walking and Spiritual Preparation
제 5 장 · Chapter 5: Models and Strategies of Church Planting
  1. Lecture 5-1: The Parent-Child Model
  2. Lecture 5-2: Networks and Denominational Planting
  3. Lecture 5-3: Organic and House-Church Multiplication
  4. Lecture 5-4: Bivocational Versus Fully Funded Planting
  5. Lecture 5-5: Choosing a Model Responsibly
제 6 장 · Chapter 6: Building a Core Team and Launch Team
  1. Lecture 6-1: Defining Roles Before Recruiting People
  2. Lecture 6-2: Recruiting a Core Team
  3. Lecture 6-3: Team Covenant and Shared Expectations
  4. Lecture 6-4: Team Health and Conflict in the Early, High-Pressure Season
제 7 장 · Chapter 7: Funding, Budgeting, and Sustainability
  1. Lecture 7-1: Funding Sources Compared
  2. Lecture 7-2: Building a Launch Budget
  3. Lecture 7-3: The Path to Self-Sustainability
  4. Lecture 7-4: Financial Integrity from Day One
제 8 장 · Chapter 8: Contextualization Across Culture
  1. Lecture 8-1: Urban Church Planting
  2. Lecture 8-2: Rural and Small-Town Church Planting
  3. Lecture 8-3: Cross-Cultural and Immigrant-Context Planting
  4. Lecture 8-4: Generational and Subcultural Contextualization
제 9 장 · Chapter 9: Pre-Launch — Evangelism, Prayer, and Preview Gatherings
  1. Lecture 9-1: Relational Evangelism — One Relationship at a Time
  2. Lecture 9-2: Sustained Prayer as Pre-Launch Infrastructure
  3. Lecture 9-3: Preview Gatherings — Rehearsing Before the Real Thing
  4. Lecture 9-4: Setting a Realistic Launch Date and Readiness Criteria
제 10 장 · Chapter 10: Launch and Early Assimilation
  1. Lecture 10-1: Designing a First Public Gathering
  2. Lecture 10-2: Preaching and Teaching in a Launch Season
  3. Lecture 10-3: First-Time Guest Follow-Up and Assimilation Pathways
  4. Lecture 10-4: Baptism, Membership, and Belonging in a New Congregation
  5. Lecture 10-5: Sustaining Momentum After the Initial Launch Excitement Fades
제 11 장 · Chapter 11: Leadership Development and Reproducing DNA
  1. Lecture 11-1: Identifying and Developing Emerging Leaders Early
  2. Lecture 11-2: Raising Up Elders in a Young Congregation — Too Fast, Too Slow
  3. Lecture 11-3: Defining and Transmitting a Plant's Theological and Missional DNA
  4. Lecture 11-4: Planning for the Plant's Own Future Multiplication
제 12 장 · Chapter 12: The Multiplication Debate, Sustainability, and a Capstone
  1. Lecture 12-1: The Church-Planting-Movements Debate — Speed and Depth
  2. Lecture 12-2: Denominational Oversight and Independent Autonomy
  3. Lecture 12-3: Planting in Persecution and Restricted-Access Contexts
  4. Lecture 12-4: Sustainability and Burnout Specific to Church Planting
  5. Lecture 12-5: Capstone — A Personal Theology and Strategy of Church Planting

핵심만 먼저 보기 ↓

16분

A launch date is, in one sense, only a date on a calendar — but it functions, in the life of a pre-launch plant, as something closer to a promise made publicly to a growing circle of relationships, a prayer team, and a launch team's own sense of forward motion. Once announced, it is genuinely costly to move, in both practical and relational terms, and this lecture argues that a plant should set that date against concrete, operational readiness markers rather than against a symbolically appealing calendar date (a New Year, an anniversary, a season's first Sunday) chosen mainly because it sounds meaningful. The two are not automatically opposed — a symbolically appealing date that also happens to align with genuine readiness is simply a good date — but this lecture insists on readiness as the deciding factor, with symbolic appeal treated as a welcome coincidence rather than a justification on its own.

This lecture closes this chapter for a reason worth stating explicitly: everything the chapter's first three lectures covered — relational evangelism building genuine trust, sustained prayer infrastructure, and preview gatherings testing logistics and gathering feedback — feeds directly into the readiness assessment this lecture describes. A plant cannot honestly evaluate its own readiness to launch without having already done that earlier work; this lecture is not a fourth, separate topic so much as the point where the chapter's other three converge into an actual decision.

이 16분으로 얻는 것

  • Name at least four concrete readiness markers (a functioning core team, a workable and secured meeting space, basic children's ministry safety practices if the plant will serve children, a clear and rehearsed first-service plan) that this lecture argues should determine a launch date, rather than a symbolically appealing calendar date alone.
  • Explain why launching on a symbolic date without operational readiness is a specific, nameable mistake, distinct from simply being cautious about launch timing in general.
  • Describe how this chapter's first three lectures (relational evangelism, sustained prayer, preview gatherings) feed directly into the readiness assessment this lecture describes.
  • State what Nehemiah 6:15-16 shows about the relationship between a finished, verifiable piece of work and the recognition that follows it, and connect that to a plant's own readiness-first approach to setting a date.

So the wall was finished in the twenty-fifth day of Elul, in fifty-two days. When all our enemies heard of it, all the nations that were around us were afraid, and were much cast down in their own eyes; for they perceived that this work was worked of our God.

Nehemiah 6:15-16 (World English Bible)

Nehemiah's wall-building project is bracketed by two kinds of pressure this lecture's own subject shares: real urgency (the exposed, vulnerable state of an unwalled Jerusalem, and genuine external opposition working to delay or derail the project throughout the preceding chapters) and the temptation that urgency creates to declare victory before the work is actually finished. The text does not record Nehemiah announcing completion on a symbolically appealing date chosen in advance; it records an actual, specific, verifiable completion date — the twenty-fifth of Elul, fifty-two days after the work began — arrived at because the wall was, as a plain matter of fact, finished. The recognition that follows in the next verse is significant for this lecture's purposes: the surrounding nations were not moved by an announcement or an event staged around a chosen date; they were moved because they could see, concretely, that a real wall now stood where none had stood before, and they drew a theological conclusion from that verifiable fact ("this work was worked of our God") rather than from any rhetoric surrounding it. A plant that launches on a date chosen for readiness, once readiness is actually, verifiably present, has something considerably more durable to offer a first-time visitor than a plant that launches on a symbolically appealing date and hopes the readiness catches up afterward.

1. Naming concrete readiness markers

This lecture treats readiness as a checklist of specific, largely verifiable conditions rather than a feeling a planter eventually arrives at. A functioning core team — not merely a list of names willing to help, but a team that has actually worked together through at least one preview gathering (Lecture 9-3) and demonstrated it can execute a plan under real conditions — is the first marker, because a launch date set before a team has been tested together asks that team to have its first real test in front of a public, first-time audience, which is a considerably higher-stakes place to discover a gap than a preview gathering is. A workable and secured meeting space — not a verbal understanding that a space "should" be available, but an actual, confirmed arrangement with known capacity, known access constraints, and a known cost — is the second marker, because meeting-space failures are among the most visible and hardest to recover from on an actual launch day. Basic children's ministry safety practices, where a plant intends to serve children at all — background checks completed for anyone working with children, a two-adult policy or equivalent safeguard in place, a clear check-in and pickup procedure — form a third, non-negotiable marker; a plant should not launch a children's ministry component it has not yet made basically safe, regardless of how ready every other part of the plant may be. A clear, rehearsed first-service plan — not merely a general sense of the service's shape, but an actual order of service that the team has walked through, ideally during a preview gathering — is the fourth marker, because a first-time visitor's experience of a plant's very first public gathering carries disproportionate weight in whether that visitor returns.

A floor, not a list

These four are not offered as an exhaustive list for every context — a plant serving a specific population, or operating under specific legal or security constraints, may have additional non-negotiable markers this general list does not name — but they represent a floor below which this lecture argues a plant should not launch publicly, regardless of calendar pressure.

2. The specific mistake: a symbolic date without readiness

The mistake this lecture names is specific enough to be worth stating precisely, because it is easy to blur with ordinary caution about timing in general. The mistake is not "choosing a date that happens to have symbolic meaning" — a launch on a meaningful anniversary or a season's opening Sunday, chosen because the team was independently ready by that point, involves no error at all. The mistake is choosing a date primarily because of its symbolic appeal, and then treating the intervening time as pressure to become ready by that date regardless of what readiness assessment would otherwise indicate, so that the calendar, rather than the readiness markers named above, becomes the actual driver of the launch decision. A team in this position tends to experience a specific and recognizable pressure in its final weeks: known gaps (an unresolved children's ministry safeguard, a meeting space arrangement still not fully confirmed, a core team that has not yet run a genuinely successful preview) get minimized in internal conversation rather than named and addressed, because naming them honestly would mean admitting the chosen date cannot actually be met. This lecture argues that when a team notices itself doing this — talking itself out of taking a known gap seriously because the calendar has already been publicly announced — the gap, not the calendar, should govern the final decision, even at real relational and reputational cost to moving a date the team has already told people about.

3. How this chapter's earlier lectures converge here

The readiness assessment this lecture describes is not a fifth, independent input; it draws directly on work this chapter has already covered. (Lecture 9-1) has, by this point, either produced a genuine circle of relationally invested contacts who would actually show up to a launch, or it has not, and a launch date set without an honest accounting of which is true is set on incomplete information. Sustained prayer infrastructure (Lecture 9-2) has, over the preceding months, either become a durable team practice that will continue past launch day, or it has remained sporadic, and a team should be honest with itself about which. Preview gatherings (Lecture 9-3) have either surfaced and resolved the practical problems a first public service would otherwise reveal for the first time, or the team has avoided holding one, or held one and not seriously debriefed it — and in either of those latter cases, readiness has not actually been tested, only assumed. Setting a launch date, in other words, is less a fifth task to complete than an honest audit of whether the first three have actually been done, and done well, rather than merely attempted.

4. A caution for varied contexts

This lecture's four readiness markers assume, in their most straightforward form, a context with reasonably stable access to a physical meeting space and predictable planning conditions. A bivocational planter juggling full-time outside employment, a rural plant drawing a launch team from a wider and more dispersed geographic area, or a plant operating under genuine security constraints in a restricted-access context may need considerably more time to meet the same four markers than a fully funded, urban, open-context plant would — and this lecture does not intend "readiness" to mean "readiness on the timeline a well-resourced plant elsewhere achieved it." The content of readiness (a tested team, a secured space, basic child safety, a rehearsed plan) holds across these contexts; the pace at which a specific plant can honestly meet it will vary, sometimes considerably, and a planter comparing their own timeline unfavorably against a different context's pace is making an unfair comparison rather than an honest readiness assessment.

Readiness sets the date, not the reverse Four concrete markers, drawn from this chapter's earlier lectures Tested core team Proven through a real preview (9-3), not just willing names Secured space Confirmed, not a verbal "should be available" Child safety basics Checks, two-adult rule, check-in — non-negotiable Rehearsed plan Walked through in a preview, not just described in a meeting The launch date decision The mistake this lecture names A symbolically appealing date chosen first, with known gaps minimized afterward to meet it.

핵심 요약

  • A launch date works like a public promise and is costly to move. Set it by concrete readiness, not by a symbolic date that merely sounds meaningful.
  • Four markers set a floor: a core team tested in a preview, a confirmed meeting space, basic child safety practices, and a rehearsed first-service plan. Some contexts may need more.
  • The mistake is choosing a date for its symbolic appeal and then minimizing known gaps to meet it. A symbolic date that matches real readiness is fine.
  • The readiness check is an audit of lectures 9-1 to 9-3: relationships built, prayer sustained, previews held and debriefed.
  • Nehemiah 6:15-16 shows recognition following a wall that was actually finished. Bivocational, rural or restricted plants may need more time, and that is not failure.

Topic: How to set a church plant's launch date by operational readiness markers rather than by a symbolically attractive date.

Remember: Readiness sets the date, not the reverse. Check team, space, child safety and first-service plan, using what the earlier lectures of the chapter built.

Caution: The four markers are a floor, not a full list, and the pace of meeting them varies by context. The lecture does not call symbolic dates wrong when readiness is real.

One line to carry into ministry: When you catch yourself minimizing a known gap to keep an announced date, let the gap decide.

이 과목 요약 전체 보기 →

스스로 확인해 보세요

읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.

묵상 및 토론

  • Nehemiah's wall was finished on a specific, verifiable date because the work was actually done — the recognition in verse 16 followed the finished wall, not an announcement about it. What would it look like for your own launch to earn that same kind of "they could see it was real" recognition rather than relying on the appeal of the date itself?
  • Of this lecture's four readiness markers, which is your own launch team's weakest right now, honestly? What is the actual obstacle to strengthening it, and is that obstacle time, resources, or something the team has been avoiding naming?
  • This lecture distinguishes "a symbolic date that happens to align with readiness" from "a symbolic date pursued regardless of readiness." Can you recall or imagine a specific case where a team talked itself into believing the second was really the first?
  • The lecture argues readiness at this point is really an audit of whether Lectures 9-1 through 9-3 were actually done well. Walk back through this chapter's first three lectures for your own context — where is the audit likely to reveal a gap?
  • The lecture cautions that a bivocational, rural, or restricted-access plant may need considerably more time to meet the same four readiness markers than a well-resourced context would. How would you resist comparing your own plant's timeline unfavorably to a different context's pace?

로그인하시면 여기에 답을 적고 보관하실 수 있습니다

다음 단계

여기까지가 강의입니다. 아래는 읽은 사람들이 남긴 글입니다.