Minnesota districts build their own teacher evaluation model under statutes 122A.40 and 122A.41, on three components: teacher practice, student engagement, and student learning (35% growth). Where AI helps with the write-up, where it doesn't.

How can AI help Minnesota evaluators write teacher evaluations?

August 02, 20269 min read

How can AI help Minnesota evaluators write teacher evaluations?

Minnesota districts build their own teacher evaluation model under statutes 122A.40 and 122A.41, on three components: teacher practice, student engagement, and student learning (35% growth). Where AI helps with the write-up, where it doesn't.

Minnesota evaluates teachers differently from most states, and the difference shapes where AI fits. There is no single statewide rubric. Instead, each district designs its own Teacher Development and Evaluation model, in agreement with its local union, resting on three components: teacher practice, student engagement, and student learning and achievement. AI can genuinely help with the first — mapping observation evidence to the right component of the teacher-practice rubric and drafting feedback in the framework's own language. What it can't do is measure student engagement or growth, run peer review, or combine the three components into a summative result. This post walks through where AI helps with Minnesota's system, where it doesn't, and what to look for.

What Minnesota's system actually is

Under Minnesota Statutes 122A.40 and 122A.41, every district must have a teacher development and evaluation process — usually shortened to TDE. The design decisions happen locally: a district, through joint agreement with its local teacher union, builds its own TDE model, or it uses the state example model the Minnesota Department of Education published. In practice, the overwhelming majority of districts have built their own local models, though many borrowed concepts from the state example.

What the statute fixes is the shape. A Minnesota evaluation must rest on three components, must use a teacher-practice rubric grounded in the state's professional standards, and must include peer review. It's a process-oriented, locally bargained system rather than one statewide instrument — which is exactly the context an AI tool has to respect.

The three components

A Minnesota teacher evaluation is built on three components:

Teacher practice. Professional practice measured against a rubric based on the Standards of Effective Practice. This is the classroom-observation piece — the part an evaluator documents in writing.

Student engagement. Longitudinal data on student engagement and connection, drawn from measures the district selects within its model.

Student learning and achievement. Student growth measures — value-added models or student learning goals, and measures that include the academic literacy and achievement of English learners — that determine 35% of the summative result.

The teacher-practice component is where the documentation hours live, and where AI has something real to offer.

The teacher-practice rubric and the Standards of Effective Practice

Minnesota law requires that the teacher-practice rubric be based on the Standards of Effective Practice in Minnesota Rules 8710.2000, include culturally responsive methodologies, and describe performance across at least three levels. It does not mandate a single rubric or a single set of rating labels — those are local decisions.

Most Minnesota districts use the Danielson Framework for Teaching, which maps cleanly to the Standards of Effective Practice, so it's worth naming its four domains:

Planning and Preparation. Knowledge of content, students, and resources, and coherent instructional design and assessment planning.

Classroom Environment. A culture of respect and rapport, clear expectations, managed routines, and a space that supports learning.

Instruction. Clear communication, strong questioning and discussion, engaging students in the work of learning, and using assessment to adjust in the moment.

Professional Responsibilities. Reflection on practice, accurate record-keeping, communication with families, professional growth, and contribution to the school community.

Because Minnesota requires at least three levels but sets no labels, a Danielson district typically uses the framework's four — Unsatisfactory, Basic, Proficient, Distinguished — while another district's model may use different terms.

Peer review and the every-three-years rhythm

Two more features shape the work. Minnesota's TDE process includes peer review and peer coaching, with trained observers or teacher peers involved in the process, and it requires a summative evaluation at least once every three years for continuing-contract teachers. Between summative years, the emphasis is on growth, feedback, and coaching rather than a rating.

That rhythm means the teacher-practice documentation, when it happens, needs to be thorough and defensible — the summative that anchors a three-year window.

After the observation: where the work piles up

The observation itself is familiar work for an experienced Minnesota evaluator. The write-up that follows is where the hours go: taking fragmentary observation notes and organizing them as evidence against the right components of the teacher-practice rubric, settling on a defensible level for each, and drafting feedback a teacher can act on — across a caseload, and in a way that will stand up as the summative record.

Where AI helps with the Minnesota write-up

The strongest fit between current AI and Minnesota's system is that teacher-practice documentation.

AI handles three parts of it reliably. First, it turns fragmentary notes into coherent, evidence-anchored prose in the framework's language — the difference between "kids explained their reasoning to each other" and a sentence tied to the instruction domain. Second, it maps evidence to the right component, including evidence that supports more than one. Third, it holds consistency across a caseload, so the same quality of evidence lands in similar territory from teacher to teacher rather than drifting with the hour of the night.

For Minnesota specifically, the value is drafting in the rubric's own language and toward your district's levels, so the teacher-practice write-up is ready for the summative rather than something you have to translate first.

Where AI doesn't help — and what stays with the evaluator

The honest scope follows from how Minnesota built the system.

AI cannot measure student engagement or student growth. Tools like EvalScribe draft the teacher-practice component. The student engagement component, the student learning and achievement component (the 35% growth share), and the combination of all three into the summative result are handled in your district's TDE process.

AI cannot run peer review. Peer review and peer coaching are collaborative, human parts of Minnesota's process by design, and they stay that way.

AI cannot supply an evaluator's professional and local judgment — what the evidence really shows, how a teacher's year unfolded, how a rating fits the context. That stays with the evaluator, who remains the last set of eyes on every rating and comment.

And general-purpose AI in particular has no built-in understanding of how Minnesota works. Paste notes into a consumer chatbot and it will invent components, assume a single statewide rubric that doesn't exist, and reach for rating labels your district may not use. For a summative that anchors a three-year window, those errors are the kind that surface at the worst possible moment.

What to look for in an AI tool for Minnesota

A few questions worth asking before committing a tool to this work.

Does the tool actually know the Danielson domains and the Standards of Effective Practice, or does it produce generic "good teaching" language?

Does it draft toward your district's rubric and labels rather than assuming a single statewide scale?

Does it stay in its lane, drafting teacher practice and leaving student engagement, the 35% growth, peer review, and the summative to your district?

Where does your observation data live? Is it stored on the vendor's servers, or used to train models?

How EvalScribe handles Minnesota evaluations

EvalScribe is built around the four Danielson domains, aligned to Minnesota's Standards of Effective Practice. An evaluator captures notes by typing, dictating, or photographing handwriting (Smart Scan OCR converts it to text), EvalScribe maps that evidence to the component it supports, and drafts a rating and evidence-anchored feedback for each — using the framework's own language and drafting toward your district's rubric levels. Every rating and comment is fully editable before you finalize it, and the evidence stays traceable to the note it came from.

Two scope notes, because Minnesota's structure calls for them. First, EvalScribe drafts the teacher-practice component — the observation piece. The student engagement component, the student learning and achievement component (the 35% growth share), peer review, and the combination of all three into the summative result are handled in your district's TDE process, not the app. Second, because each district builds its own model with its union, EvalScribe is built around the Danielson Framework and the Standards of Effective Practice it aligns to, so it fits districts using Danielson or a Danielson-aligned local rubric. Confirm your district's adopted model.

Beta testers report saving 30 to 60 minutes per evaluation versus writing the documentation by hand. Across a full caseload, that adds up to dozens of hours back — hours that can go to the coaching and feedback Minnesota's model is built around. More detail on the Minnesota workflow is available at evalscribe.com/minnesota.

Frequently asked questions about Minnesota's TDE and AI

How does teacher evaluation work in Minnesota? Each district builds its own TDE model with its union, or uses the state example model, on three components: teacher practice, student engagement, and student learning and achievement. EvalScribe drafts the teacher-practice component.

How much of a Minnesota evaluation is student growth? Student growth measures determine 35% of the summative result. EvalScribe drafts the teacher-practice piece; the growth share is handled in your district's process.

Does Minnesota require a specific rubric? No single statewide one — the rubric must be based on the Standards of Effective Practice with at least three levels. Most districts use Danielson.

What are Minnesota's rating levels? At least three levels, with labels set by your district's model. Danielson districts typically use Unsatisfactory, Basic, Proficient, Distinguished.

Does EvalScribe handle peer review and the summative? No. Those stay in your district's TDE process. EvalScribe drafts the teacher-practice observation write-up that anchors them.

If you're evaluating teachers in Minnesota, see how EvalScribe drafts in the Danielson domains and your district's rubric at evalscribe.com/minnesota. Questions, or a school or district license? Reach the team at [email protected].

References

Related articles


Page maintained by Anthony D. Neely, Ph.D. — practicing K-12 educator with nearly 20 years in the classroom, 2025–2026 Walker County Distinguished Teacher of the Year, and co-founder of EvalScribe. Framework details verified against the Minnesota Department of Education's Teacher Development and Evaluation guidance and Minnesota Statutes 122A.40 and 122A.41.

Last updated on August 2, 2026.

Anthony D. Neely, Ph.D.

Anthony D. Neely, Ph.D.

Anthony Neely is the Founder of EvalScribe, a veteran educator, an AI integration consultant for teaching & learning, researcher, & author.

Back to Blog