How we curate songs

How songs enter the library

Only administrators can add songs to the public library. They can import a song directly or approve a community request. Signed-in visitors can suggest songs; each request stays pending until an administrator approves or declines it.

Adding a song means selecting it for examination. Inclusion in the library is not an endorsement of the song, its writers, or its suitability for every congregation.

How assessments are prepared

Administrators can start an assessment for an imported song. Approving a community request also starts its assessment. The analysis uses automated retrieval and language-model systems to examine lyric claims alongside passages from the World English Bible.

Song pages present the assessment rationale, Scripture references and surrounding context, themes, doctrines, strengths, and concerns. These details help readers examine the reasoning behind a rating and decide whether they agree with it.

What the review status means

The “AI assessment complete” status means the automated assessment has completed. It does not record a separate human sign-off on every conclusion. Admin curation determines which songs enter the library; the generated assessments remain provisional and open to correction.

Administrators can run a fresh assessment or remove a song from the library. Ratings should be read alongside the explanation and cited passages, with attention to poetic language and biblical context.

How to read an assessment

Start with the song’s central message, then inspect its individual claims and explanations. A shared word or theme is not enough to show that a Bible passage supports a claim. Read who is speaking, who is being addressed, and the surrounding verses. Ask whether the lyric expresses the same meaning or extends a promise beyond that context.

“Supported” means the automated assessment found biblical support; “Compatible, not established” means a claim may fit Christian belief without being established by the evidence shown. “Needs qualification” flags wording that needs context, while “Insufficient evidence” calls for further examination. These labels are provisional judgments that readers can challenge using the cited text.

The doctrinal rating combines the assessed claims and gives greater weight to the weakest results; repeated concerns can lower it further. It is not a percentage of biblical accuracy, a measure of musical quality, or a recommendation for every church. Claims that cannot be scored do not contribute to the number. An artist’s average covers only the rated songs present in this library.

Before choosing a song for a congregation, consider how poetic language will be understood when sung, whether an introduction would clarify an ambiguous line, and whether the song fits the service’s teaching and your church’s doctrinal commitments. Use the discussion on the song page to explain a disagreement or suggest a correction.

Discussion and corrections

Signed-in readers can leave a comment on a song’s page to discuss an assessment or point out an error. Identify the conclusion or passage in question and explain your reasoning so others can consider it. Keep disagreements charitable and relevant to the song.

Readers can report inappropriate comments, and administrators can review those reports and remove comments when needed.

Using the library in your church

Our song evaluation guide works through promises, grace, and lament with Scripture in context, then provides a discussion worksheet for your worship team.

Consider the lyrics, Scripture in context, your church’s confessional commitments, and local pastoral guidance when choosing worship music. Read our theological assessment disclaimer for the scope and limitations of the assessments.