Built LMS Help Center
Data & Analytics

Review Course Intelligence

Use course improvement suggestions and course effectiveness scores to evaluate course quality.

Use course intelligence pages when you need to improve a specific course or compare whether course participation is associated with better outcomes.

Before you begin

You need analytics access and course activity data.

Before reviewing course intelligence, confirm:

  • The course is published or has meaningful learner activity.
  • The course owner can review suggested changes.
  • You know whether you need improvement suggestions or effectiveness scores.
  • Intelligence pipeline data is current.

Use Course Improvement Advisor

Open Intelligence > Courses > Improvements.

  1. Choose a published internal course.
  2. Choose a status filter: All, Pending, Accepted, Applied, or Rejected.
  3. Select Analyze Course.
  4. Wait for analysis to complete.
  5. Review the overall assessment.
  6. Expand suggestions.
  7. Accept, reject, or mark applied.

Suggestions can include:

  • Priority.
  • Category.
  • Action type.
  • Description.
  • Data-driven rationale.
  • Estimated impact.
  • Affected modules.
  • Suggested block types.

If no course is selected, choose a course first. If no analyses exist for that course, run Analyze Course.

Use Course Effectiveness

Open Intelligence > Courses > Effectiveness to review course effectiveness scores and outcome comparisons.

Use this page when comparing whether course participation is associated with better outcomes. Export from the page when you need to share the data outside Built LMS.

If the page shows stale data, check the Intelligence dashboard and Pipeline Runs.

Verify success

Course intelligence review is useful when:

  • The selected course has enough learner activity to analyze.
  • Improvement suggestions are accepted, rejected, or marked applied.
  • Suggested changes are reviewed by the course owner before implementation.
  • Course effectiveness data is exported only after filters and date ranges are confirmed.
  • Stale data is checked against Pipeline Runs before decisions are made.

Troubleshooting

On this page