> For the complete documentation index, see [llms.txt](https://help.activenow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.activenow.io/en/reports/hours-classes-and-income-in-courses-report.md). # Number of Classes, Hours and Income in Courses This group of reports helps you analyse how your courses are running and how profitable they are. ## Number of classes and hours in courses The *Number of classes in courses* and *Number of hours in courses* reports show how many classes and hours are planned across your courses in a selected period. 1. Go to *Reports → Courses*. 2. Select *Number of classes in courses* or *Number of hours in courses*. 3. Choose the period you need. 4. Click *Generate a report*.
## Income from courses The *Income from courses* report shows how much your school should earn from each course — a great starting point for figuring out which courses are worth the most to your business. 1. Go to *Reports → Finances → Income from courses*. 2. Choose the period you need. 3. Click *Generate a report*. ![Income from courses report showing projected revenue per course](https://2983515171-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL5ksnUuhXGAx5afQd3MB%2Fuploads%2Fgit-blob-fb6d247ad94bb670c07594ae46b4ee56f44c803f%2FZrzut%20ekranu%202026-05-26%20124742.png?alt=media) --- # 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://help.activenow.io/en/reports/hours-classes-and-income-in-courses-report.md?ask=&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.