> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/syntax/timing-syntax/frequency-inputs.md).

# Frequency Inputs

This article explains **frequency inputs** in the Timing modal, focusing on **schedule** and **range** modes.

You will learn:

* The difference between schedule and range inputs.
* When to use each mode.
* How frequency interacts with accrual and seasonality.

Frequency settings tell the engine how often a variable accrues.

{% stepper %}
{% step %}

### Frequency modes

There are two main ways to express frequency:

* **Range**
  * The value is spread evenly across each period in a given date range.
  * Useful for continuous items like rent, salaries or ongoing subscriptions.
* **Schedule**
  * The value occurs on specific dates or recurrence rules.
  * Useful for items like fortnightly payroll, quarterly fees or annual payments.

Both modes work with start and end dates.
{% endstep %}

{% step %}

### Range based inputs

In range mode you typically specify:

* A start date.
* An end date.
* A per period amount or total to be spread.

The engine then allocates accruals evenly across all periods between start and end, in line with the model's granularity.

Examples:

* Monthly rent across a year.
* A continuous service fee.
* Staff salaries.
  {% endstep %}

{% step %}

### Schedule based inputs

In schedule mode you specify a recurrence pattern, such as:

* Every week.
* Every month on a particular day.
* Every quarter.
* A specific list of dates.

The engine then places accruals exactly on those scheduled dates, and aggregates them into periods for reporting.

Examples:

* Payroll on the 15th of each month.
* Quarterly licence fees.
* An annual insurance payment.
  {% endstep %}

{% step %}

### Choosing between schedule and range

Use **range** when:

* The economic activity is continuous.
* Even spreading is a reasonable approximation.
* You care more about totals per period than specific calendar dates.

Use **schedule** when:

* The timing of individual events matters for cashflow.
* The pattern is discrete and recurring.
* You want to reflect real payment calendars.

Mixing both patterns across different variables gives you realistic yet manageable models.
{% endstep %}

{% step %}

### Frequency and seasonality

Frequency defines the base pattern. Seasonality can be layered on top to adjust the relative weight of periods without changing the underlying frequency mode.
{% endstep %}
{% endstepper %}

***

## Related articles

* [Editing Frequency](/syntax/how-input-fields-work/editing-frequency.md)
* [Seasonality Inputs](/syntax/timing-syntax/seasonality-inputs.md)
* [Cashflow Statement Overview](/help/financial-outputs-and-valuation/cashflow-statement-overview.md)
* [Build an Opex Planning Model](/how-tos/operations-and-unit-economics/build-an-opex-planning-model.md)