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.
- Election Management
- Features
- Delivery Operations
Delivery Operations
After a case decision, the team traces delivery through an operation key, an execution attempt and an operation run.
OverviewRuns needing reconciliation×
Election Management · Delivery Operations
New
Runs needing reconciliation
Operation runs
| Source | Operation key | Source revision | Status | Failure reason | Result reference | |
|---|---|---|---|---|---|---|
| CSS-70270 | OK-942 | 850 | Reconciliation required | Cut to length | RR-149 | |
| CSS-35619 | OK-207 | 860 | Reconciliation required | Weld frame | RR-898 | |
| CSS-88767 | OK-347 | 120 | Reconciliation required | Drill and tap | RR-612 | |
| CSS-92105 | OK-668 | 380 | Reconciliation required | Deburr | RR-226 | |
| CSS-86045 | OK-335 | 310 | Reconciliation required | Assemble | RR-897 |
6 of 6 records
OK-942Operation runs · OR-72045
Reconciliation requiredSourceCSS-70270
Source revision850
Failure reasonCut to length
Result referenceRR-149
What you can do
Keep the working record clear
After a case decision, the team traces delivery through an operation key, an execution attempt and an operation run. Ordered steps capture the inputs, outputs and any external receipt. The case carries a delivery reference and completion date when the outcome is delivered. A failed attempt records a reason, while a run requiring reconciliation calls for inspection before anyone repeats an action that might already have reached an external system.
An approved case may require an external delivery action. Execution attempts records each attempt and its provider reference. Operation runs holds the operation key, source revision, input hash, status and result reference; its ordered operation steps can retain input, output and receipt evidence. Cases and Details shows the selected case beside its operation run and step trace. A team member can inspect a failed or uncertain action without assuming that a missing success message means nothing happened.
How the work is organized
- Record. An approved case may require an external delivery action.
- Review. Agree which approved outcomes need delivery and which connected provider returns a reference or receipt.
- Handoff. At handoff, the Case Officer should identify the approved revision, operation key, attempt number, run status and result reference.
What to agree during setup
Agree which approved outcomes need delivery and which connected provider returns a reference or receipt. Use one operation key for the intended action and keep the source revision with the run. Before an officer records the case as delivered, check the result reference and any receipt from the provider. If an attempt is uncertain, decide who will inspect the external result and record the finding before another attempt.
Choose a failed and an uncertain example during rehearsal. Verify that the officer can distinguish the attempt status from the run status and locate the relevant step receipt. The Authorized Reviewer decides the case outcome; the Case Officer follows the delivery record. Keep those responsibilities separate.
Check the handoff on an actual case
Use an approved case with a delivery action. Follow its operation key from the case to the attempt, run and ordered steps. Check the result reference and any receipt before recording completion. Then rehearse an uncertain outcome: leave the run needing reconciliation, inspect the external receipt and decide whether the action already succeeded. The team should be able to explain the final case status from the retained run and step records.
At handoff, the Case Officer should identify the approved revision, operation key, attempt number, run status and result reference. When a step has an external receipt, preserve it with the step. A run needing reconciliation stays open for investigation; its status is not a reason to repeat the action automatically.
What your team sees
- Runs needing reconciliation — Inspect uncertain operation results and receipt evidence.
- Failed execution attempts — Find attempt reasons and provider references.
Follow the work through
Follow case review from preparation to independent decision. Use delivery and correction when an approved outcome needs execution or an earlier revision needs correction.
What it keeps track of
Data model- Execution attempts
- Each recorded attempt to execute an approved action for a service application.
- Operation runs
- Workflow-maintained execution runs with operation key, input hash and persisted result reference.
- Operation steps
- Ordered steps inside an operation run with input, output and external receipt state.
- Cases
- Election case records for Election Management. The parent record for requirements, documents, actions and decisions.
Who uses it
Permissions- Case Officer
- , Authorized Reviewer, Read Only Analyst
Set up Election Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.