---
title: "IFS Cloud Project Governance: Five Questions to Answer"
date: 2026-11-21
description: "Five questions every IFS Cloud steering group asks, where the answers should come from, and how a register-based tool such as Implementer helps."
author: "Dariusz Myśliwiec"
intro_image: "https://ifs-erp.consulting/images/articles/implementer-launch-ifs-cloud-projects-from-registers-en-d1ab8d2b.webp"
fulltext_image: "https://ifs-erp.consulting/images/articles/implementer-launch-ifs-cloud-projects-from-registers-en-d1ab8d2b.webp"
categories:
  - name: "How IFS Cloud ERP Transforms Business Operations Supply Chain AI and Legacy System Migration"
    url: "https://ifs-erp.consulting/ifs-cloud.md"
tags:
  - name: "IFS Cloud"
    url: "https://ifs-erp.consulting/tags/ifs-cloud.md"
  - name: "IFS implementation"
    url: "https://ifs-erp.consulting/tags/ifs-implementation.md"
  - name: "Implementer"
    url: "https://ifs-erp.consulting/tags/implementer-en.md"
---

# IFS Cloud Project Governance: Five Questions to Answer

![IFS Cloud Project Governance: Five Questions to Answer](https://ifs-erp.consulting/images/articles/implementer-launch-ifs-cloud-projects-from-registers-en-d1ab8d2b.webp)

Independent IFS Cloud practice · Project governance

 
## Five questions a steering group asks, and where the answers should come from

 **Key takeaways**

 
- Every IFS Cloud steering group asks the same five questions about versions, approvals, readiness, updates and evidence.
- If the answer to one of them takes an afternoon, the fact it depends on has no owner, state or history of its own.
- You can test this in 30 minutes on your own project, with no tool at all.
- Implementer is the tool I built for the case where the test fails: each fact is a register row, and the documents are generated from the rows.

 This is a method article first and a product article second. The method works on a spreadsheet if you are disciplined. The product exists because discipline across a whole project team does not last through a go-live.

  ## 1.Which five questions does every steering group ask?

 Across implementations, rollouts and update cycles the questions repeat. What differs is how long the answer takes.

 
1. **Which version of the migration plan is current?** Three copies and two owners give one deadline nobody can defend.
2. **Who approved this change, and when?** The answer is somewhere in a mail thread.
3. **Are we really ready for go-live?** Everyone has an opinion and nobody has the evidence next to the claim.
4. **Why did the update break our customisation again?** Users found it, not a check.
5. **Where is the test evidence?** In someone’s inbox, and an audit turns into archaeology.

 A sixth problem sits underneath all five: the consultant who knew the reason left, and the reason was never written down.

  ## 2.How do you test your own project in 30 minutes?

 Pick three of the five questions and answer each one with a document, a name, a date and a piece of evidence, using only what the project team can open without asking anyone.

 
- **It takes minutes and the evidence is attached:** the fact is already managed.
- **It takes an afternoon or needs a phone call:** the fact lives in a person, not in the project.
- **Two people give different answers:** the fact has no single owner, and that is the gap to close first.

 Close the gap that hurts most this quarter, not all of them. Start with the approval trail or the test evidence, because those are the two an auditor asks for.

  ## 3.What changes when each fact is a register row?

 In Implementer a risk, a CRIM item, a change request, a baseline and a test result are rows, and every row has an owner, a state and a history. The 24 templates of the Implementation Docs Kit are not separate files. Each is generated on demand from the rows as a versioned PDF with a checksum, so the document for the steering group is never assembled by hand.

 The same register behaves differently depending on the situation, so there are three modes:

 
- **New implementation:** five gates with 61 checklist items, closed with evidence and acceptances by people.
- **Rollout:** what is common to all sites stays common, and local differences are recorded separately.
- **BAU and Evergreen:** IFS updates run as managed cycles with a regression pack and a drift check.

 The individual registers are described in the Implementation Docs Kit series on www.ifs-erp.com, for example [Change Requests and Change Control (IDK-07)](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/07-change-request-and-change-control-procedure) and [the Go-Live Readiness Decision (IDK-21)](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/21-go-live-readiness-decision), which covers the 42-criteria readiness review.

  ## 4.What will Implementer not do?

 It reads IFS Cloud over OData with a read-only account, one account per environment, and never writes to IFS. It runs in your infrastructure, and users sign in with Microsoft Entra ID. The AI assistant is optional, switched on by an administrator, and it produces drafts only: nothing is approved until a person accepts it.

 The live demo uses fictitious data of a company called Alfa Metal S.A. It does not show your data, your IFS or your Entra ID. Microsoft Teams notifications and the Microsoft 365 calendar have not been tested on a production tenant, so judge them in a pilot, not in the demo.

  ## 5.What do you see in the 15-minute demo?

 The same path I use in a scoping call: the dashboard and gates, the CRIM board and the reason shown when an action is blocked, one change followed through its audit trail, the steering group pack read from the registers, and then either the readiness review or an update cycle with the environment matrix.

 [Open the live demo](https://implementer.ifs-erp.com/login) [Book a 30-minute scoping call](https://ifs-erp.consulting/contact)

  ## 6.Frequently asked questions

 Do I need Implementer to run the 30-minute test? No. The test needs only the project team and the files they already have. Implementer is for the case where the test shows that the answers depend on people instead of on the project.

   Does Implementer write to our IFS Cloud? No. It reads over OData with a read-only account and has a separate account for each environment. Nothing is installed in IFS, so an IFS update has no Implementer object to break.

   How does an engagement start? With a 30-minute scoping call and the 15-minute demo, followed by a pilot at a fixed price in your infrastructure. Terms are on the product site, [implementer.ifs-erp.com](https://implementer.ifs-erp.com/en/pricing). Product details are on [the Implementer page](https://www.ifs-erp.com/en/applications/implementer-implementation-support-for-ifs-cloud).

  ## 7.About the author

 **Dariusz Myśliwiec** is an independent IFS Cloud consultant with 18 years on IFS, and the person who builds Implementer.

 Independent product, not an IFS product or document. IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
