Leading a Ministry Team Meeting

Give the meeting one clear purpose

Use this original IndiaPCG tool when a ministry team needs to make a practical decision, review a shared responsibility, or prepare an activity. It works best with a named chair, a person taking brief notes, and a purpose stated before people arrive. The suggested timings and forms are local planning aids. They do not establish a required PCG committee procedure.

Write the purpose as a question the team can answer today. For example: “How will we welcome visitors at next month’s service?” is clearer than “Discuss hospitality.” Send the question and any necessary information beforehand in a language and format participants can understand. A printed sheet or a short spoken explanation may be more useful than a crowded phone message.

Read the biblical example accurately

Read Acts 15:1 to 35 before preparing the meeting. Notice the disputed claim, the consideration of testimony and Scripture, the decision, and the communication sent to the people affected. The church does not merely announce that a difficult question has been discussed. It explains what has been decided and sends people who can communicate it. ¹

The passage addresses a foundational question about the inclusion of Gentiles. It does not prescribe a forty five minute agenda for every church team. Keep that difference clear. Reading a biblical scene in its actual argument protects us from treating a convenient detail as a universal rule. ³ Philippians 2:1 to 11 supplies a fitting attitude for ordinary work together: humility shaped by Christ rather than rivalry. ¹

Prepare the people and the information

Ask who needs to be present for the decision. Include the person who will carry out the work and someone who understands the needs of those it will affect. Confirm which decisions the team may make and which need pastoral or other authorized approval. Prepare actual costs, dates, and capacity where these matter. Do not turn an estimate into a promise.

PCG’s stated mission connects sharing Christ with a life that reflects him and with the Spirit’s empowering work. ² Begin with prayer in that spirit, then attend carefully to the information before you. Prayer and clear practical responsibility can belong together. An agenda helps a team make its service dependable; it does not measure spiritual power.

A forty five minute agenda

Give everyone the agenda at the beginning. Adjust it if the issue needs more time, but say what will change. The chair can use the following sequence without reading every instruction aloud.

1. Five minutes: welcome the team, pray, and read Philippians 2:3 and 4 in their paragraph.
2. Five minutes: state the decision question and confirm who has authority to approve the outcome.
3. Ten minutes: hear the relevant facts and the needs of the people affected.
4. Ten minutes: compare realistic options, their costs, and the available people.
5. Ten minutes: agree on the next action, its owner, the approval needed, and a date.
6. Five minutes: read the decision back, check understanding, and close in prayer.

Words for the chair

Open with: “Our purpose today is to decide ____________________. We can approve ____________________, and we will refer ____________________ to the responsible leader. We will hear the information, compare the options, and finish by naming the next action.” Keep this introduction short enough that people can remember it.

During discussion, ask: “What does the person doing this work need?” or “What information would change our decision?” When one person dominates, invite another voice courteously. If an unrelated issue arises, record it for a later conversation. Do not publicly diagnose someone’s motives or call an ordinary disagreement evidence of spiritual failure.

A decision record to copy

The record should be short enough to read at the end. It records the decision and its reasons, rather than every sentence spoken. Keep personal matters in the congregation’s appropriate private process.

1. Question considered: ____________________.
2. Decision or recommendation: ____________________.
3. Main reason and relevant information: ____________________.
4. Person responsible for the next action: ____________________.
5. Resources and approval required: ____________________.
6. Date for action and date for review: ____________________.
7. Who needs to be informed and who will inform them: ____________________.

A worked example for a welcome team

Imagine a congregation preparing to welcome visitors who speak a different local language. This is an illustrative example. The team hears from a bilingual volunteer and asks about the actual service flow. It chooses one achievable action: a named person will greet visitors and explain where interpretation is available. It does not promise full interpretation until the necessary people have agreed.

The record identifies the coordinator, the service date, the person providing the greeting, and when they will check the arrangement. The pastor approves any change affecting the service. The team then tells the volunteers what to do and whom to ask for help. A clear, modest decision can be implemented and reviewed.

Finish with an action people understand

Read the record aloud and ask each responsible person to confirm the task. If someone cannot accept it, revise the action while everyone is present. An empty name on a worksheet is useful evidence that the team still needs to solve something. Filling it with an unwilling person does not solve it.

After the meeting, send the brief record through the agreed channel. At the next meeting, ask what was done, what remains, and whether anyone needs support. Reliable follow through allows a team to spend more time serving people and less time repeating the same unresolved conversation.