Why Your SIS Doesn't Cover Program-Level Consent (And What Does)

If you're a student services director or health services coordinator in Texas, you've probably had this conversation at least once since September 2025: "Can't Skyward just handle this?" The answer, for enrollment-level consent, is yes. For what SB 12 and the rest of the new consent requirements actually demand? Not really.

The gap between what a Student Information System does well and what Texas districts now need for program-level consent is where most of the operational pain lives. Understanding that gap is the first step to closing it.

What Your SIS Was Built to Do

Student Information Systems like Skyward, PowerSchool, and Ascender are excellent at what they were designed for: managing student records, enrollment data, scheduling, grading, and annual parent-facing forms. Skyward's Family Access portal, for example, handles start-of-year enrollment packets well. Parents log in, review documents, provide e-signatures, and the district gets a basic completion report.

This workflow covers what we'd call enrollment-level consent: annual forms distributed once, signed once, tracked at a basic level. Directory information opt-outs under FERPA, standard media release forms, emergency contact authorizations. These are one-time, start-of-year events, and your SIS handles them fine.

The problem is that enrollment-level consent is no longer the whole picture in Texas.

What the New Requirements Actually Demand

Since September 2025, SB 12 requires districts to obtain and track parental consent across health services, mental health and counseling, and club or extracurricular participation. Layer on SB 9's sensitive content instruction requirements, HB 1605's sex education opt-in, and the SCOPE Act's data privacy consent, and Texas districts now manage 27 or more distinct consent categories throughout the school year.

The key word is "throughout." These aren't annual forms. A school nurse needs to verify health services opt-out status before every routine screening. A counselor needs confirmed opt-in consent before every session. An activity director needs consent on file before a student joins any non-curricular club. These are daily, per-student, per-program checks that recur all year long.

That's program-level consent, and it operates on a fundamentally different rhythm than what your SIS was designed around.

Where the Gap Shows Up on the Ground

When SB 12 took effect in September 2025, the Texas Tribune reported that school nurses across the state were confused about which services they could provide and to whom. Some districts took a robust approach, offering families selective opt-out forms for individual services. Others took an all-or-nothing stance because they didn't have the tools to track granular preferences.

The numbers tell the story. According to the Texas School Nurses Organization, approximately 40% of parents had not completed required consent forms within the first month of the school year. Under SB 12, unsigned forms must be treated as denial of consent. That left a significant portion of students without access to routine health services at school — not because their parents objected, but because the paperwork hadn't been processed.

A survey from Hamshire-Fannett ISD found that nurses spent an average of 90 minutes per day on consent verification alone during those first weeks. That's 90 minutes not spent on student care, repeated every day, because the tracking tools available weren't designed for real-time, per-student eligibility checks.

Five Things Program-Level Consent Needs That Your SIS Doesn't Offer

Your SIS collects forms. Program-level consent management requires something different.

Real-time staff-facing eligibility. A nurse or counselor needs to know, right now, whether a specific student has consent for a specific service. Not a spreadsheet to cross-reference. Not a portal report to download. A live answer: yes, no, or no response yet.

Automated follow-up with non-responding families. That 40% non-response rate doesn't fix itself. Districts using automated reminder workflows see response rates above 75%. Your SIS doesn't send targeted reminders to families who haven't responded to a specific consent request.

Per-program, per-student audit trails. When TEA or an auditor asks whether consent was on file before a counseling session on October 14th, the answer needs to be a timestamped record — not a folder of paper forms or a row in a spreadsheet.

Multilingual delivery beyond the portal. Skyward's Family Access requires a login and is primarily English-facing. For families with limited English proficiency or inconsistent internet access, a portal-dependent consent workflow misses them entirely. Program-level consent needs to reach families through multiple channels and in their home language.

Recurring consent cycles. Some consent categories require fresh authorization each semester, each grading period, or before each new instructional unit. Your SIS handles annual cycles. It doesn't handle mid-year consent collection for a new club, a spring health screening, or a second-semester sensitive content unit.

What Districts Are Actually Doing About It

In conversations with administrators across Texas, what we see is a spectrum. Some districts are managing with a patchwork: Skyward for enrollment forms, Google Forms for program-specific consent, spreadsheets for tracking, and a lot of manual follow-up. It works, technically, but it takes more time than it should, and the audit trail is scattered across systems that don't talk to each other.

Other districts have started moving to purpose-built consent management tools that sit alongside the SIS rather than replacing it. These systems handle the program-level workflow — distributing consent requests through text and email (not just a portal), tracking responses at the student-program level, sending automated reminders, and giving staff real-time eligibility data. The SIS stays the system of record for enrollment. The consent system handles everything the SIS wasn't built for.

A Hill Country district of about 9,000 students made this shift and saw campus-wide consent preparation drop from 3-4 hours per grade to about 15 minutes. That's not a marginal improvement. That's the difference between consent being a recurring operational burden and consent being a background process that staff barely have to think about.

The Question Isn't Whether — It's When

Every Texas district needs a plan for program-level consent. The legislative requirements aren't going away, and TEA's guidance has made clear that districts are expected to have systems in place. The real question is whether your district addresses the gap now — when you can plan and implement thoughtfully — or later, when the next compliance review or parent complaint forces the issue.

If your district is sorting through this, we work with districts across Texas on exactly these workflows. We're always happy to share what's working for others — reach out any time.