Define: Monthly Average
In a contract, Monthly Average is the calculated mean of a metric over a calendar month, typically the sum of all daily readings divided by the number of readings taken. It is used to smooth out day-to-day fluctuations when measuring things like energy consumption, service uptime, or pricing benchmarks for billing or compliance purposes.
Legal accuracy standard set & glossary spot-checked by Imad Mohammed Nazar , Skadden-trained M&A lawyer, Legal Engineer at GenieAI
What Monthly Average Means in a Contract
Monthly Average is a calculation method used in contracts to express a single representative figure for a metric measured repeatedly throughout a calendar month. Instead of relying on a single spot measurement, which could be misleadingly high or low due to short-term fluctuations, the parties agree to smooth the data by summing all recorded values and dividing by the number of readings. This produces a figure that better reflects typical performance or consumption over time.
The term is common in agreements where a party's obligations, fees, or performance thresholds depend on usage or performance patterns rather than isolated events. For example, an energy supply contract might use Monthly Average consumption to calculate a bill, while a technology services agreement might use Monthly Average uptime to assess whether a service level has been met.
Because the calculation directly affects money owed, compliance status, or contractual remedies, the definition of Monthly Average is not merely descriptive. It functions as an operative clause that determines outcomes, and any ambiguity in how it is calculated can lead to disputes between the parties.
How Monthly Average Is Defined or Measured
At its simplest, Monthly Average is calculated by adding together every daily (or otherwise periodic) measurement taken within a given month and dividing that sum by the number of measurements recorded. The formula seems straightforward, but several variables can materially change the result.
- Frequency of measurement: daily, hourly, or per transaction readings will produce different averages even for the same underlying activity.
- Treatment of missing data: contracts must specify whether gaps in measurement are excluded, treated as zero, or estimated.
- Rounding conventions: whether the final figure is rounded up, down, or to the nearest whole number can matter when thresholds are close.
- Time zone and billing cycle alignment: a.
Relevant Circumstances
- Tracking service or product delivery metrics
- Billing for utility usage