Someone hands a first-time guest a card, and the card asks for their name, address, phone number, email, birthday, how they heard about you, whether they have kids, what they are looking for in a church, and a space for notes. It takes four minutes to fill out. Most guests fill out a third of it, if that, and the rest sits blank forever, which tells you something: you asked for more than you needed.
The point of a guest record is not to know everything about a stranger by Sunday afternoon. It is to have enough to do one thing well — reach out before the visit fades from their memory. Everything past that is either a nice-to-have you can ask for later, once there is a relationship to justify it, or a mistake you will regret the first time someone asks why you know so much about them.
Start with the two things that actually matter
A name, and one way to reach them. That is the whole job of the card. Not a name and an address and a phone and an email and a fallback contact — one channel, whichever the guest offers freely. If someone writes a phone number and leaves the email blank, that is not an incomplete card. That is a guest telling you how they would like to be contacted, and you should listen to it. Everything you collect beyond that name and one contact method is something you are asking a stranger to hand over before they have decided whether to trust you, which is backwards.
Notice what a guest gives you without asking
Most guests will tell you more than a name and a phone number, if you let them, just not on a form. They will mention they have two kids in the car, that they used to attend a church across town, that a coworker invited them, that they are only in the area for a season. None of that needs a field. It needs someone to actually listen during the thirty seconds at the welcome table and jot down one sentence afterward, from memory, in their own words. A card with checkboxes for “invited by a friend” and “new to the area” trains people to sort a guest into a category. A blank line that says only what was actually said keeps the guest a person instead of a checkbox.
Skip the fields that ask for a decision, not a fact
“What are you looking for in a church?” and “what questions do you have?” are conversations, not fields. Put them on the card and you either get silence or a guarded, polite non-answer, because nobody wants to commit their spiritual life to writing on a clipboard between the parking lot and their seat. If you actually want to know, ask in the follow-up conversation, when there is a person on the other end instead of a form. The card’s job is to get you to that conversation, not to replace it. The same goes for anything that asks a guest to rate the service, name what they liked or did not, or predict whether they will return — those are questions for a friendly phone call a few days later, asked by a real voice, not for a clipboard handed to a stranger on their way out the door. A rough rule of thumb: if a question would feel strange asked out loud, thirty seconds after meeting someone, it is too much to ask on paper as well. Paper does not make an intrusive question polite; it just makes it easier to avoid noticing that it was intrusive at all.
Write down what helps the next conversation, not what satisfies curiosity
There is a real difference between a note that serves the guest and a note that just satisfies whoever is filling in the record. “Visiting with her sister, mentioned she just moved to town” helps whoever calls next week ask a real question instead of a generic one. “Seemed nervous, kept looking at her phone” does not help anyone follow up better — it is an observation about a stranger that serves no purpose except making the record feel more complete. If a note would not change what the next person says to this guest, it does not belong on the card.
Leave anything sensitive off the guest card entirely
A first-time guest sometimes says something heavy in an unguarded moment — a health scare, a marriage falling apart, a job just lost. That information deserves care, not a checkbox on an intake form that anyone on the welcome team might later flip through. If it needs to be remembered at all, it belongs with whoever handles pastoral matters, kept discreet, not sitting in a general guest record where its only purpose is to be found by someone browsing. When in doubt, the safer choice is to not write it down at all and trust the person doing follow-up to remember the parts that matter and let the rest go.
Decide who is allowed to read the card before you decide what goes on it
The right amount of detail to record depends entirely on who can see it afterward. If every volunteer on the welcome team can pull up every guest’s card, you have already decided the record needs to stay thin, because thin is the only thing that is safe at that level of access. A smaller circle — the greeter who met them and the person who owns the follow-up — can responsibly hold a little more, because there is an actual relationship carrying that information forward instead of a drawer full of strangers’ details. This is the same logic behind building a directory your team actually trusts: the record earns trust by staying no bigger than its access controls can protect.
Ask again later, when there is a reason to
None of this means a guest’s information stops at a name and a phone number forever. It means the first visit is not the moment to collect it. Once a guest has been back a few times, joined a group, or started serving somewhere, the relationship has earned more detail — an address for a card at Christmas, a birthday for a class roster, an emergency contact once their kids are enrolled in something. Ask for those things when there is a plain reason attached to the ask, and say the reason out loud. “We’re mailing your child’s class a note next month, can I get your address” is a request a person can weigh. A blank address field on a first-visit card is a request nobody can weigh, because there is no stated reason for it yet.
Let the record answer one question, then let it go
A guest card exists to answer a single question well: did anyone reach out, and did it work. That is why the useful shape for a first visit is not a fat profile — it is a name, a contact, and a next step with a name on it, the same shape behind a written guest-to-member path. In SundayBridge that next step is a follow-up task with an owner and a date, sitting against the guest’s profile, aging visibly if nobody picks it up — which is a nudge to act, not a place to store more about the person than you need. If the guest never returns after a reasonable stretch, close the follow-up and let the thin record sit quietly rather than keep collecting detail on someone who has moved on.
None of this is about being stingy with hospitality. It is closer to the opposite: a guest who senses they are being logged, categorized, and filed feels smaller for it, even if nobody meant it that way. A guest who senses that you remembered their name and followed through on one small thing feels welcomed. The thinner, more disciplined record is usually the more human one — it forces you to keep the two things that matter and let the rest wait until it is earned. If your current process is a habit more than a plan, it may be worth moving off the spreadsheet before your next big Sunday, so the guest card stops depending on whoever remembers to update it. If a printed tracker is enough for now, the free starter kit includes a new-visitor follow-up sheet built around exactly these fields.