How the recurring monthly template and rollover work

A period is named for the month being closed (e.g. "July 2026 Close"), but the actual close work — and every due date below — falls in the month after that. Templates and generated periods are edited on the Templates tab (admin only).

Tasks and binder owners

Each template task has a Due rule, an optional Months filter, an optional Depends on (single-parent — one task before it), and an optional Category. Only one template can be active at a time — activating one deactivates the rest.

Due rule syntax

• day:N — day N of the work month, clamped to the month's last real day.
• bd:N / bd:-N — the Nth business day from the start/end (bd:0 = first business day, bd:-0 = last business day — the usual "close by month end").
• wk:W:D — week W, weekday D (e.g. wk:1:tue). This is a fixed week+weekday position, recommended for recurring tasks since it matches the real close calendars — it is not the same date every month unless the month happens to start on a Monday.

Months filter

A task with Months set (e.g. 2,5,8,10) only generates when either the period being closed or its work month falls in that list. Leave it blank (the default) to generate every period.

Generating a period

Click Generate period on the Templates tab, or let it happen automatically: a background thread checks hourly and auto-generates the period for whatever month is currently being worked, from the active template, the first time it's needed. Generating never overwrites an existing period — it's safe to run again.

What happens to a task that's still open when the period rolls

Nothing carries forward. Each generated period gets a brand-new set of tasks from the template, all starting at not started — an incomplete task from last period simply stays sitting, unfinished, in that old period's history. It doesn't block the new period or reappear there.