Resources / Signatures / Reaching parents without email

How do you collect a parent's signature when they don't have email or don't check it regularly?

The short answer

Not every parent has a working email address on file, and not every parent who has one checks it in time to matter. A signature request sent as a text to a phone number reaches someone through their phone's own signal, without requiring them to find an email, remember a portal password, or wait for something to arrive in the mail. That difference shows up directly in return rates: families respond to a text they can open and sign from immediately far more often than they respond to an email sitting unread or a paper form they have to find, sign, and mail back. The signature request has to go where the parent actually is, not where the district's system assumes they'll be.

On this page

Why the existing system does not cover it How districts handle it now Where it goes wrong

What doing it well actually requires Common questions How Flow Forms handles it

Why the existing system does not cover it

Most signature and consent workflows assume a parent has an email address, checks it within a reasonable window, and is willing to create or remember a portal login to retrieve what's inside. When that assumption holds, the system works fine. When it doesn't, the district's only lever is to keep trying the same channel: resend the email, call to ask if they got it, mail a paper copy and hope it comes back. There's no second channel built into the workflow itself, only more attempts at the first one.

How districts handle it now

In practice, staff work around this manually. Someone keeps a mental or literal list of which families don't respond to email and calls them directly, or prints a paper copy and sends it home with the student, or mails it and waits. For the small number of families with no reliable phone or internet access at all, paper is still the right answer. A form goes home, comes back signed, and someone logs that it came back.

Where it goes wrong

The pattern usually shows up the same way: a form goes out by email, nothing comes back, and nobody notices until a deadline has already passed and someone asks why a family never responded. At that point the district is not choosing a better channel, it's catching up on one that was wrong from the start.

What doing it well actually requires

Reaching a parent who doesn't respond to email means having a phone number on file and sending the signature request to both the phone and the email at once, rather than waiting on one before trying the other. It means the district can see at a glance which submissions are still pending on a parent, not just that something was sent. And it means anyone can pull up a specific submission's full history, who it went to, what happened, when, and export that record if it's ever needed for something more formal than a quick check.

Common questions

Questions we hear from every district office.

Does a signature collected by text carry the same legal weight as one collected by email?

The channel a request travels on doesn't change what the signature is. A signature collected through a text link is the same electronic signature as one collected through an email link; the phone number is only how the request got there. What carries weight is the record captured around it, who it went to, when it was opened, and when it was signed. The specifics of what makes an electronic signature hold up when it's questioned later are covered in their own article.

What happens if the phone number on file is wrong or disconnected?

Because the request goes to the phone and the email at the same time rather than one after the other, a bad number is not a dead end, the email path is already running alongside it. And the submission stays visibly pending until it's signed, so a request that hasn't landed shows up as still outstanding instead of quietly disappearing, which is the cue to try another number or fall back to paper for that one family.

Can a text-based signature request still land in the student's file the normal way?

Yes. How the request was delivered doesn't change where the signed record ends up. The signed document can attach into your student information system the same way your other signed files already do, or stay in Flow Forms as the record of that document, depending on how your district already handles it.

What if a family shares one phone number across multiple people?

The request is addressed to a specific person and opens to a specific document, so sharing a device doesn't blur the records. Each submission is tracked to the person it was sent to, and its history shows exactly who it went to and what happened, no matter how many people use the same phone.

Does this replace the paper option entirely?

No. For the small number of families with no reliable phone or internet access, paper stays the right answer, a form goes home, comes back signed, and someone logs that it came back. The point is to shrink the manual, chase-it-down work down to those genuine exceptions rather than force every family onto one channel. Keeping a required paper original while still collecting the signature digitally is its own topic, covered in Filling out required paperwork digitally, without losing the paper original you're required to keep.

How Flow Forms handles it

Flow Forms sends a signature request to whatever channel actually reaches a parent, a phone number by text or an email address, and it opens directly without a portal login. The signed record can attach into your student information system the way your other files already do, or stay in Flow Forms as the record of that document, depending on how your district already handles it.

This is proven in the field. Sweetwater County School District #2 moved its Transition Agency Consent and meeting notice requests off paper mail and onto direct links, and return rates went from 20% to 89% on Transition Agency Consent and from roughly 10% to 81% on meeting notices.

See how it would work for your district →