Skip to main content
Professional Development

PD requests shouldn't be
a full-time job.

Someone has to manage the requests, track the approvals, collect the receipts, and make sure everyone actually followed the rules. That someone is you, and the current process is making it harder than it needs to be.

No generic demo. We'll show you your process, fixed.

Trusted by
MT Office of Public Instruction · Billings Public Schools · Columbia Falls Schools · Gallatin County · BOCES 5 · Oklahoma Wesleyan University · Hardin Public Schools · Zoo Montana · City of Apopka · Sheridan County SD #2 · Weston County SD #7 · MT Office of Public Instruction · Billings Public Schools · Columbia Falls Schools · Gallatin County · BOCES 5 · Oklahoma Wesleyan University · Hardin Public Schools · Zoo Montana · City of Apopka · Sheridan County SD #2 · Weston County SD #7
What we hear

The process exists
on paper.
Somewhere.

Most schools have a PD approval process. In practice, it lives in someone's inbox — a PDF getting forwarded around, approvals happening over email, and steps that quietly get skipped every time because nothing enforces them.

When the workflow has gaps, requests fall through. Receipts don't come back. The wrong department gets looped in. A well-built form closes those gaps automatically — no extra conversations required.

Approvals happening over email

A request gets emailed to a supervisor. They reply yes. No record, no budget tracking, and no consistent way to make sure the right department was even part of the conversation.

One person submitting for a whole group

A department head sends in one form for four staff members, but each person is supposed to acknowledge the conditions of the PD. That step quietly disappears every time.

Receipts never come back

Staff go to the conference, spend the money, and forget to submit receipts. Now you're chasing them down weeks later, or writing it off and hoping nobody asks.

Wrong department gets the request

Curriculum approves some PD. Student Services approves others. Nobody remembers which is which, and submissions end up going to whoever seems right at the time.

From the field

What it looks like
when it's working.

The same process. Finally enforced.

Jackson Hole ran PD requests the way most schools do: PDFs emailed to supervisors, approvals by reply, no reliable way to make sure every attendee had actually acknowledged the conditions. Receipts came back when they came back.

When the workflow went live, that changed. Every request reached the right approver. Every attendee signed individually. Receipts came back automatically. The process finally worked the way the policy said it should.

There will be no more shenanigans. This is so professional.”

— Megan Fouts, Curriculum Director , Teton County School District #1

Schools using Flow Forms for PD

Sheridan County SD #2Carbon County SD #2Teton County SD #1Fremont County Schools #6Park County SD #6Fremont County SD #38Big Horn County #1
How it works

One submission.
Every step covered.

A single staff member submits the request, even on behalf of a whole group. From there, Flow Forms handles the rest: routing to the right approver, collecting individual acknowledgments from each attendee, and following up on receipts and evaluations when the time comes.

Nobody falls through the cracks. The system follows up automatically, so you don't have to be the person sending the third reminder email.

01

Automatic approval routing

Flow Forms determines whether a request goes to Curriculum or Student Services based on how the workflow is set up with your team — no guessing, no wrong-department emails.

02

Individual sign-off for group requests

One person submits for a whole group, but every attendee receives their own acknowledgment step. All conditions get agreed to individually, and no one slips through.

03

Automatic reminders

Receipts, evaluations, supervisor signatures. The system tracks what's outstanding and follows up on its own. Submissions don't get stuck and staff don't get to forget.

04

Receipt upload built in

Attendees upload receipts and submit evaluations directly through the same workflow — no separate form, no separate email thread, no chasing.

What we build

The full PD request
lifecycle.

From first submission to filed receipt, every step of the process handled, tracked, and closed out.

Conference & Workshop Requests

Staff submit PD requests with all required detail in one place. Group submissions supported — one person can request on behalf of multiple attendees.

Smart Approval Routing

Flow Forms automatically determines whether a request goes to Curriculum or Student Services based on your rules — no manual sorting and no wrong-department submissions.

Individual Attendee Sign-Off

Even when one person submits for a group, every attendee receives their own step to acknowledge conditions. No one attends without agreeing to the rules.

Receipt & Expense Collection

Staff upload receipts directly through the workflow after the PD. Reminders go out automatically until it's done — no more chasing people weeks later.

PD Evaluations

Post-conference evaluations collected in the same workflow. Staff complete them before the process closes — not months later when nobody remembers.

Complete Audit Trail

Every request, approval, signature, receipt, and evaluation logged in one place. When questions come up, the answer is a search, not a folder hunt.

Every request submitted. Every credit tracked.

Nothing lost in email.

Let's talk

See what done looks like.

Tell us how your PD process works today. We'll show you exactly how we'd fix it — no generic demo, no pressure.

No commitment. No deck. Just your process and ours.

Smart routing to the right approver
Individual sign-off for group requests
Automatic reminders. No chasing