← All insights

The Prompt Is Not the Work: AI Needs Accountable Release

Institutions should evaluate AI productivity across the complete path from task definition to accountable release, explicitly resourcing the human work of steering, verification, traceability, contextual repair, representation, approval and non-delegation rather than treating generated drafts as finished work.

The most impressive moment in generative AI is often the first one: a blank page becomes a polished draft in seconds. That visible speed encourages institutions to call the result productivity. Yet a draft is not a decision, a lesson, a policy, a sermon, a report or a service. It becomes useful only after someone makes it truthful, contextually credible and safe enough to release.

A research preprint posted on 22 October 2026 offers unusually relevant African evidence. Drawing on 21 semi-structured interviews with 27 workers across 21 small and medium-sized businesses in Kenya and Nigeria, the researchers found that drafting was rarely the hardest part of generative-AI use. Workers had to steer outputs, compare tools, reconstruct sources, verify claims, repair local-language and contextual failures, correct representations of African people and places, and decide what could not responsibly be delegated. The authors describe this boundary-facing labour as release work. Abdulhamid, Nyairo, Ankrah and O'Neill, 2026

This is recent qualitative preprint evidence from situated cases, not a peer-reviewed prevalence estimate and not a representative account of all Kenyan, Nigerian or Global South work. The interviews were conducted from July to October 2023, so the publication is new but the fieldwork is not contemporaneous with the latest models. Its contribution remains important: AI does not remove the work between a draft and a defensible outcome. It redistributes that work, often making human accountability less visible precisely when automated production becomes more visible.

Release work begins where generation ends

Release work is the disciplined passage from plausible output to authorised use. It asks whether the task was framed correctly, whether the source can be traced, whether the claim is supported, whether the language fits the audience, whether anyone is misrepresented, whether confidential information has been exposed and whether a competent person is willing to take responsibility for circulation.

The Kenyan and Nigerian participants reportedly used generative AI as draft labour, engaged in repeated steering, switched and compared tools, built verification gates and repaired context misfit. Those practices challenge a simplistic story in which access to AI automatically democratises skilled work. Access may lower the barrier to producing a first version while leaving the harder barriers—credibility, trust, specialised judgement, local knowledge and accountable release—firmly in place.

Institutions should therefore distinguish at least four states: generated, reviewed, approved and released. A document may be generated but unverified; reviewed but still inaccurate; approved for internal discussion but not for public use; or released under the authority of a named person. Collapsing these states invites errors to travel with institutional credibility they have not earned.

The productivity calculation must include the whole workflow

Claims that AI saved time often measure the speed of drafting while ignoring the time spent correcting fabricated citations, restoring context, changing tone, testing local language, checking policy versions, protecting confidentiality and explaining the result to those affected. This is not an argument that AI produces no efficiency. It is an argument for honest accounting.

A whole-work measure should record time to first draft, verification time, repair time, approval time, correction after release, new risks, quality, accessibility and the distribution of labour. It should ask who absorbs the checking work. If a system saves a manager twenty minutes but adds an hour of invisible verification for a junior worker, the institution has shifted cost rather than eliminated it.

The International Labour Organization's 2026 report concludes that AI is currently more likely to transform tasks and work organisation than eliminate employment on a large scale. It warns that faster processing may produce higher output expectations, tighter deadlines and compressed recovery time rather than reduced workloads. AI can support professional judgement, but it can also standardise procedures, reduce autonomy, intensify surveillance and weaken entry-level opportunities for skill acquisition. This is an official global labour assessment of emerging evidence and technical potential, not a prediction of identical outcomes in every workplace. ILO, 2026

Context misfit is a governance issue, not cosmetic editing

A system can produce grammatically fluent material that misnames a place, imports an unsuitable regulatory assumption, stereotypes an African professional, weakens a proverb, mistranslates a theological term or recommends a service that does not exist locally. These are not always minor style problems. They can distort meaning, exclude people and damage trust.

Localization is therefore more than changing spelling or currency. It requires knowledge of language, history, institutions, infrastructure, faith, law, professional norms and lived conditions. Responsible release asks whether the output can be understood and used by the people for whom it is intended—and whether those people would recognise themselves truthfully within it.

UNESCO's AI for Africa, by Africa brief reports that global large language models remain poorly adapted to African languages and links this to risks of reduced usability and representation. It also identifies major gaps in connectivity, research computing and institutional ethical capacity. These are continental policy and capacity estimates, not model-by-model performance tests. They reinforce the need for local evaluation rather than assuming that global fluency equals African fitness. UNESCO, AI for Africa, by Africa

Curriculum should teach the path from prompt to release

AI education often stops at prompt construction, output criticism and disclosure. Learners also need to practise the complete release pathway: define the purpose, identify the audience, gather authoritative sources, set data boundaries, generate a bounded draft, verify every consequential claim, reconstruct missing traceability, test local fit, check representation, revise, obtain appropriate approval and plan correction.

A useful learning sequence is: independent task framing → source assembly → bounded generation → comparison and steering → verification → contextual and representational repair → disclosure → oral or practical defence → authorised release → feedback and correction. Each stage produces evidence that an assessor or reviewer can examine without requiring indiscriminate surveillance of private activity.

Students should encounter deliberately imperfect material. Ask them to repair an outdated institutional rule, an invented citation, an imported case that fails locally, a mistranslated ministry concept or an image that misrepresents the community. Competence becomes visible in what the learner notices, refuses, corrects and can defend—not in how quickly a first draft appears.

Assessment must distinguish production from ownership

A polished submission cannot by itself establish that a learner understands the subject or owns the judgement. AI-resilient assessment should collect several forms of evidence: initial independent work, source records, reasons for accepting and rejecting suggestions, annotated revisions, oral defence, transfer to an unfamiliar case and performance in context.

The assessor should probe the release decision. Which claim carried the greatest risk? Which source controlled the judgement? What failed to fit the context? What information was excluded from the system? What would require professional referral? What correction would be issued if the work proved wrong? These questions test responsible judgement rather than memory of an AI policy.

Not every draft should be released. The capacity to withhold, escalate or start again is a positive learning outcome. A student who recognises that available evidence is inadequate may demonstrate greater competence than one who produces a confident answer on schedule.

Teachers and reviewers need protected time for accountability

Generative AI can increase the volume of material presented to educators, editors, supervisors and governing bodies. Without workload redesign, these people become a verification layer for more output at the same staffing level. Quality then depends on unpaid or hurried release work.

Institutions should specify which roles may draft, review, approve and publish. Reviewers need access to the underlying sources, criteria appropriate to the risk and authority to return or stop work. High-stakes review should not be assigned to the least powerful employee simply because that person understands the local context or speaks the relevant language.

Teacher development should include case-based practice in traceability, source verification, multilingual review, representation, data protection and correction. The institution should measure reviewer workload and error rates before promising that AI will release educators for more relational work. Saved time becomes educational value only when it actually returns to teaching, feedback, mentoring and professional learning.

Theological education must form accountable interpreters

A generated theological paragraph can sound orthodox while combining traditions carelessly, citing a work that does not exist or applying a text without regard to its literary and social context. Theological release work begins with Scripture and continues through identifiable scholarship, doctrinal accountability, African contextual engagement and the life of a worshipping community.

Learners should not ask AI to generate a sermon, verify its own claims and certify it as ready to preach. They may use bounded assistance for questions, structure, comparison or language support, but a competent person must examine the biblical text, trace sources, consider alternative interpretations, test local application and accept responsibility for the message.

The Lausanne Movement's Seoul Statement presents technology as part of human vocation while warning that innovation is shaped by sin and can deceive, manipulate, dehumanise or become idolatrous. It calls Christian technology use to truthfulness, faithful contextualisation, human dignity, love, justice and discernment about when and where adoption serves the gospel. This is a global evangelical theological commitment, not empirical evidence of ministry outcomes. Lausanne Seoul Statement

CBTE should assess release competence in ministry context

Competency-Based Theological Education can make release work observable because it evaluates ministry performance in context rather than relying only on completed academic products. The public CBTE framework emphasises contextual learning, integrated formation, collaboration and demonstrated proficiency. CBTE, About

A learner preparing an AI-assisted teaching resource should be able to define its ministry purpose, protect excluded information, identify source authority, verify theology, adapt language, obtain consent for personal stories, disclose material synthetic content, teach the material, receive community feedback and issue a correction. Mentors should witness the learner's judgement as well as inspect the artefact.

Knowing, being and doing meet at the release boundary. Knowing identifies sources, risks and contextual requirements. Being demonstrates humility, truthfulness and willingness to delay or correct. Doing produces, reviews, communicates and repairs work responsibly. A portfolio that hides this pathway may document output without demonstrating competence.

Digital ministry needs a release rule before a content engine

Churches can now produce devotionals, captions, translations, images, appeals, lesson plans and sermon clips at unprecedented speed. The capacity to generate should not become permission to publish. Every ministry needs a release rule proportionate to content, audience and possible harm.

Public biblical teaching requires theological and factual review. Translation requires competent linguistic and cultural review. Synthetic voices and images require disclosure. Testimonies require consent and truthful preservation of the person's meaning. Material involving children, counselling, safeguarding, health, conflict, discipline or crisis requires direct competent human responsibility and often professional referral.

No system should release prophecy, spiritual diagnosis, pastoral counsel or a claim of divine authority. No automated service should present itself as a confidential pastor. A person must be able to reach a competent human, challenge an error and use a non-digital route. Ministry efficiency should be measured by whether time and attention return to prayer, study, visitation, mentoring, reconciliation and care.

Governance should make release authority visible

Every consequential AI-supported workflow should identify a release owner—the human role with authority and competence to approve use. This person should not be a ceremonial signatory who lacks access to the evidence, cannot question the system or is punished for delaying publication.

A release record can document purpose, audience, sources, system and version, data used, excluded information, material AI contribution, verification, local-language review, representation check, conflicts, approval, publication channel, correction route and retention. The detail should be proportionate: a private brainstorming note does not require the same control as a public policy, learner grade, counselling communication or institutional statement.

Providers should be evaluated on more than generation speed. Procurement should examine source access, logging, data use, version control, export, local-language performance, accessibility, correction, incident support, portability and exit. Institutions should retain the ability to continue essential work manually when a system fails or a contract ends.

African AI policy must protect workable participation

The African Union's Continental AI Strategy calls for AI adoption by small and medium-sized enterprises, public services and high-value sectors while also demanding skills, diverse datasets, information integrity, ethical principles, cultural and linguistic inclusion and protection from harm. It explicitly warns that applications developed elsewhere may lack contextual and infrastructural fitness for Africa. This is continental strategy and policy direction, not evidence that implementation gaps have been closed. African Union Continental AI Strategy

The new Kenya–Nigeria study helps translate that policy concern into everyday work. Workable participation is not merely possession of an account or ability to generate text. It includes the capability, time, authority and resources to make output reliable enough for real clients and communities.

Policy and investment should therefore support local-language data, professional review, research partnerships, worker learning, accountable procurement and mechanisms for correcting representational harm. African participation in AI must include the power to define what is fit to release, not only the opportunity to consume or repair systems designed elsewhere.

Leaders should adopt a release-work ledger

Before expanding an AI use, leaders should record the whole workflow. What legitimate outcome is sought? What did the system generate? What steering was required? Which sources were checked? What traceability had to be reconstructed? What contextual, linguistic or representational repairs were made? Who performed them? How long did they take? Who approved release? What happened after publication?

The ledger should also capture displaced learning. Did a junior worker lose a task through which professional judgement was previously developed? Did an educator gain time for learners or merely receive more submissions to check? Did local-language reviewers become an invisible safety layer without authority or recognition? Did output targets rise because drafting became faster?

A trustworthy business case includes these costs and effects. It values avoided harm, retained competence and contextual quality alongside speed. It also accepts that some high-risk uses may remain unjustified even when generation is cheap.

What institutions should do in the next ninety days

First, select one real AI-supported workflow and map it from task definition to release. Separate generation, review, approval and publication. Identify every point where local expertise, verification, consent or professional judgement enters.

Second, measure the total work. Compare time, quality, errors, reviewer burden, correction and staff learning with the previous process. Do not count faster drafting as a benefit until downstream effects are visible.

Third, establish non-delegation boundaries. Name the decisions, data and relationships that must remain under competent human responsibility. Give reviewers authority to stop release and make escalation easy.

Fourth, test context fit with intended users, including language, accessibility, gender, disability and local institutional knowledge. Finally, create an accessible correction route and review the evidence after a defined period. Continue, redesign or withdraw the use according to demonstrated value rather than enthusiasm.

The research agenda should follow the hidden labour

Future research should quantify release work across sectors without reducing it to time alone. Relevant outcomes include verification accuracy, traceability, contextual fitness, language quality, representation, correction rates, reviewer workload, skill retention, autonomy and the distribution of responsibility across organisational levels.

Longitudinal studies should examine whether repeated use develops or weakens professional judgement. Comparative designs could evaluate unaided work, unstructured AI use, AI with verification training, and AI with explicit release roles, workload protection and correction systems. Researchers should observe what actually happens after a draft appears.

African studies should include small enterprises, education, public service, churches and civil society; rural and urban settings; Anglophone, Francophone, Lusophone, Arabophone and African-language contexts; and workers whose repair labour is commonly overlooked. Participants should help define what credible local output means, and findings should return to the communities whose expertise made the systems workable.

Accountability is part of the work

Generative AI can be valuable draft labour. It can reduce the friction of beginning, offer alternatives, support translation and help small organisations attempt work that once required greater resources. Those benefits become real only when the resulting material can be trusted in context.

The prompt is not the work. Neither is the first output. Work includes the judgement that makes a draft defensible, the local knowledge that repairs misfit, the restraint that refuses an unsafe release and the responsibility that remains when an error reaches another person.

Institutions should make that labour visible, teach it, resource it and govern it. When AI accelerates generation, human accountability does not become less important. It moves to the release boundary—where education, ministry, leadership and public trust are either protected or quietly surrendered.

AI Accountability & Release Work

Govern the work between generation and release

Map one AI-supported workflow, measure its hidden verification and repair labour, define non-delegation boundaries and make every consequential release traceable to a competent human owner.

Design an accountable release workflow