Open Configure Settings → Other → Cadences. The page has two buttons, New Planning Cadence and New Timebox, a Show archived toggle, and a per-cadence menu (Add timebox, Edit cadence, Delete cadence or Archive cadence).

Click New Planning Cadence and fill in the dialog.


| Field | What to enter | Example (12-week PI) |
|---|---|---|
| Label | The cadence's name | Program Increment |
| New Timebox Every + Frequency Unit | How often a new period starts: a number and Day, Week, Month, Quarter, or Year | 12, Week |
| Timebox Label Template | How each timebox is named; variables are filled in automatically. Default ${label} ${counter} | PI ${counter} → PI 1, PI 2 |
| Parent Cadence | Root for a top-level cadence, or the cadence this one nests inside | Root |
| Color | Shown on boards and Gantts |
Click Create Cadence.
Click New Planning Cadence again for the 2-week Sprint and choose the Program Increment as Parent Cadence. Sprints then sit inside each PI.

| Variable | Produces |
|---|---|
${label} | The cadence label |
${counter} | Running number of this timebox across the cadence |
${timeboxCounter} | Number of this timebox within its parent timebox (resets each parent) |
${ancestor.1.counter}, ${ancestor.1.timeboxCounter} | The parent timebox's counters (ancestor.2 for the grandparent) |
${year}, ${quarter}, ${month}, ${monthNumber}, ${week} | Calendar parts of the start date (${month} gives Jan) |
So a parent Program Increment ${counter} with a child Sprint ${ancestor.1.counter}.${timeboxCounter} yields Program Increment 2 containing Sprint 2.1, Sprint 2.2, and so on. A monthly cadence might use ${month} ${year}.

Cadences can be edited any time; archived ones keep only label and colour editable.
A cadence has no dates until you create timeboxes. Click New Timebox (or Add timebox on a cadence):

The cadence page then shows the tree of timeboxes (1) with their dates (2). Timeboxes with children cannot be deleted until the children are removed.

When you create a board in Plan Delivery, choosing a cadence makes it a cycle board; its cycles are the cadence's timeboxes, and items placed on a cycle inherit its dates when Sync work item dates with their cycles is on in Global Automations. See Using Cycle Boards.

Admin Onboarding - Organizing the When: Understanding Planning Cadences
Step 10a of admin onboarding — cadences, timeboxes, and cycles explained with one example, why nested cadences matter for scaled planning, and how to decide which cadences your teams need.
Track Progress - Gantt Charts
Step 11 of admin onboarding — once items carry dates (from cycles or by hand), Gantt charts in Track Progress lay them on a timeline with dependencies; pointer to the full guide.