# Replacement planner

> The replacement calendar - drag assets into the year you intend to replace them, ranked by a configurable priority score, then seed projects from the plan.

Source: https://app.assetlab.ca/docs/projects/replacement-planner

The planner turns the lifecycle forecast into an actual plan: a **replacement calendar** where you drag assets into the year you intend to replace them. It works on the registry you already maintain - no side spreadsheet - and what you schedule here flows into the [Lifecycle & funding](/docs/asset-management/lifecycle) picture as **Planned** funding.

## The inputs (you already have them)

| Input | Source |
|---|---|
| Installation date & useful life | [Asset records](/docs/asset-management/assets) |
| Replacement cost | Asset records / [import](/docs/start/importing-data); valued at current replacement value where cost data exists |
| Condition | [Assessments](/docs/asset-management/condition-assessments) |
| Risk / criticality | [CoF × LoF scores](/docs/asset-management/risk-and-fci) |

Inflation and replacement-value settings are organization-wide (set in Settings), so the planner, the dashboard forecast, and the Capital Brief all price assets on the same basis.

## Two planners, one toggle

Facilities and [infrastructure](/docs/infrastructure) each get their own planner, switched by a scope toggle - buildings-and-equipment assets on one side, linear features on the other. Each keeps its own priority configuration.

## Prioritization you can tune

Candidates are ranked by a weighted **priority score**, not just age. The default weights:

| Factor | Default weight |
|---|---|
| Lifecycle (age vs. useful life) | 40 |
| Condition | 25 |
| Criticality | 25 |
| Repair cost history | 10 |

Open the **Priority weights** panel (in the Filters sheet) to adjust them - your weights are remembered per browser, separately for the facilities and infrastructure planners. This is how the poor-condition, high-consequence ice plant outranks the elderly-but-fine storage garage.

## Working the calendar

Drag a recommended asset (or a whole system) into a year to schedule its replacement; drag between years to reschedule; remove it to unschedule. Each entry is valued at the asset's current replacement value, falling back to the entry's estimated cost when the asset carries no cost data.

The calendar is the source of two downstream numbers:

- The **Planner** view of the [dashboard's projected replacement chart](/docs/asset-management/lifecycle) - scheduled work by year, against the Lifecycle view's projected need.
- The **Planned** column of the Capital Brief's funding gap - scheduled work counts as funding lined up against the need.

## From plan to projects

**Create projects** turns the calendar into [projects](/docs/projects/creating-projects). How the grouping works:

- Scheduled **assets** group into one project per year + site + building; scheduled **systems** group per year + system group.
- Each proposed project's budget is the summed estimated cost of its entries, its dates span the planned year (Jan 1 - Dec 31), and it starts in **Planning** status with the asset scope pre-linked.
- You tick which proposed groups to actually create - nothing is created unseen.
- A project whose generated name already exists is skipped rather than duplicated, so re-running the dialog after adding entries only creates what's new.

Delivered projects update the assets - new install dates, new condition - and the next planning cycle starts from reality.

## Export

Managers and above can export a PDF **evaluation report** of the planned assets and systems - the take-to-the-meeting version of the calendar.

> [!tip] Inflation matters at horizon. A 20-year plan at 0% inflation understates the later years dramatically - set a defensible rate in Settings and it applies consistently across the planner and every forecast.