Know Which Families Still Owe Forms While You Can Still Ask
Six forms went home with four hundred students. They come back over a fortnight — some in backpacks, some as photographs texted at 11pm, some not at all — and the trip is on Friday.
The short answer
The useful question is never what has come back, it is who has not sent what, and email and a pile of paper answer neither. A workflow catches returns from both routes — a collection link and the Email Attachment trigger — reads each one for the student and form type, and files it under them. The file request's checklist then reports the gaps per student, which is a list an office can act on rather than a pile it has to count.
Steps this uses
Before and after
What actually changes
As they arrive
- IMG_9931.jpg
- permission.pdf
- scan0114.pdf
- Fwd: form.jpg
After the workflow
- Students/Okafor, Daniel/Forms/2026-09-02-field-trip-permission.pdf
- Students/Reyes, Marisol/Forms/2026-09-03-field-trip-permission.pdf
- Students/Nunez, A/Forms/2026-09-03-media-consent.pdf
- Outstanding/2026-09-04-field-trip-permission-missing-41-students.txt
Returns filed under each student as they arrive, with the outstanding list produced from what has not.
Setting it up
Described once, then it runs
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
When a family returns a form by email or upload, save a copy, read the student and the form type off it, and file it under that student. Post the student and the form name to the office channel as each one lands.
One destination, both routes
A collection link for parents who use it and email capture for those who reply with a photo. Paper still has to be scanned, but once scanned it joins the same flow.
Name the expected set
Which forms went out, to which year group. Without that list there is nothing to compare returns against, and the tracking collapses back into counting a pile.
Read the student off the form
The Read Details from File step identifies the child and the form type, so a photographed slip files itself under the right student without anybody typing a name.
Report by exception, daily
The file request's checklist shows who has not returned what, and smart reminders follow up on a cadence you choose. Daily rather than weekly during a collection window, because the value of the list drops to nothing once the deadline passes.
Counting a pile answers the wrong question
A stack of returned slips tells you how many came back. It does not tell you which forty-one children cannot go on Friday, and turning the first into the second means checking a pile against a roster by hand. Filing each return under its student inverts the problem: the outstanding list is simply the roster minus what is filed, produced without anyone counting anything.
The deadline is what makes this worth automating
Most document organization pays off eventually. This one pays off on a specific day and then stops mattering entirely — an outstanding list produced on Friday afternoon is worthless. That is the argument for a daily automated report during a collection window rather than a check somebody does when they get to it.
What it does not do
It tracks what has and has not come back. It does not contact parents, judge whether a signature is valid, or decide whether a child without a returned form can attend. It also cannot see a form sitting in a backpack. What it removes is the counting, which is the part that does not get done when the office is busy.
FAQ
Common questions
How do schools track which forms have been returned?
By filing each return under the student it belongs to, then comparing against the roster, so the outstanding list is produced rather than counted. The list of which forms went to which year group has to be supplied — without it there is nothing to compare returns against.
What about forms returned as photographs?
They are read for the student and form type and filed like any other return. Photographed slips texted or emailed in the evening are a normal route now, and a process that only handles paper misses a substantial share of what actually comes back.
Does this chase parents for missing forms?
Smart reminders follow up automatically with families who have not returned everything, on a cadence you set. Beyond that it produces the list and stops — whether to phone a family is the school's decision and usually needs a person, particularly when a form has been asked for twice already.
How often should the outstanding list run?
Daily during a collection window. The value of the list collapses the moment the deadline passes, which is unusual among filing problems and is the reason this one is worth automating rather than doing when there is time.
Not how many came back.
Which forty-one children still owe you a form, and it is Wednesday.
5 GB free · No credit card required