Tracking who actually completed required professional development, not just who requested it
Flow Forms · HR and personnel operations
The short answer
A professional development request and a completed PD record are two different things, and approving the request only confirms the first one. What actually needs tracking is whether each individual attendee agreed to the conditions, attended, and finished whatever comes after, like a receipt or an evaluation, not just whether a supervisor said yes to the trip. When one person submits on behalf of a group, that individual-level follow-through is exactly the part that gets skipped, because nothing forces it to happen once the request itself is approved. Doing it well means every attendee has their own step to complete, separate from the group's approval, so the record shows who actually finished the requirement rather than just who was on the original list.
Why the existing system does not cover it
Most districts already have a system that tracks staff credentials and licensure deadlines, whether that's a state reporting system or an HR platform. That system expects a finished record: hours completed, evaluation on file, requirement satisfied. It isn't built to produce that record itself. It has nowhere to capture whether four individual teachers each acknowledged the conditions of a conference before they went, or whether each of them actually turned in a receipt and an evaluation afterward. So the part of the process that generates the record, the actual completion by each person, happens somewhere else: an email approval, a paper sign-in sheet at the event, a stack of receipts that may or may not make it back to the office.
How districts handle it now
In most districts, a staff member, often a department head, submits one PD request on behalf of a group, and a supervisor approves it by replying to an email or signing a paper form. That single approval gets treated as covering the whole group. Whether every attendee actually agreed to the conditions, whether they all attended, and whether receipts and evaluations came back afterward gets tracked informally, if it gets tracked at all, usually by whoever in the curriculum office remembers to follow up.
Where it goes wrong
A single PD request for a four-person team touches an email approval, a paper sign-in sheet at the conference, a receipts folder in someone's desk drawer, and a follow-up email three weeks later asking whoever still owes an evaluation. Multiply that across every request a curriculum office handles in a year, across every building and every approval path, and it isn't any one person losing track of anything. It's a process with too many independent pieces and no single place holding them together. That's what Teton County School District #1's curriculum director, Megan Fouts, meant when she called the old way "shenanigans": a system with enough moving parts that something was always about to fall through the gap between them. "There will be no more shenanigans. This is so professional," she said, once the approval, the individual sign-off, the receipt, and the evaluation moved through one path instead of five.
What doing it well actually requires
Group approval and individual completion have to be tracked separately. One person can submit a PD request on behalf of a group, but the district needs proof that each attendee agreed to the conditions and completed the requirement, not just that a supervisor said yes to the request as a whole. Teton County School District #1 in Wyoming had exactly this gap before working with Flow Forms: one submission covered a whole group, with no reliable way to confirm every attendee had actually acknowledged the conditions or turned in what was required afterward.
Routing has to know which department owns which request, automatically. Curriculum approves some PD, Student Services approves other PD, and a request that lands in the wrong inbox is a request nobody is tracking. Flow Forms determines which department a request belongs to from rules configured with the district, so the request reaches the right approver without anyone sorting it by hand.
Receipts and evaluations are part of the requirement, not an afterthought once it's approved. A PD requirement that ends at approval treats the money and the accountability as separate problems. Districts running PD through Flow Forms have the receipt upload and the evaluation built into the same workflow the approval happened in, with automatic reminders until both are actually in hand, not chased down weeks after the conference is over.
Common questions
Questions we hear from every curriculum office.
- If one person submits a PD request for a whole group, does approving it cover every attendee?
- Approval covers the request, not each person's individual completion. Whether every attendee actually agreed to the conditions, attended, and turned in what's required afterward is a separate thing to track, and it's exactly the part that gets skipped when a group is treated as a single unit instead of individuals who each owe their own step.
- How do you make sure a PD request reaches the right department automatically?
- Requests get sorted correctly when the routing rule is set up in advance, based on the type of request rather than left to whoever reads the email first. Curriculum-related requests and student-services-related requests can follow different paths without anyone manually deciding which is which each time one comes in.
- What happens if a staff member never submits a receipt or evaluation after a professional development event?
- In most districts, it depends entirely on whether someone remembers to chase it. Without automatic follow-up built into the process, a missing receipt or evaluation often surfaces only when someone asks for it later, at which point the staff member may not remember the details or still have the receipt at all.
- Can a district require individual sign-off from every attendee even when one person submits the request?
- Yes, and it's the part most processes skip. A single submission can still generate a separate acknowledgment step for each named attendee, so the record shows who individually agreed to the conditions rather than treating the whole group as a single yes.
How Flow Forms handles it
Flow Forms routes a PD request to the right department automatically, Curriculum or Student Services, based on rules set up with the district, and every named attendee gets their own step to acknowledge the conditions even when one person submitted on their behalf. Receipts and evaluations are collected in the same workflow the approval happened in, with reminders that go out on their own until both are actually on file.
Teton County School District #1 in Wyoming runs its PD requests this way. Its curriculum director, Megan Fouts, described what changed in one line: "There will be no more shenanigans. This is so professional." A comment on a process that used to have too many independent pieces to hold together reliably.