Automations/Operations
File Four Hundred Enrollment Forms Without Naming Them by Hand
Enrollment closes and the scanner has produced four hundred files named scan0001.pdf through scan0400.pdf. Each one belongs to a different family, and the only thing distinguishing them is handwriting.
The short answer
The student's name is written on the form, which means the batch is separable without anyone opening it — but only once the handwriting has been read. A workflow uses the Read Details from File step with OCR to read the name and form type off each scan, the Rename step to name it accordingly, and the Move step to file it under that student. Forms it cannot read confidently go to a review folder rather than being filed under a guessed name, because a record filed under the wrong child is worse than one filed nowhere.
Steps this uses
Before and after
What actually changes
As they arrive
- scan0001.pdf
- scan0002.pdf
- scan0003.pdf
- scan0004.pdf
After the workflow
- Students/Okafor, Daniel/Enrollment/2026-08-14-enrollment-form.pdf
- Students/Okafor, Daniel/Enrollment/2026-08-14-emergency-contact.pdf
- Students/Reyes, Marisol/Enrollment/2026-08-15-enrollment-form.pdf
- Review/unreadable/scan0004.pdf
A scanner batch separated by the names written on the forms, with the one it could not read sent to review rather than guessed.
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 enrollment forms are scanned in, read the student name and the form type off each page, rename it by date and form, and file it under that student. Send anything it cannot read confidently to a review folder instead of guessing.
Point it at the scanner output
Whatever folder the scanner already writes to. The batch does not need separating first — that is the work being removed.
OCR does the separating
The Read Details from File step reads the handwritten name and the form type off each page. This is the whole mechanism; without it a batch of scans is four hundred identical-looking files.
Match against the roster, not just the text
Reading "Danyel Okafor" off a form is more useful when it can be matched to the roster entry for Daniel Okafor. Supplying the list of enrolled students turns near-misses into matches rather than new folders.
Send the unreadable ones to review
Ask a Person to Approve handles anything uncertain, with the proposed student shown. Handwriting varies enormously and the cost of a wrong match is high, so the threshold for asking should be low.
Handwriting is the whole difficulty, and it is uneven
A form completed in block capitals reads reliably. The same form filled in quickly in cursive, or by someone whose first language uses different letterforms, often does not. This is not a reason to skip the automation — three hundred of four hundred separating themselves is still most of the work — but it is a reason to expect a review pile and to design for it rather than be surprised by it.
Why a roster changes the accuracy
Reading a name from handwriting produces a best guess at a string. Matching that string against the list of students actually enrolled turns a fuzzy read into a decision between known options, which is a far easier problem. A form read as "Danyel" resolves to the enrolled Daniel; without the roster it creates a second folder that nobody notices for a year.
What it does not do
It separates a batch and files by student. It does not extract field values into a student information system, validate that a form is complete, or check that a required signature is present. Those are data-entry and review tasks. What it removes is the part where a person opens four hundred scans to find out whose each one is.
Then build
Variations worth building next
When a scanned stack of enrollment forms is uploaded to my Scans folder, split it into one file per form, then read the student name and form type off each and file it under that student.
Handles the copier scan that puts a whole class's forms into one PDF.
When an enrollment form is filed under a student, read the student name, grade, guardian name and contact details, and send those details to our student information system through a webhook.
Puts the details on the form into the student system without someone re-typing them.
When a parent emails an enrollment form to the office Gmail, read the student name and form type, ask AI whether it carries a signature, file signed forms under that student, and send unsigned ones to a Needs Signature folder.
Separates forms that came back unsigned so the office can follow up on them.
Limits
What to know before you build it
It runs on new files, not your backlog
This workflow fires when a file arrives. It will not go back over the documents already sitting in the folder, so switching it on leaves the existing pile exactly where it is. Working through what is already there is a scheduled run instead, which is a different workflow.
Organize the files you already haveIt needs a connected account
This workflow reads files out of an email inbox, so it cannot run until that account is connected. Connecting one is on the Max plan, or on any team workspace. There is no version of this particular workflow that runs on the free plan, because the files it organizes never arrive in The Drive AI on their own.
FAQ
Common questions
How do schools organize enrollment forms from a scanner batch?
By reading the student name written on each form with OCR and filing under that student, rather than opening each scan to identify it. Matching the read name against the enrolled roster is what makes it accurate — it turns a fuzzy handwriting read into a choice between known students.
Can handwritten forms really be read automatically?
Often, with uneven results. Block capitals read well, hurried cursive frequently does not. A realistic expectation is that most of a batch separates itself and a minority needs a person, which is still a large reduction from opening every file.
What happens to a form it cannot read?
It goes to a review folder with the proposed match shown, rather than being filed under a guessed name. Filing a student record under the wrong child is considerably worse than leaving it unfiled, so the threshold for asking a person should be low.
Does this enter data into our student information system?
No. It separates and files the documents. Extracting field values into an SIS is a data-entry task, and validating that a form is complete or properly signed is a review task. This removes the identification work that comes before both.
Four hundred scans, four hundred students.
Separated by the name written on the form.
5 GB free · No credit card required