What we believe: your church's beliefs, in your own words
Write down what your church believes, approve it, and let your team, Pad and your website read it in your own words.
is where your church sets down what it believes, and how it sounds, in its own words and at its own pace. PraisePad never writes it for you: every word is yours, or a creed or confession you chose, and nothing is used until one of the people who look after it approves it. Once a version is approved, everyone on the team reads it from the account menu (the circle with your initial), under ; Pad answers questions about it with your own sentences, word for word; the drafts PraisePad's AI writes for your church follow it; and, if you turn it on, the topics you marked Website get a page on your church site (below). It's for churches: it isn't offered to a library of your own (Solo).
Open in PraisePad to try itWho looks after it
Your church's owners, and up to six people an owner names, like a pastor or an elder. They don't have to be admins. Someone named opens from the account menu and presses , or once there's a draft.
- Only these people see the draft and its history. They write, confirm and approve.
- Everyone else on the team reads the approved version. Giving-only people don't see it.
- An admin who isn't named reads the approved version and sees who looks after it.
Write it down
The first time, choose one of two ways to begin.
. Choose , , or . For your website, type the page's address and press : PraisePad reads that one page, once, and nothing else on your site. A file can be Word, PDF or text, and it's read on your device. Creeds and confessions have their own article. Then choose how your words become topics. Whichever you choose, not a word is changed:
- , offered when your statement has headings of its own. Words above your first heading go under .
- : AI says which topic each line belongs under. It moves whole lines, and lines that fit no topic wait under . A heading of yours that names a topic PraisePad already has, like Baptism, goes into that topic, above its words. A statement holds 30 topics, counting the ones you already have and Not sorted: past that, a heading becomes a line under the topic before it. One sort takes up to 600 lines, so sort a longer statement a part at a time.
- , with no AI: your words become one topic, titled "What we believe".
. One topic a screen, like "What does Grace Church believe about the Bible?", with four answers: , , , or . goes back to the overview with everything kept, and the overview then offers to pick up at the next topic. The questions cover God, The Bible, Jesus, The Holy Spirit, People and sin, Salvation, The church, Baptism, Communion, What's to come and Our tradition.
Every word saves a moment after you stop typing, so you can stop halfway and come back next month. There's no deadline, and PraisePad won't nag you. If you're offline, your words are kept in that browser and save when you're back. If a save doesn't land, a line by the box says so, with , and PraisePad tries again by itself every 20 seconds while the page is open. Words kept in the browser belong to the person who typed them, and signing out clears them.
A topic holds up to 6,000 characters. Past that, a line says how long it is, like "A topic holds up to 6,000 characters. This is 6,412. It isn't saved until it fits."
The overview and a topic's page
Once there are topics, the edit page is an overview. says which version is in use, or that nothing is approved yet. lists each topic with its first line and where it stands, like , or .
- adds one of the usual topics, or one of your own. The ⋯ button on a row has and .
- says whether your statement is in English or Spanish.
- Open a topic to read it as your team will. opens its title and its words. shows each line with , which moves it to another topic exactly as written.
- is optional: up to two of the topic's own sentences, tapped and kept exactly as written, for places that need a short answer. When a statement is too long for a writer to read whole, it reads the longest topics' short versions instead. Only sentences that end with a full stop, a question mark, an exclamation mark or an ellipsis are offered, and a list with the line that leads into it counts as one sentence.
- makes a topic one to ask a person about. Your team's page says who to ask.
- starts at Team. A topic marked Website can go on your church site's page and be quoted by your site's chat (below, under On your website); a Team topic never leaves your team. It matters to AI writing too: words that may go on your website, like a sermon's description, read only the topics marked Website.
- takes it out of your draft.
If someone else changes a topic while you're typing in it, a line says who, with . Press it and the newer words load; the words you typed stay in a box of their own, with .
Read, confirm and approve
The main button always names the next step. While topics wait to be read it says, for example, "Read Baptism next":
- Read the topic as your team will read it.
- Tick "I've read this, and it says what Grace Church believes."
- Press . moves on and leaves the topic unconfirmed.
While you read this way, the topic's other controls are folded away under , so the words and the tick come first.
Changing a topic later clears its tick, and its row says . When every topic with words is confirmed, the main button says and its number. Before you approve, it lists the topics that change, with , and takes a short note if you like. The others who look after it get an email.
Until a version is approved, nothing is used and the team sees nothing. After that the team reads the approved version, Pad and AI writing follow it, and your draft stays with the people who look after it until the next approval. A draft is never read by AI writing, however far along it is.
How we sound
How we sound, a card on the overview, opens its own page. It tells PraisePad's AI how your church writes, so its drafts sound like you. It's part of the same statement: its changes join your draft, and the main button then names the next version to approve. Every part is optional, and it saves as you go.
- Tone: up to three words from a list of sixteen, like Warm, Plain, Reverent or Welcoming. Under the row, each word you choose shows one line of what it asks of a writer. A fourth isn't taken: it says "Three at most".
- In a sentence: optional, up to 200 characters, like "We sound like a family that's glad you came."
- Our words: press for a pair of Say and Instead of, with a Why if you like: "guests", not "visitors"; "Pastor Matt", not "Matt". Up to 30 pairs; takes one away. A pair is used once both its words are filled in. PraisePad's own word list still applies after yours.
- When you write about God: He, Him, His, or he, him, his, or Either.
- The Bible we read from: writers name it after a reference, like John 3:16, ESV, and never write out a verse. Nothing is chosen until you choose it. If your church set a usual Bible in Present's settings, the page offers it in one tap, like Use the King James Version, Present's usual Bible. The two stay separate settings: if they differ, the page says which Bible Present shows, with a link to Present's settings.
- Our welcome words as the example: your site's welcome, with a switch that's off until you turn it on, so writers read how you already sound. Without welcome words on your site, there's nothing to switch on.
rewrites your latest announcement or event words in the voice on the page, saved or not, or a sample if you have none, and shows the original beside the new words with each change marked. It uses a tiny part of your AI allowance.
The foot of the page says which version's voice writers use now, and that a change waits for the next approval. With Present, a line there points to Present's settings, where your church chooses what pictures made with AI may show. Pictures and words keep their own settings.
What reads it
Once a version is approved, AI drafts PraisePad writes for your church read its voice: announcement slides, an event's description, a thank-you to a volunteer, a sermon's description and its recap with the email, posts and handout, the Kids welcome email and the note to a parent after an incident, the line under your name, What to expect and bulletin lines on your site, and the one-sentence summary in the Monday Kids email. Pad in the app and your site's chat take its tone and its words too, inside their own rules, and they answer questions about what you believe from it (below).
What you believe is read only where it helps and is safe:
- A sermon's description and small-group questions, which may go on your website, read the topics marked Website.
- The sermon helper's , , and read every approved topic.
- A topic with no words is silence: no writer says anything about it, or works out what your church might believe.
- A confession held whole goes to a writer as its name and credit, your notes, and its part titles, never its whole text.
Some things never read it, because they work on someone's own words or aren't about your church: the sermon helper's , and , tidying wording, translating your words into Spanish, imports, the line on what each song is about, and . Songs are never judged by what your church believes.
Under each draft that read it, a quiet line says so, like "In Grace Church's voice". When the draft read your beliefs too, the line goes on "with what you believe (version 3)", and those words open your team's page. Before your church has an approved voice, a person who looks after it sometimes sees "In PraisePad's voice. Set yours" instead, at most once a week: Set yours opens How we sound, and Don't show this again keeps it away on every device.
Pad and your site's chat quote you
Asked about what your church believes, Pad and your site's chat never say it in their own words. PraisePad puts your approved sentences in, exactly as written, in quote marks, and the AI only finds which ones answer.
- Pad, in the app, for everyone on the team who reads your team's page: "What do we believe about baptism?" gets "Here's what Grace Church says about baptism:", then the topic's short version or up to two of its sentences, then Open what we believe, which opens that topic on your team's page, and a quiet line like "Approved by Grace Church, version 3". A confession you hold to whole is quoted by its section, with its credit. See Ask Pad.
- Your site's chat quotes only topics marked Website, and only while your website's page is on, with a link to that topic on the page. In Spanish it quotes your approved Spanish; where a topic has none, it says so and gives the English. See your site's chat.
- An "Ask our pastor" topic: Pad says "That's one to ask Pastor Matt about." Your site's chat never names anyone: it says it can't speak for your church on that, with your phone number.
- A topic you haven't written: Pad says "Grace Church hasn't written about that in what it believes. Ask a pastor." One of the people who look after it also sees Add it to what you believe, which opens the edit page. Nothing is ever worked out from your tradition, your songs or anything else.
- An argument or a comparison ("Isn't that wrong?", "Do you believe the same as First Baptist?") gets your own words again, never a debate, and points to a pastor for a conversation about it.
Once a version is approved, Pad's hello names what your church believes, and Try asking can offer a question about your first topic, like "What do we believe about baptism?". The quote always arrives whole with the answer: it's never typed out as if it were being written.
On your website
On the overview, the card turns on a What we believe page on your church site. It's off until one of the people who look after it turns on ; a support visit can't. The card says which topics are marked Website and, once the page is up, opens it in a new tab.
- The page shows the topics marked Website, in your order, each as its own card, with Jump to at the top, a creed in its own quiet style with its source line, credit lines where a text needs one, and "Approved by Grace Church" with the date. Never a draft, a Team topic, or anyone's name.
- Each topic has its own link, which your site's chat uses: someone who follows it lands on that topic, lit for a moment in your color.
- It's linked from Plan a visit and the foot of every page, and listed for search engines with your other pages.
- Turning it on needs nothing approved. Until a version with a Website topic is in use and your site is published, the card says it's on but nothing shows yet: nothing links to the page, and search engines are asked to leave it out. After Stop using it, the page goes away.
- Each switch on or off is a line in the activity log.
What people asked, on the overview, shows what visitors asked your site's chat about this month, by topic, like "Baptism (3, answered), something you haven't written about (2, not answered)", each topic by its title. It's counts only, never anyone's words. When people ask about something you haven't written, that may be a topic to add.
In Spanish
Each topic's page has (or , when your statement is written in Spanish). Press Write it in Spanish to write the topic in the other language yourself, or Draft the Spanish (Draft the English for a Spanish-first church): AI translates that one topic's words, and you read the draft, then press or . Nothing it wrote is kept until you press , and you can change it after. If a draft can't be made, a line by Draft the Spanish says so; pressing it again is the only way to ask again. Once there's Spanish, Draft the Spanish again from your words makes a fresh draft, and Take the Spanish out removes it. An "Ask our pastor" topic has no Spanish to write, and a confession held whole gets only a Spanish title and your notes in Spanish: press Write it in Spanish. Drafting uses a small part of your AI allowance, about a cent a topic. Whatever you write or keep is part of your draft, and nothing is used until it's approved with the next version. A translation AI drafted says so, like "Translated with AI, read by Pastor Matt" (the person who approved it), on your team's page and in History.
Your website's page in Spanish shows the Spanish where it's approved and, marked, the English where it isn't. A confession held whole shows its name and your notes, with "The confession's text is in English."
What AI does, and doesn't
AI helps in five places, only when one of the people who look after it presses its button. It never writes a word of what you believe: four never write anything that's kept, and a Spanish draft is kept only once you've read it, marked as AI's.
- moves your own lines under topics.
- , on the overview, looks for lines that may say different things, are hard to follow, or are said twice. It never changes your words and doesn't judge what you believe. Each note has , which opens the topic with those lines lit, and . The notes are kept until your words change, and the button shows the cost.
- , under when a topic has three or more sentences, lights the two it thinks answer best. You tap to keep them.
- , on How we sound, shows what your voice does to words your church already wrote. Nothing it writes is kept.
- Draft the Spanish, on a topic, translates that topic's own words for you to read and keep or not (above, under In Spanish).
These use your church's AI allowance: see the AI allowance. On the Free plan, everything else here works without them: keep your own headings or move lines yourself, pick a short version's sentences by hand, and write the Spanish yourself.
History
, on the overview, lists every approved version, newest first, with who approved it and when. A version is never changed or deleted, and it keeps its approver's name even if that person later leaves your church. opens a version's words. shows what changed, line by line, marked Added and Removed. copies a version into your draft and puts nothing in use: each topic is confirmed again, and then the draft is approved. If someone changed the draft after you opened History, it restores nothing and says so: press to read the draft as it is now, then restore.
Each approval, each restore, each Stop using it, each time the website's page is turned on or off, and each change to who looks after it is a line in the activity log, never with the words. A restore's line says the version in use didn't change.
Print it
On the team's page, opens the approved version as a plain document, for an elders' meeting or a membership class. Press there. Export everything holds the approved version too, as what-we-believe.md.
What PraisePad's team can see
PraisePad's support team reads What we believe only during a support visit, which your owners see in the list of visits. On a visit it can read, and can never change, confirm or approve anything, stop using it, turn the website's page on or off, or change who looks after it. See also Your privacy.