DigitalMediaCon puts AI editorial policies on Christian publishers’ agenda

A planned session, not an adopted standard

DigitalMediaCon’s October 20–21 online program brings AI-use policies into the work of Christian publishing teams. The conference’s official agenda schedules Misty Phillip’s session on retaining a publication’s voice for noon to 12:45 p.m. Eastern Daylight Time on October 20. It lists written policy, disclosure language and editorial workflows among the intended learning outcomes.

The Evangelical Press Association produces the event, with the National Association of Evangelicals as co-presenter. The agenda describes a framework for deciding what AI should and should not handle, alongside a staged implementation plan. These are advertised objectives, not evidence that participants have adopted a policy or that the proposed workflows improve their publications. Source: digitalmediacon.com

This brief is based on the published program before the scheduled session. No presentation, recording or participant outcome has been reviewed. The agenda does not establish a common AI standard for every participating organization.

Make the permission specific

For a small Christian publication, the immediate question is what a policy would allow someone to change. Permission to use AI for editing is incomplete if an editor and a contributor understand editing differently. Correcting punctuation, shortening a paragraph and inventing a stronger ending are not interchangeable operations.

Consider a hypothetical ministry testimony submitted for a newsletter. A local policy might allow spelling suggestions but prohibit adding an experience the contributor never described. A separate decision would address whether the original testimony may be uploaded to an outside service at all. The person’s permission to publish a story should not simply be presumed to cover every processing method. This example is our editorial proposal, not a conference rule or a report of an incident.

A useful staff exercise would put one existing, non-sensitive sample through the proposed workflow and compare the original with the suggested changes. The team could mark which edits preserve the contributor’s meaning, which require the contributor’s review and which should be rejected. A polished result is not enough if nobody can explain what changed.

Truthfulness is more than a label

Ephesians 4:17–32 places truthful speech within a changed life together in Christ. Verse 25 connects honesty with membership in one body; verse 29 asks that speech serve the hearer’s needs. The passage does not prescribe publishing software, but it gives Christian communicators a reason to protect a contributor’s meaning rather than merely improve the sound of a sentence. Ephesians 4:17-32 (NIV)

An AI-assistance label cannot make an invented detail faithful to its source. A workable policy therefore needs both an outward explanation for readers and an inward account of permitted changes. The conference agenda offers an occasion to ask for that specificity; whether a team actually achieves it will require evidence from its subsequent practice.