무료

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

PT736E Short-Term Mission Teams: Planning, Sending and Following Up Honestly

Lecture 2-1: Beginning With an Invitation

목차 31
PT736E Short-Term Mission Teams: Planning, Sending and Following Up Honestly
제 0 장 · Introduction: Sent, Welcomed, Accountable
  1. Lecture 0: Introduction: Sent, Welcomed, Accountable, and What This Course Does Not Teach
제 1 장 · Week 1: Sending and Welcoming: Why We Go and How We Argue About It
  1. Lecture 1-1: Sent and Welcomed: Scripture and the Long History of Going
  2. Lecture 1-2: The Honest Argument About Short-Term Trips
  3. Lecture 1-3: Whose Work Is It? Hosts, Guests, Power and Money
  4. Lecture 1-4: Kinds of Teams, Kinds of Trips
  5. Lecture 1-5: Practice Lab: Why We Want to Go
제 2 장 · Week 2: Planning With the Host
  1. Lecture 2-1: Beginning With an Invitation
  2. Lecture 2-2: Designing the Days: What a Visit Leaves Behind
  3. Lecture 2-3: Teams With Special Skills: Medical, Teaching, Building, Youth
  4. Lecture 2-4: Near Home and Far Away: Local Trips and Online Teams
  5. Lecture 2-5: Practice Lab: A Shared Plan With the Host
제 3 장 · Week 3: Choosing, Preparing and Protecting the Team
  1. Lecture 3-1: Choosing the Team
  2. Lecture 3-2: Training the Guests
  3. Lecture 3-3: Health, Safety and Documents: Preparing Without Giving Advice
  4. Lecture 3-4: Safeguarding Children and Vulnerable People
  5. Lecture 3-5: Practice Lab: A Code of Conduct
제 4 장 · Week 4: Money, Words and Pictures
  1. Lecture 4-1: What a Trip Costs and What It Is Worth
  2. Lecture 4-2: Raising Support Honestly
  3. Lecture 4-3: Photographs, Stories and Social Media
  4. Lecture 4-4: Reports and Testimonies That Tell the Truth
  5. Lecture 4-5: Practice Lab: Checking a Fundraising Letter and a Post
제 5 장 · Week 5: On the Ground and When Things Go Wrong
  1. Lecture 5-1: The Guest's Posture: Serving Under Local Leadership
  2. Lecture 5-2: Planning for Crisis and for Withdrawal
  3. Lecture 5-3: Team Conflict, Tiredness and Spiritual Care
  4. Lecture 5-4: When Harm Has Happened: Honest Reporting and Accountability
  5. Lecture 5-5: Practice Lab: A Crisis Scenario
제 6 장 · Week 6: Coming Home and What Remains
  1. Lecture 6-1: The First Days Home: Debriefing and Hearing the Host
  2. Lecture 6-2: What Remains: Continuing, Changing or Ending a Partnership
  3. Lecture 6-3: Calling, Discernment and the Ones Who Stay Home
  4. Lecture 6-4: Judging the Programme: Evaluation With Humility
  5. Lecture 6-5: Practice Lab: A Statement of Principles for Our Church

핵심만 먼저 보기 ↓

27분

Most short-term trips begin in the wrong place. They begin with a team. Someone in a sending community feels a desire to go, a date is chosen, people sign up, and only then does somebody ask, "Where shall we go, and who will have us?" By that time a good deal has been promised to the team, and very little has been asked of the host.

This lecture turns the order round. A trip is planned with the host, not for the host, and a trip begins with an invitation, not with a team. An invitation is not a form. It is the end of a conversation, and the conversation usually starts long before anyone buys a ticket.

This is the first lecture of the chapter on planning, and it serves the course's central claim. A short-term trip is a humble partnership: guests who serve and learn under the leadership of a local church. If that is true, the first act of the partnership must be the host's free "yes". The claim closes two doors. If the trip is an experience for the traveller, the host's "yes" is only a permission slip. If the host is a stage or a project, the host's "no" is a nuisance. In both cases the host cannot really answer.

The lecture does not say that guests may never have an idea, or that every good idea must come from the host. It does not say that a written agreement makes a partnership safe. It says that nothing begins without a free yes, that the host may say no, or later, or smaller, without paying for it, and that the agreement, when there is one, is a help to memory and not a substitute for trust.

This lecture gives no legal advice. Where an agreement touches law, tax, insurance or permissions, ask a qualified person and the organisations concerned.

이 27분으로 얻는 것

  • Describe how a partnership with a host begins, and why a relationship should come before a team.
  • Say what a visit to listen is for, and why a single visit is not enough to choose a partner.
  • List the matters a written understanding between guests and host should cover.
  • Explain what "a free yes" means, and how the host's right to say no, later or smaller can be made real.
  • State fairly two positions on whether guests may propose a project, and say what this course requires.
  • Say what an agreement is not.

Where there is no counsel, plans fail; but in a multitude of counselors they are established." — Proverbs 15:22

World English Bible

For which of you, desiring to build a tower, doesn’t first sit down and count the cost, to see if he has enough to complete it? Or perhaps, when he has laid a foundation, and is not able to finish, everyone who sees begins to mock him, saying, ‘This man began to build, and wasn’t able to finish.’" — Luke 14:28-30

WEB

But let your ‘Yes’ be ‘Yes’ and your ‘No’ be ‘No.’ Whatever is more than these is of the evil one." — Matthew 5:37

WEB

The proverb is about plans and the people who share in making them. We use it for one narrow point: a plan that only the planner has seen has not been tested. Jesus' picture of a builder who counts the cost has a host in it too, if we read it with a partnership in mind. The person who will live with the unfinished tower is seldom only the one who began it. In the third passage, plain speech is plain speech: a "yes" that cannot be told from a "no" helps nobody. Hosts and guests both need this.

1. The order of things

Here is the order in which a trip is often planned, and the order in which it should be planned.

The common order: a desire to go, a team, a date, a search for a place that will receive us, a proposal to the host, a reply, a trip. The host is the last to hear and the first to be asked to adjust.

The better order: a relationship, a conversation, a visit to listen, a written understanding, a plan, a team chosen for that plan, a trip. In this order the host helps to shape the trip before it is a trip, and the team is formed for the host and not the host for the team.

The two orders may look the same on a calendar. They are not the same in power. In the first, the decisions are taken at home, and the host answers. In the second, the decisions are shared, and the host also asks.

2. How a partnership begins

A partnership begins with people who know each other. That sounds obvious, but it has practical results.

Through an existing network. Many congregations meet their hosts through something that already exists: a diocese or a religious order with houses in more than one place, a denomination, a partnership of churches, a school or university, an agency whose staff know local leaders, or a member of the congregation who was born in the place. Each way has a strength and a risk. A diocese or order brings trust and history, and may carry its own habits of who decides. An agency brings contacts and experience, and may stand between the guests and the host so that the two never really speak. A member who was born there brings knowledge, and may be asked to carry the whole relationship alone. The course does not rank these. It asks only: whose voice reaches the sending community, and whose voice reaches the host?

Through a person met. Sometimes a leader meets a pastor at a conference, or a nurse meets a clinic's director. This is a good beginning, and a fragile one. A friendship between two people is not yet a partnership between two communities. Ask early: who else knows about this on each side?

Through a request. Sometimes a host church writes first. It deserves a careful reply and not a quick yes. Ask what is being asked, who is asking, and what the writer's own congregation thinks.

In each case the first work is slow. People exchange letters, calls and news. They pray for each other by name. They learn who the leaders are and how decisions are made. A sending community that is in a hurry will find that the host is in no hurry at all, and has good reasons.

3. The visit to listen

Before a team goes, one or two people should go alone, or the host should visit the sending community, to listen. This visit is not an inspection and not a rehearsal. It has no programme to deliver and nothing to build. It asks questions such as these.

  • What is the church or community already doing, and what does it want to do?
  • What does it not want?
  • Who decides here? Who must be asked before anything is agreed?
  • What would a team cost you in time, food, space, translation and attention?
  • What has happened when teams came before? What would you like us to learn from that?
  • What would you want us to do if we found that we could not keep a promise?

A single visit is not enough to choose a partner, and it is not wise to decide after one. A visit shows the best of a place: the hosts prepare, the weather is fair, and nobody wishes to disappoint a guest. The visitor sees a few days. Take time. Visit again, or invite the host to visit. Let a season pass.

Here the host's side matters. A host pastor may have received many visitors. Some came with respect. Some came with a plan already in hand and asked for a signature. Some asked questions and never wrote back. A host who answers politely may be keeping his real opinion to himself, because he does not know whether this visitor will take a no kindly. That is not dishonesty. It is the ordinary result of unequal power, and the guests must go out of their way to make an honest answer easy.

4. Written expectations

When the two sides know each other well enough, it helps to write down what they expect. The writing need not be long, and it should not be written only by the guests. It should be in a language both sides read well, and both sides should have a copy.

The usual matters are these.

  1. Purpose. What is this trip for, in the host's words as well as the guests'?
  2. Roles. Who leads on the ground? Who does what? What is the team not to do?
  3. Dates and length. When, and for how long, and how flexible are they?
  4. Money. Who pays for what: travel, lodging, food, interpreters, materials, any gift? What does the host not have to pay for?
  5. Decisions. Who decides about the programme, and who decides if there is a disagreement?
  6. What is not asked of the host. For example: no special meals beyond what the family would eat, no gifts in return, no public thanks, no report to the sending church that the host has not seen.
  7. Pause or withdrawal. How may either side stop, delay or change the plan, and how will the other side be told? What will happen to the money already spent?
  8. After the trip. How will the host be heard, and what happens next?

Here is a short sample. It is invented and uses invented clauses, and it has no figures because figures belong to the people who sign.

A shared understanding (an invented example) Between the congregation of Alder Lane and the church of Salt Reach in the town of Orrin.

  1. The purpose of the visit is the one Pastor Tembo gave in his letter: to help paint and repair the church hall during the school holiday, and to learn from the church how it runs its evening classes for adults. Alder Lane has added one hope: that members may meet families in the congregation. Salt Reach may decline this.
  2. Salt Reach's building committee decides what is painted and in what order. Alder Lane's team leader answers to the committee while on site. Alder Lane will not begin any work that is not on the committee's list.
  3. The team will arrive on the date agreed and stay the number of days agreed. Salt Reach may shorten the stay at any time and will not be asked why.
  4. Alder Lane pays for the team's travel, lodging and meals, and for the paint and materials in the list. Alder Lane will not ask Salt Reach to pay for any item without agreeing it in writing first. Where possible, paint and tools are bought locally.
  5. Alder Lane's team will not take photographs of the congregation without the person's agreement, and will post none of children.
  6. Either church may pause or end the arrangement by telling the other in writing. Costs already agreed and spent are not asked back from Salt Reach.
  7. After the visit Pastor Tembo will write what he thinks went well and what did not. Alder Lane will read it before it says anything to its own congregation.

Notice what the sample does not contain. It does not say that Salt Reach is grateful. It does not make any promise about the next trip. It does not say what Alder Lane will achieve. Notice also that clause 3 and clause 6 give the host a way out that costs the host nothing. This is what "a free yes" means in practice: the yes is free because the no is free.

5. The host's right to say no, later or smaller

A host may say three things besides yes. No: we do not want a team. Later: not this year. Smaller: fewer people, shorter time, a different task. Each should be possible without a price.

The price is often not stated. It is understood. A host may fear that a no will end the friendship, stop the gift that supports the clinic, or lose a goodwill that took years to earn. Where money moves one way, the host has a good reason to say yes to everything. This is the imbalance of power that lecture 1-3 described. A guest cannot cancel it by saying "you are free to refuse", because the host may not believe it. The guest has to show it, over time:

  • by asking again and meaning the question, because a first yes may be politeness;
  • by naming a person on the host side who can speak for the congregation, so that the pastor does not have to carry a refusal alone;
  • by saying that a smaller plan is as welcome as a larger one, and keeping the promise when the plan is smaller;
  • by keeping any gift or support that was already promised, whatever the host decides about the team (lecture 6-2 returns to this).

6. This is a point where readers will not agree

This is a point where readers will not agree: whether guests should ever propose a project. One position holds that every project must begin with a local request. The reasons are strong. A project that the guests thought of, and for which the host then makes room, is a project owned by the guests. It will be supervised, reported on and funded by them, and when they stop it will stop. A host who says yes to a guest's idea may be saying it because the guest is a friend or a donor. Those who hold this position say: wait to be asked, and ask questions until you are.

A second position holds that a guest who has a skill may offer it, and that a host who is never offered anything is not better served. A nurse may know that a clinic could use a particular kind of training and may not be asked simply because the clinic does not know that it exists. A host may find it harder to ask for something it has never seen than to say yes or no to something placed in front of it. Those who hold this position say: offer, but plainly as an offer, and then be quiet.

This course requires less than either side asks for. It requires only this: nothing begins without the host's free yes, and the host can say no, or later, or smaller, without cost. Whether the first idea came from the host or from the guest is less important than whether the host was able to turn it down. Honest people may still differ about how a guest ought to raise an idea. A guest who is unsure should ask two people on the host side, separately, whether the idea is welcome.

7. Power, and choosing a partner

A guest from a church with more money, more people, or a larger travel budget holds power, even where nobody wants it. This is a fact about the arrangement. It is not a fact about a continent or a nation. A prosperous church in one region may host a visiting team from a smaller church in a richer city. A rural congregation may send a team to a large urban parish. In every case, ask: who can afford to say no?

Do not choose a partner after one visit. Do not choose the first host who says yes, and do not choose the host who is most welcoming, since a very warm welcome can be a sign of a host who cannot afford to disappoint you. Do not choose a host because the place makes a moving photograph. Choose because the church there has its own leaders, its own plans, its own accounts, and its own freedom to say what it needs. If a host cannot say no to you, say so aloud to the people who will go, and slow down.

8. What an agreement is not

An agreement is a help to memory. It is a way of saying, "this is what we understood," so that two good people who remember differently can look at the same page. It is not a substitute for trust. A partnership held together only by clauses will break when the first thing happens that no clause foresaw. A partnership with no written understanding at all depends on each side's memory and good will, and memories differ.

An agreement is not a contract in a legal sense unless people with legal training have written it as one, and a short plain understanding is not a replacement for any permission, licence or insurance that law or an organisation requires. Where those matter, find out in advance from the host country's and the organisation's own rules, write them down and keep them where they can be reached. This is not legal advice. Ask a qualified person.

An agreement is also not a weapon. It must not be used by the guests to say, "you promised," when the host's circumstances have changed. Equally it must not be used by the host as a cover for hiding what the guests need to know. Its purpose is to make the next conversation easier, and the first thing it should say is how the two sides will talk when something changes.

9. The same matter from three sides

From the sender's side, an invitation is a gift and a discipline. It is a gift because a host has opened a door. It is a discipline because it slows down the team's eagerness and forces the senders to ask what they would otherwise assume.

From the leader's and team member's side, the invitation defines the job. A team member who joins late may think the plan was made for the team's sake. The leader's task is to tell them honestly that the plan is the host's.

From the host's side, an invitation is a risk. The host takes on guests who need to be fed, housed, interpreted for and protected, and takes on the consequences for the congregation if the visit goes badly. A host may also have good reasons to welcome a team that have nothing to do with the team's plan: the visit may encourage a small congregation, or give its young people a hearing, or persuade the town council that the church is not alone. The host knows what the visit is for. A guest who asks, and then listens, will usually be told.


Diagram 1. Two orders of planning

Who Is Asked, and When The same seven steps, in two orders. The host's yes must be free. The common order: the host hears last A wish to go A team A date A place A proposal Host replies The trip Decisions are taken at home. The host is asked to adjust. A "yes" may only be a permission slip. The better order: the host shapes the plan Relationship Conversation Visit to listen Written terms A shared plan Team chosen The trip Decisions are shared. The host may say yes, no, later or smaller, at no cost. The team is formed for the plan, not the plan for the team.

핵심 요약

  • A trip is planned with the host, not for the host. It begins with a relationship and an invitation, not with a team.
  • A visit to listen has no programme to deliver. One visit is not enough to choose a partner.
  • A written understanding names purpose, roles, dates, money, decisions, what is not asked of the host, how either side may pause, and what happens afterwards.
  • Nothing begins without the host's free yes. The host may say no, later or smaller at no cost.
  • An agreement is a help to memory, not a substitute for trust. This lecture gives no legal advice.
Front Back
A free yes A yes is free only if the no is free: the host may say no, later or smaller without losing friendship or support.
The visit to listen One or two people go with no programme and ask what the host already does, wants, does not want, and what a team would cost.
What a written understanding covers Purpose, roles, dates, money, who decides, what is not asked of the host, how to pause, and what happens after.
What an agreement is not It is not a substitute for trust, a legal contract unless drawn as one, or a weapon against the host.

One sentence to remember A trip begins when a host freely says yes, and the yes is free only when the no costs nothing.

This week's action Write three questions you would ask a host on a visit to listen, and ask one trusted person whether any of them would be hard to answer honestly.

이 과목 요약 전체 보기 →

스스로 확인해 보세요

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

묵상 및 토론

  • Describe the common order of planning and the better order in your own words. Which is closer to what you have seen, and why?
  • What would a visit "to listen" ask that a visit "to inspect" would not? Write three questions you would take on such a visit.
  • In the sample understanding, which clause gives the host a way out at no cost? Why does that matter?
  • A host pastor says yes to everything you propose. List two possible reasons, one of them kind and one of them worrying. How would you find out which it is?
  • State, as fairly as you can, the case for "every project must begin with a local request" and the case for "a guest may offer". Where do you stand, and what does this course require whichever you choose?
  • What is the difference between an agreement that helps memory and an agreement that replaces trust?

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

다음 단계

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