A visitor card has one job: get a first-time guest’s name and a way to reach them into your hands before they walk out the door. That is the whole job. Most cards fail it by trying to do six other things at the same time — survey their giving history, ask about their spiritual background, collect an emergency contact for a child they did not bring — and end up so long that a guest either abandons it halfway through or never picks up the pen at all.
Below is a layout you can copy as it stands: print it, hand it to a greeter, and use it this Sunday. Underneath it is the harder part, the reasoning for what got left off, because the fields you resist adding matter as much as the ones you keep.
The card, field by field
Print this on a half sheet or a standard index card. A pen clipped to a connection table or handed over at the door removes the last excuse not to fill it in.
- Name. First and last, one line. Do not split this into separate boxes for a first, middle, and last name — that belongs on a form for a mortgage, not a Sunday visit.
- Phone or email, whichever they prefer. One line, labeled “best way to reach you,” not two separate required fields. Let the guest pick.
- First visit or returning. A single checkbox pair. This is the field that turns a stack of cards into a usable follow-up list, because it tells whoever reads them who is new.
- Household, if it applies. A short line for “anyone with you today” — a spouse, kids by first name and age range. Optional, and only useful if you plan to actually use it when you set up their record.
- How you heard about us (optional). One short line, clearly optional, near the bottom where skipping it does not interrupt the flow of the card.
- A request or a note (optional). A short blank line for anything the guest wants staff to know — a prayer request, a question, an interest in a group. Keep it small enough that it does not read as an essay prompt.
That is six fields, two of them optional, on one card. A guest can fill the whole thing out in under a minute, which is roughly the amount of patience most first-time visitors have for paperwork before or after a service.
What to leave off, on purpose
Every one of these shows up on a card somebody built with good intentions, and every one of them makes the card slower to fill out without adding much:
- A full mailing address. You rarely need it on the first visit, and it is the field most likely to make a guest pause and wonder what it is for. Ask for it later, once there is a relationship, not on card one.
- Birthdate. Useful eventually, unnecessary on day one, and it can feel like an odd thing to hand over to a stranger at a connection table.
- A giving or income question of any kind. A visitor card is not the place, ever, to ask whether someone tithes elsewhere or plans to give. It turns a welcome into a solicitation on the very first visit.
- A ranked list of ministry interests. Checkboxes for six different volunteer areas ask a stranger to commit to something before they know if they are coming back. One open line for interests, if any, does the same job without the pressure.
- A signature line. This is a welcome card, not a contract. A signature line makes it look like one.
The pattern across all of these is the same: anything that can wait until a second conversation should wait. A card stuffed with fields for a relationship that does not exist yet reads as presumptuous, even when the intent behind it is entirely warm.
What happens to the card after the service
A card that sits in a folder until Wednesday has already lost most of its value. The best pattern is simple: whoever collects the cards sorts the first-time visitors out that same day, and each one becomes a follow-up with a name attached — a call, a handwritten note, a coffee invite — owned by a specific person, not a general to-do. If your church already runs a guest-to-member path, the card is simply the first document in that process, not a separate system of its own.
In SundayBridge, that follow-up step is a board where a guest becomes a next step with an owner and a date, and the board ages whatever nobody has picked up. The card itself still gets filled out by hand and typed in by a person — SundayBridge does not scan or import the card for you — but once the name is in, nothing about that first Sunday gets forgotten because nobody remembered to check a folder.
Adjusting the card for your own church
The layout above is a starting point, not a fixed script. A church that runs children’s ministry every week may want a line for which classroom a child was dropped into. A church in a multilingual community may want the card printed in two languages on either side of the same sheet. Change what you need to, but hold the line on the principle underneath it: every field should earn its place by making the very next follow-up conversation easier, not by satisfying curiosity about a guest you just met.
A card is not a database
It is worth saying plainly: a stack of filled-out cards is not the same thing as a record of your guests. The card is the moment of capture. What happens next — someone typing the name and contact into a place your church can search, follow up on, and look back at months later — is the part that actually matters. Churches that get the card right but stop there end up with the same problem as churches with no card at all: a growing pile of good intentions nobody can find again. If your current system is still a shoebox of cards and a spreadsheet someone updates when they remember, it may be worth reading about moving off spreadsheets before your next visitor season picks back up.
Print it, use it, revise it in a month
Do not wait for a perfect card. Print this one, use it for four Sundays, and see what actually happens: which fields guests skip, which ones a greeter has to explain, which answers never get used by whoever does the follow-up. A card is a small, cheap thing to get slightly wrong the first time. The only real mistake is making it long enough that a guest hands it back half-finished, or short enough that nobody can act on it afterward.