Think about the workflows your district runs on — approvals, screeners, compliance filings, vendor contracts, and more. Ask yourself this question: What happens if the person who owns that process is out tomorrow?
If your answer is some variation of “things slow down” or “we have to go digging,” you might think you have a staffing problem. What you actually have is a systems problem, one that IT leaders are responsible for solving.
Manual workflows that rely on printed PDFs, email threads, shared drives, and one person’s institutional knowledge are commonplace in many K-12 environments. They seem functional until something inevitably falls through the cracks.
- You miss a federal deadline.
- You delay support for a student because a form didn’t route correctly.
- You spend an afternoon chasing down a request that’s been sitting in someone’s inbox for two weeks.
Unfortunately, these aren’t edge cases. They’re exactly what happens when you build critical processes on tools that were never designed to handle them. For K-12 IT leaders, the stakes are only getting higher.
Compliance obligations are non-negotiable, headcount isn’t growing, and the expectation to do more with less isn’t going away. The districts managing this well aren’t adding staff — they’re building systems that keep running no matter who’s in the office that day.
What a Modern Workflow Actually Looks Like
This might sound like a pipe dream, but it’s more achievable than you might expect with intentional workflow design and purpose-built tools. Without that level of intention, dependency starts to form around whoever knows how to keep things running. A well-designed workflow removes that risk. It offers:
- One structured intake: There’s a single place to submit a request, rather than three different forms scattered across shared drives and email chains.
- Automated routing: Requests move to the right people based on rules you set, not based on whoever remembers to forward it.
- Built-in deadline tracking: The system monitors timelines so a person doesn’t have to.
- Automatic reminders: Follow-ups go out without anyone sending them manually.
- Real-time status visibility: When someone is wondering where a request stands, they can simply log in to find the answer. No digging or endless back-and-forth.
- Reporting without manual effort: When you need to demonstrate compliance or find a bottleneck, the data is already there.
A modern workflow is about more than convenience. It’s how you prove compliance, identify where things get stuck, and stop wasting hours figuring out what happened to a request that should have been closed weeks ago.
From Workarounds to Workflows: How Two Districts Built Processes That Scale
Knowing what a modern workflow should look like is one thing. Building one — inside a real district with real constraints, pressures, and risks — is another.
Take a look at how two different school districts made it happen.
Richland One: Making a Broken Approval Process Visible
Richland School District One (“Richland One”) serves more than 21,000 students across 51 sites in Columbia, SC. Like most districts, they had a process for approving new digital tools and resources before educators could use them with students. They called this process the Digital Requisition Acquisition Process Expedited — more commonly referred to as DRAPE. But, despite the name, there was nothing expedited about it.
These requests moved as paper packets — one department at a time, one person at a time. They lived in email folders, shared drives, and even individual OneDrives. Unfortunately, a DRAPE could sit unseen for weeks.
Nobody knew it was stuck because nobody could see it.
That visibility problem cut both ways. Staff couldn’t see where their requests stood, and IT couldn’t see where things were getting held up. And when someone left the district, all of the documents they’d saved locally went with them. Richland One knew something needed to change, so the district rebuilt DRAPE in Softdocs with a single structured intake form. It provides one place for staff to submit requests, with all of the necessary information collected upfront.
From there, routing is automatic. Requests move to the right reviewers in the right sequence without anyone forwarding an email or chasing paperwork. Every department sees what’s in their queue, what’s pending, and what’s already been approved.
In this live, panel-style conversation (no slides), the Richland One team will share how they made approvals faster, improved cross-department collaboration, and built a more transparent, reliable process for staff across the district. You’ll hear directly from the IT leaders and system administrators who support these workflows every day and see the impact firsthand. Duration: 60 minutes.
IT can now pull up a dashboard and see exactly how many requests are active, where each one sits, and how long it’s been in each step.
As Dr. Candice Coppock, Executive Director of IT, explained, “When people say, ‘These things are tied up in IT,’ we can say, ‘No, it’s been in the supervisor’s queue for 100 days. It never made it to IT.’” That kind of transparency changes the conversation.
The results were immediate. Requests that used to take months now move in about a week when submitted correctly. And because everything is stored centrally, documentation survives staff turnover and role changes. So, when auditors (or anyone else) ask questions, the answers are always just a few clicks away.
Kyrene School District: Automating a Federal Compliance Deadline
Kyrene School District in Tempe, AZ, serves 13,000 students across 25 schools. Every year, more than 1,300 kindergarteners enroll—and every one of them (along with any other new students) is required by federal law to complete a 45-day screener. This assessment is designed to identify potential hearing, vision, behavioral, or learning concerns within the first 45 days of school.
It’s a tight window, and missing it doesn’t just bring on administrative headaches. It also means a student who might need support won’t get it, and that the district is non-compliant.
Previously, the process was patched together with a lot of manual effort and institutional knowledge. Teachers received individualized links generated through a complex mail-merge process. Staff spent one to two hours every week syncing spreadsheets, sending reminders, and manually routing completed forms to principals. Parent notification letters required separate tools. And keeping track of who had completed their screener (and who hadn’t) meant chasing down schools one by one.
Compliance shouldn’t depend on who’s in the office that day. But that’s exactly what Kyrene was up against.
Kyrene rebuilt the entire process end-to-end in Softdocs. Now, once a student has been enrolled for 21 days, their information is automatically uploaded, and a pre-filled screener is generated—with no manual setup or mail merges. Teachers receive an email notification with everything already populated, while automated reminders handle follow-up.
The 45-Day Screener is more than a compliance requirement. It’s about giving educators clarity, giving administrators confidence, and giving students the timely support they deserve. Join Christie McDougall from Kyrene School District for a 30-minute demo of their 45-Day Screener workflow—one of the most important processes districts manage each year. Duration: 30 minutes.
When a screener is completed, it routes automatically:
- If no concerns are flagged, the workflow closes and files on its own.
- If concerns are present, it goes directly to the principal for review.
Parent notification letters are generated within the same system, which also automatically captures dates for compliance.
The results speak for themselves. Kyrene processed more than 1,700 screeners in the first four months after launch—putting them on pace to exceed their volume for the full prior year. The staff’s weekly workload dropped from one to two hours to about 10 minutes.
State monitoring, which previously took days, now takes roughly an hour. "For state monitoring, we'll be able to finish in maybe a minute per kid,” said Christie McDougall, Director of Assessment and Student Outcomes. “We just pull the data from Softdocs. No more contacting schools or digging through files."
If a teacher leaves mid-year, the workflow doesn't break. Forms are reassigned, and the process keeps moving.
Don’t Let the Patch Become the Problem
Richland One and Kyrene are different districts with different challenges. But they were both running the same playbook: patching critical processes with manual effort and tools that were never built for the job. They are both proof that, eventually, the patches stop holding. If your district is still running high-stakes workflows on email and spreadsheets, these are the reminders worth paying attention to:
-
If it lives in email, it's not scalable. Inboxes weren't built to manage approvals, track deadlines, or give anyone else visibility into where things stand.
-
If one person owns the process, it's fragile. The moment they're on leave or gone, the process is at risk.
-
If deadlines aren't automated, you're exposed. Manual tracking is only as reliable as the person doing it.
-
If status isn't visible, frustration is inevitable. Staff lose confidence in processes they can't see—and that frustration lands on IT.
-
If you can't measure it, you can't improve it. Without data, you're managing by feel.
Ultimately, districts don’t need more tools and stopgaps. They need one system that’s built for the way schools actually operate—one that’s supportive, secure, visible, and reliable enough that compliance doesn’t depend on any one person to hold it all together.
Want to see what this looks like in practice? Explore how other schools are approaching it or schedule a quick walkthrough to see how it could work in your environment.
Tags
.png)
