# How an IFS Cloud project runs

An IFS Cloud project has five phases. Each phase ends with a gate. The steering group opens the gate, and only then does the next phase start.

This page applies to every stage.

IDK templates: IDK-01, IDK-08

Five phases, five gates. After go-live the system stays current through the update cycle.

1. **Initiate project.** Both teams start. You set up the plan, the scope and the controls.
    - IDK templates: IDK-01, IDK-02, IDK-03, IDK-04, IDK-05, IDK-06, IDK-07
    - Gate: Project initiated
2. **Confirm prototype.** You build key processes on customer sample data and confirm the solution scope.
    - IDK templates: IDK-09, IDK-10
    - Gate: Solution confirmed
3. **Establish solution.** You finish design, build and tests. The phase ends with acceptance testing.
    - IDK templates: IDK-11, IDK-12, IDK-14, IDK-15, IDK-16, IDK-17, IDK-18
    - Gate: Solution established
4. **Implement solution.** You train users, rehearse the cutover and pass the operational readiness test.
    - IDK templates: IDK-19, IDK-20, IDK-21
    - Gate: Go live authorised
5. **Go live.** You run the cutover, retire the old system, hand over to support and close the project.
    - IDK templates: IDK-20, IDK-22, IDK-24
    - Gate: Go live complete
6. **Maintained after go-live.** The system stays current through service and release updates.
    - IDK templates: IDK-23

## What the app keeps for you

You work in the registers. The documents are views built from them, so they never go stale.

1. **Registers.**
    - Risks and issues
    - Change requests
    - CRIM objects
    - Interfaces
2. **Rules.**
    - Phases and gates
    - Status flows
    - Who may approve
    - Audit trail
3. **Documents.**
    - IDK templates
    - PDF packs
    - Status reports
    - Gate checklists

## How to do it

1. **Initiate.** Both teams start. You agree the plan, the scope, the roles and the risks.
2. **Confirm the prototype.** You build the first version of key processes with real sample data. The customer confirms the solution scope.
3. **Establish the solution.** You finish design, build and tests. The phase ends with acceptance testing.
4. **Implement.** You train users, rehearse the cutover and pass the operational readiness test.
5. **Go live.** You switch over, retire the old system, hand over to support and close the project.

## Good to know

- The steering group decides at every gate. A project manager only recommends.
- The app is a tool for the project team. It does not replace the steering group.
- AI in this app only writes drafts. A person always approves.

## Related topics

- [Qualification gates](https://implementer.ifs-erp.com/help/en/gates.md)
- [New project, rollout or BAU](https://implementer.ifs-erp.com/help/en/modes.md)
- [Roles and who may do what](https://implementer.ifs-erp.com/help/en/roles.md)
- [Dashboard](https://implementer.ifs-erp.com/help/en/dashboard.md)
- [Guide: set up the system and the project](https://implementer.ifs-erp.com/help/en/stage.config.md)

Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.

Last updated: 13 November 2026
