# IFS Cloud BAU and Evergreen updates as managed cycles

In BAU mode Implementer runs each IFS Cloud service or release update as a managed cycle with a plan, a verification stage with a regression pack and drift checks, and a recorded production decision.

## How does an update cycle run?

Every service or release update is a cycle with three stages and a decision on record.

1. **Plan**

   Window, scope, CRIM objects and interfaces affected, freeze periods and environment rules from the update policy.

2. **Verify**

   Re-verify CRIM objects, check interfaces, run the pinned regression pack and read the drift check against IFS.

3. **Decide**

   The production decision goes through approval, with the system owner, optional supplier verification and the chair of IT governance.

![Updates page with policy, decisions, cycles and calendar tabs](https://implementer.ifs-erp.com/site-assets/img/en/idk-23-updates.png)

*Updates page in the demo project, demo data*

## What is BAU and Evergreen mode?

BAU and Evergreen mode is the project mode in Implementer for the time after go-live, when IFS Cloud keeps changing through service updates and release updates. There are no implementation phases. The Go-live and Closure pages are hidden, and the Updates page opens on the cycles. The mode builds on IDK-23, the update strategy template. Compare it with [new implementation](https://implementer.ifs-erp.com/en/new-implementation.md) and [rollout](https://implementer.ifs-erp.com/en/rollout.md).

## What does the update policy hold?

The update policy is one record per project that fixes the rules before the first update arrives:

- cadence decisions and freeze periods,
- the role that may approve an exception,
- environment rules for refreshes and overwrites,
- the regression scope and the customisation policy,
- the system owner and the update coordinator.

Each later decision (cadence, exception, customisation, environment, regression) is an entry in the update decision log with a reason, a date, a decider and a review date. See the [glossary](https://implementer.ifs-erp.com/en/glossary.md) for Evergreen and CRIM.

## What is in an update cycle?

Each cycle has a verdict for three stages: plan, verification and decision. In verification you work through the six-step impact assessment from the template: CRIM re-verification, interface checks and regression. The regression pack of a cycle pins the scenarios worth re-running and judges them against their latest results, instead of inventing the regression for every release. A calendar shows update windows, refreshes and freeze periods.

## How does the IFS check work?

Implementer reads from IFS Cloud through read-only OData, with one OAuth2 client per environment. A drift check compares the stored projection results and flags what changed. A blocking drift check and an informational stale check feed the verification stage, so the team sees a change before users report it. Implementer never writes to IFS. See [security and trust](https://implementer.ifs-erp.com/en/security-and-trust.md).

## What else belongs in BAU?

Support requests and the handover records from the implementation stay in the same project, so the knowledge does not leave with a person. [AI search and chat](https://implementer.ifs-erp.com/en/ai-assistant.md) answer from those records with citations to the source.

## What does it cost?

A BAU and Evergreen licence is EUR 3,600 per project and year, up to 25 named users, net, plus VAT. See [pricing](https://implementer.ifs-erp.com/en/pricing.md), the [pilot](https://implementer.ifs-erp.com/en/pilot.md) and the [FAQ](https://implementer.ifs-erp.com/en/faq.md). You can also [open the live demo](https://implementer.ifs-erp.com/login) or [book a scoping call](https://www.ifs-erp.com/en/book-time-with-me).

Last updated: 13 November 2026

## Ready for a pilot?

A 30-minute scoping call and a 15-minute demo on demo data.

[Book a scoping call](https://www.ifs-erp.com/en/book-time-with-me)
