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
- Features
- Campuses
Campuses
Schools and campuses served by the program.
OverviewActive campuses×
Teacher Performance Mgmt · Campuses
New
Active campuses
Customers
| Code | Name | Contact name | Eligibility note | |
|---|---|---|---|---|
| CDE-308 | Customer 142 | Contact 395 | EN-321 | |
| CDE-242 | Customer 569 | Contact 543 | EN-785 | |
| CDE-787 | Customer 393 | Contact 844 | EN-943 | |
| CDE-346 | Customer 317 | Contact 235 | EN-446 | |
| CDE-188 | Customer 942 | Contact 131 | EN-381 |
6 of 6 records
CDE-308Customers · CST-15906
NameCustomer 142
Contact nameContact 395
Eligibility noteEN-321
What you can do
Know which schools you serve and who to call
Campuses are the schools and sites your observation program serves. Each has a code, a name, a contact, an address and an eligibility note that records anything the observers should know, such as visiting rules or which year groups are in scope. A campus can be made inactive without losing its history, and requests can only be opened for active campuses in the same organization.
Because every request is recorded against a campus, you can see at a glance which schools have open requests, which are past due and how quickly each school is being served. The campus contact is the person observers coordinate with to schedule visits.
How the work is organized
The observation coordinator maintains campuses; observers use the contact details.
- Active campuses only. Requests are opened only for active campuses.
- Notes for observers. Eligibility notes carry visiting rules and scope.
- History kept. Inactive campuses keep their past requests.
What to agree during setup
Agree your campus list and codes, matching your district or network records. Agree what goes in the eligibility note and who keeps contacts current. Decide how campuses that merge or close are handled. Prepare examples of a new campus joining the program, a campus with visiting restrictions and a campus closing.
Check the handoff on an actual case
A new primary campus joins the program mid-year. The coordinator adds it with its code, the deputy head as contact and a note that observations happen only on Tuesdays and Thursdays. The first request is opened for it the same week, and the observer sees the visiting rule before contacting the school.
When a campus closes at the end of the year, the coordinator makes it inactive. Its past requests and observations stay in the record, but no new requests can be opened for it.
Coordinators can also compare campuses over a term: which schools ask for the most support and which wait longest for a first response.
What your team sees
- Active campuses — Campuses with codes, contacts and notes.
- Unresolved requests — Open requests by campus.
Follow the work through
- Request to resolution: How campus requests are handled.
Check the data model before loading campuses.
What it keeps track of
Data model- Customers
- Schools and campuses served by the observation program.
- Organizations
- School districts and networks operating teacher observation programs.
Who uses it
Permissions- Observation Coordinator
- , Admin.
- The coordinator maintains campuses; admin manages organizations.
Set up Teacher Performance Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.