A volunteer application asks who someone is and where they would like to serve. A background check consent form asks for permission to go verify part of what they said, using a legally specific process. Churches that staple these two documents together, or worse, fold the consent line into the bottom of the application, end up with a form that is either legally thin or so intimidating that people stop filling it out.
The fix is not complicated. It is two documents, not one, each doing a single job, handed to the volunteer in the right order. What follows is how to structure both, and why the split matters more than it looks like it should.
Two different questions, two different signatures
The application is a get-to-know-you document. Name, contact information, which ministries they are drawn to, maybe a reference or two, maybe a faith statement if your church asks for one. Nobody signs it expecting anything but a phone call back.
The consent form is a legal instrument. It says, in effect: you may contact a third party, hand them my name and identifying information, and they will search records and report back to you. That is a different kind of agreement, and it carries different rules about disclosure depending on what kind of report you are pulling and where your church is located. Treating it as one more line on a general form is how churches end up with consent that will not hold up if a denied volunteer ever pushes back.
Why the consent form needs to stand alone
In the United States, a background check that is furnished by a third-party screening company for a “permissible purpose” falls under the Fair Credit Reporting Act, which requires a clear and conspicuous disclosure, in a document that consists solely of the disclosure, before you can run the check. “Consists solely of” is the phrase that matters here. A consent line buried in paragraph nine of a membership application does not meet that bar. A standalone page that says what will be checked, who will check it, and asks for a signature does.
Even if your church uses a screening vendor that is not a full consumer reporting agency, or you are only checking a sex-offender registry yourself, the same logic holds for a simpler reason: a volunteer should be able to look at one document and know exactly what they are agreeing to, without having to parse it out of a form that is mostly about their Sunday school preferences.
What belongs on the application
- Name, contact information, and how long they have attended.
- Which team or role they are interested in.
- Availability and any relevant experience.
- A reference or two, if your church asks for them.
- A short note that roles working with children or finances require a background check as a condition of serving, so it is not a surprise three pages later.
That last item matters. The application can and should mention that a check will happen. What it should not do is ask them to consent to it right there.
What belongs on the consent form
- A plain statement of what will be checked and by whom.
- The identifying information the screening company needs to run it.
- A note on how results are used and stored, and who at the church sees them.
- A single, dedicated signature and date line.
Keep the language plain. This is not the place for theological framing or a welcome paragraph. It is the place for exactly what is being agreed to, said once, clearly.
The order matters as much as the content
Hand out the application first. Let someone say yes to the idea of serving before you hand them a legal disclosure to sign. Once a role is identified as one that requires screening, that is when the consent form comes out, on its own, with someone available to answer questions about it. A volunteer who has already committed to a role in their head reads a standalone consent form very differently than one who is handed both papers at once and told to sign everywhere there is a line.
This ordering also protects your church. If you only ever run checks on people who have applied for a role that needs one, and the consent form is specific to that request, you have a clean record of why the check happened and what it was for. A single form that everyone signs on intake, whether or not their role requires screening, is harder to explain later.
Who should see which document
The application can be read by whoever manages volunteer scheduling for that ministry. The consent form, and anything that comes back from it, should be seen by as few people as possible — typically one coordinator who submits it to the vendor and files the result. This is not about secrecy. It is about not turning a background check into something the whole serving team gossips about, and about limiting who has access to identifying information that does not need to circulate.
Scheduling volunteers and screening volunteers are two different jobs even when the same person does both. It helps to think of them that way on paper too.
Keeping track of who has signed what
Once you have two documents per volunteer instead of one, the real risk is losing track of which ones are current. A check from three years ago is not the same as a check from three months ago, and a volunteer who moved from greeting to children’s ministry may need a form they never signed. SundayBridge does not run the check or store the consent form itself, but the background-check alert on the serving-team dashboard gives a coordinator a simple, current view of who is due for a re-check and who has a role that has never been screened at all, so the paperwork gap gets caught before someone is scheduled, not after.
A short version for a small church
If two separate documents feels like more process than your church needs right now, the minimum version still holds the line: one page for the application, one page for consent, two signatures, handed over in that order. It takes five more minutes than a single combined form and it is the difference between a check you can defend and one you are hoping nobody ever questions.
For churches building this out for the first time, it is worth reading alongside how to run a serving team without burning people out once the paperwork stops being the bottleneck, and keeping one people record your team trusts so the consent form is not the only place that information lives.