--- title: "Reporting features" slug: "reporting-features" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:46:26Z published: 2026-09-07T17:46:26Z canonical: "docs.trellix.com/reporting-features" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Reporting features You can use the preconfigured queries, create custom queries, use the output of the queries to perform tasks, and create reports as output. > [!NOTE] > Note > > Whenever you change a policy, configuration, client or server task, automatic response, or report, export the settings before and after the change. To view one of the preconfigured queries, click **Run**. You can then perform the following tasks: - Save the output as a report. - Duplicate the query and change the output. - View results in the query system. - Take action on the results as you normally would in the System Tree. > [!NOTE] > Note > > As you add new products using extensions to ePO - On-prem, new preconfigured queries and reports become available. ### Reporting lag time When you run ePO - On-prem query reports, you must be aware that reports have a lag-time. This lag-time means information is not added to the report during the time when it's actually being run. This information lag-time begins when you start the query, lasts until the query is done, and varies depending on the time it takes to run the query. Report lag-time example: - You run a query hourly and the query takes 10 minutes to run. - Events that occur during the 10 minutes, while the query is being run, are not included in that report, but are written to the database. - Those events appear in the next query report run an hour later.