United Methodist resource brings AI questions into the preaching calendar

A resource for seasonal preaching

A new Discipleship Ministries resource gives United Methodist pastors and lay worship leaders a way to address artificial intelligence from the pulpit without supplying a ready-made sermon. “Keeping Awake, Awaiting Dawn” connects seasonal Bible readings with questions about attention, work, relationships and responsibility. Its relevance this week is specific: the November 8 entry pairs Matthew 25:1–13 with reflection on readiness and spiritual formation.

The agency’s page metadata records publication on October 28 and an update on October 29. Its dated sections run from November into Christmastide, including Advent and Christmas services. The introduction describes theological starting points rather than a sermon manuscript or worship script. That distinction matters: this is material for preaching about AI, not a demonstration that software can undertake the preacher’s task.

The resource approaches these questions through Wesleyan theology and Christian community. It is a published teaching proposal, not evidence of congregational adoption, changed behavior or measured benefits. The reviewed page does not establish how churches have used it. Source: umcdiscipleship.org

Reading the passage before applying the analogy

For a congregation considering the November 8 material, a useful first step is to read the whole parable. In Matthew 25:1–13, both the wise and foolish bridesmaids fall asleep while waiting for the bridegroom. The difference is their preparation: some have brought extra oil and others have not. Readiness, rather than literal sleeplessness, is central to the story’s warning about an arrival whose timing is unknown. Matthew 25:1-13 (NIV)

That context helps prevent an AI discussion from becoming a sermon against screens with a Bible verse attached. The passage is not a prediction about chatbots. A Christian application to technology must explain its reasoning instead of presenting a modern analogy as the text’s original subject.

One practical distinction for worship leaders is between producing an answer and taking responsibility for teaching it. A fluent paragraph, whether obtained from software or another resource, does not by itself show that the speaker understands the passage, knows the congregation’s questions or can defend the application. Those remain questions for the person delivering the message.

A small preparation exercise could make that responsibility concrete. Before introducing an AI example, the preaching team could write down what the biblical passage says, what the contemporary example adds, and which factual claims need separate checking. If the illustration depends on a claim about employment, children or a company’s conduct, Scripture cannot establish that claim’s accuracy.

These are editorial suggestions, not practices already tested by the agency. They offer a way to use a timely resource without confusing a discussion starter with a finished sermon, or theological judgment with evidence of a technology’s effects.