Worship Team Volunteer Management: How to Schedule and Retain Musicians

Worship Team Volunteer Management: How to Schedule and Retain Musicians

Illustration of a church leader managing worship team schedules and availability on a laptop.

Worship team volunteer management covers four connected jobs: building a rotation schedule that spreads out serving load, onboarding new musicians so they’re ready to play with the team, tracking availability so the lineup doesn’t fall apart two days before Sunday, and running the kind of team culture that keeps experienced players from quietly drifting away. 

A rotation schedule is the recurring lineup that assigns volunteers to specific services on a repeating cycle, usually two to four weeks. Onboarding is the structured process that takes a new volunteer from audition to first live set. Availability management is the system a team uses to know, in advance, who can and can’t serve on a given date.

Barna and Gloo’s 2025 State of the Church report found weekly church volunteering climbed to 24% of U.S. adults in early 2025, up from 15% the year before. But VolunteerBadge’s 2026 analysis of church volunteering notes the average congregation still pulls its serving roles from just 4 to 5 people out of every 10 who could serve. That concentration is what breaks most worship teams. The same three vocalists and two guitarists carry every set, and burnout sets in long before a pastor or team leader notices. The fixes below are specific and mostly mechanical.

How a Rotation Schedule Spreads Out the Serving Load?

A rotation schedule assigns each volunteer to a fixed serving frequency instead of asking week to week who’s available. Most healthy worship teams land on a 1-in-3 or 1-in-4 rotation: a volunteer serves one Sunday, then has two or three Sundays off before serving again. Serving every single week is the single fastest way to burn out a musician, even one who loves serving.

Here’s a working example for a ten-person team, running a 3-week rotation with two teams of five (vocals, acoustic guitar, bass, drums, keys):

Week

Team A

Team B (off)

1

Vocals, Acoustic, Bass, Drums, Keys

Rest week

2

Rest week

Vocals, Acoustic, Bass, Drums, Keys

3

Vocals, Acoustic, Bass, Drums, Keys

Rest week

4

Rest week

Vocals, Acoustic, Bass, Drums, Keys

Bigger churches with three or four vocalists and multiple guitarists can run the same logic across three teams instead of two, which drops individual serving frequency to roughly once a month. 

Smaller churches with only six or seven total volunteers often can’t hit a full 1-in-3 rotation and end up closer to 1-in-2. In that case, protect at least one guaranteed week off per month per volunteer, even if it means the team leader fills a gap themselves that Sunday.

Build the rotation around instrument roles, not just names. A volunteer who only plays acoustic guitar can’t cover for a bassist. List every role your team needs covered (lead vocals, harmony vocals, acoustic, electric, bass, drums, keys, and audio if you schedule tech volunteers on the same sheet), then slot people by role first and by rotation cycle second.

How Onboarding Prepares a New Volunteer to Serve?

Onboarding for a worship team volunteer typically runs 30 to 60 days from first contact to first live set, broken into three stages: audition and skill check, rehearsal shadowing, and a supervised first service. Skipping stages is where most new-volunteer dropout happens. A guitarist who gets handed a chord chart Thursday night and plays live  morning with no rehearsal reps usually doesn’t come back for a second try.

A workable 30-day onboarding sequence looks like this:

  • Week 1: Informal audition or skill conversation with the worship leader. Confirm instrument, vocal range if applicable, and reading ability (chord charts, Nashville Number System, or ear-only).

  • Week 2: Attend one full rehearsal as an observer, then run through 2-3 songs live with the team after regular rehearsal wraps.

  • Week 3: Join the actual team rehearsal for an upcoming Sunday, playing the full set list alongside the regular team.

  • Week 4: Serve on a Sunday with an experienced volunteer seated or positioned next to them, ready to cover a missed cue or chord change.

After week 4, a short check-in (five minutes, not a formal meeting) with the team leader catches problems early: sound levels the new volunteer wasn’t comfortable adjusting, confusion about the click track, or uncertainty about when to arrive on Sunday morning. Teams that skip this check-in tend to lose new volunteers around the eight-week mark, once the initial excitement of joining wears off and small frustrations go unaddressed.

How Availability Management Prevents Last-Minute Scheduling Problems?

Availability management means collecting each volunteer’s blackout dates and preferred serving frequency before building the schedule, not after. Two systems work well for worship teams:

Monthly blackout collection. Around the 20th of each month, send every volunteer a simple request for any dates they can’t serve the following month. Worship Teams can run this on a scheduling tool like OnStage.

Rolling 90-day windows. Volunteers submit availability three months out and update it as life changes. Larger teams and churches with volunteers who travel often do better with this setup, since it gives the team leader more runway to fill gaps.

Either system fails without a hard deadline. If blackout dates aren’t submitted by a set date each month, publish the schedule anyway and treat that volunteer as available by default. Chasing down stragglers every month trains the team that deadlines are optional, and the problem gets worse, not better.

Build a two-week buffer into the published schedule. If Sunday, June 14 is being staffed, the schedule for that date should be locked and visible to the whole team by May 31 at the latest. A volunteer who finds out they’re serving three days before the service has less time to prepare and is more likely to ask someone else to cover, which starts the scramble the buffer was supposed to prevent.

What Actually Retains Musicians on a Volunteer Team?

Retention on a worship team comes down to three things volunteers consistently name when they leave: feeling unprepared on stage, never getting a real break, and feeling like a slot to fill rather than a person on a team. Fixing rotation frequency and onboarding handles the first two. The third takes more deliberate effort.

Quarterly one-on-ones between the worship leader and each volunteer catch problems long before a resignation text arrives. A 15-minute conversation asking what’s working, what’s frustrating, and whether the current serving frequency still fits their life surfaces issues that never come up in a group rehearsal setting. Teams that run these check-ins consistently report far fewer surprise departures than teams that only talk to volunteers about logistics.

Song selection also affects retention more than most team leaders expect. A drummer who’s played the same eight songs on repeat for a year loses interest faster than one working through a rotating catalog of 20-25 songs. Rotate at least a few songs in and out of the set list each quarter, even in a small church where the congregation prefers familiar music.

Public, specific appreciation works better than a generic thank-you. Naming what a volunteer actually did well, like a bass player who nailed a tricky transition or a vocalist who covered a missed harmony part without missing a beat, lands differently than a blanket “thanks for serving today” sent to the whole team group chat.

Scheduling Mistakes That Push Volunteers Toward Burnout

Scheduling the same people every week because it’s easier. Filling gaps with your most reliable volunteers instead of recruiting and onboarding new ones concentrates serving load on a shrinking group of people. That group eventually quits, and the team loses its most dependable members all at once.

Publishing the schedule less than two weeks out. Short-notice scheduling forces volunteers to choose between family plans and serving, and they’ll start declining more often once this becomes the pattern.

Treating rotation as flexible instead of fixed. A rotation schedule only works if the team leader protects it. Pulling someone from their off week “just this once” trains volunteers that off weeks aren’t guaranteed, which erodes the entire point of having a rotation.

Skipping onboarding for volunteers who “already know how to play.” Musical skill and team fit are different things. A skilled musician who’s never learned the team’s specific workflow, in-ear mix preferences, or cue system will still struggle in a live setting without a shadowing period.

Never asking about availability until a gap already exists. Reactive scheduling, where the team leader only asks who’s free after discovering an open slot, creates constant last-minute pressure and signals to volunteers that the team isn’t organized enough to plan ahead.

Frequently Asked Questions

How often should worship team volunteers serve?

Most teams do best with a 1-in-3 or 1-in-4 rotation, meaning a volunteer serves one Sunday and has two to three Sundays off before serving again. Weekly serving without a break is the most common cause of volunteer burnout on worship teams.

How long should onboarding take for a new worship team volunteer?

A full onboarding cycle, from first audition to an independent first service, typically takes 30 to 60 days across four stages: audition, rehearsal shadowing, a supervised trial rehearsal, and a first live set with support nearby.

What’s the best tool for scheduling worship team volunteers?

Teams under 10-15 people can run scheduling on a shared spreadsheet with a monthly blackout-date request. Larger teams or multi-service churches typically move to dedicated software like OnStage, which handles rotation logic, availability requests, and automated reminders in one place.

Why do worship team volunteers quit?

Volunteers most often cite feeling unprepared on stage, never getting a real break from serving, and feeling like a schedule slot instead of a team member. All three trace back to rotation frequency, onboarding quality, and whether leaders run regular one-on-one check-ins.

How far in advance should a worship team schedule be published?

At least two weeks before the service date. Publishing later than that increases last-minute cancellations and makes it harder for volunteers to plan rehearsal prep around their week.

Worship team volunteer management covers four connected jobs: building a rotation schedule that spreads out serving load, onboarding new musicians so they’re ready to play with the team, tracking availability so the lineup doesn’t fall apart two days before Sunday, and running the kind of team culture that keeps experienced players from quietly drifting away. 

A rotation schedule is the recurring lineup that assigns volunteers to specific services on a repeating cycle, usually two to four weeks. Onboarding is the structured process that takes a new volunteer from audition to first live set. Availability management is the system a team uses to know, in advance, who can and can’t serve on a given date.

Barna and Gloo’s 2025 State of the Church report found weekly church volunteering climbed to 24% of U.S. adults in early 2025, up from 15% the year before. But VolunteerBadge’s 2026 analysis of church volunteering notes the average congregation still pulls its serving roles from just 4 to 5 people out of every 10 who could serve. That concentration is what breaks most worship teams. The same three vocalists and two guitarists carry every set, and burnout sets in long before a pastor or team leader notices. The fixes below are specific and mostly mechanical.

How a Rotation Schedule Spreads Out the Serving Load?

A rotation schedule assigns each volunteer to a fixed serving frequency instead of asking week to week who’s available. Most healthy worship teams land on a 1-in-3 or 1-in-4 rotation: a volunteer serves one Sunday, then has two or three Sundays off before serving again. Serving every single week is the single fastest way to burn out a musician, even one who loves serving.

Here’s a working example for a ten-person team, running a 3-week rotation with two teams of five (vocals, acoustic guitar, bass, drums, keys):

Week

Team A

Team B (off)

1

Vocals, Acoustic, Bass, Drums, Keys

Rest week

2

Rest week

Vocals, Acoustic, Bass, Drums, Keys

3

Vocals, Acoustic, Bass, Drums, Keys

Rest week

4

Rest week

Vocals, Acoustic, Bass, Drums, Keys

Bigger churches with three or four vocalists and multiple guitarists can run the same logic across three teams instead of two, which drops individual serving frequency to roughly once a month. 

Smaller churches with only six or seven total volunteers often can’t hit a full 1-in-3 rotation and end up closer to 1-in-2. In that case, protect at least one guaranteed week off per month per volunteer, even if it means the team leader fills a gap themselves that Sunday.

Build the rotation around instrument roles, not just names. A volunteer who only plays acoustic guitar can’t cover for a bassist. List every role your team needs covered (lead vocals, harmony vocals, acoustic, electric, bass, drums, keys, and audio if you schedule tech volunteers on the same sheet), then slot people by role first and by rotation cycle second.

How Onboarding Prepares a New Volunteer to Serve?

Onboarding for a worship team volunteer typically runs 30 to 60 days from first contact to first live set, broken into three stages: audition and skill check, rehearsal shadowing, and a supervised first service. Skipping stages is where most new-volunteer dropout happens. A guitarist who gets handed a chord chart Thursday night and plays live  morning with no rehearsal reps usually doesn’t come back for a second try.

A workable 30-day onboarding sequence looks like this:

  • Week 1: Informal audition or skill conversation with the worship leader. Confirm instrument, vocal range if applicable, and reading ability (chord charts, Nashville Number System, or ear-only).

  • Week 2: Attend one full rehearsal as an observer, then run through 2-3 songs live with the team after regular rehearsal wraps.

  • Week 3: Join the actual team rehearsal for an upcoming Sunday, playing the full set list alongside the regular team.

  • Week 4: Serve on a Sunday with an experienced volunteer seated or positioned next to them, ready to cover a missed cue or chord change.

After week 4, a short check-in (five minutes, not a formal meeting) with the team leader catches problems early: sound levels the new volunteer wasn’t comfortable adjusting, confusion about the click track, or uncertainty about when to arrive on Sunday morning. Teams that skip this check-in tend to lose new volunteers around the eight-week mark, once the initial excitement of joining wears off and small frustrations go unaddressed.

How Availability Management Prevents Last-Minute Scheduling Problems?

Availability management means collecting each volunteer’s blackout dates and preferred serving frequency before building the schedule, not after. Two systems work well for worship teams:

Monthly blackout collection. Around the 20th of each month, send every volunteer a simple request for any dates they can’t serve the following month. Worship Teams can run this on a scheduling tool like OnStage.

Rolling 90-day windows. Volunteers submit availability three months out and update it as life changes. Larger teams and churches with volunteers who travel often do better with this setup, since it gives the team leader more runway to fill gaps.

Either system fails without a hard deadline. If blackout dates aren’t submitted by a set date each month, publish the schedule anyway and treat that volunteer as available by default. Chasing down stragglers every month trains the team that deadlines are optional, and the problem gets worse, not better.

Build a two-week buffer into the published schedule. If Sunday, June 14 is being staffed, the schedule for that date should be locked and visible to the whole team by May 31 at the latest. A volunteer who finds out they’re serving three days before the service has less time to prepare and is more likely to ask someone else to cover, which starts the scramble the buffer was supposed to prevent.

What Actually Retains Musicians on a Volunteer Team?

Retention on a worship team comes down to three things volunteers consistently name when they leave: feeling unprepared on stage, never getting a real break, and feeling like a slot to fill rather than a person on a team. Fixing rotation frequency and onboarding handles the first two. The third takes more deliberate effort.

Quarterly one-on-ones between the worship leader and each volunteer catch problems long before a resignation text arrives. A 15-minute conversation asking what’s working, what’s frustrating, and whether the current serving frequency still fits their life surfaces issues that never come up in a group rehearsal setting. Teams that run these check-ins consistently report far fewer surprise departures than teams that only talk to volunteers about logistics.

Song selection also affects retention more than most team leaders expect. A drummer who’s played the same eight songs on repeat for a year loses interest faster than one working through a rotating catalog of 20-25 songs. Rotate at least a few songs in and out of the set list each quarter, even in a small church where the congregation prefers familiar music.

Public, specific appreciation works better than a generic thank-you. Naming what a volunteer actually did well, like a bass player who nailed a tricky transition or a vocalist who covered a missed harmony part without missing a beat, lands differently than a blanket “thanks for serving today” sent to the whole team group chat.

Scheduling Mistakes That Push Volunteers Toward Burnout

Scheduling the same people every week because it’s easier. Filling gaps with your most reliable volunteers instead of recruiting and onboarding new ones concentrates serving load on a shrinking group of people. That group eventually quits, and the team loses its most dependable members all at once.

Publishing the schedule less than two weeks out. Short-notice scheduling forces volunteers to choose between family plans and serving, and they’ll start declining more often once this becomes the pattern.

Treating rotation as flexible instead of fixed. A rotation schedule only works if the team leader protects it. Pulling someone from their off week “just this once” trains volunteers that off weeks aren’t guaranteed, which erodes the entire point of having a rotation.

Skipping onboarding for volunteers who “already know how to play.” Musical skill and team fit are different things. A skilled musician who’s never learned the team’s specific workflow, in-ear mix preferences, or cue system will still struggle in a live setting without a shadowing period.

Never asking about availability until a gap already exists. Reactive scheduling, where the team leader only asks who’s free after discovering an open slot, creates constant last-minute pressure and signals to volunteers that the team isn’t organized enough to plan ahead.

Frequently Asked Questions

How often should worship team volunteers serve?

Most teams do best with a 1-in-3 or 1-in-4 rotation, meaning a volunteer serves one Sunday and has two to three Sundays off before serving again. Weekly serving without a break is the most common cause of volunteer burnout on worship teams.

How long should onboarding take for a new worship team volunteer?

A full onboarding cycle, from first audition to an independent first service, typically takes 30 to 60 days across four stages: audition, rehearsal shadowing, a supervised trial rehearsal, and a first live set with support nearby.

What’s the best tool for scheduling worship team volunteers?

Teams under 10-15 people can run scheduling on a shared spreadsheet with a monthly blackout-date request. Larger teams or multi-service churches typically move to dedicated software like OnStage, which handles rotation logic, availability requests, and automated reminders in one place.

Why do worship team volunteers quit?

Volunteers most often cite feeling unprepared on stage, never getting a real break from serving, and feeling like a schedule slot instead of a team member. All three trace back to rotation frequency, onboarding quality, and whether leaders run regular one-on-one check-ins.

How far in advance should a worship team schedule be published?

At least two weeks before the service date. Publishing later than that increases last-minute cancellations and makes it harder for volunteers to plan rehearsal prep around their week.

Worship team volunteer management covers four connected jobs: building a rotation schedule that spreads out serving load, onboarding new musicians so they’re ready to play with the team, tracking availability so the lineup doesn’t fall apart two days before Sunday, and running the kind of team culture that keeps experienced players from quietly drifting away. 

A rotation schedule is the recurring lineup that assigns volunteers to specific services on a repeating cycle, usually two to four weeks. Onboarding is the structured process that takes a new volunteer from audition to first live set. Availability management is the system a team uses to know, in advance, who can and can’t serve on a given date.

Barna and Gloo’s 2025 State of the Church report found weekly church volunteering climbed to 24% of U.S. adults in early 2025, up from 15% the year before. But VolunteerBadge’s 2026 analysis of church volunteering notes the average congregation still pulls its serving roles from just 4 to 5 people out of every 10 who could serve. That concentration is what breaks most worship teams. The same three vocalists and two guitarists carry every set, and burnout sets in long before a pastor or team leader notices. The fixes below are specific and mostly mechanical.

How a Rotation Schedule Spreads Out the Serving Load?

A rotation schedule assigns each volunteer to a fixed serving frequency instead of asking week to week who’s available. Most healthy worship teams land on a 1-in-3 or 1-in-4 rotation: a volunteer serves one Sunday, then has two or three Sundays off before serving again. Serving every single week is the single fastest way to burn out a musician, even one who loves serving.

Here’s a working example for a ten-person team, running a 3-week rotation with two teams of five (vocals, acoustic guitar, bass, drums, keys):

Week

Team A

Team B (off)

1

Vocals, Acoustic, Bass, Drums, Keys

Rest week

2

Rest week

Vocals, Acoustic, Bass, Drums, Keys

3

Vocals, Acoustic, Bass, Drums, Keys

Rest week

4

Rest week

Vocals, Acoustic, Bass, Drums, Keys

Bigger churches with three or four vocalists and multiple guitarists can run the same logic across three teams instead of two, which drops individual serving frequency to roughly once a month. 

Smaller churches with only six or seven total volunteers often can’t hit a full 1-in-3 rotation and end up closer to 1-in-2. In that case, protect at least one guaranteed week off per month per volunteer, even if it means the team leader fills a gap themselves that Sunday.

Build the rotation around instrument roles, not just names. A volunteer who only plays acoustic guitar can’t cover for a bassist. List every role your team needs covered (lead vocals, harmony vocals, acoustic, electric, bass, drums, keys, and audio if you schedule tech volunteers on the same sheet), then slot people by role first and by rotation cycle second.

How Onboarding Prepares a New Volunteer to Serve?

Onboarding for a worship team volunteer typically runs 30 to 60 days from first contact to first live set, broken into three stages: audition and skill check, rehearsal shadowing, and a supervised first service. Skipping stages is where most new-volunteer dropout happens. A guitarist who gets handed a chord chart Thursday night and plays live  morning with no rehearsal reps usually doesn’t come back for a second try.

A workable 30-day onboarding sequence looks like this:

  • Week 1: Informal audition or skill conversation with the worship leader. Confirm instrument, vocal range if applicable, and reading ability (chord charts, Nashville Number System, or ear-only).

  • Week 2: Attend one full rehearsal as an observer, then run through 2-3 songs live with the team after regular rehearsal wraps.

  • Week 3: Join the actual team rehearsal for an upcoming Sunday, playing the full set list alongside the regular team.

  • Week 4: Serve on a Sunday with an experienced volunteer seated or positioned next to them, ready to cover a missed cue or chord change.

After week 4, a short check-in (five minutes, not a formal meeting) with the team leader catches problems early: sound levels the new volunteer wasn’t comfortable adjusting, confusion about the click track, or uncertainty about when to arrive on Sunday morning. Teams that skip this check-in tend to lose new volunteers around the eight-week mark, once the initial excitement of joining wears off and small frustrations go unaddressed.

How Availability Management Prevents Last-Minute Scheduling Problems?

Availability management means collecting each volunteer’s blackout dates and preferred serving frequency before building the schedule, not after. Two systems work well for worship teams:

Monthly blackout collection. Around the 20th of each month, send every volunteer a simple request for any dates they can’t serve the following month. Worship Teams can run this on a scheduling tool like OnStage.

Rolling 90-day windows. Volunteers submit availability three months out and update it as life changes. Larger teams and churches with volunteers who travel often do better with this setup, since it gives the team leader more runway to fill gaps.

Either system fails without a hard deadline. If blackout dates aren’t submitted by a set date each month, publish the schedule anyway and treat that volunteer as available by default. Chasing down stragglers every month trains the team that deadlines are optional, and the problem gets worse, not better.

Build a two-week buffer into the published schedule. If Sunday, June 14 is being staffed, the schedule for that date should be locked and visible to the whole team by May 31 at the latest. A volunteer who finds out they’re serving three days before the service has less time to prepare and is more likely to ask someone else to cover, which starts the scramble the buffer was supposed to prevent.

What Actually Retains Musicians on a Volunteer Team?

Retention on a worship team comes down to three things volunteers consistently name when they leave: feeling unprepared on stage, never getting a real break, and feeling like a slot to fill rather than a person on a team. Fixing rotation frequency and onboarding handles the first two. The third takes more deliberate effort.

Quarterly one-on-ones between the worship leader and each volunteer catch problems long before a resignation text arrives. A 15-minute conversation asking what’s working, what’s frustrating, and whether the current serving frequency still fits their life surfaces issues that never come up in a group rehearsal setting. Teams that run these check-ins consistently report far fewer surprise departures than teams that only talk to volunteers about logistics.

Song selection also affects retention more than most team leaders expect. A drummer who’s played the same eight songs on repeat for a year loses interest faster than one working through a rotating catalog of 20-25 songs. Rotate at least a few songs in and out of the set list each quarter, even in a small church where the congregation prefers familiar music.

Public, specific appreciation works better than a generic thank-you. Naming what a volunteer actually did well, like a bass player who nailed a tricky transition or a vocalist who covered a missed harmony part without missing a beat, lands differently than a blanket “thanks for serving today” sent to the whole team group chat.

Scheduling Mistakes That Push Volunteers Toward Burnout

Scheduling the same people every week because it’s easier. Filling gaps with your most reliable volunteers instead of recruiting and onboarding new ones concentrates serving load on a shrinking group of people. That group eventually quits, and the team loses its most dependable members all at once.

Publishing the schedule less than two weeks out. Short-notice scheduling forces volunteers to choose between family plans and serving, and they’ll start declining more often once this becomes the pattern.

Treating rotation as flexible instead of fixed. A rotation schedule only works if the team leader protects it. Pulling someone from their off week “just this once” trains volunteers that off weeks aren’t guaranteed, which erodes the entire point of having a rotation.

Skipping onboarding for volunteers who “already know how to play.” Musical skill and team fit are different things. A skilled musician who’s never learned the team’s specific workflow, in-ear mix preferences, or cue system will still struggle in a live setting without a shadowing period.

Never asking about availability until a gap already exists. Reactive scheduling, where the team leader only asks who’s free after discovering an open slot, creates constant last-minute pressure and signals to volunteers that the team isn’t organized enough to plan ahead.

Frequently Asked Questions

How often should worship team volunteers serve?

Most teams do best with a 1-in-3 or 1-in-4 rotation, meaning a volunteer serves one Sunday and has two to three Sundays off before serving again. Weekly serving without a break is the most common cause of volunteer burnout on worship teams.

How long should onboarding take for a new worship team volunteer?

A full onboarding cycle, from first audition to an independent first service, typically takes 30 to 60 days across four stages: audition, rehearsal shadowing, a supervised trial rehearsal, and a first live set with support nearby.

What’s the best tool for scheduling worship team volunteers?

Teams under 10-15 people can run scheduling on a shared spreadsheet with a monthly blackout-date request. Larger teams or multi-service churches typically move to dedicated software like OnStage, which handles rotation logic, availability requests, and automated reminders in one place.

Why do worship team volunteers quit?

Volunteers most often cite feeling unprepared on stage, never getting a real break from serving, and feeling like a schedule slot instead of a team member. All three trace back to rotation frequency, onboarding quality, and whether leaders run regular one-on-one check-ins.

How far in advance should a worship team schedule be published?

At least two weeks before the service date. Publishing later than that increases last-minute cancellations and makes it harder for volunteers to plan rehearsal prep around their week.