Content workspace

The Learning Content Workspace is the main work screen for an item. Its status board lets the team find content by lifecycle state. Selecting an item opens its content context, state history, pending review decision, operation run, step trace and child interaction strip. The operator can see the revision being prepared without losing the course definition or owner who is accountable for it.

Each learning content record carries a number, name, interaction date, organization, owner, course definition and status. The revision distinguishes a corrected item from the version already reviewed. When an item is returned, the operator should preserve the earlier decision and prepare a successor revision with its own evidence. The status history gives the team a dated trail of transitions.

• Assign the owner. Put preparation with the person who can respond to a returned review.
• Keep revisions distinct. Compare the source revision on the decision with the revision on the item before moving it onward.
• Read the history. Use the recorded actor and reason to explain a change in status.

Agree what a complete draft contains, who can submit it, and which evidence must accompany a revision. Define how the organization and course definition are selected. Prepare an example that is submitted, returned and corrected so the team can test whether the review still points to the intended revision. Decide what a completed date means for delivered content and which delivery reference the team will keep.

An operator creates a lesson for a course and assigns it to a named content owner. The item starts as a draft. The operator adds interaction lines and a supporting document, then submits the current revision. A reviewer opens the same item, inspects the interaction outcomes and records a decision against the revision under review.

If the reviewer returns the lesson, the reason belongs with that decision. The operator creates a correction action, updates the lesson and prepares the next revision. The original decision must remain legible beside the earlier revision. The reviewer should not have to guess whether a prior approval covered the changed material.

Run this case through the workspace. Have the operator open the item from their queue, then use the status board to confirm where it appears after submission. Have the reviewer point to the pending decision and source revision. After the correction, ask both people to find the earlier history and identify which version is now being considered. The same item number should carry the work without erasing its prior trail.

• Content work queue — Items being drafted, submitted or verified, with owner and revision visible.
• My content — Items assigned to the current operator.
• Content status board — The lifecycle arranged by the content status.

Prepare content, then review a revision. Review the roles before assigning people to the first cycle.