무료

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

PT703E Church Planting: Theology and Practice

Lecture 6-3: Team Covenant and Shared Expectations

카드로 보기 (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

핵심만 먼저 보기 ↓

12분

A core team that has been honestly recruited still needs its expectations written down somewhere both sides can return to, because memory of a verbal conversation is not a reliable record once months have passed and circumstances have changed. A team covenant is a written document — not a legal contract, and not a substitute for the bylaws and governance documents this school's church administration course covers, but a plainer, more relational document — stating what the team members hold in common theologically, what they are committing to practically, and, just as importantly, how someone leaves the team well if the fit turns out not to be right. This lecture treats the covenant not as paperwork but as the place where a team's most important agreements are made explicit before pressure makes them hard to discuss honestly.

이 12분으로 얻는 것

  • State what a team covenant should contain: shared theological convictions, practical commitments, and an exit process, and explain why each of the three is necessary.
  • Connect Nehemiah 9:38 and 10:29's account of a returned community's own written, mutual commitment to the practice of a modern team covenant, naming both the parallel and its limits.
  • Explain why an exit process written into the covenant before anyone needs it protects the team member leaving as much as it protects the team that remains.
  • Identify at least one commitment that belongs in a team covenant's theological section and one that belongs in its practical section, and explain the difference between the two categories.

Yet for all this, we make a sure covenant, and write it; and our princes, our Levites, and our priests, seal it.

they joined with their brothers, their nobles, and entered into a curse, and into an oath, to walk in God's law, which was given by Moses the servant of God, and to observe and do all the commandments of Yahweh our Lord, and his ordinances and his statutes;

Nehemiah 9:38 (World English Bible)

Nehemiah 10:29 (WEB)

The returned community under Nehemiah is not forming a church plant's core team; they are a whole restored nation renewing obligations under Mosaic law after generations of exile and failure, and the scale, the theological weight of a covenant with God, and the historical particularity of that moment do not transfer directly to a document five or six people sign before a Sunday launch. What does transfer, carefully, is a narrower observation: this community, having just heard its own history of failure read aloud (the preceding chapters recount exactly how earlier generations broke faith), responds not merely with an emotional resolve to do better but with a specific, written, sealed document — put in a form that outlives the emotional intensity of the moment it was made in. A team covenant borrows that same instinct at a much smaller scale: an agreement made while everyone is enthusiastic and aligned is more durable, and more useful later, if it is written down rather than left as a shared feeling that each person remembers slightly differently six months on.

1. Why a covenant needs to be written, not assumed

A core team at the start of a plant typically shares a strong, felt sense of alignment — everyone wants the same thing, trusts the planter, and would likely describe their expectations of one another in fairly similar terms if asked. That felt alignment is real, and it is also unreliable as a long-term foundation, for a reason that has nothing to do with anyone's sincerity: unstated expectations tend to diverge quietly over time, and each person discovers the divergence only when it is tested by an actual disagreement, usually under some degree of stress. A written covenant does not prevent disagreement, but it gives the team something to return to that is not simply whoever's memory of the founding conversation happens to be most confidently recalled in the moment.

2. Theological convictions

The covenant's theological section states, in specific and checkable terms, what the team holds in common — not a full doctrinal statement duplicating a denomination's confession, but the convictions that actually bear on how this particular team will function together: agreement on the gospel itself, on the authority of Scripture, and on whatever specific doctrinal or practical questions are live enough in this team's own context to cause real division if left unstated (views on , on the roles of men and women in specific ministry functions, on baptism and church membership, will differ by tradition and do not need to be resolved by this lecture — but they do need to be named explicitly in the covenant of any specific team, because an unstated disagreement on one of these discovered mid-plant is far costlier than the same disagreement discovered and worked through at the covenant stage).

3. Practical commitments

The covenant's practical section states what each team member is actually committing to in concrete, measurable terms: expected time commitment (a specific number of hours, or a specific set of responsibilities, rather than "as much as needed"), an expectation regarding giving (whether the team commits to a specific level of financial participation in the plant, which many planting networks treat as a meaningful marker of buy-in), and an expectation of relational engagement — attendance at team meetings, participation in the life of the group beyond formal duties, a stated posture toward conflict (addressed directly and promptly rather than allowed to accumulate). None of these commitments needs to be extreme to be useful; the value is in their specificity, not their intensity. A vague commitment ("we'll all pitch in") produces exactly the kind of divergent, unstated expectation this section exists to prevent.

4. An exit process, agreed before it is needed

The most commonly missing piece of a team covenant, and the one this lecture emphasizes most, is a stated process for a team member to leave well if the fit is not right. Teams rarely discuss this at the founding stage, for an understandable reason — nobody wants to plan for failure while everyone is enthusiastic about the beginning — but the absence of a stated exit process has a real cost precisely when it is most needed: at the moment someone realizes, mid-plant, that they need to leave, with no agreed way to do so that does not feel like betrayal or failure. A covenant that states in advance, calmly and without anyone's personal situation attached to it yet, how a team member raises the question of leaving, how much notice is reasonable, and how the team will speak about the departure afterward (a genuine commitment to speak well of someone who leaves in good faith, rather than allowing the departure to become a source of gossip or resentment) protects the person leaving from having to invent a graceful exit under pressure, and protects the remaining team from a departure that becomes more damaging than it needed to be simply because nobody had thought about how to handle it well.

A team covenant, three sections Written before pressure makes it hard to discuss Theological Shared gospel conviction Authority of Scripture Live, context-specific doctrinal questions named explicitly, not assumed Practical Specific time commitment Giving expectation Relational engagement, meeting attendance, a stated posture on conflict Exit process How to raise leaving Reasonable notice A commitment to speak well of a good-faith departure Agreed before anyone needs it

핵심 요약

  • A team covenant is a plain, relational written document, not a legal contract and not a replacement for bylaws. It records agreements while the team is aligned.
  • Nehemiah 9:38 and 10:29 show a returned community making a written, sealed commitment. The parallel is the written form that outlasts feeling. The scale and weight are very different.
  • The theological section names shared convictions, including live questions like spiritual gifts, men's and women's roles, and baptism, which differ by tradition. Unstated disagreement costs more later.
  • The practical section sets specific time, giving and relational commitments. Vague promises like "we'll all pitch in" cause hidden divergence.
  • An exit process, agreed early, protects both the one who leaves and the team that stays.

Topic: Writing a team covenant covering theology, practical commitments and a way to leave well.

Remember: Felt alignment fades and memories differ, so write the agreements down early, including how someone may leave.

Caution: The covenant is not a legal contract or a full confession. Nehemiah's national covenant does not transfer directly to a small team. The lecture does not resolve disputed doctrinal questions.

One line to carry into ministry: Write down what you share, what each person commits to in specific terms, and how to leave well, before pressure arrives.

이 과목 요약 전체 보기 →

스스로 확인해 보세요

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

묵상 및 토론

  • Which of the three sections — theological, practical, or exit process — do you think your own tradition or context is most likely to skip, and why?
  • Nehemiah's community wrote and sealed their covenant after hearing their own history of failure read aloud. What is the equivalent moment for a church-planting team — is there a comparable occasion where writing things down matters more than usual?
  • Why might an exit process feel presumptuous or discouraging to write at the start of a plant, and how would you introduce the idea to a team without it landing that way?
  • Name one practical commitment (time, giving, or relational engagement) that you think is easy to leave vague, and state how you would make it specific instead.

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

다음 단계

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