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
- Observation requests
Observation requests
Requests from campuses routed to an observer with due dates.
OverviewPast due requests×
Teacher Performance Mgmt · Observation requests
New
Past due requests
Tickets
| Record number | Subject | Counterparty | Priority rank | Resolution due at | Owner | |
|---|---|---|---|---|---|---|
| TCK-63391 | New tck-796 | CST-5461 | 910 | 04 Oct | ||
| TCK-30258 | Triaged tck-221 | CST-3250 | 940 | 09 Oct | ||
| TCK-93650 | Assigned tck-623 | CST-3898 | 910 | 05 Oct | ||
| TCK-29083 | Waiting tck-418 | CST-9775 | 90 | 10 Oct | ||
| TCK-64247 | Resolved tck-670 | CST-2351 | 90 | 08 Oct |
6 of 6 records
New tck-796Tickets · TCK-63391
NewCounterpartyCST-5461
Priority rank910
Resolution due at04 Oct
What you can do
Every observation starts with a request someone owns
An observation request records which campus asked for support, what it is about, how urgent it is and when it should be resolved. It has an owner, the coordinator responsible for it, and a status: new, triaged, assigned, waiting, resolved, closed or reopened. The resolution due date and priority are set when the request is opened, so it is clear from the start which requests need attention first.
When a request is opened, the system checks that the campus is active and belongs to the same organization, and that the owner is an active team member there. The coordinator then triages the request and routes it to an observer. Every change raises the request’s revision, so decisions are always taken on the current version.
How the work is organized
The observation coordinator opens and routes requests; observers take them from there.
- Owned from the start. Each request has one owner who answers for it.
- Priority and due date up front. Past-due requests are visible by priority.
- Routed, not emailed. Assignment to an observer is recorded on the request.
What to agree during setup
Agree how schools ask for observations (through the coordinator, a form or a scheduled cycle) and how priority and due dates are set. Agree who triages and how observers are matched to campuses. Prepare examples of a routine termly observation, an urgent request from a principal, a request for a campus that is no longer active and a request reassigned to another observer.
Check the handoff on an actual case
A principal asks for a follow-up observation of a new science teacher before the end of the month. The coordinator opens a request for the campus with high priority and a due date three weeks out, triages it and routes it to the science coach. The request now shows on the coach’s list and on the past-due list if it slips, so nothing depends on a forwarded email.
What your team sees
- Unresolved requests — Open, assigned and waiting requests by campus and priority.
- Past due requests — Requests beyond their resolution due date.
- My requests — Each person’s own requests.
Follow the work through
- Request to resolution: The full path of a request.
Review the implementation plan before loading campuses.
What it keeps track of
Data model- Tickets
- Observation and support tickets opened for a campus.
- Customers
- Schools and campuses served by the observation program.
- Team members
- Staff members who own, prepare or review observation work.
Who uses it
Permissions- Observation Coordinator
- , Observer.
- The coordinator opens and routes; observers work the requests.
Set up Teacher Performance Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.