These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Teacher Performance Mgmt
- Implementation and migration
How a Teacher Performance Mgmt rollout works
Start with one region's campuses and one term's observation cycle.
Agree the operating boundary
The system holds observation requests, events, observation reviews, decisions and evidence. Lesson planning, student data and HR performance systems stay connected. The school decides observation policy and what a development plan requires.
Map the source data
Agree campus codes, rubric and request priorities. Load campuses and open requests.
Configure a bounded pilot
Run one term's observations for one region: requests, responses, reviews and approval.
Rehearse the exceptions
The first response time is set once, an observer cannot approve their own review, a request closes only from resolved, and paused time is excluded from response measures.
Reconcile and release
Compare requests and observations with your current records, get sign-off from the coordinator and agree the rollback window.
What the customer provides
- Campus list with codes, contacts and visiting rules.
- Rubric and development plan expectations.
- Open requests and the coaching team.
- The reviewers and their roles.
Changing it afterwards
Use Proto to prepare changes on a branch. Review changed fields, permissions and reports with the coordinator and replay the pilot’s exception cases before release. Approved reviews keep the rubric that applied at the time.
Set up Teacher Performance Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.