T-TESS Observation Tracking for Principals

The T-TESS Framework: A Quick Overview

The Texas Teacher Evaluation and Support System (T-TESS) is the state's official teacher appraisal framework. It replaced PDAS in 2016 and is organized around four domains, each containing multiple dimensions that principals must evaluate through classroom observations and artifact review.

Each dimension within these domains is scored on a 1–5 scale: Improvement Needed, Developing, Proficient, Accomplished, and Distinguished. Principals must provide evidence-based justification for each score — which is where the documentation burden becomes real.

The Documentation Problem Principals Face

Here is the math that no one talks about in principal preparation programs:

A campus with 35 teachers requires at minimum 35 formal observations per year. Each formal observation involves:

• Pre-conference (15–20 minutes) — reviewing the teacher's lesson plan, discussing goals, and setting the observation focus
• Classroom observation (45 minutes minimum) — scripting evidence aligned to T-TESS dimensions
• Evidence organization (30–60 minutes) — sorting raw observation notes into the appropriate domains and dimensions, selecting evidence that justifies each score
• Post-conference (20–30 minutes) — sharing feedback, discussing growth areas, and agreeing on next steps
• Documentation entry (15–30 minutes) — entering scores and evidence into the district's appraisal system

That is roughly 2.5 to 3 hours per teacher for formal observations alone. Multiply by 35 teachers and you are looking at 85–105 hours — more than two full work weeks — just for the formal observation cycle.

Now add informal walkthroughs. Most effective principals conduct 3–5 walkthroughs per teacher per year. Each walkthrough is 10–15 minutes of observation time, but the write-up and feedback loop adds another 15–20 minutes. That is another 50+ hours.

TIA and the Rising Stakes of Observation Quality

The Teacher Incentive Allotment (TIA) has raised the stakes for observation accuracy. Under TIA, teacher designations (Recognized, Exemplary, Master) are determined partly by observation scores. This means:

• Inter-rater reliability matters. If your campus scores consistently higher or lower than comparable campuses, TEA will flag it. Principals need calibration, and calibration requires documented evidence to review.
• Evidence trails are auditable. TIA-approved systems must demonstrate that observation scores are based on documented classroom evidence, not general impressions.
• Financial consequences are real. TIA designations translate to real salary supplements — $3,000 to $32,000+ per teacher depending on the designation and campus. Inaccurate scoring affects both teacher compensation and district funding.

What Good Observation Tracking Looks Like

An effective T-TESS tracking tool should compress the documentation timeline without sacrificing quality. Here is what to look for:

• Voice-to-text scripting: Record observation notes by speaking instead of typing. The system transcribes and timestamps your evidence in real time, so you can focus on watching the lesson instead of staring at a laptop.
• Automatic domain alignment: When you capture a piece of evidence ("teacher used exit tickets to check understanding"), the system should suggest which T-TESS dimension it maps to. This eliminates the post-observation sorting step that eats 30–60 minutes.
• Walkthrough templates: Quick-entry forms for informal walkthroughs that capture the essentials (teacher, date, focus area, 2–3 evidence points, a coaching note) in under 2 minutes.
• Teacher dashboard: Each teacher should have a profile showing all observations, walkthrough trends, growth areas, and coaching history in one view. This makes pre-conferences and end-of-year summative conversations data-driven instead of memory-driven.
• TIA-ready scoring: Built-in 1–5 rubric aligned to T-TESS dimensions, with the ability to export scores in a format compatible with district TIA submissions.
• Coaching feedback loop: A way to share feedback with teachers digitally after each observation, with space for teacher reflection and goal-setting.

Streamlining Your Workflow: Practical Tips

Even without a specialized tool, principals can reduce observation documentation time with a few workflow changes:

1. Script during the observation, not after. Take evidence notes in real time using shorthand or voice recording. Reconstructing an observation from memory doubles the time and halves the accuracy.
2. Use a walkthrough rotation schedule. Instead of cramming all walkthroughs into observation season, spread them across the year. Two walkthroughs per week (20 minutes each) keeps you in classrooms consistently without creating a documentation backlog.
3. Batch your post-conferences. Schedule post-conferences in 25-minute blocks on specific days rather than scattering them. This reduces context-switching and keeps the momentum going.
4. Keep a running coaching log. Instead of writing detailed narratives for every walkthrough, maintain a brief running log per teacher: date, what you saw, one compliment, one growth area. This becomes your evidence base for the summative conference.