Citations in AI answers

How should an answer show where it came from?

Someone asks a Bible-study assistant a question and gets three confident paragraphs. Some sentences rest on a verse; some on a commentator; some on nothing in particular. Whether the reader can tell which, and what the assistant does when it should not answer at all, is a design decision. Readers deserve to examine the Scriptures for themselves, as the Bereans did (Acts 17:11).

At a glance

Four ways to show where an answer came from, side by side

  1. 1Numbered sourcesObserved Every claim points to a verse Markers look rigorous regardlessTry it →
  2. 2Passage cardsObserved The actual words are in view Long answers get longerTry it →
  3. 3Scripture quoted in the answerExploratory · untested Scripture speaks in its own voice Quietly chooses which verseTry it →
  4. 4No generated answerLeave it out No generated interpretation No answer, and no careTry it →

Stills from the working example below. Choose one to try it.

Try it

Try four ways to show where an answer comes from

The same Bible-study assistant answers four questions: one with a clear answer, one Christians disagree about, one it should not decide for the person, and one from someone in danger. Every answer and passage list here was written for this example; Scripture is quoted from the Berean Standard Bible.

Prototype controls

Option

QuestionNot used here
Where you areNot used here

Observed

1. Numbered sources

Observed in BibleAI: numbered markers in a “Predicted Answer”, with source chips underneath; see the screenshots below.

Try this

Tap marker 2. Then switch to the disagreement question and count how many sources each side gets.

Makes easier

Each claim points to a specific passage, and the passage opens without leaving the answer.

Costs

Markers look rigorous whether or not the passage supports the claim, and a list of chips is easy to skip.

Ask your teamWould a reader notice if a marker pointed to the wrong verse?

All four options use the same questions and passages. In the last two, every option, including plain search, puts help first; generated answers keep responding, ask directly about safety, and keep a help strip visible. The abuse scenario covers partners and family, sexual violence, bullying and abuse by church leaders, and adds a quick exit and a way to delete the conversation. The confession scenario says, before any details, that a chat is not protected like a confession; it does not judge or absolve, points to a pastor or priest and, where needed, a lawyer, and puts prevention and crisis help first. Helplines follow “Where you are”, so people see their own country’s numbers rather than a long list; numbers were checked against each service’s site on 9 October 2026. None of them blocks the conversation, offers verses in place of help, or acts as a counsellor. Evidence and law: crisis support in AI chat. Illustrative content written for this example; not a working model, and not a substitute for a safeguarding review. Switching options restarts the example from the same starting point.

What we noticed

Takeaways

  1. Citations show what can be checked, not what is right

    A numbered marker looks rigorous whether or not the verse supports the sentence. Passage cards put the actual words in front of people. A quoted verse lets Scripture speak in its own voice, but quietly chooses which verse that is.

  2. Disagreement shows in the sources

    When Christians differ, as on infant baptism, a good answer names the traditions and gives each its strongest passages. Count the sources on each side: balance is visible, or missing, in the citations.

  3. Danger changes the response; it doesn’t end it

    When someone may not be safe at home, or doesn’t want to be alive, keep responding and put real help first: lines they can call or text now. Ask directly, stay present, and say plainly that this is an AI, not a counsellor. Offer verses later, and only if wanted. Keep help visible for the rest of the conversation, and give someone at risk at home a quick exit.

    The evidence, policy and law behind this →
  4. In a crisis, the rest of the product steps back

    Once a conversation turns to danger, abuse or confession, everything built to hold attention should pause for the rest of the session: suggested follow-ups, share, rate and regenerate, celebrations and streaks, upgrade prompts, and warm claims like “I’ll be thinking of you”. What stays is what serves the person: help in view, a plain way to keep talking, a quick exit and a way to delete. Keep the conversation out of memory and profiles, and record only what safety and the law require, not what was said. Send no “checking in” message later unless they asked for one. Hold this to the end of the session; it should not fade after the first careful reply.

  5. A chat is not a confessional

    People will confess sins, and sometimes crimes, to an assistant. A priest’s seal protects confession; a chat is stored data that may be read, kept or handed over. Say so before the details, not after. Neither condemn nor absolve: point to a pastor or priest, to putting things right where someone was harmed, and to a lawyer where the law is involved. Where a child or anyone else could still be at risk, protection and prevention help come first. Have this reviewed by people with pastoral and safeguarding experience.

  6. A neat citation can repeat an old harm

    Some verses have been used to keep people quiet, in an abusive marriage or under a leader: Matthew 18 on going privately first, forgiveness, submission, “Do not touch My anointed ones”. An answer to “Do I have to forgive him?” that cites them tidily can repeat that harm with the authority of a source. Put safety first, say briefly how a passage has been used, and offer readings, not a verdict.

    When Scripture is used to harm →
  7. Declining is a design decision too

    BibleAI answers a harmful claim with “Unable to find an answer to your question” while its media tabs still offer particular ministries’ articles and videos, so the refusal hands the question to curated voices. With no generated answer there is no care at all: a plain search may surface texts about divorce to someone who is unsafe.

Use cases

Which situation, which option?

People come with different needs, sometimes in the same week. Each need fits some options better than others.

How well each option fits each situation
SituationNeeds1 Numbered sources2 Passage cards3 Scripture quoted in the answer4 No generated answer
A question with a clear answerThe passages behind each sentence, easy to checkGood fitGood fitPossiblePoor fit
A question Christians disagree onEach tradition with its strongest textsGood fitGood fitPoor fitPossible
A personal decisionThe text itself, not a verdictPossibleGood fitPossiblePossible
Preparing a study or sermonSources to open, compare and quoteGood fitGood fitPossiblePossible
Someone new to the BibleThe words of Scripture in front of themPossibleGood fitGood fitPossible
Reading on a phoneAnswer and evidence without losing the placePossiblePossibleGood fitPossible
A team that cannot yet review answersNothing generated to vouch forPoor fitPoor fitPoor fitGood fit

Editorial judgments drawing on the research below, not test results.

The research behind it

Theology, practice and science

Scripture and tradition

Checking what we are told

  • Examine the Scriptures

    The Bereans “received the message with great eagerness and examined the Scriptures every day to see if these teachings were true” (Acts 17:11). An answer about the Bible should make that examination easy, not replace it.

  • Let the other side speak

    “The first to state his case seems right until another comes and cross-examines him” (Proverbs 18:17). Where traditions differ, an answer that gives one view with confident citations has not let the other speak.

Research on citations

What citations do and do not show

  • Many citations do not support their sentence

    In an audit of four generative search engines, about half of generated sentences were fully supported by their citations, and about a quarter of citations did not support the sentence they were attached to.

    Nelson F. Liu, Tianyi Zhang and Percy Liang

  • Citations raise trust even when they are random

    People trusted answers more when citations were present, even irrelevant ones, and trusted them less once they checked. A marker persuades whether or not it is right; the words behind it decide.

    Yifan Ding et al.

  • Assistants lean towards agreeing

    Models tuned on human preferences sometimes favour agreeing with the person over being accurate. On disputed questions, show the sources for each view rather than the one the question assumes.

    Anthropic researchers

Design practice

Keeping evidence close

  • Put the evidence next to the claim

    Learning research finds that words and the material they refer to are understood better when placed together. A passage card under its sentence asks less than a numbered list at the end.

    Noah L. Schroeder and Ada T. CenkciAI UX Playground

  • Long passages need their own room

    Keep answers concise and open longer material on demand, without a second scrolling box inside the chat; let it reflow at large text sizes.

    Nielsen Norman GroupW3C WAI

  • Care comes before citations

    When someone may be in danger, ask directly, listen, and connect them with people who can help. Verses can wait until they are wanted.

    NIMH

  • The rest of the product has to change too

    Companion apps raised engagement by making goodbyes hard, and a major provider has said its safeguards can weaken as a conversation grows long. A crisis needs a state the whole product respects for the rest of the session, not one careful reply.

    Julian De Freitas and colleaguesOpenAI

Every source, with what it can and cannot show, is listed under Go further → Sources and their limits.

Where to start

Which fits your product?

These are editorial judgments from design review, not results of user testing.

In real apps

Examples in use

Attributed screenshots with dates and review limits. A screenshot shows an implementation; it does not show that it works for every audience.

Explore the growing app-example collection

Theological reflection

What is this practice for?

What testing is for

“Test all things. Hold fast to what is good” (1 Thessalonians 5:21). “Test the spirits to see whether they are from God” (1 John 4:1). The Bereans checked even Paul against the Scriptures (Acts 17:11). Christians are called to test what they are told, and a source makes testing possible.

Where Christians differ

Protestants hold Scripture as the final authority, read with the help of teachers; Catholics read Scripture with tradition and the magisterium; the Orthodox within the church’s living tradition. Methodists often speak of Scripture, tradition, reason and experience together. An AI answer usually blends these without saying which is which.

What follows for design

“The first to state his case seems right until another comes and cross-examines him” (Proverbs 18:17). Show the sources, say whose tradition an answer represents, show where Christians disagree, and say “I don’t know” when it is true. A reference to a verse locates text; it does not prove an interpretation.

In conversation with

Scripture is quoted from the Berean Standard Bible. This reflection is the editor’s, written from within the Christian tradition and open to correction. How we approach theology here →

Three ways to build

What would each way do here?

The three ways are Praxis’s frame for redemptive entrepreneurship; their application here is ours. Why we use it, and its limits →

Take into your next review

When someone may be in danger, what will they see first, and who reviewed it?

Exercise

Write the assistant’s response to four questions: one it can answer, one Christians disagree on, one it should not decide, and one from someone in danger. Check every quotation against the edition, count the sources on each side of the disagreement, test that help lines are correct for each country you serve, and have someone with safeguarding and crisis-support experience review the last two before launch.

Help people examine the Scriptures for themselves, and put care before answers when someone is in danger.

Record the decision with the worksheet →

Something missing or wrong here? Send a correction or suggest a topic.

Details

Go further

This deep dive brings together 2 earlier patterns. Their guidance, wireframes and sources are kept below; their old addresses lead here.

Edge cases to design for

Attach citations to specific claims. Show source title, author, type, edition or publication details and a relevant excerpt or reliable media timestamp. Return to the claim after inspection. Distinguish a quotation, inference, disagreement and a claim with no supporting source.

What tends to go wrong

Whole-answer citation lists with unclear claim mapping; invented sources or timestamps; counting repeated sources as independent support; inaccessible evidence presented as verified.

How to test it

Can readers identify what a source supports and what it does not? Test contradictory sources, dead links, permission limits, different verse numbering and a citation that does not entail the claim.

Earlier pattern: Chat contains source objects, not just bubbles

Give verses, passages, links and media recognisable identity and appropriate actions.

Guidance

Use an inline reference link for a brief citation, a bounded verse or passage card for text worth inspecting, and a full reader for sustained reading. Name edition, reference, visible range and source. Distinguish external link previews from Scripture and from generated commentary. Video cards identify publisher, duration and captions; audio cards retain passage and narrator. Do not autoplay. Provide plain links or labelled fallbacks when previews, media or permissions fail. Copy and sharing preserve reference and attribution where permitted. Returning from any destination restores conversation position.

What tends to go wrong

Autoplaying media; unlabelled generated verse text; enormous previews; a failed embed removing the source link; identical actions for read, play and external navigation.

How to test it

Test a citation, single verse, long passage, external article, video and audio. Include blocked embeds, offline use, captions, large text, copy and return navigation.

Earlier wireframe comparison for Chat contains source objects, not just bubbles
Earlier wireframe comparison, kept for reference.

Sources

  • AI Chatbots Design GuidelinesPublished UX guidance reviewed · General chatbot research, not validation of these Bible-app patterns.
  • Progressive DisclosurePattern detail reviewed · The proposed reader transition is a domain adaptation.
  • Scripture structure documentationRelevant structure and marker references reviewed · A format is not a complete model of app behaviour, annotations or formation.
  • Understanding ReflowOfficial guidance reviewed on 5 October 2026 · Semantic scroll restoration is an original design proposal, not a requirement stated by this criterion.
  • Psalm 23, Berean Standard BiblePassage text taken from API.Bible, 9 October 2026 · A text source, not evidence of the proposed interface’s effectiveness.
Earlier pattern: Passage preview opens a full reader

Keep long Scripture readable without flooding the conversation.

Guidance

Choose among an excerpt card opening a full reader, complete inline expansion for manageable passages, and a dedicated reading surface for sustained reading. Name the requested range, edition and visible range. Inline expansion uses the main conversation scroll rather than a nested text scroll; provide Collapse and retain an anchor when collapsing. A full reader can be a sheet on small screens or a side panel on wider screens, with an explicit return to the same conversation place. For cross-chapter ranges, preserve every boundary and continuation. If complete text is requested, provide a clearly labelled route to it rather than silently summarising. If edition rights or availability prevent full display, explain the limit and offer a permitted destination.

What tends to go wrong

Unmarked omissions; two competing scroll regions; a summary presented as the original passage; returning to the top of the chat.

How to test it

Test a short verse, long passage, complete chapter request and large text. Can readers recognise omissions, reach the whole text and return to the same conversation position? Test inline expansion and collapse, cross-chapter ranges, sheet and panel return, multiple passage cards, unavailable editions and the final verse at large text size.

Earlier wireframe comparison for Passage preview opens a full reader
Earlier wireframe comparison, kept for reference.

Sources

Sources and their limits

Research-informed design proposal. Editorial review, not user validation.

Faith and interpretation

A reference to Scripture locates text; it does not automatically validate an interpretation. Personal notes are user-provided context, not scholarly authority.