Whatever You Do: The 1 Corinthians 10:31 Test for Church Tech
TL;DR: 'Do it all for the glory of God' is not a vague aspiration. It is a practical test that produces clear answers when applied honestly to specific church technology decisions.
Paul was writing about food. Specifically, about whether Christians in Corinth could eat meat that had been offered to idols in a pagan temple before being sold in the market. It was a first-century question with no modern equivalent.
But the principle he landed on in 1 Corinthians 10:31 has outlived the question that prompted it. Paul writes: "So whatever you do, do it all for the glory of God."
Whatever you do. The scope is deliberately total. Eating and drinking are chosen as the most ordinary examples Paul could find. If even those pass through this test, everything does. Including decisions about what software to run in the church office, how to prepare Sunday's sermon, and what AI tools to put in the hands of volunteers.
Why This Verse Works as a Technology Test
Most frameworks for evaluating church technology get complicated quickly. They require weighing costs against benefits, comparing feature sets, predicting adoption rates, and assessing whether the denomination will have concerns. These are real considerations, but they can also produce paralysis or, worse, a kind of technical evaluation that never touches the actual question: is this good for the people of God?
The 1 Corinthians 10:31 test cuts straight to that question. Does this practice, this tool, this workflow, this policy, glorify God? Not in a vague sense, but in the concrete sense of: does it build people up toward God, does it represent him honestly to the watching world, and does it serve the real flourishing of the community he has called?
Psalm 24:1 provides the theological ground: "The earth is the Lord's, and everything in it, the world, and all who live in it." Technology is not a neutral zone outside God's concern. It belongs to his world and falls under his lordship. The question of how a church uses it is a question of stewardship.
Applying the Test to Specific Decisions
The test is most useful when applied to specific decisions rather than to "technology" in the abstract. Here is what it looks like in practice.
AI sermon generation. Does outsourcing sermon creation to an AI tool glorify God? The question requires honesty. If the congregation receives content that was not produced by genuine pastoral engagement, and the implicit representation is that it was, the practice does not glorify God. It may be efficient. It may produce content that is technically accurate. But it involves a kind of deception and bypasses the formation process that makes pastoral ministry genuine. The test fails.
AI for sermon research. Does using AI to find background on ancient Near Eastern culture, look up Hebrew word ranges, or quickly identify where a theme appears across Scripture glorify God? Yes, clearly. This is a tool in service of the pastor's genuine engagement with the text. It makes the study richer and helps the congregation receive better-prepared teaching. The test passes.
AI-generated content for church communications. Does using AI to draft newsletter copy, social media posts, or event announcements glorify God? Here the answer depends on context. If a volunteer coordinator is not a writer and AI helps them communicate clearly about a food drive, that seems straightforwardly fine. If the lead pastor is sending AI-written pastoral letters that the congregation believes were personally composed, the representation problem resurfaces. The test requires honesty about what is being represented.
Surveillance and member data. Does using data analytics to track member engagement patterns, attendance behavior, and giving trends glorify God? The test here points toward the dignity of persons. God's glory is not served by treating church members as data points to be optimized. Using analytics to identify someone who has stopped attending and prompt a personal pastoral phone call is different from building detailed behavioral profiles to maximize retention metrics.
The Two Failure Modes
Churches that skip this test tend to fail in one of two directions.
The first failure is uncritical adoption. New tools are adopted because they are new, because other churches are using them, or because a staff member is enthusiastic about them. The question of whether they serve God's glory in the life of this community is never seriously asked.
The second failure is reflexive avoidance. Technology is treated as inherently suspect. New tools are rejected not because they fail the test but because asking the test feels like it might open a door to compromise. This produces churches that are not more holy, just less useful, still failing the test because the caution is not grounded in genuine discernment.
1 Corinthians 10:23-24 describes the right posture: "Everything is permissible, but not everything is beneficial. Everything is permissible, but not everything is constructive. No one should seek their own good, but the good of others." The test is not about personal preference or institutional comfort. It is about what builds up the people of God.
Making the Test a Habit
The 1 Corinthians 10:31 test is most useful when it becomes a standing question in church leadership conversations rather than a one-time framework applied at a policy retreat.
When a staff member proposes a new tool, when a vendor pitches a church management system, when a deacon asks whether the children's ministry should use an AI curriculum platform: ask the question. Does this glorify God? What would need to be true for it to pass? What would need to change in how we are planning to use it?
The question is simple. The answers it produces are honest. And the habit of asking it keeps the church's technology decisions grounded in the thing that actually matters.
How to Apply the Test When the Answer Is Not Obvious
Some technology decisions produce clear answers when the test is applied. AI for full sermon writing (fails: representation problem). AI for word study (passes: serves genuine engagement). But many decisions fall in the middle, where the answer depends on specifics of how the tool will be used.
For those decisions, a few follow-up questions help:
Who knows what? The test is often clarified by asking who knows what is happening and what they would think if they knew. If a congregation believes their pastor's pastoral letter was personally composed but it was written by AI, would they feel deceived if they learned the truth? If yes, the representation problem is real and the test fails. If the church knows AI is used for communications drafts and the pastor reviews and personalizes them, the test is different.
What is being optimized? The purpose of the 1 Corinthians 10:31 test is to ask whether a practice serves God's glory and the community's genuine good. Some technology decisions optimize for efficiency, which is not itself bad. The concern is when efficiency optimization conflicts with genuine care for people. Using AI to process member attendance data to identify people who have stopped attending and prompt a pastoral phone call optimizes efficiency in service of genuine pastoral care. Using AI to build behavioral profiles to maximize retention metrics optimizes efficiency in service of institutional metrics. The first passes; the second fails.
What does this communicate to people? Technology decisions communicate to the congregation about what the church values. A church that uses AI for administrative efficiency communicates that it takes good stewardship seriously. A church that uses AI to simulate pastoral presence communicates something different. Ask what a thoughtful member of your congregation would understand from seeing how this technology is used.
A Framework for Church Technology Decisions
The 1 Corinthians 10:31 test can be built into a decision-making process that leadership teams use routinely. It does not require a long meeting. It requires honest questions:
Does this build people toward God, or does it optimize for something else? Efficiency, engagement metrics, and cost reduction are not bad goals. They become problematic when they replace the question of whether people are genuinely being served.
Does this represent us honestly? Any technology that involves representation, communication that carries an implicit claim about who produced it or how, should be evaluated for honesty. The question is not whether AI was used but whether the representation is accurate.
Does this treat people as ends or as means? God's glory is not served by treating church members as data points to be optimized. Technology that helps staff love people better passes the test. Technology that reduces people to behavioral inputs for institutional optimization fails it.
What does this say to the watching world? Ephesians 4:17 frames the church's conduct against the backdrop of how "the Gentiles live." Technology choices that distinguish the church as a community that genuinely cares for people are part of its witness. Technology choices that make the church indistinguishable from any other organization optimizing engagement are not.
Comparing Technology Decisions Under the Test
Technology use · Glorifies God? · Notes
AI word study for sermon prep · Yes · Helps pastor engage the text more deeply
AI-generated full sermons, presented as pastor's own · No · Representation problem; bypasses genuine pastoral engagement
AI drafts for newsletter, pastor reviews and edits · Likely yes · Depends on whether review is genuine
AI to identify members who have stopped attending · Yes · Serves pastoral care
AI behavioral profiles to maximize giving · No · Treats members as means, not ends
AI for children's ministry curriculum planning · Likely yes · Helps teachers prepare; not substituting for the teaching relationship
AI-generated pastoral letters presented as personal · No · Representation problem
The pattern: AI as a research and preparation tool, explicitly serving the person doing genuine ministry, passes. AI as a substitute for genuine ministry or honest representation fails.
What This Comes Down To
"Whatever you do, do it all for the glory of God" (1 Corinthians 10:31) applies to eating and drinking and to church technology decisions.
The test cuts through cost-benefit analysis to the question that actually matters: does this build people toward God, represent the church honestly, and serve the community's genuine flourishing?
Follow-up questions when the answer is not obvious: Who knows what? What is being optimized? What does this communicate to people?
Both failure modes, uncritical adoption and reflexive avoidance, skip the actual test. The right posture is honest evaluation of each decision on its own terms.
---
Frequently Asked Questions
What does "do it all for the glory of God" actually mean in a church technology decision?
It means asking whether a technology choice builds people toward God, represents him honestly, and serves the genuine flourishing of the congregation. Glorifying God is not an abstract aspiration here. Paul applies it to eating and drinking, the most mundane acts possible, which means it applies to software decisions, communication choices, and AI tool adoption.
Is it wrong for a church to use AI for sermon writing?
The 1 Corinthians 10:31 test applied honestly suggests that fully outsourcing sermon creation to AI fails the test, because it involves a representation problem: the congregation receives content not produced by genuine pastoral engagement while implicitly believing it was. Using AI as a research assistant for the pastor who genuinely engages the text is a different matter. The distinction is honest use versus deceptive representation.
How should churches handle AI-generated content in communications?
Context determines the answer. A volunteer coordinator using AI to write a food drive announcement is different from a pastor sending AI-written pastoral letters as if they were personal. The test is always: what is being represented, and is that representation honest?
What are the two main failure modes the article identifies?
Uncritical adoption (using new tools without asking whether they serve God's glory) and reflexive avoidance (rejecting tools not because they fail the test but because asking the question seems risky). Both failures skip the actual test. The right posture is honest evaluation, not enthusiasm or fear.
How often should a church apply this framework?
As a standing habit in leadership conversations, not as a one-time exercise at a policy retreat. Every time a staff member proposes a new tool, every time a vendor pitches software, every time a ministry considers an AI platform, the question belongs in the room: does this glorify God for this community in this specific use?
Helpful Scripture resources
Contact & support
Email the FaithGPT team at hello@faithgpt.io or visit the contact page .
Explore FaithGPT
