Most visitor cards are written like a survey. Name, address, birthday, how many are in your household, which ministries interest you, how you heard about the church. It reads like the church wants to know the guest before it has even said thank you for coming. And then, on Tuesday, whoever pulls the stack of cards out of the basket is holding twelve small surveys and no idea which of them need a phone call tonight.
A visitor card has exactly one job worth designing for: it should tell somebody, by Tuesday, who to contact and what to say. Everything else on the card is either in service of that job or it is dead weight. Once you start from the follow-up board instead of the filing cabinet, the right questions get obvious fast — and so do the wrong ones.
Start from the board, not the form
Design backward from the moment someone sits down to make calls. That person needs three things for every card in front of them: a name, a way to reach the guest, and some sense of how ready that guest is for contact. If a question does not feed one of those three things, it is not helping the follow-up — it is helping fill out the card, which is a different and much less useful goal. A card built for the board looks shorter and plainer than most churches expect, and that is the point.
Treat the card as the very first step of the guest-to-member path rather than as a record of the visit. The card is not the destination. It is the fuel for what happens after.
The questions that earn a place on the card
A handful of questions do almost all of the useful work. Keep the list short enough that a guest can finish it while a hymn is still playing.
- Name. Obvious, but worth saying: first and last, in handwriting someone else will have to read later. A guest who writes only a first name has already told the follow-up caller something — go gently.
- Phone or email, your choice. Do not require both. Offering a choice tells you which channel the guest is comfortable with, which is more useful than the contact detail itself.
- Is it okay to call you this week? A simple yes or no, sometimes with a checkbox for a preferred time of day. This one question does more for the follow-up board than any other, because it removes the guesswork about whether reaching out will feel welcome or invasive.
- How did you hear about us? Short and optional. It is useful for the church over months, not for the individual follow-up, so keep it light — a line, not a paragraph.
- Anything you would like us to know? One open line. This is where a guest tells you their kid is starting kindergarten, or they just moved from out of state, or they lost someone last year. It rarely gets filled in, but when it does, it is often the single most useful line on the whole card.
Five questions. A guest can finish that before the offering plate reaches the next row.
The questions that feel like due diligence and aren't
Every question you add past those five is a question that costs you something — a slower card, a guest who feels reviewed instead of welcomed, a field nobody downstream will ever act on. A few common ones are worth cutting outright.
Household size and ages of children ask for information you can gather in the actual conversation, once someone calls. Denomination or prior church background rarely changes the first contact, which is the same warm, low-pressure call regardless of what pew someone used to sit in. Ministry interest checkboxes look useful but almost never get used — the follow-up call that matters is the one about coming back, not about which committee a first-time guest might someday join. Mailing address is the biggest offender: it takes real time to fill out, it is rarely correct on a card written on a knee, and almost no small church actually mails anything to visitors anymore.
If a question would be reasonable for a member profile six months from now but does nothing for a follow-up call this week, it does not belong on the card. Ask it later, in person, when it has a chance of being both accurate and welcome.
Consent is a question, not an assumption
The single most underused question on most visitor cards is also the simplest: may we contact you? Churches often skip it because they assume filling out the card is consent enough. It is not, and treating it that way is how a well-meaning call lands as an intrusion. Asking directly does two things at once — it protects the guest from an unwanted call, and it protects your volunteer from that awkward opening line where they are not sure if the person even wants to hear from them.
It also sorts your stack of cards for you. A yes with a phone number is a same-week call. A yes with only an email is a warm note instead of a phone call. A no, or a blank, is still worth a name in the system and a much gentler, much slower touch — an invitation to a coming event rather than a personal call.
Design the card for the greeter, not just the guest
A visitor card also has a second reader nobody designs for: the greeter or volunteer who collects it at the end of the service. Leave a blank line at the top for that person to jot down anything they noticed — a name they caught in conversation, a mention of a rough week, whether the guest came with someone or alone. That single line, filled in by a human before the card even reaches the follow-up board, often carries more useful context than every checkbox on the form.
This is also where a simple Sunday check-in process and the visitor card overlap. Both exist to capture a guest before they are back in the parking lot, and both fail for the same reason when they try to do too much at the door on a busy morning. Keep the door-side capture short; save depth for the follow-up conversation that comes later in the week.
What happens to the card by Tuesday
None of the questions above matter if the card sits in a basket until someone remembers to look. The test of a good visitor card is not how it reads — it is what happens to it forty-eight hours after the service ends. Every card should become a named next step with a person attached and a date attached, the same day or the next. Twenty cards from a big Sunday should become twenty tracked follow-ups, not one volunteer's overwhelming stack of paper. A big Sunday makes this especially easy to lose, since the volume of cards can outpace any one person's ability to just remember who needs a call.
SundayBridge is built around exactly that step: typing in what a card says turns a guest into a follow-up task with an owner and a date, and the board ages anything nobody has picked up so it cannot quietly disappear. The card still does the human work of asking the right five questions — the software just makes sure the answers do not get lost between the basket and the phone call.
One card, one clear question behind it
Before you print the next batch of visitor cards, ask one question of the design itself: if I handed this stack to a volunteer on Tuesday, would they know exactly who to call, how, and by when? If the answer is yes with five short questions, you have a good card. If it takes twelve fields and a filing system to get there, the card has quietly become a survey again — and the follow-up, which is the whole point, will keep slipping through the gap between the basket and the phone. A guest's profile can hold the rest of the story later, once a directory your team actually trusts is where that detail belongs. The card's job is smaller, and more urgent, than that.