FREE

Course certificates are free until March 31, 2027.

PT730E Leading Worship: Music, Art and Media

Lecture 2-4: Rehearsal and the Week Before Sunday

Contents 31
PT730E Leading Worship: Music, Art and Media
Chapter 0 · Introduction: Clearing a Road
  1. Introduction: Clearing a Road
Chapter 1 · Week 1: Planning Worship
  1. Lecture 1-1: What Planning Worship Is, and Is Not
  2. Lecture 1-2: Reading the Gathering
  3. Lecture 1-3: Shapes of a Service
  4. Lecture 1-4: Welcome, Transitions and Silence
  5. Lecture 1-5: Practice Lab, Read One Service
Chapter 2 · Week 2: Building a Team
  1. Lecture 2-1: Who Serves
  2. Lecture 2-2: Calling, Trying Out and Saying No
  3. Lecture 2-3: Training, Rotas and Rest
  4. Lecture 2-4: Rehearsal and the Week Before Sunday
  5. Lecture 2-5: Practice Lab: Map Your Team
Chapter 3 · Week 3: Music and Choosing Songs
  1. Lecture 3-1: Choosing Songs
  2. Lecture 3-2: The Congregation's Voice
  3. Lecture 3-3: Leading Without Performing
  4. Lecture 3-4: Permission to Use Music
  5. Lecture 3-5: Practice Lab, A Month of Songs
Chapter 4 · Week 4: Art, Space and Access
  1. Lecture 4-1: Where Traditions Differ on Art
  2. Lecture 4-2: Seeing, Moving, Reading Aloud
  3. Lecture 4-3: The Room
  4. Lecture 4-4: Worship Everyone Can Join
  5. Lecture 4-5: Practice Lab: Walk the Room
Chapter 5 · Week 5: Media and Online Worship
  1. Lecture 5-1: Screens, Words and Sound
  2. Lecture 5-2: Recording and Streaming
  3. Lecture 5-3: Those Who Join Online
  4. Lecture 5-4: Testing a Tool
  5. Lecture 5-5: Practice Lab: One Slide, One Broadcast
Chapter 6 · Week 6: Care, Review and the Long Run
  1. Lecture 6-1: Looking Back at a Service
  2. Lecture 6-2: Bringing Change
  3. Lecture 6-3: Caring for the Team
  4. Lecture 6-4: Safe Rooms, Safe Equipment
  5. Lecture 6-5: Practice Lab: Three Months Ahead

Jump to the key points ↓

18 min

Between one gathering and the next there is a week. What happens in that week decides much of what happens on Sunday. Not because a perfect rehearsal makes a perfect service. It does not. But because the week is where a team learns the order, hears one another, settles who does what, and meets as people before it meets as a team.

Many teams use the week badly. They hold a rehearsal that is really a performance practice, with everyone watching for the leader's face. Or they hold none, and meet for the first time in the minutes before the people arrive. Or they fill the week with messages at all hours until the team feels watched even when it is asleep.

This lecture asks what a rehearsal is for, how a week may be shaped, what rules keep messages kind, what to do when a mistake happens in the service, and how to treat disagreement about taste during the week. Everything in it is a pattern to adjust, not a rule of hours.

What these 18 minutes give you

  • State four purposes of a rehearsal and one thing it is not for.
  • Plan a simple rehearsal that begins in prayer and ends with the whole order.
  • Write three rules for team messages that protect rest and privacy.
  • Explain what a team does when a mistake happens during the service.
  • Say how a question of taste is raised in a way that does not become a quarrel.

And whatever you do, work heartily, as for the Lord, and not for men," — Colossians 3:23

World English Bible

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

WEB

Colossians gives the spirit in which a team prepares: wholeheartedly, and as an offering, not as a show for people's approval. Proverbs gives a method: plans are made firm by many voices. A good rehearsal is where those voices are heard before the people arrive.

1. What a rehearsal is for

Here are four purposes, in the order of how often they are forgotten.

To know the order and the changes. The most common failure in a service is not a wrong note. It is a muddle at a change: who speaks next, who stands, where the book is, when the music stops. A rehearsal that walks the whole order once, from the first word to the last, finds the muddles while they are cheap.

To hear one another. In a service, a musician is listening to the people, to the leader, to the room. In a rehearsal there is time to learn how the guitar and the voice sit together, how loud the reader can be without the speaker, whether the tempo is too fast for older singers.

To fix the one or two things that would stop the people. A rehearsal that tries to polish everything polishes nothing. Ask: "What is the thing that would make the people stop singing, or stop following?" Perhaps it is a key that is too high in the second line. Perhaps it is a verse the team does not know. Perhaps it is a long silence that no one has explained. Fix that first.

To be together as people. A team that meets only on duty, and never as friends, is a staff and not a community. A few minutes at the start for "how was your week?" are not a delay. They are the beginning of the work.

What a rehearsal is not for: it is not a performance, not a place where people are judged, and not a place where the leader proves that the leader is best. If the team leaves a rehearsal feeling smaller, something has gone wrong. If a team member dreads the Thursday meeting, the team is not being formed.

2. A rehearsal that serves the people

One way to shape a rehearsal (an invented example, about an hour):

  1. Begin in prayer (three minutes). A short prayer, in the way your community prays: a set prayer, a free prayer, a silence. It need not be long. It says that this is not only a practice but a preparation. Nobody should be pressed to pray aloud.
  2. A word about the people (two minutes). The leader reads the plan for the coming gathering and says, in a sentence, who will be there: a child's baptism, a family in grief, a group of visitors. This puts the rehearsal in front of the people it is for.
  3. The changes first (fifteen minutes). Walk through each transition: who speaks, who moves, what is said. Do not play the whole song yet.
  4. The hard places (twenty minutes). The two songs or readings that need work. Fix what would stop the people; leave the rest.
  5. The whole order once (fifteen minutes). From start to finish, as nearly as possible as on Sunday, without stopping for anything but a real problem.
  6. A closing word (five minutes). What is settled? What does each person do before Sunday? Thanks. A short prayer.

A rehearsal should end on time. A team that is kept late learns that its evenings are not respected.

If the community cannot meet in the week, as often happens when people live far apart or work long hours, the same shape can be compressed into thirty minutes before the gathering, in the room itself, with the people not yet arrived. And if the team is one person and a phone, the rehearsal is a quiet walk through the plan, reading the readings aloud and speaking the changes.

3. The week

A week may be shaped like this (an invented example, to be adjusted). The days are not a rule.

  • Monday or Tuesday. The planner sends the plan for next Sunday: the songs, the readings, the order. The team reads it. The planner also thanks the people for last week.
  • Midweek. Each person practices alone what they need: the guitarist the chords, the reader the passage aloud, the one who prays the structure of the prayer.
  • Thursday or Friday. The team rehearses together.
  • Saturday. Rest. The team does not rehearse, practise or message. Whatever is not ready is left for the minutes before the service or is simplified.
  • Sunday. The team arrives early. Setting up, a quick check of sound and screens, and a prayer together. During: serve. After: thank, tidy, and go to eat with the people.

The team's week is one thing and the individual's week is another. A person with a full-time job and children cannot give the same hours as a person who is retired. A team should ask each person what they can give, and plan the week around that.

Colossians 3:23 says "work heartily, as for the Lord, and not for men." In a week of preparation this does two things. It forbids laziness, since the work is for the Lord. And it also forbids perfectionism driven by the fear of what people will think. The team prepares well because the people deserve a cleared road, not because it will be praised.

4. Messages: hours and privacy

Today much of a team's life is carried by messages. Without rules, the team can be wearing, intrusive and unkind. Three rules are enough to begin.

  1. Agree quiet hours. Name the hours, for example evenings and early mornings, when no one expects a reply or sends a message unless it is urgent. Include the day of rest.
  2. Keep plans in one place. One list or one page, always current, so that no one needs to read forty messages to find the order.
  3. Keep the group for the work. Disagreements, personal news, criticism and complaints belong in a conversation, not in a group message where a dozen people see them. Do not share photographs or details of other people without their permission. Do not send private information about a member of the congregation.

An additional rule for young people: an adult does not message a young person alone. Messages go to a group that includes a second adult or the parents. Follow your community's written rules and local law.

5. When a mistake happens in the service

It will. A song begins in the wrong key, a reading is skipped, the microphone cuts out, a candle drips, the projector freezes, a cue is missed. Teams that fear mistakes tend to make the fear worse, since a frightened team looks at each other and not at the people.

A team can prepare.

  • Agree that the leader goes on. The default is: keep going, quietly, and repair later. A leader who stops and says "sorry, sorry" makes the mistake larger.
  • Agree small signals. A nod that means "start again at the chorus." A glance that means "we are cutting the last verse." The team should not have to talk across the room.
  • Know the plain fix. If the speaker fails, the people can sing without it. If the page is missing, a reader can say it from the book. A team that has thought of the plain fix is calm.
  • Say it simply if it must be said. "Let us begin that again" in a calm voice is better than a long apology.
  • Do not hold a post-mortem in the room. After the service, thank the people. Save the review for the week. A review is described in lecture 6-1.

In many small gatherings, a missed note does less harm than a leader who stops, shows anger, or loses the people's attention. That is a judgement to test in your own place and not a law. The principle is that the people have come to answer God, and the team's task during a mistake is not to be perfect but to keep the road open.

After the service, a short word to the person who made the mistake is kind: "That was hard, and you kept going." No more is needed. If the same difficulty is repeated, it belongs to rehearsal and to training, not to the person's worth.

6. Disagreements about taste

During the week, someone will say "I don't like that song" or "the arrangement is too loud." Teams quarrel about this more than almost anything. This lecture gives only a small rule. For more, the course PT714E is the place.

The small rule: a question of taste is raised after the rehearsal, as a question about the people, not as a verdict about who is right. "Do you think the older singers can follow this?" is a question about the people. "This is a terrible song" is a verdict. The first can be answered; the second starts a war. The decision belongs to whoever the community's policy says plans the service, who listens, decides, and says why. Proverbs 15:22 does not say that all counsellors rule; it says that plans become firm when counsel is sought. The leader asks for counsel and then decides, and the team agrees to go forward together.

Lecture 6-2 returns to change and to disputes about style.


Diagram 1. The week before Sunday

A Week Before Sunday, and an Hour of Rehearsal A pattern to adjust, not a rule of hours Mon-Tue plan sent; thanks for last week Midweek each person prepares alone Thu-Fri team rehearses together Saturday: rest no rehearsal, no practice, no messages Sunday arrive early, check, pray; serve; thank; eat with the people the rehearsal in detail 1. Pray (3 min) Short, in your community's own way. Nobody pressed to speak. 2. The people (2) Who will be there on Sunday? Say it in a sentence. 3. Changes (15) Who speaks, who moves, what is said. Before any song is polished. 4. Hard places (20) Fix only what would stop the people. Leave the rest. 5-6. Whole order, close Once through. What is settled? Thanks. End on time. A rehearsal is not a performance and not a trial. It prepares a road for the people.

Diagram 2. Three rules for team messages

Rule Why
Agree quiet hours, and a day without messages A team that is always reachable is never at rest
Keep the plan in one place Nobody should read forty messages to find the order
Keep the group for the work Criticism, news about others and photographs need a person's permission, and are better in a conversation

In short

  • A rehearsal exists to learn the order and the changes, to hear one another, to fix what would stop the people, and to be together as people.
  • It is not a performance and not a trial; a team that leaves smaller has been rehearsed badly.
  • A good rehearsal begins in prayer, looks at the changes first, tries the whole order once, and ends on time.
  • Message rules protect rest and privacy: quiet hours, one place for the plan, the group for the work; an adult does not message a young person alone.
  • When a mistake happens, the leader goes on, signals are small, and the review waits for the week.
  • A question of taste is raised after rehearsal as a question about the people, and a person named by the community's policy decides.
Front Back
Four purposes of rehearsal Know the order and changes; hear one another; fix what would stop the people; be together as people.
What a rehearsal is not A performance, a trial, or a place for the leader to prove anything.
Three message rules Quiet hours; one place for the plan; the group is for the work.
When a mistake happens Go on; use small signals; know the plain fix; review later.

One sentence to remember A rehearsal prepares a road for the people; it is not a stage for the team.

This week's action Write a six-step rehearsal plan for your next meeting, with times, beginning in prayer and ending with the whole order once.

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

  • Think of a rehearsal you know. Which of the four purposes did it serve? Which did it forget?
  • What would the people lose if the team rehearsed the changes before the songs?
  • What quiet hours would suit your team? Who might need them most?
  • Describe a mistake in a service you remember. What did the team do? What might have been agreed beforehand?
  • How does your community decide a question of taste? Does the person who raises it feel heard?

Sign in to write and keep your answers

What next

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