Judgment Calls: Drawing the Line Between What Algorithms and Educators Should Decide
Photo: 999real, CC0, via Wikimedia Commons
Walk through any district administrative office in 2025 and you will find artificial intelligence quietly at work. Software sorts bus routes, predicts enrollment dips, flags chronic absenteeism, and drafts parent communications. Much of this is genuinely useful. Some of it, however, has begun to creep into territory that no algorithm should occupy: decisions about children, careers, and consequences.
The question facing school leaders is no longer whether to adopt AI. It is where to draw the line—and whether they can articulate that line clearly enough to defend it to a school board, a reporter, or a parent at a PTA meeting.
The Temptation of Efficiency
The appeal is understandable. Principals are drowning in administrative load, and vendors arrive with compelling demos: an engine that screens résumés, a dashboard that recommends disciplinary responses, a model that scores student writing in seconds. Each tool promises to reclaim hours that leaders desperately need.
But efficiency gains come bundled with an uncomfortable transfer of authority. When a district adopts a tool that recommends which students receive intervention, or which candidates advance to a second interview, it has not merely automated a task. It has outsourced a judgment—and, with it, accountability. When the algorithm errs, and it will, the district cannot credibly claim that a vendor's black box made the call. The superintendent's signature is still on the policy.
A Two-Question Test for Every AI Adoption
Leaders need a filter they can apply before any tool touches a consequential decision. Two questions suffice.
First: Does this decision involve a specific human being's future, rights, or reputation? If yes—hiring, discipline, special education placement, grades, teacher evaluation—it belongs to a person. Pattern analysis may inform the decision, but a human must own it, review the inputs, and be able to explain the reasoning without hiding behind a confidence score.
Second: Can the district explain, in plain language, how the recommendation was produced? If no one on staff can articulate what the tool actually does, the district is not deploying AI; it is deferring to it. That distinction matters legally under emerging state-level AI statutes and matters ethically everywhere.
Where Algorithms Belong
There is real value in computational muscle, and leaders should claim it without apology. Appropriate domains share three traits: they involve populations rather than individuals, they are reversible, and they are verifiable.
- Scheduling and logistics. Master schedules, bus routing, and substitute coverage are optimization problems. A model can test thousands of configurations a human never could.
- Early-warning aggregates. Attendance trend data at the school or district level can surface systemic issues—say, a ninth-grade cohort disengaging after lunch periods—without labeling any individual child.
- Resource forecasting. Enrollment projections, budget scenario modeling, and facilities planning benefit enormously from analytic tools that stress-test assumptions.
- Drafting and summarizing. First drafts of routine correspondence or board summaries, always reviewed by a human, are low-risk time savers.
In each case, the output is a starting point, not a verdict.
Where It Must Never Go
Some decisions are constitutive of what it means to run a school. Discipline determinations, hiring and termination, special education eligibility, student evaluation, and teacher ratings all involve individual stakes, legal exposure, and moral weight. Delegating them to a model—however sophisticated—reduces persons to data points and districts to bystanders in their own institutions.
The record so far is cautionary. Automated screening tools in hiring and admissions have repeatedly reproduced the biases of their training data. A district that adopts such a tool for teacher recruitment is not neutral on equity; it has simply relocated its bias into software that is harder to interrogate.
Governance Before Purchase
The practical recommendation is straightforward: no AI tool should enter a district through a procurement back door. Boards should require an inventory of every algorithmic system in use, a documented human-review requirement for consequential outputs, a designated administrator accountable for each tool, and an annual audit of outcomes disaggregated by student subgroup.
None of this slows innovation meaningfully. It simply ensures that when the difficult question arrives—who decided this, and how—the answer is a person with a defensible rationale, not a vendor's documentation.
Schools are institutions of human formation. Their tools should serve that mission, never quietly redefine it.