Ask five churches which comes first, the membership application or the membership class, and you will get five confident, different answers. Some hand over the form on someone’s first Sunday and treat the class as a formality for people who have already decided. Others will not let anyone near the form until they have sat through four weeks of teaching, which quietly tells a ready, eager person to wait.
Neither failure is really about the form or the class. It is about not having decided, on purpose, what each one is for. Once you separate what the class teaches from what the application records, the order stops being a debate and becomes an easy default.
They are answering two different questions
A membership class answers do you understand what this church believes and how it works. It covers doctrine, history, expectations, maybe a walkthrough of how decisions get made. It is teaching, and teaching does not require a commitment in advance to be worth attending.
A membership application answers a narrower question: has this specific person decided to join, and on what date. It is a record, not a lesson. Once you hold those two purposes apart, it becomes obvious that a form which only records a decision has no reason to gate access to a class which only teaches.
The default order: class first, application at the end
For most churches the simplest working order is to let the class come first and treat the application as its natural close. Someone curious can sit in on session one with no paperwork and no pressure. By the last session, the people still in the room have usually already decided, and handing them the application at that point feels like the next step in a conversation, not a cold form dropped on them out of nowhere.
This order also solves the awkward case of someone who attends the whole class and quietly decides membership is not for them right now. If the application came first, that person is now a half-member on paper who never really joined. If it comes last, they simply finish the class and nothing else happens — no form to walk back, no record to correct.
When it makes sense to flip the order
There is one situation where taking the application first is the better call: a transfer member who was already active and known at another church, moving in with a letter of standing or a clear history your leadership already trusts. Making that person sit through the full class before they can be recognized as a member often reads as bureaucracy rather than care. A short conversation plus the application, with an invitation to attend a future class session out of interest rather than obligation, respects both the process and the person.
The same logic can apply to a longtime attender, someone who has been at the church for years, served on a team, and simply never formalized things. A class built to introduce a stranger to your church is not really what that person needs. Ask what they actually need to know that they do not already, and build the shortest path to the application from there.
What belongs on the application, and what does not
Keep the application to what it exists to record:
- Name and contact information, if it is not already on file from an earlier visit.
- The date of the decision — the single fact your records will be checked against for years, at baptism anniversaries, at annual meetings, whenever someone asks how long they have been a member.
- Which class or track they completed, if you run more than one version.
- A signature or a checked box acknowledging whatever statement of faith or covenant your church asks new members to affirm.
Leave off anything that belongs to pastoral care instead of a record: a question about past struggles, a request to describe a testimony in detail, a box asking what ministries someone hopes to join. Those are good conversations. They are bad form fields, because a required field turns a personal story into a compliance exercise, and because none of that information is what you will actually go looking for a year from now.
The class needs an attendance record too, not just a roster
A common gap: churches track who signed up for the membership class but not who actually showed up, session by session. That gap is exactly what makes the handoff to the application feel arbitrary. If a class is genuinely a prerequisite, someone has to be able to answer, without guessing, whether a given person actually completed it. A simple session-by-session attendance note against each person’s profile does that job, and it means nobody has to rely on a leader’s memory of who was in the room in March.
Where the record actually lives once the form is signed
The single biggest failure in this whole process has nothing to do with ordering. It is the signed application landing in a filing cabinet, or a folder on someone’s desk, disconnected from the person’s actual record. Six months later, nobody can say with confidence when someone joined, or whether they joined at all, without physically digging through paper.
In SundayBridge, that decision date becomes part of the person’s own profile — sitting alongside their groups, their giving, and their serving history, not in a separate spreadsheet that has to be cross-referenced by hand. The signed form itself still needs somewhere to live, physically or scanned, but the fact and the date of membership stop depending on someone remembering where that form was filed.
A sequence you can actually run
Put together, a workable default looks like this: someone is welcome to attend the membership class with no form required. Attendance is noted session by session. At or near the end of the class, the application goes out, asking only what a record needs to hold. Once it is signed, the decision date gets entered against that person’s profile the same week, not whenever someone gets around to the filing.
That order treats the class as an open door and the application as a close, honest record of a decision already made — instead of a hoop and a formality fighting over which one matters more. If your church is still tracking this on a spreadsheet with a tab for class attendance and another for applications, the same logic applies before you even get to software: decide what each document is actually for, and the question of what comes first mostly answers itself. For churches weighing whether it is worth moving that tracking somewhere sturdier, the considerations are the same ones covered in moving a church off spreadsheets and choosing church management software.