Yes, CCLI reporting is required, and it's not optional paperwork you can shove in a drawer. If your church holds a Church Copyright License, Streaming License, Streaming Plus License, or Rehearsal License, you're on the hook to tell CCLI what songs you're using so royalty payments reach the songwriters and publishers who wrote them. Skipping this step doesn't just risk your license standing. It means the people who wrote "Way Maker" or your favorite Sunday opener don't get paid for your church using their work.
Here's what to do right now, before you finish reading this article:
- Log into or create your CCLI Profile at reporting.ccli.com.
- Confirm exactly which licenses you hold (Church Copyright License, Streaming, Streaming Plus, or Rehearsal Licensing all have different reporting rules).
- Choose your path: connect auto-reporting through your worship software, or pull together your last few weeks of setlists for a manual report.
For manual reporting under the Church Copyright License, CCLI works on a 2.5-year rotation, selecting about 20% of customers every six months to report. That means you might not be due right now, but you need to check your CCLI Profile to know for sure. Tools like SongSelect and Song7 make gathering the right song data far less painful than digging through a filing cabinet of old bulletins.
Key Takeaways
Accurate CCLI reporting depends on knowing your license type, following its specific reporting frequency, and keeping one clean, shared setlist record your whole team trusts.
| Point | Details |
|---|---|
| Reporting requirement varies by license | Church Copyright License rotates roughly every 2.5 years; Streaming, Streaming Plus, and Rehearsal require ongoing reporting. |
| Auto-reporting reduces errors | Connecting your worship software to CCLI makes reporting continuous and cuts missed entries. |
| Field accuracy matters most | Always verify CCLI numbers through SongSelect before submitting any report. |
| "Nothing to report" is valid | Use it when your reporting window genuinely had no covered song usage. |
| Late reporting is fixable | Contact CCLI support promptly to submit overdue reports or correct discrepancies. |
Table of Contents
- Which CCLI Licenses Require Reporting?
- How Often Do You Need to Report to CCLI?
- What Is Auto-Reporting and How Do You Set It Up?
- How Do You Manually Report Song Usage to CCLI?
- What Details Does CCLI Expect in Every Report?
- Common CCLI Reporting Mistakes and How to Fix Them
- How Song7 Helps You Prepare CCLI-Ready Reports
- Your Ready-to-Report Checklist
- How Does CCLI Protect Your Reporting Data?
- What Happens If You Report Late or Don't Report at All?
- Editorial Perspective: Reporting Is Stewardship, Not a Chore
- Useful CCLI Resources
- Sources
- FAQ
Which CCLI Licenses Require Reporting?
Not every CCLI license carries the same reporting obligation, and mixing them up is one of the most common mistakes churches make. Here's the breakdown:
- Church Copyright License: covers copying lyrics into bulletins, projecting words on screens, and printing chord charts. Reporting happens on a rotating schedule, not every single week.
- CCLI Streaming License: covers streaming your worship service online. This requires ongoing reporting whenever you stream a song.
- CCLI Streaming Plus License: an expanded version covering both streaming and on-demand video, also requiring ongoing reporting tied to actual usage.
- Rehearsal Licensing: covers sharing practice tracks and rehearsal recordings with your team, and it also calls for reporting as you use it.
The reason behind all of this isn't bureaucratic box checking. CCLI frames reporting as stewardship, a way of making sure the songwriter who wrote the bridge that brought your congregation to tears on Easter Sunday actually gets compensated. Your specific terms, including which license type you hold and your reporting window, live inside your CCLI Profile. If you've never logged in, that's your first stop, and SongSelect is where you'll confirm song titles and CCLI numbers match what CCLI has on file.
How Often Do You Need to Report to CCLI?
The frequency question trips up more churches than anything else in this process, mostly because it's not the same answer for every license.
For the Church Copyright License, you're on a rotation. CCLI selects roughly 20% of license holders every six months, which works out to every license holder reporting once every 2.5 years. You don't need to submit a report every single week under this license. You need to know when your window opens and report accurately during it.
Streaming, Streaming Plus, and Rehearsal Licenses work differently. These require ongoing reporting tied to actual usage, not a rotating schedule. If you stream a service or share a rehearsal track, that use needs to get reported. When you enable auto-reporting, this reporting becomes essentially continuous, happening in the background as your team plans and presents songs.
- Church Copyright License: reporting on a rotation schedule.
- Streaming, Streaming Plus, Rehearsal Licensing: ongoing, tied to usage.
- Auto-reporting: continuous, once properly connected.
Pro Tip: Log into your CCLI Profile and check the reporting method listed there. If you've enabled auto-reporting, verify it's still connected after any major update to your worship software. Integrations sometimes break silently, and you won't know until a report goes missing.
What Is Auto-Reporting and How Do You Set It Up?
Auto-reporting connects your worship planning or presentation software directly to CCLI's Reporting tool, so your setlists get reported without anyone manually typing song titles into a web form every week. For a busy volunteer team already juggling sound checks and slide decks, this is the closest thing to reporting on autopilot.
The setup flow generally looks like this:
- Create or log into your CCLI Profile at reporting.ccli.com.
- Enable auto-reporting within your CCLI account settings.
- Connect your worship planning, presentation, or setlist app to CCLI.
- Map your setlist fields (song title, CCLI number, service date) so they match what CCLI expects.
- Run a test and confirm the connection is pulling data correctly.
Participating software generally falls into three categories: worship planning platforms, presentation apps, and dedicated setlist tools. When evaluating any of these for CCLI compatibility, look for a few specific features rather than just trusting a marketing claim:
- A built-in SongSelect integration or a dedicated CCLI-number field on every song entry.
- Automatic timestamps tied to service dates, so reports reflect when songs were actually used.
- Clean export options that don't require manual reformatting before upload.
Song7 fits into this category as a setlist and worship planning tool built around exactly this kind of field structure, which we'll walk through in more detail shortly.
Pro Tip: Link your song library to SongSelect first, before connecting auto-reporting. This ensures every song carries its correct CCLI number from the start. Then run a two-week verification window after setup to confirm entries are landing correctly on CCLI's end, as CCLI itself recommends for anyone new to auto-reporting.
How Do You Manually Report Song Usage to CCLI?
If your church isn't using auto-reporting, you've got two solid manual paths: report-by-entry for single services, and report-by-spreadsheet for bulk uploads. CCLI actually recommends reporting weekly, or whenever you've copied or shared songs, rather than waiting until the last minute of your reporting window.
Report-by-entry works like this:
- Log into reporting.ccli.com.
- Select your license type and confirm your church account.
- Choose "Report song use."
- Enter the song title, CCLI number, date used, and number of copies or uses.
- Verify the entry and submit.
Report-by-spreadsheet works like this:
- Download the CCLI reporting template (CSV format).
- Populate the required columns: song title, CCLI number, date, copies or uses, and media type.
- Cross-check every CCLI number against SongSelect before uploading, since a mistyped number can misdirect royalties entirely.
- Upload the completed spreadsheet and confirm it processed without errors.
If you've genuinely used no copyrighted songs during a reporting window, that is, your church didn't project, copy, stream, or record anything covered by your license, you can submit "Nothing to report" instead of leaving your account dormant. This keeps your account status accurate and avoids confusion the next time your rotation comes up.
- Watch for duplicate entries when combining multiple services into one spreadsheet upload.
- If you spot a conflict between two entries for the same song and date, keep the more detailed one and delete the duplicate before submitting.
What Details Does CCLI Expect in Every Report?
CCLI reports live or die on specificity. A vague entry like "worship songs, various" won't cut it. Here's the field list to keep on hand, whether you're filling out a web form or a spreadsheet column:
- Song title (exact match to the official title in SongSelect)
- Writer credit(s), if your license or report format requests them
- CCLI song number (the unique SongSelect ID for that song)
- Date(s) used
- Number of uses or copies
- Service type or media: in-person, live stream, or rehearsal
- Any additional note field your specific license requires
Two quick examples make this concrete:
Single-service use: "Way Maker," CCLI #7115744, used June 14, 2026, in-person Sunday service, one projection use.
Streamed rehearsal: "Goodness of God," CCLI #7117726, used March 3, 2026, rehearsal recording shared via private link, one copy distributed to three team members.
Keep your original setlist backups even after submitting a report. If you've used multitrack recordings or purchased backing tracks, hang onto those permission or purchase records separately. Reports get audited, and a paper trail (or a digital one) saves you a scramble months later.
Common CCLI Reporting Mistakes and How to Fix Them
Most reporting errors aren't dramatic. They're small oversights that compound over a busy ministry season.
The usual suspects: wrong or missing CCLI numbers (easy to mistype, especially with seven-digit codes), duplicated entries when two volunteers report the same service, missed rehearsal uses that nobody thought to log, and auto-reporting connections that quietly break after a software update.
The fixes are just as unglamorous, but they work. Run a SongSelect lookup on any number you're unsure about before submitting. Deduplicate spreadsheet entries before upload rather than after. Designate one shared setlist source of truth so two volunteers aren't reporting from two different documents. And after any major update to your worship software, check that your auto-reporting connection is still live, since CCLI itself recommends periodic verification to catch broken mappings early.
- Assign one person as your reporting coordinator, even if it's a part-time volunteer role.
- Export and archive setlists after every service rather than weeks later.
- Keep an interim tracking spreadsheet if you're between reporting cycles.
- Schedule a quarterly audit to compare your records against what's actually been submitted.
Pro Tip: A shared setlist source of truth sounds like a small thing, but it's the single fix that prevents the most reporting headaches. Pick one tool, get the whole team using it, and stop letting song lists live in five different group texts.
How Song7 Helps You Prepare CCLI-Ready Reports
Getting from "we sang some songs" to a clean, submittable report is where most volunteer teams lose momentum. Song7 was built to close that gap. It gives your team a shared setlist builder, CCLI-number fields you fill in once and reuse forever, CSV export options, and real-time syncing so every team member is working from the same data instead of five different text threads.
A typical workflow looks like this: build your setlist in Song7 for the week, confirm or add each song's CCLI number as you go, then export a CSV formatted around the same fields CCLI expects (title, number, date, usage type). From there, you either upload that file directly to reporting.ccli.com or keep it as a clean backup for your next manual reporting window.
- Drag-and-drop setlist building with CCLI-number fields built in.
- CSV export formatted for direct upload or manual backup.
- Real-time team syncing so volunteers aren't duplicating work.
One quick note on security: use unique, secure login credentials for your Song7 account and set role-based access so only your reporting coordinator or designated staff can submit final reports. This keeps your CCLI data both accurate and protected.
Your Ready-to-Report Checklist
Before you submit anything or flip the switch on auto-reporting, run through this:
- Log into your CCLI Profile at reporting.ccli.com.
- Confirm which licenses are active on your account.
- Gather your last several weeks of setlists, or confirm auto-reporting is connected.
- Verify every CCLI number against SongSelect.
- Submit a test report or upload, then confirm CCLI received it.
If anything looks off, CCLI's support team and step-by-step guides are one click away, and the "Nothing to report" option is there if your window genuinely had no covered usage.
How Does CCLI Protect Your Reporting Data?
Your church's reporting data, song titles, service dates, usage counts, isn't the kind of information that invites identity theft, but it still deserves careful handling, especially since your CCLI Profile is tied to your church's account and billing information.
CCLI's reporting portal operates through a secured account login system, meaning only authorized users with your church's credentials can submit or edit reports. This is exactly why role-based access matters on your end too. If your presentation software or planning tool connects via auto-reporting, that connection uses an authorized integration rather than sharing your full login credentials with a third party, which limits exposure if any single tool in your stack gets compromised.
The practical takeaway for your team: treat your CCLI login the same way you'd treat your church's bank login. Don't share the password over group text. Rotate who has admin access when volunteers transition off the team. And if you're using a third-party planning app for auto-reporting, confirm it's on CCLI's list of participating applications rather than an unofficial workaround that might handle your data less carefully. CCLI's own reporting guidance emphasizes secured, authorized connections as the standard for any integration touching your account.
What Happens If You Report Late or Don't Report at All?
Missing a reporting window doesn't trigger an instant penalty notice, but it does create real problems down the line. Late or missing reports mean songwriters and publishers don't receive the royalties they're owed for your church's usage during that period, which undermines the entire purpose of holding the license in the first place. Persistent non-reporting can also put your license standing at risk, since the completed report is described as essential for accurate royalty processing.
If you've already missed a window, the fix is straightforward: log into your CCLI Profile, check whether a report is currently overdue, and submit as soon as possible rather than waiting for the next rotation. CCLI's support team can help you understand your specific reporting history and whether a supplemental report is needed to correct the gap.
If you spot a discrepancy after submitting, like a wrong CCLI number or a duplicated entry, don't panic. Contact CCLI support directly, explain the error, and ask how to submit a correction. Reporting mistakes happen constantly with volunteer-run teams, and CCLI's process accounts for that reality. What matters most is catching the gap and fixing it, not achieving a spotless record on the first try.
Editorial Perspective: Reporting Is Stewardship, Not a Chore
Most guidance on CCLI reporting treats it like tax paperwork, something to dread and delay. That framing misses the point entirely. Every accurate report you submit puts real royalty dollars into the hands of the person who wrote the song that carried your congregation through a hard season. Treating reporting as an afterthought is treating songwriters as an afterthought.
Where conventional advice falls short is in overcomplicating the manual process while underselling auto-reporting. Plenty of churches assume manual reporting is simpler because it feels more familiar, but it's actually where most errors creep in, mistyped CCLI numbers, forgotten rehearsal uses, duplicate entries from two volunteers working off different lists.
If you take one thing from this article, prioritize a single shared source of truth for your setlists before anything else. Auto-reporting, spreadsheet templates, SongSelect lookups: none of it matters if three people on your team are tracking songs three different ways. Fix that first, and everything downstream gets easier.
Useful CCLI Resources
- Reporting portal: submit reports and manage your CCLI Profile.
- SongSelect: confirm official song titles and CCLI numbers.
- CCLI support guides: step-by-step instructions and video walkthroughs.
- Check your CCLI Profile login for your specific notification window and reporting status.
Sources
FAQ
Does CCLI Require Reporting?
Yes. Churches holding a Church Copyright License, Streaming License, Streaming Plus License, or Rehearsal License must report song usage so royalties reach songwriters and publishers correctly.
How Do I Report to CCLI?
Log into reporting.ccli.com and either submit a manual report by entry or spreadsheet, or connect auto-reporting through a participating worship planning or presentation app.
Is CCLI International?
CCLI operates in multiple countries, but this article focuses on reporting requirements and processes for churches in the United States through reporting.ccli.com.
Does My Church Need a CCLI License?
If your church copies lyrics, projects song content, streams services, or shares rehearsal recordings of copyrighted worship songs, you need the corresponding CCLI license and its associated reporting obligation.
How Often Do I Need to Report Under the Church Copyright License?
CCLI selects about 20% of customers every six months for reporting, meaning most churches report once every 2.5 years unless using auto-reporting.