> For the complete documentation index, see [llms.txt](https://docs.myvega.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myvega.ai/operations/analytics-and-report/batches-analytics.md).

# Batches Analytics

## **Understanding Batch Analytics**

### What is Batch Analytics?

**Batch Analytics** helps you take a deep look at how one specific batch (or group of users) is performing. A **batch** is a group of learners — like a classroom, coaching group, or training cohort — that you’ve created earlier in the Operations > Batches section.

In this view, you can pick a batch from a dropdown menu and see:

* How that group is performing overall
* What they are good at
* Where they are struggling
* How much time they are spending
* What topics need attention

This helps you understand how your batch is learning as a group so you can take better actions — like revising topics, changing teaching pace, or helping specific users.

***

### Why use Batch Analytics?

Imagine you're a teacher with 30 students in one class. Some are doing great, some are struggling, and some are somewhere in the middle. Batch Analytics is like a **health report for your entire class**.

It helps you answer questions like:

* Is this batch ready for the next test?
* What topic do they find most difficult?
* Are they using their study time well?
* Who in the batch needs more help?

This makes it easier to **teach smarter, not harder**.

***

### What You’ll See in Batch Analytics

Once you select a batch from the dropdown, the page will show detailed data for that batch only.

#### 1. **Performance Zones (Red, Yellow, Green)**

Just like in overall analytics, learners in the batch are grouped into:

* **Red Zone** – Low mastery; needs help urgently
* **Yellow Zone** – Medium mastery; some understanding but still improving
* **Green Zone** – High mastery; doing very well

You’ll see how many users fall into each zone.\
This tells you how the batch is doing as a whole and which learners to focus on.

<figure><img src="/files/aWQh3LOMyUDs84otFTDA" alt=""><figcaption></figcaption></figure>

***

#### 2. **Average Mastery Score**

This shows the **average learning score** for all users in the batch. It gives you a quick snapshot of how confident and prepared the batch is overall.

For example:

* A score above 80 means your batch is strong
* Around 60–70 means they’re doing okay
* Below 60 means they need more support

This helps you decide if you should move forward, revise, or slow down the pace.

<figure><img src="/files/w9nbLKoxXn9BoEwcdRod" alt=""><figcaption></figcaption></figure>

***

#### 3. **Common Errors**

This shows what types of mistakes the batch is making most often. For example:

* Grammar errors in subject-verb agreement
* Math mistakes in word problems
* Confusion in reading logic questions

If many learners are making the same mistake, it’s likely a **teaching gap**, not just a student mistake. This tells you **what needs to be explained again**.

<figure><img src="/files/7lzjhxmCNRam6cg5JG0E" alt=""><figcaption></figcaption></figure>

***

#### 4. **Time Management**

This graph shows how much time the batch is spending on different question types or sections.

You can see:

* If users are spending too much time on easy questions
* If they are rushing through difficult ones
* If they’re balancing time well in full tests

Why it matters:

* Helps you **train them to manage time better**, especially for exams like the SAT or GRE

<figure><img src="/files/9nK6bsop12beEfJtePcx" alt=""><figcaption></figcaption></figure>

***

#### 5. **User-Level Table (Within the Batch)**

You’ll also get a list of all users in the batch with details like:

* Their Mastery Score
* Number of questions attempted
* Time trained
* Learning Journey assigned
* A link to see their personal analytics

This helps you **zoom in on individuals** who are falling behind or leading the way.

<figure><img src="/files/n0Xc8W0bC7aSho1mlQO2" alt=""><figcaption></figcaption></figure>

***

### How You Can Use Batch Analytics

| What You Want to Know            | What to Look At                     | What You Can Do                                 |
| -------------------------------- | ----------------------------------- | ----------------------------------------------- |
| Is the batch doing well overall? | Mastery Score and Zone Distribution | Adjust teaching speed or batch schedule         |
| What topics are weak?            | Topic Mastery bars                  | Revise or assign extra practice in those topics |
| What errors are common?          | Error pattern section               | Re-teach those areas to the whole batch         |
| Is time being used wisely?       | Time Management graph               | Coach learners on pacing and test strategy      |
| Who needs 1-on-1 help?           | User list with low scores           | Schedule personal sessions or extra tasks       |

***

**Batch Analytics is your teaching assistant.**\
It gives you clear insights about how your group is doing, so you don’t have to guess. It helps you make smart decisions that can really improve learning outcomes — for everyone in the batch.

Need more support? Our support team is available 24/7 through:

* Email: <support@myvega.ai>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.myvega.ai/operations/analytics-and-report/batches-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
