A four-domain rubric framework seeds automatically per district, or a district imports its own via CSV. Evaluators run walkthroughs and formal observations with per-indicator ratings, time-stamped notes, and an evidence portfolio, all visible to the school or district the way an observation always has been.
Coaching cycles hold focus areas, sessions, next steps, and PD-resource links, and they are mechanically sealed off from admin and evaluator visibility, not just a permissions convention a future change could loosen. A district-level PD-suggestion engine separately surfaces low-rated indicators across observations and matches them to PD library resources, and district reporting shows a heatmap by school and domain and a goal-completion rate, counts and averages only, never the content of an individual observation or coaching cycle.
A rubric-based observation an evaluator and their admin can both see, next to a coaching cycle only the coach and the teacher can ever open, mechanically walled off, not just a convention.
Bring your hardest scenario, a multilingual community, a PBIS rollout, a vendor consolidation, and we'll walk through the actual product.