FREE

Course certificates are free until March 31, 2027.

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

Lecture 5-1: The Guest's Posture: Serving Under Local Leadership

Contents 31
PT736E Short-Term Mission Teams: Planning, Sending and Following Up Honestly
Chapter 0 · Introduction: Sent, Welcomed, Accountable
  1. Lecture 0: Introduction: Sent, Welcomed, Accountable, and What This Course Does Not Teach
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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

Jump to the key points ↓

30 min

The team has landed. The planning, the training, the letters and the packing are finished, and the real thing begins. This is the moment when everything the course has said so far is tested by small things: who speaks first at the church door, who decides what time breakfast is, who answers when a stranger asks the visitor for money.

This lecture makes one argument: a guest serves under the leadership of the host, and the guest's first task is to learn. The trip belongs to the local church. The team does not run it, improve it or rescue it. A team that has trained well and wants to help can still take over, and it usually does so with good manners and good intentions, one small decision at a time.

This lecture applies the central claim of the course to the days on the ground. A short-term trip is a humble partnership, not a tour with a service stop. On the ground, humility is not a feeling. It is a set of habits: following the host's order, lowering the host's burden, passing requests to the host's leader, keeping promises small, and not giving the impression that all is well when it is not.

The lecture gives no safety, legal or security advice. Where it touches such matters, it names a category and sends you to your organisation's written rules, the host's leaders and the local law.

What these 30 minutes give you

  • Explain what it means to serve under local leadership, and describe three ways a well-meaning team takes over.
  • Name the costs a host bears in receiving a team, and list practical ways a team can lower them.
  • State the rule for personal requests, gifts and promises, and say why the answer goes through the host's leader.
  • Describe the boundaries a guest keeps in relationships and in contact after the trip.
  • Say how a team can avoid giving a false impression that all is well, and why learning comes first.

Into whatever house you enter, first say, ‘Peace be to this house.’ If a son of peace is there, your peace will rest on him; but if not, it will return to you. Remain in that same house, eating and drinking the things they give, for the laborer is worthy of his wages. Don’t go from house to house. Into whatever city you enter, and they receive you, eat the things that are set before you." — Luke 10:5-8

World English Bible

In love of the brothers be tenderly affectionate one to another; in honor preferring one another;" — Romans 12:10

WEB

doing nothing through rivalry or through conceit, but in humility, each counting others better than himself; each of you not just looking to his own things, but each of you also to the things of others." — Philippians 2:3-4

WEB

Luke 10 describes workers sent out and told how to be guests: begin with peace, stay in the house that receives you, eat what is set before you. We take from it a narrow point. The guest here is not the manager of the place. The guest receives, and the household decides. Romans and Philippians give the attitude behind the habits: honour one another first, and look to the things of others. Scripture does not describe a "short-term team" with a schedule. These verses are about the manner of a guest, and we use them for that.

1. A guest is first of all received

Lecture 1-1 said that a guest is first of all received. That sentence carries a good deal of weight on the ground. The host has opened a door, a schedule, a kitchen and a church. The guest enters something that already belongs to someone.

So the first habit is to ask before acting. Where do we sit? Who greets us? What do you want us to do first? Is there anything we should not do in this place? The team that arrives with a full plan and an urge to begin has already answered, in its own mind, questions that belong to the host.

Three small pictures show the difference.

A team that arrives as a visitor to someone's home asks where to put its bags, takes the host's greeting first and waits to be shown the day.

A team that arrives as a staff looks round, decides where the work is needed, divides itself into groups and begins.

A team that arrives as an audience waits to be entertained and shown the interesting parts.

The first is a guest. The second has taken over. The third has turned the host into a stage. None of the three need be unkind. All three can be corrected by the same question: whose day is this?

2. How a good team takes over

Here are three ways a team takes over without meaning to. We name them so that a team can see them early.

It fills the silence. In many places a host will not say no to a guest. The host may say "it is possible", "perhaps", or nothing at all, and mean something quite different. A team that hears no objection takes it as agreement. Lecture 1-3 spoke of this: where the guest holds the money, honest answers become harder to give. On the ground, the team's task is to make a no easy to say. Ask "Is there a better way to do this?" and "What would you prefer?" and leave room for an answer that costs the host nothing.

It repairs what it was not asked to repair. A leaking tap, an untidy store, a Sunday programme that seems disorganised to a visitor. The team has skills and sees a need. But a kind of help that was not asked for tells the host that he did not see his own house. The team may mention what it noticed, privately and politely, to the host leader, and then leave the decision with him.

It makes itself the centre of the programme. A team can arrive with a performance, a testimony slot, a children's programme and a set of gifts, and the host's own congregation becomes the audience. The host's pastor has a Sunday to lead. A team that takes the pulpit unasked has used the host's people as a stage.

(An invented example.) A team from Lindenmoor Chapel, led by Tamsin Okoro, arrived in the town of Brae Narrow to stay for some days with Hollin Street Church. Tamsin had trained her team well. They had read the agreement, learned some local words and promised each other to listen. On the second morning one of the team, an experienced primary-school teacher named Rudo, saw that the church's Sunday-school room was cluttered and had no shelf for the children's books. By noon she had asked two of the team, cleared the room and built a shelf from wood she had found in the yard.

The church's Sunday-school leader, Mrs Adaeze Veli, came in the afternoon and said nothing for a while. Then she said, "Thank you. The wood was for the new door." She was not angry. The books had been kept in a certain order that the children knew. The clutter was the system. The shelf was a good shelf and in the wrong place, and the door would now have to wait for wood that the church had not planned to buy.

Rudo was upset and wanted to put it right. Tamsin told her to say "I am sorry" and then ask Mrs Veli what she would like done, and to do that. Mrs Veli asked for the room to be put back as it had been, except for the shelf, which she kept. Later she told the pastor, "She meant well. It would have been easier if she had asked."

Look at it from each side. From the team member's side, a need was visible and her skill was ready, and waiting felt like a waste of a short visit. From the host's side, a room was being managed in a way the visitor could not see, and a gift of work arrived with a cost: the wood and the order. From the leader's side, the training had been good, and it had still not reached a person's hands at nine on a Tuesday morning. Nobody was careless. The habit of asking had not yet become a habit.

3. Learning is the first task

A guest who arrives to serve may be surprised to hear that the first task is to learn. But the reasons are practical. The host knows the people, the roads, the quarrels, the history and the season. The team knows very little of it. A team that spends the first days looking, asking and listening will do less harm in the days that follow.

Here is a small example of listening before acting, as a short exchange.

Before: "We saw the clinic waiting room is crowded. We could set up a system with numbered tickets."

After: "We saw the waiting room is crowded. Is that a problem for you? Is there anything you already tried?"

The second sentence costs nothing and may save the team from repeating an experiment the clinic abandoned last year.

The team learns in more than one way. It learns by asking its host leader. It learns from the interpreters, who often see the team more clearly than the team sees itself. It learns from the families who receive it, from the children, and from the ordinary Sunday. And it learns by noticing what it does not understand, and saying so.

4. What the host carries

Receiving a team is work. The host gives time: meetings, travel, explanation, a place to sleep, meals, a programme. The host gives people: an interpreter who has taken time off work, a cook, a driver, a pastor who sits through a long meeting. The host gives risk too: a team that misjudges something may leave the local church to answer for it after the visitors have gone.

We do not say that hosts resent this. Many hosts receive teams gladly, and some hold that visitors bring encouragement and friendship that they could not otherwise have. We say only that the cost is real and belongs to someone, and that a team should not assume it costs nothing.

Practical ways a team can lower the burden include:

  • Arriving when it said it would, and leaving when it said it would.
  • Keeping its own needs plain and few. If the team has dietary needs or other needs, it says so before arriving, in writing, and does not add new ones on the way.
  • Asking what is a help and what is a burden, and believing the answer.
  • Paying what was agreed to pay, on time, without making it a favour.
  • Thanking the pastor, the interpreters, the cook, the driver and the families who gave a bed, by name and in person, and in writing afterwards. Thanks should go to the people who carried the cost and not only to the one at the top.
  • Taking care of its own washing up, cleaning, rubbish, noise and timekeeping.
  • Treating the interpreters as colleagues, not as equipment. An interpreter is tired at the end of a day of speaking in two languages. Give breaks, check that you are not speaking too fast, and ask what the interpreter thinks was understood.

This is not a matter of manners alone. A host who has to manage the team's needs is a host who has less strength for his own work.

From the host's side, a pastor might put it this way: "A team that comes and asks 'What can we carry for you?' is a gift. A team that comes and asks 'What can we do for you?' sometimes gives me a second job: finding something for them to do." Hosts differ. Some enjoy the bustle and some are tired by it. The only way to know is to ask.

5. Gifts, money and personal requests

On the ground the team is asked for things. A person at the church door asks for help with school fees. A child asks for a pen. A family says that their roof leaks. A man says that he needs a loan until the end of the month. A woman asks the team member to carry a letter, a parcel or a message home. The team member is touched and the sum asked seems small.

The rule is simple and hard to keep: any personal request is passed to the host's leader before any answer is given. The team member says: "Thank you for telling me. I am a guest here. I will speak to Pastor ___, and he will tell you what is possible." Then the team member does so.

The reasons are not hard-hearted. First, the host leader knows the person and the situation, and may know that the story is true, or that it is more complicated, or that help is already coming from another place. Second, a gift from a guest to one person can start a quarrel in a family or a congregation, and the host will live with the quarrel. Third, giving directly teaches the people nearby that the guest is a source of money. The next team will meet the same request, and the host will have to hold the line that a visitor wished to cross. Fourth, a promise made in a moment of feeling can rarely be kept from a distance, and an unkept promise is a debt that the host collects.

Where the team has money that it intends to give, it is agreed with the host in advance, in writing, and given through the host leader (lecture 2-1; lecture 4-1). A team does not carry cash for unplanned giving. This is not advice about money. It is a courtesy about whose community this is.

The same applies to promises. "We will send you a laptop." "We will come back next year and build it." "We will pay for his studies." Before the team says any such thing, it must ask whether it has the authority to promise it, whether it can keep it, and whether the host leader knows and agrees. When in doubt, the words are: "I would like to help. I cannot promise. I will speak to our leader and to yours." A modest promise kept is worth more than a generous one broken.

And the same applies to gifts and souvenirs. Gifts to the host church are agreed with the host. Gifts to individual children are not made at all (lecture 3-4). A team that scatters sweets, toys or pens from a vehicle or at a church door has taught children to run to visitors, and has taught the adults something they may not like.

From the sender's side, a congregation at home may have asked the team to "bless" a family it has heard about. The honest answer is that the team can carry the congregation's wish to the host leader, and that the host leader decides whether and how it is done.

6. Boundaries in relationships

A short trip makes intense friendships. People eat together, share a language that is partly gesture and laugh a good deal. Some of it is a real beginning of a long friendship, and that is a good thing. Some of it is not what it seems.

Several boundaries are worth keeping, and all of them should be stated in the team's code of conduct before the trip (lecture 3-2).

Romance. A romantic relationship between a team member and a local person, begun during a short visit, often involves a great inequality of power: the guest can leave, may hold money, and may be thought to hold a visa, a future or a way out. Many teams therefore hold that romantic and sexual relationships with local people are not begun during the trip. If a real attachment arises, it is brought to the team leader and the host leader, and it waits, and it is not pursued in secret. The code of conduct says so in advance.

Private contact. A team member does not arrange private meetings, outings or messaging with a local young person, and never with a child (lecture 3-4). Adults of the host church may also be put in an awkward place if a guest asks them for a private favour.

Ongoing contact after the trip. Many team members wish to keep in touch with the people they met. That is usually good. But contact has a cost to someone. A steady flow of messages, requests or promises can be a burden on the host and on the person, who may feel unable to refuse. Contact is best open, shared with the host leader, and given with a plain mind about what it can and cannot become. Messages to children are not private, and not at all unless the organisation's rules and the child's parents allow it.

The team's own relationships. Within the team, the same honesty applies. Friendships and attractions within a team are ordinary. They are handled by the code and the leader and are not hidden.

7. Local believers who may be at risk

In some places, to be a Christian or to be seen with Christians carries a cost. A visitor who comes, takes pictures, speaks loudly in public, posts online or gives out printed material may put a local believer in danger that the visitor never sees and never pays for.

This lecture gives no security advice. The principle is simple. The host decides what is safe to say, show and share, and the guest follows. Ask the host leader what the team should and should not do in public, which names and places it should never mention, and which pictures should never be taken. Do not ask the host to explain the reason if the host would prefer not to. Lecture 4-3 takes up photographs and posts. Do not publish the names, faces or places of local believers or workers without their free consent, and when in doubt, do not publish.

Do not teach methods of concealment, and do not suggest ways round the law. If the host wishes to take a precaution, the host's way is the way.

8. Not creating the impression that all is well

A team arrives for a short time, is shown the best of the place, and goes home. Everyone is polite. The host is warm. Some things go badly and nobody says so. The leader of the team may notice a tension between the pastor and a , a shortage the host hides, or a project that is not working. The team writes home that all went well.

The pressure to say "all is well" comes from several sides, and each deserves understanding. The host may not wish to look weak before a partner whose money matters. The team may not wish to cause trouble or to seem ungrateful. The congregation at home wants good news, and the leader wishes to give it.

But a trip that creates the impression that all is well when it is not has several costs. It deceives the senders. It hides a need the host might want help with. And it makes the next trip harder, because the real difficulty has not been named.

The honest course is quieter than it sounds. Notice, ask, and do not report what you were not told. If something troubles you, you may say to the host leader, privately and kindly, "I noticed this. Is it something you would like to talk about?" If the host says no, you accept it. You do not report the tension to the home church as a fact. You report what you saw and what the host said, no more. Lecture 4-4 shows how reports are written without inflating or exposing.

9. Putting it together: a short check for each day

A team may find it helpful to ask five questions at the end of each day, together, aloud.

  1. Whose plan did we follow today?
  2. What did we receive, and from whom? Did we thank them?
  3. Did we take any request, gift or promise? Was it passed to the host leader?
  4. Did anyone cross a line in the code, even slightly? Who will raise it?
  5. What did we learn that we did not know yesterday?

These are not a test. They are a way of keeping the habits alive on a tiring day.


Diagram 1. Whose day is this? The guest's posture in six habits

The Guest's Posture: Serving Under Local Leadership The host leads. The guest learns first. Not safety or legal advice. 1. Ask before acting Where do we sit? What first? Make a no easy to say. Whose day is this? 2. Lower the host's load Few needs, on time, paid as agreed. Thank cook, driver, interpreter, families, by name. 3. Requests go to the host Money, gifts, favours, promises: "I will speak to Pastor ___." No answer before that. 4. Keep relationships clear No private contact with children. Attachments go to both leaders. Contact after the trip is open. 5. Protect local believers The host says what is safe to say, show and share. When in doubt, do not publish. 6. Report what you saw Do not say "all is well" unless it is. Do not report what you were not told. How a good team takes over without meaning to It fills the silence: it hears no objection and takes it as yes. It repairs what it was not asked to repair, and tells the host he did not see his own house. It makes itself the centre: the host's people become the audience. Each is corrected by one question: whose day is this?

In short

  • A guest is received first. The host leads, and the team's first task is to ask and to learn.
  • A good team can take over by filling silence, repairing what it was not asked to repair, or making itself the centre.
  • Receiving a team costs the host time, people and risk. A team can lower the cost by plain habits.
  • Personal requests, gifts and promises go to the host's leader before any answer is given.
  • Relationships keep clear boundaries; local believers are protected by what the host says is safe.
  • Do not say "all is well" when it is not; report what you saw, not what you were not told.
Front Back
"Whose day is this?" The question that tests whether a team is following the host or taking over.
A personal request from a local person Do not answer. Say you will speak to the host's leader, and then do so.
What a host carries Time, people and risk. A team lowers it by being on time, few in needs and generous with thanks to those who carry the cost.
Not creating the impression that all is well Notice, ask, and report what you saw. Do not report what you were not told.

One sentence to remember A guest serves under the host's leadership, learns first, and sends every request to the one who lives with the answer.

This week's action Write down one thing you tend to decide on your own when you are a guest, and plan the question you could ask first next time.

Review every summary in this course →

Check yourself

Not "did you read it" but "can you explain it". Ticks are kept on this device only.

Reflection and discussion

  • In the story of the shelf, what did Rudo see, and what did she not see? What did Mrs Veli know that nobody had asked about?
  • Why might a host say "it is possible" when he means "please do not"? What can a team do to make a no easy to say?
  • Why does the rule send every personal request to the host's leader? Say it once from the team member's side, once from the host's side.
  • Which costs of receiving a team would be easiest for a visitor to overlook? Who bears them?
  • Where might a team be tempted to write "all went well" when it was not true? What would a more honest sentence be?
  • If you host visitors, what is the one thing you would most like a team to ask before it begins?

Sign in to write and keep your answers

What next

The lecture ends here. What follows was written by its readers.