> For the complete documentation index, see [llms.txt](https://sunbird.gitbook.io/sunbird-spark/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sunbird.gitbook.io/sunbird-spark/learn/components/course-and-batch-management.md).

# Course and batch management

### Creating a course

A course in Spark is a **trackable collection**. It is a structured set of content units, or lessons, organised into a hierarchy and associated with one or more batches.

{% stepper %}
{% step %}

#### A content creator builds the course structure

A content creator builds the course structure in the Collection Editor and adds lessons and assessments.
{% endstep %}

{% step %}

#### The creator submits the course for review

The creator submits the course for review.
{% endstep %}

{% step %}

#### A content reviewer approves and publishes the course

A content reviewer approves and publishes the course.
{% endstep %}

{% step %}

#### A course mentor creates batches

A course mentor creates one or more batches for the course and defines enrolment windows and certificate rules.
{% endstep %}
{% endstepper %}

### Batch management

Each course batch is an independent enrolment and tracking context:

* Learners enrol in a specific batch, not just a course
* Progress is tracked per batch
* Certificate rules are defined per batch
* A course can run multiple simultaneous or sequential batches for different cohorts, regions, or time periods

### Progress tracking

Progress is tracked at the individual lesson level:

* Lesson completion is recorded when a learner reaches the end of a content item
* Course-level completion is calculated as the percentage of lessons completed
* Certificate issuance is triggered when a learner's completion percentage meets the batch threshold, typically `100%`
* If an assessment is part of the course, its score can also be used as a certificate criterion


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://sunbird.gitbook.io/sunbird-spark/learn/components/course-and-batch-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.