If you’re a Worship Leader, you’ve probably been asking the same question: can I keep using beautiful, powerful
songs from Bethel, Hillsong, and Elevation now that those organizations carry public scandals and theological
concerns? This article breaks the issue into three practical arguments you’ll hear in staff meetings, explains the
theological and practical stakes, and gives a clear, pastoral plan you can take back to your team.

Why this matters for the Worship Leader

Songs aren’t neutral. As a Worship Leader you are a teacher, shepherd, and cultural steward. The songs you select
shape your congregation’s theology, their personal prayers, and what they hum on the drive home. That’s why this
debate isn’t merely about taste — it’s about responsibility.

The three core arguments you’ll hear

  1. Financial support: Singing a song generates performance royalties, and royalties often filter back
    to the writer’s home church or label. That means, intentionally or not, churches can underwrite ministries whose
    theology or practices they might reject.
  2. God uses sinners: Great worship songs can come from flawed people. David sinned and wrote Psalms.
    Sin doesn’t automatically nullify spiritual truth in a song. Many Worship Leaders point to this as a reason to
    continue using powerful material regardless of the songwriter’s failings.
  3. Pipeline to theology: Songs are a discovery gateway. When congregants stream a song after church,
    algorithms can surface sermons and teachings from that songwriter’s church. As a Worship Leader you can unintentionally
    create a pathway for your people into teaching you’d rather they avoid.

All three are valid. All three collide in the real world. And the crosswriting reality complicates everything: many
songs we think belong to safe writers are co-written by people connected to those controversial ministries. That makes
a clean cut nearly impossible.

BLOCK QUOTE: The songs we select inform our people’s theology. As Worship Leaders we must steward that influence.

How I wrestled with it (and what finally helped)

I sat in a leadership huddle and listened to colleagues land on different answers. Some wanted an immediate boycott.
Others said, “We can’t control co-writes or commerce.” But the argument that stopped me cold was the pipeline effect:
a moving congregation member streams a song, clicks further, and ends up watching a sermon or conference clip that
subtly shifts their theology.

When I took the matter to God, the surprising answer I received was not: “Boycott.” It was: “Write for your church.”
That answer is practical, pastoral, and generative. It doesn’t pretend the problem is simple; it gives a long-term
solution that restores agency to the Worship Leader.

Practical plan for the Worship Leader

If you’re wrestling with this (and you’re not alone), here’s a clear, balanced approach to implement this week and
over the next 12 months:

  1. Short-term stewardship: Continue using the best, cleanest, most theologically sound songs you can
    find from any source. Don’t panic-shelve your entire catalogue overnight; shepherding well often means thoughtful,
    incremental change.
  2. Audit song theology: Make a simple vetting checklist (lyrical theology, biblical clarity, potential
    for misunderstanding). Use it as a quick filter when new songs arrive in your inbox.
  3. Limit the pipeline risk: When a congregant sings a song you introduced, give brief context on the
    theology. Teach them how to steward their listening—encourage discernment when they search songs online.
  4. Start writing for your people: Commit to creating a unique worship vocabulary for your congregation.
    Writing for your church solves crosswriting royalties concerns, reduces dependence on external theology, and helps
    your people sing words that reflect your local story.
  5. Build a writing rhythm: Even simple songs matter. Try writing one short congregational song each month.
    Put it into rotation, teach it well, and let it grow. Over time you’ll assemble a catalog that belongs specifically
    to your church.
  6. Train your team: Develop songwriting sessions with your musicians. Invite honest theological review
    from your pastor to keep lyrics sound and gospel-centered.

You don’t need a record deal to serve your people’s worship. A Worship Leader who equips a local catalog is doing
long-term pastoral work.

If you want a realistic plan to start writing, begin with two short templates: a simple confession/response chorus,
and a single-verse testimony song. Keep melodies singable, ranges congregational, and lyrics plainly gospel-centered.

Communicating this to your leadership and congregation

  • Be transparent with your team about why you’re changing song strategy.
  • Frame it pastorally: this is about protecting people’s theology and nurturing local worship language.
  • Celebrate wins: teach new local songs slowly and intentionally so the congregation carries them into life.

Quick checklist for song selection (for the Worship Leader)

  1. Does the lyric point clearly to Christ?
  2. Are there ambiguous theological phrases that need explaining?
  3. Is the melody congregationally singable?
  4. Who owns the songwriting credits (is crosswriting a factor)?
  5. Could streaming the original lead listeners into questionable teaching?

BLOCK QUOTE: As shepherds we must care for what we let into people’s hearts. Choosing songs is part of pastoral care.

If we keep singing a song, are we funding that church?

Yes, in a practical sense performance royalties can flow back to songwriters’ publishers and affiliated labels. But
the crosswriting reality makes an all-or-nothing boycott nearly impossible. The wiser route is to steward your set
lists, audit song theology, and invest in local songwriting so you reduce that dependency over time.

Does a songwriter’s sin invalidate a song?

Not automatically. Scripture records beautiful worship arising from flawed lives. However, there’s a difference
between historical sin and active institutional influence. If a songwriter’s current platform is promoting harmful
teaching, you must weigh the ongoing influence on your people.

How do I start writing if I’ve never written before?

Start small. Write one chorus that names who God is and how He’s acted in your church. Keep the melody simple,
teach it acoustically, and refine it after a few congregational sings. Enlist one teammate to co-write and build
momentum together.

What if my team disagrees with me?

Invite conversation, not conflict. Use your vetting checklist, present pastoral concerns, and propose a trial period:
keep the best external songs while you introduce one local song each month. Give time for the congregation to adapt.

Conclusion — a pastoral invitation for Worship Leaders

This is a messy season for many Worship Leaders. There is no perfect, immediate solution. But there is a faithful,
long-term one: steward what you sing, teach your people to listen carefully, and begin to write songs that belong to
your congregation. That pathway preserves theological care, reduces unintended financial support for troubling
systems, and empowers your church to sing its own testimony.

How are you handling this in your church? Are you still singing songs from Bethel, Hillsong, or Elevation — or are you
starting to write more locally? Leave a note on your planning board, talk with your pastor, and most of all, pray for
wisdom. The role of the Worship Leader is weighty and beautiful — let’s steward it well.