How to Manage Copyright and CCLI for Displayed Song Lyrics

Every church that puts song lyrics on a screen needs to think about licensing at some point, and most tech volunteers inherit that responsibility without ever getting a clear explanation of what it actually covers. Getting CCLI song lyrics copyright right isn't about becoming a legal expert. A quick, practical primer saves a lot of guesswork, though for anything specific to your church's situation, your CCLI account or a copyright attorney is the actual authority, not a blog post.

What a CCLI license is generally for

A CCLI (or similar) license is what allows a church to legally reproduce and display copyrighted song lyrics — on a screen, in a bulletin, in a slide deck — for use in congregational worship. It's a blanket license covering a large catalog of songs from participating publishers, which is why most churches can display the vast majority of contemporary worship music without negotiating permission song by song. Without a license covering displayed lyrics, putting copyrighted words on a screen for a gathered congregation is a copyright issue, even if no money changes hands.

It's worth knowing that the license type matters. A license that covers displaying lyrics in the room isn't automatically the same license that covers streaming that same content online — livestreaming and on-demand video often fall under a separate reporting category or license tier. If your church livestreams its services, confirm specifically that your license covers streamed use of the songs you're displaying, not just in-room use.

Reporting is the part churches forget

A license alone doesn't finish the job. Most licensing organizations expect churches to periodically report which songs were actually used in services, since that reporting is how songwriters and publishers get paid their share. It's easy for this to slip when a rotating cast of volunteers is building slides week to week and nobody owns the reporting task specifically.

A few habits keep this from becoming a scramble at renewal time:

• Assign the reporting task to one person or role, not "whoever remembers"
• Keep a running log of songs used each week as part of the normal setlist process, rather than trying to reconstruct months of services later
• Reconcile that log against your license's reporting requirements on whatever cadence they specify

Original songs and special cases

Original songs written by your own worship team generally don't require a CCLI license to display, since your church already holds the rights. That said, if an original song is registered with a performing rights organization, or if a guest artist's original material is being performed, it's worth confirming who holds what rights before assuming it's automatically clear to display and stream freely. When in doubt, ask the songwriter directly. Most are glad to clarify, and it's a much easier conversation before a Sunday than after.

Guest worship teams and touring artists bring their own wrinkle: confirm their material is covered under your license, or under theirs, rather than assuming it carries over automatically.

Making the practical side easier

None of this changes because of what software a church uses, but keeping original songs, guest material, and licensed catalog songs organized in clearly separated places does make the reporting and compliance side easier to manage. AllStreamHub keeps a church's own original and guest songs in a personal library, distinct from the main Lyrics Library of widely available worship music, which makes it straightforward to see at a glance which songs in a given week's set are licensed catalog material and which are originals your church already owns outright.

Copyright compliance isn't the most exciting part of running a worship service, but it's a lot less stressful handled as a standing weekly habit than as a once-a-year fire drill before a license renewal. A five-minute log entry after each service beats a frantic reconstruction of six months of setlists when the paperwork finally comes due.