How the CCLI Top 100 Project Came to Be  🔗 **Source:** [How the CCLI Top 100 Project Came to Be](https://www.umcdiscipleship.org/blog/how-the-ccli-top-100-project-came-to-be) > [!note]+ Document Notes > tags: #worship-music #vetting #contemporary-worship #united-methodist #liturgy > author: Taylor Burton-Edwards > source: UMC Discipleship Ministries > reference: https://www.umcdiscipleship.org/blog/how-the-ccli-top-100-project-came-to-be > date created: 2024-12-19 10:30 > > # 🏷️ Title: How the CCLI Top 100 Project Came to Be > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Research open source liturgy development practices — explore vetting methodologies #liturgy - [H2] Develop contemporary worship music evaluation criteria — theology, language, singability focus #worship-music - [H3] Create consensus-driven recommendation system — green/yellow list approach #vetting ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [UMC Discipleship Ministries](https://www.umcdiscipleship.org/) - [CCLI Top 100](https://us.ccli.com/) ## 📝 Summary - **What happened**: The United Methodist Church developed a systematic vetting process for contemporary worship music, focusing on CCLI's Top 100 most-used songs - **Why it matters**: Millions of contemporary songs exist with no denominational vetting process, yet UMC is CCLI's second-largest subscriber base - **Key stakeholders**: Church musicians, worship leaders, hymnal revision committees, congregations using contemporary worship - **Risks and tradeoffs**: Balancing theological integrity with musical accessibility; managing subjective evaluation criteria - **Bottom line takeaway**: Rigorous vetting processes adapted from open source software development can successfully evaluate contemporary worship music for denominational use ## 📖 Main Content The CCLI Top 100 Vetting Project emerged from the convergence of three strategic initiatives within The United Methodist Church. The project addresses a critical gap in contemporary worship music evaluation, applying systematic vetting principles borrowed from open source software development to sacred music curation. The genesis involved three concurrent projects: the Open Source Liturgy Project (already underway), preparation for the Fusion worship gathering (recently begun), and anticipated hymnal revision work (forthcoming). Chuck Fromm's insight that "a hymnal is a vetted, curated collection of congregational song" provided the conceptual framework. The methodology emphasizes theology as the primary criterion, following Wesleyan tradition, while incorporating language and singability assessments. The scoring system double-weights theological considerations, and final recommendations emerge through consensus conversation rather than purely algorithmic scoring. ## 🗒️ Notes #### 📋 [Opening] — [H1] Three foundational projects converge - Key idea: CCLI Top 100 project emerged from intersection of liturgy, worship event planning, and hymnal development needs - Evidence: "The CCLI Top 100 Vetting Project has its roots in three other projects" #### 🖥️ [Background] — [H2] Open source software principles inform liturgy - Key idea: Liturgical development can adopt rigorous vetting processes from Linux and browser development - Evidence: "At the heart of these projects is a rigorous process of vetting at two levels" #### 💡 [Insight] — [H1] Chuck Fromm defines hymnal value proposition - Key idea: Vetting and curation constitute a hymnal's core value, not just song collection - Evidence: "A hymnal is a vetted, curated collection of congregational song. That's all it is. Its real value is in the vetting" #### 📊 [Context] — [H2] UMC represents major CCLI user base - Key idea: United Methodist churches significantly influence CCLI's Top 100 through high subscription usage - Evidence: "The UMC is CCLI's second largest denominational subscriber base in the US" #### 🎯 [Strategy] — [H3] Top 100 provides manageable scope - Key idea: CCLI Top 100 list offers practical limitation for reviewing millions of contemporary songs - Evidence: "There are literally millions of songs in this literature. We needed some limitation" #### 👥 [Team Building] — [H2] Diverse expertise recruitment process - Key idea: Project assembled qualified reviewers through network referrals seeking diverse perspectives - Evidence: "I asked them for two things: their possible interest in participating...and the names of others" #### ⚖️ [Criteria] — [H1] Three core vetting dimensions identified - Key idea: Theology, language, and singability emerged as primary evaluation criteria - Evidence: "Theology, language, and singability rose to the top of our list as the core criteria" #### 🛠️ [Tools] — [H3] Technology supports systematic evaluation - Key idea: Custom spreadsheet and database scoring instrument standardizes assessment process - Evidence: "We used those criteria to work with our IT staff to build a spreadsheet and database driven scoring instrument" #### 🗣️ [Process] — [H2] Consensus conversation trumps algorithmic scoring - Key idea: Final recommendations require human discussion beyond numerical scores - Evidence: "Scoring and comments alone would not decide our final recommendations. We still needed conversation" #### 🚦 [Output] — [H3] Two-tier recommendation system balances utility - Key idea: Green list (recommended) and yellow list (conditional) provide nuanced guidance - Evidence: "A 'green list' for those we commended without major reservation, and a 'yellow list' of songs we commended with some significant caveats" #### ⛪ [Theology] — [H1] Wesleyan tradition prioritizes theological evaluation - Key idea: Theological soundness receives double weight following John Wesley's emphasis - Evidence: "Theology was for us, as it was for John Wesley, perhaps the most important factor" #### 📈 [Evolution] — [H2] Multi-year cumulative approach builds comprehensive resource - Key idea: Annual reviews create growing database of vetted contemporary worship songs - Evidence: "Our Green and Yellow lists will continue to reflect all of these songs...from 2015-2017" ## 📚 References - [UMC Discipleship Ministries](https://www.umcdiscipleship.org/) - [CCLI (Christian Copyright Licensing International)](https://us.ccli.com/) - [United Theological Seminary](https://united.edu/) - [Worship Leader Magazine](https://worshipleader.com/) ## 🗣️ Paraphrase - The United Methodist Church created a systematic way to evaluate popular contemporary worship songs by adapting quality control methods from open source software projects - Chuck Fromm's insight that hymnals are primarily valuable for their curation rather than just song collection sparked the realization that contemporary music needed similar vetting - The team developed a scoring system emphasizing theology (following Wesley's priorities), language, and singability, but relied on group conversation for final recommendations rather than purely numerical results ## 📰 Newsletter 🎵 **Contemporary Worship Gets the Open Source Treatment** The United Methodist Church just cracked the code on something many faith communities struggle with: how do you responsibly choose contemporary worship music when there are millions of options? Their solution? Borrow quality control practices from Linux development. The CCLI Top 100 Vetting Project applies rigorous, systematic evaluation to popular worship songs, creating "green" and "yellow" recommendation lists based on theology, language, and singability. **Why this matters for your worship planning**: Instead of flying blind with contemporary music selection, you get expert theological and practical evaluation. The double-weighting of theological criteria follows Wesleyan tradition while acknowledging that great theology can sometimes come in hard-to-sing packages. **Key insight**: "A hymnal is a vetted, curated collection of congregational song. Its real value is in the vetting." This applies whether you're choosing from a traditional hymnal or downloading from CCLI. **Resources**: [UMC CCLI Top 100 Reviews](https://www.umcdiscipleship.org/), [CCLI Song Select](https://us.ccli.com/), [Worship Planning Resources](https://www.umcdiscipleship.org/worship-planning) ## ✅ Action Items #### Community - **Contributors**: Develop nomination process for diverse vetting team members with expertise across musical genres and cultural backgrounds - **Maintainers**: Create documentation templates for evaluation criteria and consensus-building processes that other denominations can adapt #### WordPress - **Documentation**: Develop case study showing how systematic content curation principles from this project could inform WordPress plugin/theme review processes - **Community**: Explore how consensus-driven recommendation systems (green/yellow lists) might improve plugin directory guidance #### OSPO - **Community Engagement**: Study how open source vetting principles successfully transferred to liturgical content curation - **Developer Support**: Document methodology for adapting technical quality assurance processes to non-technical content domains ## 🧪 Hypotheses - Systematic vetting processes from software development can successfully transfer to content curation in religious and cultural domains - Double-weighting core values (theology) in evaluation systems improves alignment between quantitative scores and qualitative recommendations - Diverse expert teams using standardized criteria produce more reliable content recommendations than individual or homogeneous group evaluation - Multi-tier recommendation systems (green/yellow) provide more practical guidance than binary approve/reject decisions ### 📊 Methodology - **Study design for hypothesis 1**: Compare adoption rates and satisfaction scores for vetted vs. unvetted contemporary worship music across multiple denominations - **Data sources for hypothesis 2**: Analyze correlation between weighted theological scores and final team recommendations across 300+ songs over three years - **Experiments for hypothesis 3**: A/B test recommendation accuracy using diverse vs. homogeneous evaluation teams with identical criteria and training ### ❓ Questions - How might AI-assisted preliminary screening enhance human expert vetting without replacing theological and cultural judgment? - What evaluation criteria would be most valuable for vetting worship music across denominational boundaries rather than within single traditions? - How could decentralized, federated vetting networks allow smaller faith communities to benefit from systematic music evaluation? ### 🔮 Future Research - **Cross-denominational vetting standards**: Investigation of shared criteria that respect theological diversity while maintaining quality standards - **Cultural context evaluation**: Methods for assessing worship music appropriateness across different cultural and linguistic communities - **Longitudinal impact studies**: Analysis of how systematic music vetting affects congregational engagement and spiritual formation over time ### 💡 Implications - **Practice**: Worship planners need systematic evaluation frameworks rather than purely subjective music selection processes - **Policy**: Religious organizations benefit from adapting secular quality assurance methodologies to sacred content curation - **Education**: Seminary and ministry training programs should include content evaluation and consensus-building methodologies - **Funding**: Denominational investment in systematic vetting creates reusable infrastructure that benefits multiple congregations and reduces individual preparation time ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade (Flesch-Kincaid) #### 👀 Visual learners - **Present**: Clear project timeline and process flow descriptions - **Improve**: Process flow diagrams, evaluation criteria matrices, team structure charts #### 🔊 Aural learners - **Present**: Emphasis on consensus conversation and team discussion - **Improve**: Audio interviews with team members, podcast discussion of methodology #### 🗣️ Verbal learners - **Present**: Strong definitions of vetting, curation, and evaluation terminology - **Improve**: Glossary of technical terms, analogies between software and liturgical development #### 🧩 Kinesthetic learners - **Present**: Step-by-step team building and criteria development process - **Improve**: Interactive evaluation worksheets, hands-on scoring exercises #### 🧠 Logical learners - **Present**: Clear causal relationship between project needs and solution design - **Improve**: Decision trees for recommendation categories, weighted scoring formulas #### 🧑‍🤝‍🧑 Social learners - **Present**: Collaborative team process and consensus-building emphasis - **Improve**: Discussion prompts for evaluation teams, peer review protocols #### 🧘‍♀️ Solitary learners - **Present**: Individual scoring and reflection before group consensus - **Improve**: Self-assessment rubrics for evaluators, independent study materials #### 🌿 Naturalistic learners - **Present**: Organic evolution from existing projects and identified needs - **Improve**: Ecosystem thinking about worship music within broader liturgical context ### 📊 Accessibility Assessment #### Screen reader semantics - **Present**: Clear heading structure and process descriptions - **Improve**: ARIA landmarks for main content sections, descriptive section labels #### Keyboard navigation - **Present**: Standard web navigation structure - **Improve**: Skip links to main content sections, keyboard-accessible evaluation tools #### Contrast and readability - **Present**: Standard black text on white background - **Improve**: Color-coded recommendation categories need sufficient contrast ratios #### Text resizing and reflow - **Present**: Responsive text layout - **Improve**: Ensure evaluation spreadsheets remain usable at 200% zoom #### Media and captions - **Present**: Text-based content with no multimedia - **Improve**: Future audio/video content needs full transcription #### Forms and interactions - **Present**: Basic web forms for team communication - **Improve**: Accessible scoring interfaces with proper labels and error handling ### 🌍 DEIB Assessment #### Cultural breadth - **Present**: Acknowledgment of need for diverse team perspectives - **Improve**: Specific examples of cultural considerations in worship music evaluation #### Inclusive language - **Present**: Professional, accessible terminology throughout - **Improve**: Plain-language summaries of technical evaluation processes #### Neurodiversity support - **Present**: Well-structured content with clear headings and logical flow - **Improve**: Content warnings for potentially sensitive theological discussions #### Representation - **Present**: Focus on diverse team recruitment and qualification - **Improve**: Specific examples of how different backgrounds contribute to evaluation quality #### Psychological safety - **Present**: Consensus-based rather than hierarchical decision making - **Improve**: Explicit guidelines for respectful disagreement during evaluation discussions ### ✅ Logical Validity #### Strong reasoning - **Deductive strength**: Clear logical progression from identified need (contemporary music vetting gap) to solution (systematic evaluation process) - **Inductive strength**: Good use of specific evidence (Chuck Fromm's insight, CCLI statistics) to support general conclusions - **Causal reasoning**: Sound connection between open source vetting practices and liturgical content evaluation - **Analogical strength**: Appropriate analogy between software quality assurance and worship music curation #### Fallacies - **Appeal to authority**: Slight over-reliance on Chuck Fromm's single statement, though appropriately contextualized - **Post hoc reasoning**: Minor assumption that UMC's high CCLI usage necessarily makes them qualified to drive Top 100 selection #### Tone of voice - **Overall tone**: Professional, methodical, and reflective with appropriate academic formality for denominational leadership audience ### 🛡️ DARVO Analysis - **Deny**: No evidence of denial or minimization present - **Attack**: No attacks on accusers or critics identified - **Reverse victim/offender**: No victim/offender reversal detected - **Emotional cues and rhetoric**: Straightforward explanatory tone with no manipulative language patterns ## 🎯 Conclusion - **Key takeaway**: Systematic vetting processes can successfully bridge technical and theological domains, creating reliable evaluation frameworks for contemporary worship music - **Practical next steps**: Faith communities should develop explicit criteria and diverse evaluation teams rather than relying on individual taste or tradition alone for contemporary music selection - **Broader implications**: This methodology demonstrates how open source principles can enhance quality and transparency in content curation across multiple domains beyond software development ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Open source vetting principles transfer to liturgical content > [!quote] [How the CCLI Top 100 Project Came to Be](https://www.umcdiscipleship.org/blog/how-the-ccli-top-100-project-came-to-be) by [[Taylor Burton-Edwards]] via [[UMC Discipleship Ministries]]. Published 2017-12-19. Accessed 2024-12-19. > "At the heart of these projects is a rigorous process of vetting at two levels." Demonstrates successful methodology transfer from software development to sacred music curation, establishing precedent for cross-domain quality assurance. [view highlight](https://www.umcdiscipleship.org/blog/how- <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/How the CCLI Top 100 Project Came to Be.md|How the CCLI Top 100 Project Came to Be by umcdiscipleship.org]] ## Highlights - 2018 will mark our third release of the CCLI Top 100 reviews. Our website will continue to carry reviews of all songs that have appeared from 2015-2017, and our Green and Yellow lists will continue to reflect all of these songs, not just those that appeared on the Top 100 for the first time in 2017. We’ve not changed our scoring tool since our initial release in 2015. As hoped, several of the participants in the CCLI Top 100 Vetting Team will be part of the hymnal revision process approved by the 2016 General Conference, and we trust their experience with this work has prepared them well for that larger task. ([View Highlight](https://read.readwise.io/read/01kprfk9z4tvgcdwtbkcmawzwa)) - Tags: 👻 ai highlighted