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.
- Learning Management System
- Features
- Follow-up and correction
Follow-up and correction
Assign corrections and preserve the case's earlier decisions.
OverviewEnrollment History×
Learning Management System · Follow-up and correction
New
Enrollment History
State history
| Source | From status | To status | Occurred at | Actor | Reason | |
|---|---|---|---|---|---|---|
| ENR-81152 | FS-807 | TS-601 | 12 Oct | History 1 | ||
| ENR-81932 | FS-108 | TS-224 | 03 Oct | History 2 | ||
| ENR-80244 | FS-257 | TS-901 | 10 Oct | History 3 | ||
| ENR-78800 | FS-531 | TS-748 | 09 Oct | History 4 | ||
| ENR-60964 | FS-159 | TS-522 | 06 Oct | History 5 |
6 of 6 records
FS-807State history · SH-64212
SourceENR-81152
To statusTS-601
Occurred at12 Oct
ReasonHistory 1
What you can do
Give returned work an owner
A follow-up action links an enrollment to a title, assignee, due date, status, completion date, and resolution. It gives the Learning Management Operator a concrete piece of work to resolve after a review return or a delivery correction. The state history keeps the earlier status transitions, actor, reason, source revision, and operation key available for later inspection.
How the work is organized
An action can be Open, in progress, Completed, or Cancelled. Use those values to distinguish a correction in progress from one whose resolution has been recorded. When a delivered revision needs correction, preserve the original decision and execution evidence. The team should be able to identify a successor revision and the compensating action without rewriting the earlier record.
- Assign the work. Name the employee responsible for a correction and give it a due date.
- Keep the reason. Record what the reviewer returned and how the operator resolved it.
- Preserve the trail. Use state history to explain a status change without replacing the prior decision.
What to agree during setup
Decide which returned decisions require an action, who assigns it, and how completion is checked. Agree what to do when a document changes after an approval. For a delivered case, decide who authorizes a successor revision and what compensating work is needed with the receiving system or team. Prepare examples of a simple missing document and a materially changed delivered case.
Check the handoff on an actual case
A reviewer returns an enrollment because a source document is illegible. The operator creates an action for the employee who can obtain a replacement and records a due date. After the replacement is attached and verified, the action resolution explains what changed. The reviewer sees both the new evidence and the earlier return when considering the revised case.
In a second case, delivery has already been recorded when the underlying requirement is corrected. The operator should not edit the earlier operation result into a different outcome. Keep the original run and receipt, record the correction work, and route the successor revision for independent review. Rehearse how the organization would reconcile any external delivery that the earlier run produced.
What your team sees
- Open Follow-up Actions — Outstanding work with its assignee, due date, and current state.
- Enrollment History — Prior status changes, actors, revisions, and reasons for a selected case.
Follow the work through
What it keeps track of
Data model- Follow up actions
- Assigned outstanding actions, corrections and outstanding requests for a case.
- State history
- Immutable workflow-written status transition history for each case.
- Enrollments
- Learner enrollments submitted for completion, review and certification.
- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- Operation runs
- Workflow-maintained execution runs with operation key, input hash and persisted result reference.
Who uses it
Permissions- Learning Management Operator
- , Learning Management Reviewer.
- The operator owns correction work.
- The reviewer decides on a revised case independently.
Set up Learning Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.