Built LMS Help Center
Data & Analytics

Review Generated Course Drafts

Review pending course outlines and content briefs before AI-generated modules are rendered.

Use generated draft review when Built LMS has created an outline or content brief that needs admin approval before course generation continues.

Before you begin

You need access to the organization and course that generated the draft.

Before reviewing, collect:

  • The intended learner audience.
  • The source materials used for generation.
  • The learning objectives the course must satisfy.
  • The course owner or subject-matter expert who can approve the draft.
  • Any deadline or publishing constraint.

Do not approve a draft just because it is complete. The review step exists to catch weak structure, unsupported source use, missing coverage, and confusing lesson flow before rendering begins.

Review pending course outlines

Open pending outlines

Open Pending Course Outlines when Built LMS has generated outlines that have not finished content generation yet.

The page loads the latest outline per course for your organization, then hides courses whose generation is already marked complete. If there is one pending course, Built LMS opens it directly. If there are several, you see a list.

The list shows:

FieldWhat it means
Course titleThe course attached to the generated outline.
DescriptionThe course description or outline description.
MicrolearningAppears when the delivery format is microlearning.
Pending ApprovalThe outline still needs admin review.
GeneratedDate the outline version was created.
Modules or ScreensStandard courses show modules; microlearning courses show screens.
VersionThe outline version being reviewed.

If the page says No Pending Outlines, there are no unfinished generated outlines for your organization. Use Generate New Course to start a new generation workflow.

Check the outline quality

The outline review page shows the generated course title, description, course learning objectives, lessons, modules, block summaries, Bloom levels, source references where available, and generated statistics.

Review these items before approving:

  • Course learning objectives describe outcomes, not broad topics.
  • Lesson titles form a sequence a learner can follow.
  • Modules are not duplicated or out of order.
  • Module descriptions are specific enough for content generation.
  • Block summaries tell the generator what each block should teach.
  • Source references match the intended source material.
  • Microlearning outlines have focused screens rather than full course-style modules.
  • Estimated length and depth match the intended learner experience.

For source-backed generation, pay close attention to source references. If the outline points at the wrong section or invents unsupported claims, stop and request changes instead of approving.

Approve, save, or request changes

The pending outline review surface has three main decisions:

ActionWhat happens
Approve OutlineBuilt LMS records the outline approval checkpoint and redirects back to the generation workflow so module generation can continue.
Request ChangesYou enter feedback. Built LMS currently saves that feedback on a new outline version for review history; treat this as a note for regeneration, not a fully automated regenerate loop.
CancelReturns to the pending outline list or previous page without approving.

Use Approve Outline only when the course structure is ready for content generation. Approving a weak outline creates more review work later because the module renderer follows the approved structure.

Review content briefs

Open the content brief

Open Content Brief when the generation workflow asks you to review what each lesson and module will teach before rendering.

The content brief page requires a courseId. If you open it without a course, Built LMS shows No course specified. Open this page with a courseId.

If the selected course has no saved brief, the page shows No Content Brief and tells you to plan the brief from the generation workflow.

Check what the brief controls

The content brief is stricter than the outline. It defines:

  • Which lesson each module belongs to.
  • The lesson arc role for each module.
  • Claims each module must teach.
  • Source material IDs and section labels for each claim.
  • Terms introduced and terms assumed.
  • Bridge copy from the previous module where present.
  • Quality-gate flags that survived generation.

The renderer is expected to teach the listed claims and avoid introducing claims that are not in the brief. That means the content brief is the best place to catch unsupported facts, weak source usage, missing coverage, or an awkward lesson arc before rendering begins.

Edit the content brief

For each lesson, expand the lesson section and review its modules.

You can edit:

  • Lesson arc: choose a registered arc that matches the Bloom level and intended learning flow.
  • Module role: set the role, such as context, content, guidance, practice, assessment, or transfer.
  • Claims to teach: edit, add, or remove the specific claims the module must cover.
  • Source: edit the source material ID for a claim.
  • Section: edit the source section label for a claim.
  • Bridge from previous: adjust transition guidance when a module depends on the previous one.

The brief may show warning badges when:

  • A lesson has unresolved quality-gate flags.
  • A module has no claims.
  • A claim points at a source outside the known allocation.

Do not ignore these warnings. A module with no claims will teach nothing specific, and an off-source claim can lead to unsupported generated content.

Save or approve the brief

The content brief review surface has these actions:

ActionWhat happens
Save DraftSaves your edits and keeps you on the brief for more review.
Approve & RenderSaves the approved brief and returns to the AI generation workflow to render the course.
CancelReturns to Courses without approving the brief.

Use Save Draft when you need another reviewer to inspect source alignment or lesson flow. Use Approve & Render only after the claims, sources, and lesson arcs are ready.

Verify success

The generated draft is ready when:

  • The outline sequence supports the intended learner outcome.
  • Source references match the source material.
  • Microlearning drafts stay focused and do not become full course outlines.
  • Content brief claims are specific, sourced, and assigned to the right module.
  • Quality-gate warnings have been resolved or deliberately accepted by the reviewer.
  • The next generation step starts only after the reviewer approves the draft.

Troubleshooting

On this page