arrow_drop_down
Back To Docs Home
Songs

Auto-reporting to CCLI®

WorshipTools makes it easy to report your song usage to CCLI with Auto-reporting. When songs are used in your WorshipTools services, WorshipTools will send that data directly to CCLI, saving your church the extra work of reporting through CCLI's reporting portal.

You can turn on this automated reporting feature in any of the three WorshipTools apps: Presenter, Music Stand, or Planning apps (instructions below). Once the setting is turned on, it will be turned on across all three apps so you do not need to repeat the process. (Note: you must be a WorshipTools Org Admin to see this setting and turn it on.) Data is sent over to CCLI a day or two after your scheduled service, so if you made any last-minute or on-the-fly changes to the set list during service, make sure those changes are reflected in WorshipTools before the end of the day to ensure accurate reporting.

Presenter

To turn this setting on in Presenter, click the ⚙ gear icon in the upper right corner and go to the Settings page. From the left Settings menu, open the Connections tab. There, under your CCLI connection, check the box next to "Automatically report songs used in WorshipTools to CCLI."


Music Stand

Head to the Music Stand's Settings page. Towards the bottom, you will find your CCLI SongSelect Connection with the new option to "Auto-report song usage to CCLI." (You may need to scroll down on the Settings pop-up window to see the Auto-reporting button.)

fullsize


Planning

In the Planning web app, click on your name in the upper right corner and go to the Settings page. Check the box for "Automatically report songs used to CCLI" under your CCLI SongSelect® Integration.

Planning also keeps an ongoing record of your ministry's automated reporting activity. Click on your name in the upper right corner and go to the Activity Log. There, you'll be able to see how many songs were reported. To see or modify your reports after submission, you can log in to the CCLI Reporting Portal.

fullsize

Related docs: