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
- Operations control
Operations control
Operation receipts, exceptions and reconciliation.
OverviewFailed and needs-review receipts×
Teacher Performance Mgmt · Operations control
New
Failed and needs-review receipts
Operation receipts
| Id | Operation key | Action | Parent | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| IDD-908 | OK-941 | ACT-573 | TCK-37510 | Failed | 10 Oct | |
| IDD-381 | OK-121 | ACT-713 | TCK-55211 | Needs review | 08 Oct | |
| IDD-341 | OK-546 | ACT-957 | TCK-90290 | Failed | 18 Oct | |
| IDD-947 | OK-598 | ACT-352 | TCK-53580 | Needs review | 07 Oct | |
| IDD-855 | OK-119 | ACT-629 | TCK-20787 | Failed | 17 Oct |
6 of 6 records
IDD-908Operation receipts · OR-73906
FailedOperation keyOK-941
ActionACT-573
ParentTCK-37510
Occurred at10 Oct
Failure reasonCut to length
What you can do
Be sure every action really took effect
Every guarded action, whether opening and routing a request, responding, pausing, resolving, approving a review or correcting scope, writes an operation receipt. The receipt holds a stable key, the action, the revision expected, the time and a result: pending, completed, failed or needs review. It lists the effects the action should have produced and, when something went wrong, the reason.
Receipts make repeats safe: an action sent twice takes effect once. Reconciliation reads the request’s saved events, reviews and decisions before marking a receipt completed. Anything it cannot confirm stays marked for review, so program reports are built on what actually happened.
How the work is organized
The operations analyst works the exception queue.
- One key, one effect. Each operation key takes effect once.
- Checked against the request. Completion is confirmed from saved records.
- Exceptions in one list. Failed and needs-review receipts appear together.
What to agree during setup
Agree who works the exception queue, how often reconciliation runs and when an exception is escalated to the coordinator. Prepare examples of a completed approval, a timed-out resolution that did complete, one that did not, and a correction refused because the request had moved on.
Check the handoff on an actual case
A coach resolves a request from a school with poor Wi-Fi and the save times out. The receipt is left pending. Reconciliation finds the resolution event and resolution time saved, and completes the receipt. Another pending receipt for a review approval finds no decision saved, so it stays in the queue and the reviewer re-records the decision under the same key.
At term end the coordinator checks that the queue is empty before reporting observation numbers to the district, so the report counts only what was actually recorded.
Over a term the queue also shows where problems repeat, such as one campus with unreliable connections, so the coordinator can plan around it.
Nothing in the queue is retried automatically against outside systems.
What your team sees
- Failed and needs-review receipts — Receipts waiting for attention with their reason.
Follow the work through
- Operation reconciliation: From pending receipts to verified results.
What it keeps track of
Data model- Operation receipts
- Durable receipts for guarded operations and their effects.
- Tickets
- Observation and support tickets opened for a campus.
Who uses it
Permissions- Operations Analyst
- , Observation Coordinator.
- The analyst reconciles; the coordinator follows exceptions.
Set up Teacher Performance Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.