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.
- Coaching Institute Mgmt
- Features
- Delivery
Delivery
Trace a decided enrollment to its recorded delivery result and exceptions.
OverviewDelivered Enrollments×
Coaching Institute Mgmt · Delivery
New
Delivered Enrollments
Enrollments
| Number | Name | Course | Owner | Completed at | Delivery reference | |
|---|---|---|---|---|---|---|
| ENR-91911 | Enrollment 883 | CRS-6907 | DR-766 | |||
| ENR-20953 | Enrollment 409 | CRS-9637 | DR-490 | |||
| ENR-81636 | Enrollment 131 | CRS-2049 | DR-867 | |||
| ENR-89680 | Enrollment 405 | CRS-6026 | DR-941 | |||
| ENR-60336 | Enrollment 201 | CRS-1979 | DR-453 |
6 of 6 records
Enrollment 883Enrollments · ENR-91911
CourseCRS-6907
Delivery referenceDR-766
What you can do
Delivery in the working cycle
After an approved decision, the team records the delivered outcome on the enrollment. The delivery reference and completion date identify the result. Operation runs and their steps retain the operation key, source revision, status and result reference, while execution attempts show each try and its provider reference.
For an approved course enrollment, the Instructor checks the decided revision before recording its delivered result. If the action fails, the run and attempt keep the failure reason visible. The team investigates a reconciliation-required result before treating it as complete or issuing the same action again.
How the work is organized
- Check the decision. Instructor compares the enrollment revision with the independent approval before delivery.
- Keep the result. The enrollment delivery reference and completion date identify the recorded outcome.
- Investigate exceptions. Runs, steps and attempts retain statuses, references and failure reasons for the action.
What to agree during setup
Agree what external acknowledgement establishes delivery, who investigates failed or uncertain attempts, and how the provider reference is retained. A local delivered label should correspond to the result recorded for the accepted revision.
Agree what result reference establishes delivery and who investigates a failed or uncertain attempt. The decision revision, operation key and result reference should describe the same action. A repeated action needs its earlier attempt visible so the team can reconcile the outcome.
Check the handoff on an actual case
Compare a delivered enrollment with its operation run, steps and attempts. Confirm that the source revision and result reference identify the same action. Rehearse a failed attempt so the team can find the exception without losing the earlier decision.
Use a decided enrollment with a recorded operation run. Compare the run source revision with the reviewer decision and enrollment delivery reference. If an attempt failed or its result is unknown, inspect the step and attempt before treating the case as delivered.
The delivery reference on the enrollment identifies the reported outcome. The operation run records the source revision and result reference, while steps and attempts show how the action proceeded. Those records let the Read Only Analyst inspect an exception without changing it. If an attempt is marked Failed or Unknown, the team should check the provider reference and failure reason before repeating the action. A run requiring reconciliation needs an investigated result tied to the same operation key. The Instructor should compare that result with the reviewed revision before the enrollment is treated as delivered.
What your team sees
- Delivered Enrollments — Inspect the completed case and its delivery reference.
- Delivery Exceptions — Find failed runs or runs requiring reconciliation.
Follow the work through
Read the enrollment review path and delivery path when preparing a rehearsal.
What it keeps track of
Data model- Enrollments
- Enrollment records linking a person to a course offering: intake, requirement lines, evidence, review decisions and delivered outcome.
- 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.
- Execution attempts
- Each recorded attempt to execute an approved action for a service application.
- State history
- Immutable workflow-written status transition history for each case.
Who uses it
Permissions- Instructor
- , Academic Reviewer, Read Only Analyst
Set up Coaching Institute Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.