← All articles

Planning Center Worship Workflow: Getting More from PCO

Planning Center Online is where most worship teams live. Scheduling, song lists, chord charts, service orders. It's the backbone of church worship planning, and if your team has been on it for any length of time, you've probably built up years of data in there.

But PCO is a generalist tool. It handles scheduling and service planning across every ministry in the church. That breadth means it doesn't go deep on the music-specific parts of worship planning. This article covers how to get the most out of PCO for your worship workflow, and where the gaps are.

Set up your service types intentionally

Most churches create one service type and dump everything into it. Sunday morning, Wednesday night, special events. Six months later, the song history is a mess because Christmas Eve songs are mixed in with regular rotation data.

Create separate service types for recurring formats that have different musical needs. Your main Sunday gathering is one type. A midweek acoustic set is another. Special events get their own. This keeps your song frequency data clean and your scheduling templates relevant.

Use plans as the weekly unit

Each plan in PCO represents one date for one service type. Build your weekly set inside the plan, not in a separate document. The more consistently you use plans, the better your historical data becomes. Song usage counts, last-played dates, and scheduling patterns all depend on plans being filled out.

Song arrangements: the feature most teams underuse

PCO lets you create multiple arrangements per song. Most teams ignore this and end up with one arrangement that has chord charts in three different keys pasted into the notes field.

Instead, create a separate arrangement for each key you regularly play a song in. Name it clearly: "Goodness of God (Bb)" and "Goodness of God (G)". Attach the correct chord chart to each. When you add the song to a plan, pick the arrangement that matches who's leading that week.

This takes a bit of upfront work but eliminates confusion on Sunday morning. The band opens their chart and sees the right key immediately.

Scheduling: reduce the back-and-forth

The scheduling confirmation flow in PCO works well when people actually respond. The challenge is the team members who don't check their email or forget to confirm. A few things that help:

• Schedule further out. Giving people three to four weeks of lead time instead of one dramatically improves response rates. They can see conflicts before they become last-minute problems.
• Use blockout dates. Encourage your team to enter blockout dates at the start of each quarter. This saves you from scheduling someone who's traveling and waiting days for a decline.
• Set needed positions clearly. Define every role for each plan (lead vocals, keys, electric, etc.) so PCO shows you exactly what's unfilled. Vague team lists lead to vague commitments.

Attachments and chord charts

PCO's attachment system works fine for storing chord charts and lyric sheets. Keep it organized:

• One chord chart per arrangement (not per song).
• Use consistent file naming: "Song Name - Key - Chart.pdf".
• Delete outdated charts. If you haven't played a song in the key of E in two years, remove that arrangement and its chart.
• Link to external resources (YouTube rehearsal videos, Multitracks pages) in the arrangement notes rather than uploading large files.

Where PCO falls short for music directors

PCO is excellent at what it does: scheduling people and organizing service plans. But it was built to answer "who's playing this Sunday," not "how are the people who play doing." That gap is where a lot of quiet attrition happens.

It shows you the schedule, not the people behind it

PCO knows who served last week. It doesn't tell you that someone who used to serve twice a month has quietly dropped to once, or gone three weeks without a plan. The signal is in the data you already keep, but reading it means scrolling through weeks of plans one person at a time, which most leaders never have time to do.

No sense of who's carrying too much

The same few dependable people get scheduled again and again because you know they'll say yes. PCO doesn't flag when one person is over-leaned on or when a whole section is resting on two team members. Rotation balance is a judgment call you make from memory, not something the schedule surfaces on its own.

No memory of who you've already reached

When you notice someone slipping and reach out, that moment lives in your text messages, not your planning tool. PCO has no place to mark "checked in on James" so the next time you glance at the team, you're starting from memory again. Caring for people well means not losing track of who you've already talked to.

Working with PCO, not against it

The best approach is to use PCO for what it's good at (scheduling, service plans, chord chart storage) and add a layer for the part it wasn't built for: seeing how the people on your team are doing over time. Don't try to force PCO into tracking that by cramming notes into custom fields. Use it as the operational backbone, and let something purpose-built read the participation it already records.