> 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/how-input-fields-work/entering-schedules.md).

# Entering Schedules

This article explains how to **enter schedules** in Model Reef input fields.

You will learn:

* What a schedule is in the context of the timing engine.
* How to define recurring and one off schedules.
* How schedules interact with accrual, payment timing and seasonality.

Schedules define **when** something happens, not how much it is worth. They are a key part of the Timing modal and some preset formulas.

{% hint style="info" %}
The Timing modal previews patterns and indicates which layer (accrual or payment) you are configuring. Use the preview to validate results after entry.
{% endhint %}

{% stepper %}
{% step %}

### What a schedule represents

A schedule describes the timing pattern for events such as:

* Payroll on specific days of the month.
* Rent paid monthly or quarterly on set dates.
* One off items like a large project payment.
* Irregular events such as staged milestone payments.

Schedules overlay timing on top of a base amount or formula.
{% endstep %}

{% step %}

### Entering simple recurring schedules

In many timing configurations you can choose simple recurring options, for example:

* Every month on the same day.
* Every quarter at the start or end of quarter.
* Once a year on a specified month.

To enter these:

* Open the Timing modal for the variable.
* Select a recurring frequency (for example monthly).
* Choose the specific schedule rule (for example 15th of each month).
* Confirm and preview the resulting pattern.

The engine applies this schedule across the model horizon, respecting the start and end dates.
{% endstep %}

{% step %}

### Entering one off or irregular schedules

For one off or irregular events you can:

* Enter explicit dates or periods for each event.
* Assign amounts or percentages per event if the interface supports it.

Examples:

* A single capex payment in a specific month.
* Three milestone receipts over the life of a project.

The pattern you enter tells the engine in which periods accrual or cash should occur.
{% endstep %}

{% step %}

### Interaction with accrual and delays

Schedules can be applied to:

* **Accrual timing**, controlling when revenue or expenses hit P\&L.
* **Payment timing**, controlling when cash moves relative to accrual.

Depending on configuration:

* A schedule might define the accrual periods and a delay then shifts cash.
* Or a schedule might directly define when cash events occur, with accrual assumed to match.

The Timing modal will indicate which layer you are configuring and provide a preview.
{% endstep %}

{% step %}

### Schedules and seasonality

Schedules can be used alongside seasonality:

* The schedule defines when events are allowed to occur.
* Seasonality multipliers adjust the magnitude of those events across the year.

For example, you might have a monthly schedule but apply higher multipliers in peak months and lower ones in off peak periods.
{% endstep %}

{% step %}

### Validating schedules

After entering a schedule:

* Use the preview in the Timing modal to check the pattern.
* Confirm that P\&L lines and cash movements appear in the expected periods.
* Adjust the schedule rules if the pattern does not match the real world behaviour you intend.

Well defined schedules make your model's timing assumptions explicit and easier to maintain.
{% endstep %}
{% endstepper %}

***

## Related articles

* [Timing Modal Overview](/syntax/timing-syntax/timing-modal-overview.md)
* [Timing Preview](/syntax/timing-syntax/timing-preview.md)
* [Actuals Import](/help/xero-integration/actuals-import.md)
* [Build a Cost of Goods Model](/how-tos/operations-and-unit-economics/build-a-cost-of-goods-model.md)