The top of the report displays identifying information for the report and the controller it was generated from:

Company – The organization associated with the site.

Site – The specific location the controller is installed at.

Controller – The controller ID assigned to the device.

MAC / Serial Number – Hardware identifiers for the controller.

Type – The controller model (e.g., BL-3200S).

Version – The firmware version running on the controller at the time the report was generated.

Period – The date range the report covers.

Prepared on – The date the report was generated.

By – The AppManager user who generated the report.

Near the top of the report, three summary figures are displayed:

Scheduled Usage – The total volume of water (in gallons) used while a program or zone was actively running. i.e. Intentional irrigation events.

Unscheduled Usage – The total volume of water (in gallons) detected by the flow meter while no program or zone was running.

Total Usage – The combined total of scheduled and unscheduled usage for the report period.

The year-over-year section displays the total water usage recorded for the same date range as the current report, pulled from the previous three calendar years. For example, if the current report covers March 8 to April 6, 2026, the comparison will show usage for March 8 to April 6 for 2025, 2024, and 2023.

Each year is displayed as a separate figure, along with a percentage change relative to the comparison period. 

If a prior year displays "No usage recorded," it means no flow data was captured for that controller during the equivalent period in that year. This may indicate the controller was not yet installed, was not connected, or that flow data was not being logged at that time. It does not necessarily mean that no irrigation occurred.

A progress bar at the top of each water source entry provides a visual representation of how much of the effective budget has been consumed, shown as a percentage. The following fields are shown:

Monthly Budget – The budget amount entered per month, in gallons, for this water source.

Budget Period – The number of months the budget spans.

Effective Budget – The total budget available across the full budget period (Monthly Budget × Budget Period).

Used – The total gallons consumed during the report period.

Available Budget – The remaining gallons available within the budget period.

Status – Indicates whether the site is currently under or over budget.

If a controller has more than one water source configured, each water source will appear as a separate entry in the Budget Progress section, with its own budget values and progress bar.

This section displays a day-by-day chart overlaying actual water usage (in gallons) against the evapotranspiration (ET) value recorded by the assigned weather station (shown in inches). ET represents the amount of water lost from the soil and plant surfaces due to evaporation and transpiration. Higher ET values indicate greater evaporative demand, which typically corresponds to higher irrigation needs.

Below the chart, and with data points enabled on your report, a data table lists the exact water used and ET value for each interval in the report period.

This section compares what the system expected to use each day against what was actually recorded. It also breaks the actual usage down into scheduled and unscheduled components.

Expected Water Used – Calculated based on the scheduled program runtimes and the design flow configured for each zone. This requires either a Learn Flow to have been performed or design flows to have been manually entered for each zone.

Actual Water Used – The total volume of water recorded by the flow meter for that day.

Scheduled Usage – The portion of actual usage that occurred while a program or zone was running.

Unscheduled Usage – The portion of actual usage that occurred outside of any scheduled program or zone runtime.

The number of flow meters being tracked is displayed above the chart.

Actual usage can vary from expected usage for several reasons, including controller start, stop, and pause conditions during a run. The expected value is a calculated estimate based on configured design flows (Requires learn flow to have been performed or design flows to have been manually entered) and scheduled runtimes — it does not account for real-time variations such as pressure fluctuations, zone pauses, or manual interventions.