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
- Data model and import order
The tables behind Teacher Performance Mgmt
Teacher Performance Mgmt ships with 10 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 10
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Observation requests:
Tickets. Requests per campus with priority and due date.
Responses and follow-up:
Ticket events. Responses, notes, pauses and resolutions.
Observation reviews:
Observation reviews. Teacher, time, rubric score and development plan.
Campuses:
Customers. Schools served by the program.
Review and evidence:
Review decisions, record attachments.
Operations and people:
Operation receipts, Organizations, team members, Users.
Every table, by feature
- Observation requests3
- Responses and follow-up2
- Observation reviews3
- Campuses2
- Review and evidence4
- Operations control2
- Shared and settings1
- Tickets
Observation and support tickets opened for a campus.
Linked to Organizations, Team members, Customers - Customers
Schools and campuses served by the observation program.
Linked to Organizations - Team members
Staff members who own, prepare or review observation work.
Linked to Organizations, Users
- Ticket events
Chronological events recorded against a ticket.
Linked to Tickets - Tickets
Observation and support tickets opened for a campus.
Linked to Organizations, Team members, Customers
- Observation reviews
Teacher classroom observation reviews supporting approval.
Linked to Tickets, Organizations - Tickets
Observation and support tickets opened for a campus.
Linked to Organizations, Team members, Customers - Record attachments
Evidence files attached to a ticket or review.
Linked to Tickets, Team members
- Customers
Schools and campuses served by the observation program.
Linked to Organizations - Organizations
School districts and networks operating teacher observation programs.
- Review decisions
Independent reviewer decisions on submitted observation reviews.
Linked to Tickets, Team members - Record attachments
Evidence files attached to a ticket or review.
Linked to Tickets, Team members - Tickets
Observation and support tickets opened for a campus.
Linked to Organizations, Team members, Customers - Team members
Staff members who own, prepare or review observation work.
Linked to Organizations, Users
- Operation receipts
Durable receipts for guarded operations and their effects.
Linked to Tickets - Tickets
Observation and support tickets opened for a campus.
Linked to Organizations, Team members, Customers
Keys and references
Events, reviews, decisions, attachments and operation receipts reference their request. Requests reference their campus, owner and organization. Team members link to user accounts. Keep request record numbers and campus codes stable and import by them.
Migration order
- Load Organizations, Users and team members.
- Load Customers for each campus.
- Load open Tickets with their owners and due dates.
- Load approved observation reviews from the current year if you need history.
- Reconcile open requests with your current tracker and test permissions before go-live.
Set up Teacher Performance Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.