How can AI help Oregon evaluators write teacher evaluations under the Model Core Teaching Standards?
How can AI help Oregon evaluators write teacher evaluations under the Model Core Teaching Standards?
Oregon's teacher evaluation system runs on the Oregon Model Core Teaching Standards — the state's adoption of the InTASC Model Core Teaching Standards under ORS 342.856. Every Oregon district builds its own evaluation and support system around this ten-standard, four-domain rubric, with a four-level rating scale (Does Not Meet, Developing, Proficient, Exemplary). AI can meaningfully help with the documentation burden of Oregon evaluations: translating observation notes into rubric-aligned language, mapping evidence to the ten standards, and producing draft ratings consistent with the framework. AI does not replace evaluator judgment — particularly the Proficient-to-Exemplary call that pivots on cultural responsiveness as an active asset and student ownership of learning. AI also doesn't handle Oregon's distinctive Student Learning and Growth (SLG) goal-setting process, which stays with the teacher and evaluator. Where AI lifts the most weight is the observation-based write-up itself.
What Oregon's teacher evaluation system is
The Oregon Framework for Teacher and Administrator Evaluation and Support Systems is administered by the Oregon Department of Education (ODE). Statutory authority sits at ORS 342.856, which requires Oregon to adopt Model Core Teaching Standards for use across the state's teacher evaluation systems. Licensure — a related but separate function — is handled by the Teacher Standards and Practices Commission (TSPC).
Unlike states with a single mandatory statewide rubric applied uniformly across every district (Georgia TKES, Texas T-TESS, Florida FEAPs, Tennessee TEAM, Arkansas TESS, North Carolina NCEES, Mississippi PGS), Oregon uses a district-flexibility model. Every district designs its own evaluation and support system through a collaborative process between teachers and administrators. What ties every district's system together is the shared foundation of the Oregon Model Core Teaching Standards — the ten-standard rubric that every district's system must be grounded in.
The Oregon Framework requires three components in every district's system: (A) Professional Practice, (B) Professional Responsibilities, and (C) Student Learning and Growth (SLG). Professional Practice and Professional Responsibilities are the observation-based components — where the ten standards actually get applied through walkthroughs, formal observations, and post-observation conferences. Student Learning and Growth is the goal-setting component, and it's distinctive enough to Oregon that it deserves its own section below.
The four domains and ten standards
The Oregon Model Core Teaching Standards organize teaching practice into four domains covering ten standards, mapped directly from the InTASC Model Core Teaching Standards developed by the Council of Chief State School Officers.
Domain A: The Learner and Learning covers three standards. Standard 1 (Learner Development) asks whether the teacher understands how students develop across cognitive, linguistic, social, emotional, and physical areas — and designs developmentally appropriate learning experiences. Standard 2 (Learning Differences) asks whether the teacher uses understanding of individual differences, diverse cultures, and community context to create inclusive learning environments. Standard 3 (Learning Environments) asks whether the teacher works with others to create environments supporting individual and collaborative learning, positive social interaction, active engagement, and self-motivation.
Domain B: Content covers two standards. Standard 4 (Content Knowledge) asks whether the teacher understands the central concepts, tools of inquiry, and structures of the discipline — and makes content accessible and meaningful. Standard 5 (Application of Content) asks whether the teacher connects concepts across disciplines and uses differing perspectives to engage learners in critical thinking, creativity, and collaborative problem solving related to authentic local and global issues.
Domain C: Instructional Practice covers three standards. Standard 6 (Assessment) asks whether the teacher uses multiple assessment methods to engage learners in their own growth, monitor progress, guide instructional decisions, and track progress toward SLG goals. Standard 7 (Planning for Instruction) asks whether the teacher plans instruction that supports every student in meeting rigorous learning goals by drawing on content knowledge, pedagogy, cross-disciplinary skills, and knowledge of learners and community. Standard 8 (Instructional Strategies) asks whether the teacher understands and uses a variety of instructional strategies to encourage deep understanding of content and build skills for meaningful application.
Domain D: Professional Responsibility covers two standards. Standard 9 (Professional Learning and Ethical Practice) asks whether the teacher engages in ongoing professional learning, evaluates the effects of practice on students, and adapts practice to meet each learner's needs — including analysis of SLG data. Standard 10 (Leadership and Collaboration) asks whether the teacher seeks leadership roles, collaborates with learners, families, colleagues, and community members, and contributes to advancing the profession.
Ten standards. Three, then two, then three, then two. That's the surface area Oregon evaluators document across every observation write-up.
The rating scale and the Proficient-to-Exemplary pivot
Oregon uses four performance levels: Does Not Meet, Developing, Proficient, Exemplary.
Does Not Meet (Level 1) indicates performance below expectations — the teacher lacks understanding of the standard and requires direct intervention and support. Developing (Level 2) indicates the teacher is making sufficient progress toward meeting the standard, meeting expectations most of the time with continuous improvement expected. Proficient (Level 3) is the expected standard: the teacher consistently meets expectations and demonstrates effective practices with impact on student learning. Exemplary (Level 4) is beyond effective: the teacher consistently exceeds expectations, demonstrates highly effective practices, and expands expertise through leadership opportunities.
The Proficient-to-Exemplary distinction is the sharpest calibration call in Oregon's framework, and it pivots on two consistent themes across nearly every standard.
The first pivot is cultural responsiveness as an active asset rather than a passive stance. At Proficient on Standard 2 (Learning Differences), the teacher plans instruction that is inclusive and responsive to individual and cultural differences — differentiation is built in for ELs, students with IEPs, and students from diverse backgrounds. At Exemplary, the teacher "deliberately leverages student diversity as an instructional asset" and creates conditions where "all students see themselves reflected in the curriculum." The difference isn't warmer intent; it's whether diversity is a design principle of the instruction itself.
The second pivot is student ownership. At Proficient on Standard 3 (Learning Environments), the teacher creates and maintains a safe, respectful environment supporting individual and collaborative learning. At Exemplary, "students self-initiate and sustain a positive, collaborative learning community." At Proficient on Standard 6 (Assessment), the teacher uses assessment to inform instruction. At Exemplary, "students track their own progress toward SLG goals using data they generate and interpret." Across most of the ten standards, Exemplary requires students to be doing something specific — leading, sustaining, tracking, generating — that Proficient teachers direct rather than students owning.
If the teacher is running effective, inclusive, standards-aligned instruction but hasn't built the conditions where students take over that ownership, the correct rating is Proficient, not Exemplary. That's the distinction Oregon's rubric asks evaluators to protect.
Student Learning and Growth (SLG) goals — the Oregon-distinctive component
Oregon's SLG goals sit alongside the ten Model Core Teaching Standards but operate on a different rhythm than observation-based evaluation. SLG goals are Oregon's answer to the student-outcomes component that many other states handle through statewide summative assessment data alone.
Under Oregon's Framework, every teacher sets two SLG goals per school year, following ODE's eight required components for goal setting. For teachers who provide instruction in academic content areas, at least one of the two goals must reflect the standards of the content area they teach. Measures are locally-selected — Oregon does not require specific state assessments — and ODE explicitly does not support using statewide summative assessment results as the primary source of evidence for SLG goals. The rationale: local, teacher-selected measures reflect the teaching and learning actually happening in the classroom better than statewide instruments can.
Districts have discretion in determining scoring methods for SLG goals. What ODE requires is that measures be school-wide or district-wide (rather than teacher-specific) to ensure reliability and validity, and that the SLG Goal Quality Review Checklist be used as part of the goal-setting process. Districts are collaboratively responsible — through the teacher-administrator process — for how goals get scored into the summative evaluation.
Importantly for anyone building tools around Oregon evaluation: SLG goals are a separate documentation and tracking process from observation-based evaluation. They live on a school-year rhythm — goals set early in the year, progress reviewed at midpoint conferences, attainment scored at year-end. AI can help with framing goal language, but the actual work of setting valid measures, collecting the student data across the year, and scoring attainment stays with the teacher and evaluator. Any tool that claims to handle SLG goals should clarify exactly where its scope ends.
The Oregon evaluation cycle
Oregon evaluation operates on district-defined cycles that meet Oregon Framework requirements. Most Oregon districts follow a multi-year cycle for tenured teachers — typically a two-year or three-year rotation with summative evaluations in "on-cycle" years and formative/support work in intervening years. Probationary teachers receive annual summative evaluation.
Within any given year on the cycle, districts typically conduct a combination of informal walkthroughs, formal observations with pre-conferences and required post-observation conferences, and evidence collection for the SLG component across the school year. Each teacher's evaluation ends with a summative determination that integrates the observation-based work (Professional Practice and Professional Responsibilities) with the year-long SLG goal attainment.
ODE's Principal and Teacher Evaluation Data Collection captures summary data from each district's evaluation cycle — used to monitor whether Oregon's focal students are being taught at disproportionate rates by ineffective teachers, an equity accountability originally established under Oregon's ESEA plan. The 2025-2026 Principal and Teacher Data Collection Yearly Checklist governs current data submission timelines.
After the walkthrough: where the work actually piles up
The observation itself is the part most Oregon evaluators trained for. What no one warned them about was the volume of writing that follows.
A single formal Oregon observation can produce three to seven pages of documentation: rubric ratings across the ten Model Core Teaching Standards, narrative justifications for each rating, evidence quotations from observation notes, cultural responsiveness observations for Standards 2 and 3, cross-disciplinary connection notes for Standards 4 and 5, and language for the required post-observation conference. Multiply that across a caseload of teachers on-cycle for summative review, and layer on the year-end integration with SLG attainment data, and the observation write-up load becomes the biggest single time cost in the Oregon evaluator's year.
This is where the day actually goes. The observation takes thirty minutes. The write-up takes ninety.
Where AI helps with Oregon evaluation write-ups
The strongest fit between current AI and Oregon evaluation work is the translation problem. An evaluator captures observation notes in shorthand — half-sentences, abbreviations, fragments — and then has to translate those notes into the formal language of the Oregon Model Core Teaching Standards.
AI handles three pieces of that translation reliably. First, it can take fragmentary observation notes and produce coherent, evidence-anchored prose in the voice of the Oregon rubric. Second, it can map specific pieces of evidence to the relevant standards across all four domains — telling the evaluator that the note about the teacher's culturally-connected examples supports Standard 2 (Learning Differences), while the note about the students' collaborative problem-solving supports Standard 5 (Application of Content). Third, it can maintain internal consistency across the ten standards in the same evaluation, so the observation write-up reads as a coherent document rather than ten disconnected paragraphs.
The Oregon-specific piece AI can help with is the cultural responsiveness translation. Oregon's Standard 2 language explicitly emphasizes that student cultural backgrounds should be leveraged as instructional assets — the difference between Proficient ("respected and incorporated") and Exemplary ("deliberately leveraged as an instructional asset"). Evaluators who saw genuinely responsive teaching often struggle to translate that observation into language that names what they saw with precision. AI can help move from "students seemed engaged with the material" to "the teacher's use of Spanish-language literary references drew participation from students who had been quieter in earlier lessons — evidence of Standard 2 language and cultural background being used as bridge to content."
Where AI doesn't help — and what stays with the evaluator
The honest scope is narrower than the marketing on most AI tools suggests.
AI cannot make the borderline Proficient-to-Exemplary judgment for an evaluator. That call requires watching the lesson in real time, knowing whether cultural responsiveness is showing up as active instructional design or as respectful posture, and judging whether students are actually taking ownership or the teacher is running an excellent teacher-directed lesson. AI can suggest a rating based on the notes provided, but the evaluator owns the final call.
AI cannot navigate Oregon's SLG goal-setting and scoring process. The SLG component of an Oregon evaluation requires selecting valid measures, collecting student data across the school year, applying the SLG Goal Quality Review Checklist, and scoring attainment through the district's chosen methodology. That work is teacher-driven, evaluator-supported, and district-scored. AI can help draft framing language but cannot do the year-long tracking or the local scoring decisions.
AI cannot replace the relational work of the post-observation conference. The coaching conversation with a probationary teacher after their first formal observation, the harder conversations with a tenured teacher whose evidence is trending toward Developing on Standards 6 or 7, the mid-year SLG progress review — these are human work.
And AI cannot do the contextual reasoning a long-tenured Oregon evaluator brings — knowing that this teacher moved buildings midyear when the district reconfigured, that this lesson followed a fire drill, that this classroom has three newly-arrived students still working in their first year of English. Local context shapes evaluator judgment in ways no chatbot will reconstruct from observation notes alone.
What AI does well, it does well. What it doesn't do, it shouldn't pretend to do. Pasting observation notes into ChatGPT works fine as a glorified search engine — but for standards-aligned Oregon documentation that will integrate cleanly with your district's evaluation and support system, the gap between "sounds polished" and "actually defensible" is wider than the polish suggests.
Observable evidence: what each Oregon domain looks like in practice
Each Oregon domain has its own surface features — the things an evaluator actually sees, hears, and notes during an observation.
Domain A (The Learner and Learning) is where cultural responsiveness lives most visibly. Look for whether the teacher knows individual students' backgrounds, home languages, and community contexts (not just IEP accommodations and EL codes). Look for materials that reflect student diversity beyond the token poster on the wall. Look for how transitions and routines run — students self-initiating (Exemplary) versus teacher-directing (Proficient). For Standard 3 at Exemplary, students are sustaining the community, not just participating in it.
Domain B (Content) is most visible in the depth and precision of the teacher's language. Look for accurate academic vocabulary consistently used, explicit connection to authentic local or global problems (Standard 5), and cross-disciplinary connections made explicitly during instruction ("Like in your science class..."). At Exemplary on Standard 5, students are the ones generating the real-world applications and connections — not receiving them.
Domain C (Instructional Practice) is where SLG-related evidence appears in-lesson. Look for rubrics or success criteria provided to students before tasks (Standard 6), evidence that formative assessment is driving in-lesson adjustments rather than just being collected, backward design from clear learning goals in visible lesson artifacts (Standard 7), and multiple instructional strategies within the same lesson that match strategy to goal (Standard 8). At Exemplary, students are tracking their own SLG progress and interpreting their own data.
Domain D (Professional Responsibility) is largely evident outside the observation window. Look for documentation of specific PD applied to practice tied to SLG data analysis (Standard 9), evidence of PLC contribution and family engagement patterns (Standard 10), and evidence of specific advocacy for student needs. At Exemplary, the teacher is a recognized school leader — mentoring peers, facilitating PLCs, engaging families as authentic partners.
Common scoring mistakes under the Oregon MCTS
Even experienced Oregon evaluators slip into patterns worth naming.
The first is over-Exemplifying on Standard 2 (Learning Differences). Because inclusive intent is what most Oregon teachers demonstrate, evaluators sometimes credit warm inclusive posture with Exemplary when the evidence supports Proficient. Exemplary on Standard 2 requires teacher advocacy for culturally responsive practice school-wide and diversity being deliberately leveraged as an instructional asset. Warm inclusive teaching is Proficient.
The second is the Proficient default. When evidence is thin in either direction, evaluators slot Proficient because it feels safe. But Oregon's framework requires evidence of Proficient practice — "consistently meets expectations and demonstrates effective practices with impact on student learning" — not the absence of Developing. A standard with insufficient evidence is a coaching opportunity, not a default Proficient.
The third is Domain D over-scoring, particularly on Standard 10 (Leadership and Collaboration). Because Domain D lives partly outside the lesson observation window, evaluators tend to credit "professional-feeling" teachers with high ratings regardless of specific evidence. Exemplary on Standard 10 requires the teacher to be a recognized school leader — facilitating PLCs, mentoring peers, advocating publicly for equity. Not just being professionally collegial.
The fourth is confusing SLG evidence with observation evidence. Standard 6 (Assessment) is closely tied to SLG goals, and evaluators sometimes let SLG documentation stand in for observation evidence of assessment practice — or vice versa. They're linked but distinct. Observation evidence supports the Standard 6 rating on the observation-based rubric; SLG scoring is a separate district-determined process. Keep them clean.
The fifth is over-emphasizing cross-disciplinary connections. Standards 4, 5, and 7 all reference cross-disciplinary work, and evaluators sometimes double-count evidence — a single instance of a cross-curricular reference supports one standard, not three. Each standard needs its own evidence.
Oregon in context — the InTASC-aligned district-flexibility model
Oregon's approach to teacher evaluation is different from both the mandatory-statewide-rubric states (Georgia TKES, Texas T-TESS, Florida FEAPs, Tennessee TEAM, Arkansas TESS, North Carolina NCEES, Mississippi PGS) and from other district-flexibility states like Kentucky, Wyoming, Indiana, Missouri, and Massachusetts.
Unlike the mandatory-statewide-rubric states, Oregon leaves the specific evaluation and support system design to districts. Unlike some other district-flexibility states, Oregon anchors that district flexibility in a specific rubric — the Oregon Model Core Teaching Standards — that every district must use. The InTASC foundation gives Oregon evaluators a rubric that will feel familiar to evaluators moving from other InTASC-adopting states (a number of states have adopted InTASC-aligned frameworks), while Oregon-specific emphases on cultural responsiveness, SLG goals, and community context distinguish practical application from state to state.
For Oregon evaluators, this means the underlying rubric structure is stable — the ten Model Core Teaching Standards, the four-level rating scale — but the specific evaluation and support system, cycle timing, observation cadence, and SLG scoring methodology are all determined by your district's collaborative committee process.
How EvalScribe handles the Oregon Model Core Teaching Standards
EvalScribe is built around the actual Oregon Model Core Teaching Standards structure — all four domains, all ten standards, the four-level rating scale with Oregon's exact labels (Does Not Meet, Developing, Proficient, Exemplary) — rather than approximating it with generic teaching-evaluation prose. The tool handles the translation problem natively. An evaluator captures observation notes by typing, dictating, or photographing handwritten notes (Smart Scan OCR converts handwriting to text), and EvalScribe maps that evidence to the relevant Oregon standards and drafts ratings and comments in the rubric's actual voice.
Beta testers report saving 30 to 60 minutes per evaluation versus writing the documentation traditionally. Across a typical Oregon evaluator's load — say a caseload of thirty teachers with a mix of on-cycle summative reviews and formative observations — that math adds up to dozens of hours back over an evaluation cycle.
An honest scope note: EvalScribe handles the observation-based components of Oregon evaluation (Professional Practice and Professional Responsibilities). The Student Learning and Growth component — SLG goal setting, year-long tracking, district-specific scoring — remains outside the tool. That work is teacher-driven, evaluator-supported, and lives on a school-year rhythm rather than an observation rhythm. EvalScribe supports the piece where documentation time actually piles up: the standards-aligned observation write-up.
The evaluator stays in control of every rating, every comment, and every piece of mapped evidence. EvalScribe drafts; the evaluator decides. The Proficient-to-Exemplary judgment call, the SLG scoring, the harder coaching conversations, and the final summative determination remain with the practitioner who knows the teacher. More detail on the Oregon workflow is available at evalscribe.com/oregon.
Frequently asked questions about Oregon MCTS and AI
Where can I read the official Oregon Framework and Model Core Teaching Standards? The primary sources are maintained by ODE: the Oregon Model Core Teaching Standards and the Oregon Framework for Teacher and Administrator Evaluation and Support Systems. Statutory authority is ORS 342.856.
Does AI replace evaluator judgment in Oregon evaluation? No. AI drafts evidence-mapped observation write-ups and suggested ratings; the evaluator reviews, edits, and finalizes every document. The borderline judgment calls — particularly Proficient-to-Exemplary, which pivots on cultural responsiveness as active asset and student ownership — stay with the evaluator.
Does AI handle Oregon SLG goals? No. EvalScribe is focused on the observation-based portion of Oregon evaluation — the standards-aligned documentation piece. SLG goals are a separate process: teacher-driven, based on locally-selected measures, tracked against actual student data across the school year, and scored per your district's chosen methodology under ODE's SLG Goal Quality Review Checklist. That process stays with the teacher and evaluator.
Is the Oregon Model Core Teaching Standards the same as InTASC? Oregon's Model Core Teaching Standards are Oregon's adoption of the InTASC (Interstate Teacher Assessment and Support Consortium) Model Core Teaching Standards developed by the Council of Chief State School Officers. The four-domain, ten-standard structure is InTASC. Oregon layers its own emphases — culturally responsive teaching, community context, cross-disciplinary connections, SLG goals — on top.
My district's evaluation system looks different from other Oregon districts. Does AI still work? Yes. Oregon's Framework requires every district to design its own evaluation and support system through collaboration between teachers and administrators, so cadence, observation types, and SLG scoring vary by district. What stays constant across districts is the Oregon Model Core Teaching Standards themselves. EvalScribe handles the standards-aligned observation write-up regardless of your specific district system.
How can I see what EvalScribe looks like for Oregon specifically? The Oregon page at evalscribe.com/oregon walks through the ten-standard workflow, the framework handling, and a sample exported evaluation. EvalScribe is available on iOS and macOS via the App Store, with three free evaluations to start.
If you're evaluating teachers in Oregon under the Model Core Teaching Standards, see how EvalScribe handles the observation-based workflow at evalscribe.com/oregon.
References
Oregon Department of Education, Oregon Model Core Teaching Standards
Oregon Department of Education, Oregon Framework for Teacher and Administrator Evaluation and Support Systems
ODE Principal and Teacher Evaluation Data Collection Manual (2025-2026)
Council of Chief State School Officers, InTASC Model Core Teaching Standards
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 current ODE source documents.
Last reviewed: July 1, 2026.
