# Average Revenue Report The **Average Revenue Report** provides a doctor-wise summary of visits and revenue within a selected date range. This report is used by finance teams, administrators, and management to review income performance for each doctor. It helps track total visits, paid and non-paid visits, package visits, and the average revenue generated per doctor. *** ### Steps to Generate the Average Revenue Report * Open the **Average Revenue Report** by navigating to **Home > Reports > Revenue Reports > Average Revenue Report**. * Set the **From** and **To** date fields to define the reporting period. * Optionally, use the **Doctor** filter to generate the report for a specific doctor. * Click **Search** to generate the report. *** ### Report Structure The report displays doctor-wise revenue details for the selected duration. Each row represents a doctor and includes the columns **Doctor Name, Department Name, Speciality Name, Total Visits, Followup Visits, New Visits, Revisits, Package Visits, Non Paid Visits, Paid Visits, Total Revenue,** and **Average Revenue**. This structure helps users compare consultation volume with revenue performance and identify the average revenue generated per visit for each doctor. The screen also includes functional tools: **Pagination** (to browse multiple pages of results), **Zoom and Refresh** controls, **Search within the report, Print,** and **Export** options. *** --- # Agent Instructions: 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: ``` GET https://unitecare.gitbook.io/uniteemr/reports/revenue-reports/average-revenue-report.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.