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.
- EdTech Content Platform
- Features
- Follow-up control
Follow-up control
Assign corrections and keep the earlier revision and decision visible.
OverviewMy follow-ups×
EdTech Content Platform · Follow-up control
New
My follow-ups
Follow up actions
| Source | Title | Status | Due date | Assigned to | |
|---|---|---|---|---|---|
| LC-75819 | Open fua-781 | Open | 12 Oct | ||
| LC-95983 | In progress fua-404 | In progress | 20 Oct | ||
| LC-99873 | Completed fua-550 | Completed | 04 Oct | ||
| LC-51589 | Cancelled fua-666 | Open | 10 Oct | ||
| LC-51840 | Open fua-868 | In progress | 04 Oct |
6 of 6 records
Open fua-781Follow up actions · FUA-50415
OpenSourceLC-75819
Due date12 Oct
What you can do
Give corrections an owner and due date
A returned review or delivery exception creates work for someone. Follow-up actions keep the title, assignee, due date, status and resolution beside the learning content item. The operator can see what remains open while the reviewer retains the earlier decision. State history records content status changes with a source revision, actor and reason, so the next person can understand why the item changed.
How the work is organized
An operator links a follow-up to the content source and assigns it to a person. The action moves from open into progress, then to completed or cancelled with a resolution. If a delivered revision must be superseded, the successor revision needs its own review and an explicit action for any corrective delivery work. The earlier operation steps and evidence remain useful when explaining the change.
- Assign one owner. Put the action with the person who can resolve the issue.
- Keep the reason. Record the return or delivery problem in the action title and resolution.
- Preserve the trail. Compare the earlier decision and state history before submitting the successor revision.
What to agree during setup
Decide who may open a correction, how due dates are set, and when a cancelled action needs a resolution. Agree how the team handles a content revision already delivered to an external system. Identify who checks whether a compensating action is required there. Prepare a returned-review example and a delivered-item correction example, each with a named assignee.
Check the handoff on an actual case
A reviewer returns a lesson because the quiz interaction outcome conflicts with the attached evidence. The operator creates a follow-up action for the content item, assigns it and sets a due date. The assignee checks the interaction source, fixes the content and records a resolution. The earlier review decision and its source revision remain available when the corrected item is submitted.
A second lesson has already been delivered when the content owner discovers a bad reference. The operator records the correction as a successor revision and assigns a follow-up for the external publication. The team checks the delivery reference and operation trace to determine what the external system received. A reviewer considers the new revision separately; the previous decision still explains why the earlier material was released.
Rehearse both cases with the operator, reviewer and administrator. Have the assignee find their action, state what is due, then show the resolution. Have the reviewer compare the old and new revision before making a new decision. Have the administrator identify the external receipt if delivery was affected. The case is ready when no one needs to overwrite a prior decision to describe the correction.
What your team sees
- Open follow-ups — Corrections and requests still open or in progress.
- My follow-ups — Actions assigned to the current person.
- Returned decisions — The review reasons that prompted correction.
Follow the work through
Manage correction and delivery. Review the implementation sequence before rehearsing a superseded item.
What it keeps track of
Data model- Follow up actions
- Assigned outstanding actions, corrections and outstanding requests for a case.
- Learning content
- Learning content items, video and interactive course records created and published from the course catalog.
- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- State history
- Immutable workflow-written status transition history for each case.
- Operation runs
- Workflow-maintained execution runs with operation key, input hash and persisted result reference.
Who uses it
Permissions- Ed tech Content Platform Operator
- Assigns and resolves follow-ups.
- Ed tech Content Platform Reviewer
- Reviews the successor revision.
- Ed tech Content Platform Administrator
- Checks external delivery context.
Set up EdTech Content Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.