Sunday attendance without a sign-in sheet

There is a clipboard by the door of a lot of small churches. It has a sheet on it with four columns — name, phone, email, first time? — and by the end of the service it has eleven rows, three of them illegible, one of them a child's name written by a child. Somebody carries it to the office. It goes in a drawer with the other ones.

Nothing about that is anyone's fault. The welcome desk is staffed by a volunteer who also has to find the nursery, and the clipboard is genuinely the cheapest thing that works on a Sunday morning. The problem is what happens on Monday, which is nothing. The sheet is not data. It is a photograph of a room, and a blurry one.

So the useful question is not "how do we get people to sign in?" — they already do. It is: what has to happen for the eleventh row on that sheet to still exist in March, attached to a person, next to everything else you know about them?

What a check-in system has to do

Before you evaluate any tool, it helps to know what the job actually is. Four things, in order of how often they get skipped:

It has to be faster than the clipboard. If a first-time visitor has to download an app, create an account, verify an email and set a password, they will not do it. They will walk past the desk. A check-in flow that asks more of a stranger than paper does is worse than paper, because paper at least gets filled in.

It has to work for somebody who has never been there before. A flow built around looking up an existing record has nothing to offer the people you most want to capture. On a Sunday with visitors, half the point is the people who are not in the system yet.

The list has to leave the room. A live count on a screen is nice on the day and useless by Tuesday. Whatever captures the names has to hand them to whatever holds your people long-term, without a human retyping anything.

It has to survive the volunteer. The person on the desk changes every few weeks. If the process only works when the one competent person is holding the clipboard, you have a process with an expiry date — which is its own problem, and a bigger one than attendance.

A checklist you can use this Sunday, with or without software

You can fix most of this with a printed code and twenty minutes of thought:

1. Pick the single question you actually need answered. Usually it is "who was here" — not age, not address, not how they heard about you. Every extra field costs you completions.
2. Put the code where the queue already is. Taped to the door frame at eye height, on the welcome desk, on the back of the seat in front. Not on a table in the corner that nobody walks to.
3. Have a manual fallback. Somebody's phone will be dead. Somebody will not have a phone. The person on the desk needs a way to add a name by hand without it becoming a second, separate list.
4. Decide before Sunday who reads the list, and when. A name captured and never looked at is the clipboard again, in a nicer font. Wednesday is a good default: soon enough to matter, late enough that you are not doing it while stacking chairs.
5. Write down what "first time" triggers. A text, a call, a coffee, nothing — any of these is a legitimate answer. Not having decided is not.

How this works in Harvest

Harvest's Check-In System is on the Small Team and Ministry plans. You create a check-in session — optionally linked to an event — and it gives you a QR code to print. Somebody scans it with their phone camera, enters a first name, and they are done: no app, no account, no login. What they see is a branded self check-in page, not a generic form with somebody else's logo on it.

On your side, you get a live attendee count while the service is running, the ability to check somebody in by hand when their phone is dead, and a CSV export of the full attendee list. There is also a bundled QR generator that produces codes for five destinations, so the one you tape to the door comes from the same place as everything else.

The part that matters on Monday: attendance auto-links to CRM contacts. The scan does not create a parallel list. It lands on the person.

Why the last paragraph is the whole argument

Here is the version of this problem a lot of churches actually have. The check-in tool is one subscription. The giving platform is another, with its own list of people. The church management system is a third, holding the "real" records, which are the least current of the three. Three bills, three member lists, and no agreement between them about who anybody is.

Now somebody checks in for the first time on a Sunday in October. In a stack like that, the name enters at the edge and has to be walked inward by hand — exported, deduplicated, imported, retyped. It usually isn't. That is why, in January, the person assembling year-end giving statements discovers three records for the same household and no way to prove which is right.

In Harvest the scan lands on a contact record that is already the only one. The CRM is on every paid plan, it merges app members and manually added contacts into one list, and it deduplicates on email — so a person's history does not scatter across three rows. On the Small Team plan, where check-in starts, that record carries giving, events, check-ins and forms on a single timeline, and it sits in a five-stage discipleship pipeline that runs from New to Champion — so "came twice in October" is a thing you can see rather than a thing you half-remember. It is the same row whichever surface the person touched, rather than three vendors' copies of them.

A standalone check-in app cannot do that, and it is not a criticism of the app — it does not hold your giving history, so there is nowhere for the scan to land. You pay a second subscription for the privilege of moving names between systems yourself.

Harvest's platform fee is 0% on every paid plan — the company takes no cut of a gift. Card processing is charged separately by whoever handles the payment and is not a Harvest number, so a gift does not arrive in full. Check-in itself starts on Small Team, at $40/mo, or $31.67/mo billed as $380 every 12 months. What you get for it is not a check-in feature. It is one subscription, one member record, one login — and a clipboard you can finally throw away. The full ladder is on the pricing page.