The CharterLab

Compliance Mistakes That Sink Charter Schools

@charterlab Season 1 Episode 9

Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.

0:00 | 14:43

https://charterlabconsulting.org

SPEAKER_00

So every charter school leader has had this moment. Someone asks a very simple compliance question, something like, Did we submit that CalPADS report yet? Or did we submit our LCAP on time? And suddenly three people in the room look at each other, and one says, Well, I thought you submitted it. Another says, I thought the consultant submitted it. And someone else says, Wait, which report are we talking about? Now, most of the time, that moment ends with someone sending an email and everything works out. But occasionally, those small moments turn into very large conversations during oversight visits or renewal reviews. And that's why today we're talking about charter code system four, the Almighty Compliance. Because in the charter world, compliance isn't paperwork, it's protection. Welcome back to the Charter School's work. I'm your host, Don Patzer, a longtime charter school administrator and creator of the Charter Code Framework. On this podcast, we talk about the real mechanics behind successful charter schools, not just the vision language and charter petitions, but the operational systems that actually keep schools strong, sustainable, and defensible. Each episode, we break down one of the seven systems of the charter code, a framework built from years of experience working inside charter schools and alongside authorizers. Today we're stepping into charter code system for compliance. Now I realize something, of course, compliance is not exactly the topic that gets people excited. Nobody walks into a charter conference and says, before we start, the keynote, can we all talk about all our reporting deadlines? That's usually not the room with the long line outside the door. But here's the truth: every experienced charter leader eventually learns. Charter schools rarely fail because of academics, they fail because of compliance mistakes. And most of those mistakes are completely preventable. The compliance reality is that if you've spent enough time around charter schools, you start noticing a pattern. Schools that get in trouble rarely believe they're doing anything wrong. They're working hard, they care about students, they're solving problems every day, but they're also moving really fast. And when organizations move fast, systems sometimes fall behind. Policies don't get updated, board trainings get postponed or ignored. Someone assumes report, like we said earlier, gets filed. And someone also assumes someone else filed it. And eventually someone says a sentence every charter leader has heard. Wait, who is responsible for that? So I'm going to share with you a couple stories. This is just from stories that I've heard out in the charter world. Um, I once saw a school uh with a strong academic program, great teachers, happy families, solid results. What could be wrong? But during a renewal review, the authorizers started asking questions about, of all things, board agendas, specifically when they were posted. And if you've dealt with the Brown Act, you know the rule. Agendas must be postponed 72 hours in advance. It's a simple rule, except sometimes people get busy. Someone says, we'll post it tonight, and technically, tonight might be a little closer to that meeting than the law prefers. It's nothing malicious, just a habit that uh developed over time. And during renewal, that habit suddenly became very interesting to the authorizer. So small compliance habits become big conversations when the stakes are high. And so some of the myths that revolve around compliance, and one of the biggest myths is charter leadership, um, in charter leadership is that compliance is basically paperwork. Something that lives in a binder or spreadsheets or a folder labeled compliance stuff important. But authorizers don't see compliance as paperwork, they see it as evidence. Evidence that the organization running the school is capable of managing a public institution responsibly. Because remember, always remember that charter schools are public schools. They operate with public funds, and authorizers are responsible for ensuring those schools follow the law. So when compliance systems appear sloppy or reactive, authorizers don't see a documentation problem, they see organizational risk. And risk gets attention. Inside the charter code, system four organizes compliance into four major pillars. These pillars support the stability of the entire organization. And because eventually every charter school faces some level of scrutiny. Oversight visits, audits, renewal reviews, new district leadership. And when that moment arrives, systems matter. That first pillar within the charter code is the governance. Charter boards govern public institutions, which means they operate under rules like the Brown Act compliance, conflict of interest disclosures, public transparency, board policies, accurate minutes. Most governance mistakes aren't caused by bad actors, they're caused by good people who are never trained properly. Board members are often volunteers, you know, parents, community leaders, business professionals, people who genuinely want the school to succeed, and suddenly they're responsible for governing a public agency. It's a big leap, which is why strong charter schools treat board training as a system, not a one-time orientation. So that leads us into our second pillar, which is financial compliance. If you want to see how quickly authorizers can become interested in a school, start showing signs of financial instability. Academic concerns create discussions, but financial concerns create meetings, balanced budgets, multi-year projections, clean audits, responsible reserves, and internal controls. These are signals that the school is managing public funds responsibly. Which leads us into our next little war story. That is the audit surprise. So a cheat charter leader once described their annual audit to me as pretty straightforward, which is a phrase that tends to make auditors quietly reach for another cup of coffee. Most audits do go smoothly, but occasionally auditors discover something unexpected. Maybe documentation isn't complete, or maybe the financial procedures weren't followed exactly the way they were written. Suddenly, what was supposed to be a routine audit becomes a much longer meeting. And most of the time, the issue isn't fraud, it's simply systems that weren't quite tight enough. Which is why strong financial controls are one of the best compliance investments a school can make. The third pillar is programmatic compliance. This includes areas like special education, English learner services, attendance accounting, independent study rules, teacher credentialing. These are areas that are all governed by educational law, which means they're not optional. Charter schools can be very creative in designing programs, but education code still exists. And education code tends to win arguments every single time. Okay, our fourth pillar is reporting compliance. This is where charter schools interact with state reporting systems. These are systems such as CalPADS, LCAP, SARC reports, dashboard indicators, and oversight reports. If you've worked in charter schools long enough, you've probably looked at a data report and thought, well, that's interesting. Because at some point, um every charter leader learns that data systems have personalities. But again, the issue isn't one mistake, it's patterns. Repeated reporting issues signal weak internal systems, and that invites additional oversight. Alright, another war story, the renewal file. An authorizer once told a charter leader something very simple during a renewal meeting. He said, renewal is rarely about what happened this year, it's about the pattern we see over time, and that's really the key insight. Renewal reviews aren't looking for perfection, they're actually looking for consistency, consistent academics, consistent finances, consistent compliance. And when those systems are stable over time, renewal tends to be a calm conversation, which is actually how renewal should feel. So the charter code rule. Inside the charter code, there's a simple rule when it comes to compliance, and that is never give your authorizer an easy reason to question you. Again, never give an authorizer an easy reason to question you. Strong compliance systems keep the focus on student outcomes. Weak compliance systems shift the conversation toward oversight. And that oversight can change the entire dynamic of the relationship. So before we wrap up today's episode, let's open the charter lab inbox. This is where we take questions from charter leaders navigating real operational challenges. So question one is um about board training. So how much board training should charter boards receive? Um, I would say more than most boards currently receive. Board members should understand things such as Brown Act rules, conflict of interest requirements, financial oversight, and authorizer expectations. Strong boards make strong schools. Question number two revolves around CalPAD's errors. Um, our authorizer mentions some CalPADS errors. Should we worry? Well, um, like in anything, one error usually isn't a crisis, but repeated errors can signal um weak in internal um data systems. So a simple solution is a two-person verification process before submissions. One person prepares the report, another reviews it. All right, our next question is about renewal preparation. Our renewal is two years away. What should we focus on? So renewal decisions are based on patterns over time. So focus on academic outcomes, financial stability, and organizational compliance. And when those systems are strong, renewal becomes far less stressful. So focus on those three things academic outcomes, financial stability, and organizational compliance. Be able to tell that story, start preparing that narrative, and you should be in good shape. Timeline you know, most uh charter renewals start looking at their process anywhere from 18 to 24 months. All right, in closing, um, charter schools are mission-driven organizations built by educators and community leaders who want to create something better for students. But they are also public institutions, which means transparency, accountability, and operational discipline matter. So compliance systems don't limit a charter's vision. They protect it. They protect the board, they protect the leadership, and most importantly, they protect the charter itself because without the charter, the mission disappears with it. And that's the purpose of Charter Code System 4. Not bureaucracy, protection. Thanks for joining me for another episode of the Charter Lab Podcast. If you're enjoying the show, share it with a charter leader, board member, or educator working to build strong schools. And if you want to learn more about the charter code framework and the work we're doing to support charter schools, visit charterlabconsulting.org. Till then, stay clear, stay alive, and stay authorized or ready. I'm Don Patzer, and this is the Charter Lab Podcast. Have a good one, everybody.