It is the Tuesday before a new member class, and the church secretary is rewriting the membership application again — the third rewrite this year, because the last version asked a question that made someone uncomfortable and nobody wants that to happen twice. Down the hall, the treasurer is retyping the counting checklist from memory because the version taped inside the safe walked off sometime last spring. Neither of these is a big problem. Both of them are the kind of small, recurring problem that eats an afternoon every few months at a church with no full-time staff to spare for it.
This page exists because most of what a small church needs in writing — visitor cards, membership forms, giving statements, background check policies, counting procedures, small group covenants, welcome letters — has already been worked out by thousands of churches before yours. The wording differs by congregation, but the shape of the problem does not. What follows is not a list of downloads. It is the reasoning behind each form: what it needs to ask, what it must not ask, and where getting the wording wrong actually costs something — a lost visitor, a failed audit, an unusable tax statement, an unfair denial nobody can explain.
Visitor cards: the first form a guest ever fills out
A visitor card has one job on the first Sunday: let someone be known without asking them to commit to anything. Most churches get the tone wrong before they get the questions wrong — a card covered in numbered boxes and a line for "how did you hear about us" reads like paperwork, not a welcome. The cards that actually get filled out and returned ask for very little, and ask for it kindly. a visitor card template you can copy today is the starting point if you have never had a written one, or if the one you have has not been looked at in years.
Wording matters more than most churches expect. "Are you a first-time guest?" lands differently than "Tell us about yourself," and a card that opens with an open-ended question tends to get left blank more often than one that opens with a simple choice. visitor card wording that does not feel like an interrogation walks through the actual phrasing, line by line, including the lines worth cutting entirely.
What the card asks should be driven by what happens next, not by curiosity. If nobody is going to call within the week, asking for a phone number is a formality that adds friction for nothing. what to ask on a visitor card so follow-up is not guesswork looks at this from the other direction — starting with the follow-up call your team is actually capable of making, and working backward to the two or three questions that make that call possible. Some churches have moved the card to a phone or a QR code at the welcome table, and some have deliberately kept it on paper because paper feels lower pressure to a nervous first-time guest; the right answer depends more on your greeting team than on any trend.
The card itself is only half the job. What happens once someone fills it out — who reads it, who calls, how soon — is a separate problem from the wording, and it is the one that actually determines whether a first-time guest becomes a second-time guest.
Membership: the application, and what should come before it
A membership application is a heavier document than a visitor card, and it should be, because it asks for a heavier commitment. The mistake most churches make is treating it as a formality — a page of contact fields — when it is really the place to be clear about what membership means at this specific church, doctrinally and practically, before someone signs anything. a church membership application template that is not intimidating is the full-shape version, built to be adapted rather than used word for word.
Getting the tone right is its own skill, separate from getting the structure right. A form can ask every necessary question and still feel cold, or like a test someone might fail. the questions worth asking on a membership application works through what to ask and how to ask it so the form reads as an invitation rather than a screening — and the same tension shows up in the choice of whether the application should come before or after a new member class, since a doctrinally distinctive church often wants the class first, while others use the application to gauge interest before investing class time in someone only mildly curious.
Once someone is in, the welcome does not end at the application. A written note that sounds like a person wrote it does more than any packet of photocopied handouts. a new member welcome letter template that does not read as a form letter is that note — short, warm, and specific enough that it does not read as something sent to everyone the same way.
Giving statements: wording the IRS actually requires
Of everything on this page, the year-end giving statement has the least room for improvisation, because the IRS has specific requirements for what a statement must say if a donor is going to use it as proof of a charitable deduction. Getting the wording wrong does not just look sloppy — it can make the statement unusable at tax time, which is a genuinely bad outcome for someone who trusted the church to handle it correctly. what the IRS actually requires on a giving statement lays out exactly what has to be there, and just as importantly, what does not.
The core template — amount, date, a statement about whether goods or services were exchanged — is the same for every church. year-end giving statement wording template is the full document, and it is worth pairing with a short cover note that turns a compliance document into something that also reads as a thank-you.
Non-cash gifts complicate the wording further. A church that receives a donated vehicle, stock, or a piece of equipment cannot simply write a dollar figure the way it would for a check, because a church generally cannot assign a value to a non-cash gift on the donor's behalf. how to word non-cash gifts on a giving statement covers the correct phrasing for describing what was given without stepping into valuation the church should not be doing.
This is one of the two places worth mentioning SundayBridge directly, because it is a genuine fit: giving is recorded, edited, and totaled in the app across the year, and the year-end statement itself is generated from those same records and ready to print, rather than assembled by hand from a spreadsheet in December. It will not decide what wording your statement needs — that is a legal question, not a software one — but once you know the wording, it removes the retyping.
Counting the offering: a checklist two people can actually follow
Every church that handles cash on a Sunday morning eventually asks the same question: what happens if the count is wrong, or worse, what happens if someone later asks how it could have been wrong. The answer that holds up is not a smarter counter. It is a written procedure that two people follow the same way every week, so the count does not depend on memory or on the same two volunteers always being available. an offering counting procedure for a two-person team is the starting document — short enough to actually get followed, specific enough to close the gaps that cause problems.
The rule that shows up in nearly every church's counting policy, and the one most often skipped when someone is out sick, is that no one person should ever count or handle the offering alone. Writing that rule down is not the same as following it, which is why the documentation matters as much as the rule itself. documenting the two-person rule for counting the offering covers how to record that the rule was followed, week to week, not just state that it exists — the kind of record an outside auditor or a new board member will actually want to see.
Background checks and volunteer applications
A background check policy and the consent language a volunteer signs are two separate documents, and a surprising number of churches have only written one of them — usually the consent form, supplied by an insurer or a background check vendor, while the policy explaining what happens with the results never got written down at all. a background check policy template for small churches is the piece most churches are missing: what disqualifies someone, who reviews results, and how that decision gets communicated. Consent itself belongs on the volunteer application, near the top rather than buried after someone has already emotionally committed to serving.
The hardest document on this page to write well is the one almost no church prepares in advance: what to say when a background check does not clear. Handled badly, this becomes a rumor before it becomes a conversation. Handled well, it is a private, respectful, and specific explanation that protects both the church and the person being told no. what to say when a background check does not clear exists because improvising this conversation in the moment is where the most damage gets done.
The application underneath all of this needs its own baseline of questions, regardless of ministry area — experience, availability, references, and a tone that takes the role seriously without reading like an interrogation. what belongs on a volunteer application form is that baseline. Children's and youth ministry adds its own layer on top — references, sometimes a minimum length of attendance before serving unsupervised with minors — and is worth treating as its own template rather than the standard form with an extra line added.
None of this is a one-time task either. A check run three years ago tells you nothing about what has happened since, and a church that only checks once, at intake, has a gap it may not notice until something has already gone wrong. A shared, dated record of who was checked and when — even a simple one — turns renewal from a thing someone has to remember into a thing that shows up on its own.
Small groups: the covenant that sets expectations before the first meeting
Small groups tend to run into trouble not because people dislike each other, but because nobody said out loud, before the group started, what was expected — how often the group meets, what happens when someone misses repeatedly, whether what is shared in the room stays in the room. A written covenant fixes that by making the expectations explicit instead of assumed. a small group covenant template you can adapt is the general-purpose version most groups can start from.
Confidentiality is usually the single line in a covenant that generates the most disagreement if it is left vague — does "what's shared here stays here" cover a comment about someone's marriage, a mention of financial trouble, or both, and does it have any exceptions. wording a confidentiality clause into a group covenant works through phrasing that sets a real boundary rather than a feel-good sentence nobody actually follows under pressure. A first-time leader needs a slightly different document than an experienced one — less about what the covenant says and more about how to introduce it without the first meeting feeling like a syllabus — and someone joining a group already in progress needs their own, shorter welcome, distinct from the church-wide new member letter.
Attendance and benevolence: two more forms worth getting right
Attendance sounds like the simplest form on this page, and it usually is, but it is also the one most likely to be filled out badly under time pressure — a volunteer trying to count heads and manage a classroom at once will make mistakes a cleaner sheet design would have prevented. a weekly attendance sheet template for Sunday services is the general version; Sunday school and children's classes need a version organized by classroom rather than by service, since the person filling it out is usually managing one room, not the whole building. Worth saying plainly here: SundayBridge charts attendance against its own history once it is entered, but it does not add a session for you — attendance in the app is a read-only view, not a data-entry screen, so whatever sheet you land on, the numbers still get typed in by hand.
Benevolence requests bring urgency and money together, which is exactly the combination that produces inconsistent decisions if there is no written process in place. A request form that asks the same questions every time — what is needed, how much, what has already been tried — turns a stressful, case-by-case judgment call into something closer to a repeatable process. a benevolence request form template for small churches is that form, and it works best paired with a policy written before the fund gets its first request of the year, not while someone is waiting in the office. Whatever the decision, it needs to be written down afterward, not just made — both to protect against giving the same assistance twice through two different people who never compared notes, and to have an answer ready if anyone asks later how a decision was reached.
Where a template ends and your church's judgment begins
None of the documents above are meant to be used exactly as written. A template is a first draft of the hard thinking, not a substitute for it — every church has its own polity, its own state's mandatory reporting rules, its own denomination's expectations about membership, and those differences matter more in a legal document than in almost anything else a church writes. The right use of a template is to start from something close, then change the five or six lines that reflect your specific church, rather than staring at a blank page.
It is also worth being honest about what a piece of software can and cannot do with these documents. SundayBridge has no CSV import, so nothing on this page gets loaded in automatically — a signed membership application still becomes a person's profile because someone typed it in, a completed volunteer application still becomes a serving assignment because someone entered it. If you have years of this information sitting in a spreadsheet already, that loading gets done by hand, for free, as part of getting a church set up, rather than by any automated import — there is not one to lean on instead. What changes once the information is in is what happens next: a follow-up that ages on a board until someone with a name and a date closes it, a giving record that turns into a statement in December instead of a spreadsheet rebuilt every year, a background check that shows up as a dashboard alert instead of a note in a drawer. The forms get you the information. What you do with it afterward is the part worth thinking hardest about.