How the Song List Reaches the Person Building the Slides

Saturday evening, a text goes out: "Can you do 312 before the sermon instead? And skip verse three of the invitation song."

The person who builds the slides reads it at a stoplight, or does not read it until Sunday morning at eight, when the deck is already finished and the projector is already warm.

Nobody in this story did anything wrong. The song leader chose well. The projection volunteer is faithful. The failure is in the space between them, which in most congregations is a text thread, a printed sheet, or a memory.

The List Is a Message, and Messages Get Lost

A song list feels like a document. It behaves like a message, because its whole purpose is to change what a second person does before a deadline that neither of them can move.

Documents can sit in a folder. Messages need to arrive, and the sender needs to know they did. Three things go wrong with song lists in particular:

The list changes after it is sent. The first version is rarely the last one. Without one shared copy, the person building the deck is working from whichever version they saw most recently, and neither of you can tell which that was.

The details live in the margins. Which verses to sing, where in the service the song falls, a note about a key change. These are the things that get lost when a list is typed into a text message as a bare line of numbers.

Nobody confirms. The leader assumes the slides will be right. The projection volunteer assumes the list is final. Each is trusting the other, and the first moment either finds out otherwise is in the assembly.

What a Plan Should Carry

In BetterGather, a song list belongs to one service occurrence. That detail matters more than it sounds: the service already has a date, a time and a roster, so the list does not need to repeat any of it, and there is only ever one list per service to argue about.

Each song on the list sits at a position and can carry the following, written the way the leader would write it:

• Where it falls. Opening, before communion, before the sermon, invitation, closing, or any slot name your congregation uses. The slot is free text, because a Wednesday study is not a Sunday morning.
• Which verses. "1, 2, 4" or "all." This is shown to the projection desk exactly as typed. It is not interpreted, which means it also cannot be misread.
• A note. Anything the person building the deck needs to know and would otherwise get by text.

Songs are chosen from the songbooks your congregation has loaded, so the leader is picking a numbered song from a book rather than retyping a title from memory. Reordering is a drag, and the numbering stays continuous after any change.

Hand It Over, and Say So

A list moves through three states. It starts as a draft, which is still the song leader's own work and is not yet anyone else's assignment. When the leader submits it, it goes to the projection desk. When the projection volunteer confirms the deck is built, it is marked ready.

Two small rules keep this honest. A list with no songs on it cannot be submitted, so nobody receives an empty plan and assumes it is final. And a list cannot be marked ready before it has been submitted, so the confirmation always refers to something the leader actually handed over.

The projection sheet for the service shows the plan along with whoever is rostered to the projection-type role for that service. BetterGather works out who that is from the roster you already keep, matching role names such as projection, slides, screen or media, rather than asking you to maintain a second list of who does what.

It is worth being plain about the limit. For now, the hand-off is recorded and shown on the projection sheet. It does not text or email the volunteer for you. If your projection person lives in their phone rather than in a web page, the leader still needs to tell them the list is there. What changes is that the list itself, the verses and the notes are in one place, and the status says whether the deck has been confirmed.

What Was Planned Is Not What Was Sung

Every song leader knows the Sunday where the plan changed at the last minute. A hymn was swapped because a visiting family asked for it. A song ran long and the closing was dropped.

BetterGather keeps the two apart on purpose. The plan says what the leader intended. A separate record says what was actually led at that service, along with who led it. The same hymn can be recorded twice in one assembly if that is what happened, because that is a real thing congregations do.

Once that record exists, questions that were previously guesses become answerable:

• Which songs has the congregation sung most over a period you choose?
• How many songs in the books you own have never been sung at all? Not "not recently": never.
• Which songs have not been led for a long time, listed with the never-sung ones first, so a leader can bring an older hymn back deliberately?
• How much has each leader led?

The never-sung question tends to be the surprising one. A hymnal is something a congregation owns and barely opens, and most of us have no idea how much of it we have never used.

The record can also be exported as a spreadsheet file with the service date, song, book, number, leader and copyright status on each row. That means you are never locked in to the app, and it gives whoever keeps your licensing paperwork something to start from. It is raw material, not a finished report, and what your licence requires you to report is a question for the licence holder.

What This Will Not Do

It will not choose the songs. The revival list tells you what has been neglected. It does not know what fits the sermon, and it should not.

It will not fill in what was sung. The record of what was led is entered after the service. A plan that nobody reconciles produces a history that is a list of intentions.

It will not store lyrics for songs it is not allowed to. Words are only kept for songs established as public domain, or where your congregation has declared the licence that covers it. A licence is recorded as the congregation's own statement and is not verified by BetterGather.

Where to Start

Before any software, settle one question: who builds the slides, and what is the last moment a change can reach them? Write both down. Most "Saturday night scramble" stories are a missing deadline rather than a missing tool.

Then make the list a single shared thing. One list per service, with the verses and the notes on it, handed over once and confirmed once. The leader knows it arrived. The projection volunteer knows it is final. Nobody has to find out in the middle of the assembly.