# Implementer help

Every help topic of the Implementer application, grouped by project stage.

## System and project configuration

- [Guide: set up the system and the project](https://implementer.ifs-erp.com/help/en/stage.config.md): Do this once per installation and once per project, before phase 1. It makes the app safe to use and the project ready for people.
- [Approval rules](https://implementer.ifs-erp.com/help/en/approval-rules.md): See who must approve which change. The rules come from the methodology pack.
- [Privacy and erasure](https://implementer.ifs-erp.com/help/en/privacy.md): Ask to erase a person’s data, and approve such requests. Records that the law requires stay, in anonymous form.
- [Methodology pack upgrade](https://implementer.ifs-erp.com/help/en/pack-upgrade.md): Move the project to a newer version of the methodology pack. See what changes before you confirm.
- [Notifications](https://implementer.ifs-erp.com/help/en/notifications.md): Choose how you are told about approvals, gates and other events. Project administrators set the channels of the project.
- [My profile](https://implementer.ifs-erp.com/help/en/profile.md): Connect your Microsoft 365 calendar so Implementer can find a free time for meetings, and create tokens for Excel and Power BI. Both are optional.
- [Project members](https://implementer.ifs-erp.com/help/en/members.md): Add people to the project and give each one a role. Roles decide what they can see and do.
- [API tokens](https://implementer.ifs-erp.com/help/en/api-tokens.md): Let a reporting tool read project data without a person signed in. A token only reads, and it expires.
- [New project](https://implementer.ifs-erp.com/help/en/new-project.md): Create a project and choose its kind. Only a platform administrator can do this. The kind shapes the whole project.
- [Administration](https://implementer.ifs-erp.com/help/en/admin.md): System settings for the whole installation: sign-in, storage, AI, IFS connections and the methodology packs.
- [First-time setup](https://implementer.ifs-erp.com/help/en/setup.md): Set up a new installation step by step. When done, the first admin signs in.
- [Licence](https://implementer.ifs-erp.com/help/en/admin.licence.md): The signed licence file of this installation. The app checks it offline and sends nothing anywhere.
- [Error log](https://implementer.ifs-erp.com/help/en/admin.errors.md): Server failures and errors reported by browsers. Administrators use it to find the cause of a problem and to brief support.
- [AI policy](https://implementer.ifs-erp.com/help/en/ai-policy.md): Decide which external model providers this project may use, and with which data. Without an approved policy all AI runs locally.
- [AI providers and models](https://implementer.ifs-erp.com/help/en/admin.ai.md): Register external model providers and choose the local chat and embedding models.
- [Extensions](https://implementer.ifs-erp.com/help/en/admin.extensions.md): Install services that receive a signed notice when something happens in a project that allows them.
- [Sign in](https://implementer.ifs-erp.com/help/en/login.md): Sign in with your company account. The app does not keep your password.

## Phase 1: Initiate project

- [Guide: phase 1, Initiate project](https://implementer.ifs-erp.com/help/en/stage.initiate.md): Both teams start. You set up the plan, the scope and the controls, and you close the phase at the Project initiated gate.
- [Plan and baselines](https://implementer.ifs-erp.com/help/en/plan.md): The project schedule with milestones and four baselines. A baseline is a signed copy you measure against.
- [Scope](https://implementer.ifs-erp.com/help/en/scope.md): What the project delivers and what it does not. Includes benefits, processes, data, interfaces and exclusions.
- [Organisation and RACI](https://implementer.ifs-erp.com/help/en/organisation.md): Who is on the project, what role each person plays and who is responsible for each activity.
- [Steering group](https://implementer.ifs-erp.com/help/en/steering.md): Meetings, decisions, actions and the status report. This is where the project is governed.
- [Communication plan](https://implementer.ifs-erp.com/help/en/communication.md): Who needs to hear what, how often and from whom. Includes the stakeholder list and the meeting calendar.
- [Environments](https://implementer.ifs-erp.com/help/en/environments.md): PROD, TEST, training and other IFS environments. See the version of each and what is planned next.

## Phase 2: Confirm prototype

- [Guide: phase 2, Confirm prototype](https://implementer.ifs-erp.com/help/en/stage.prototype.md): You build key processes on customer sample data and confirm the solution scope. The Solution confirmed gate closes the phase.
- [CRIM log](https://implementer.ifs-erp.com/help/en/register.crim.md): CRIM stands for configuration, report, integration and modification. Every tailored object gets a line here, so its update and test cost stays visible.
- [Interface register](https://implementer.ifs-erp.com/help/en/register.interface.md): List every link between IFS and another system. Decide what happens to the old system at go-live.
- [Book of Rules](https://implementer.ifs-erp.com/help/en/bor.md): The agreed business rules for each process area, with their exceptions and open questions. The process owner signs it.

## Phase 3: Establish solution

- [Guide: phase 3, Establish solution](https://implementer.ifs-erp.com/help/en/stage.solution.md): You finish design, build and tests. The phase ends with acceptance testing and the Solution established gate.
- [Defects](https://implementer.ifs-erp.com/help/en/register.defect.md): A defect is a fault found in testing. Log it, rate its severity and follow it until it is fixed and checked.
- [Data migration](https://implementer.ifs-erp.com/help/en/migration.md): Plan what data moves, clean it, and load it in cycles until the customer accepts it.
- [Specifications](https://implementer.ifs-erp.com/help/en/specs.md): Write down what you will build before you build it. One kind covers links and changes. The other covers settings and reports.
- [Testing](https://implementer.ifs-erp.com/help/en/testing.md): Test cycles, scenarios, runs and defects. Ends with the acceptance test (SAT) and the operational readiness test (ORT).
- [Step-by-step guides](https://implementer.ifs-erp.com/help/en/guides.md): Short guides that show users how to do a task in IFS Cloud. Used for tests, training and support.

## Phase 4: Implement solution

- [Guide: phase 4, Implement solution](https://implementer.ifs-erp.com/help/en/stage.implement.md): You train users, rehearse the cutover and pass the operational readiness test. The Go live authorised gate closes the phase.
- [Training](https://implementer.ifs-erp.com/help/en/training.md): Who needs training, which courses, and when. Attendance is personal data, so only a few roles see it.
- [Cutover](https://implementer.ifs-erp.com/help/en/cutover.md): The plan to move from the old system to IFS Cloud. You rehearse it with full data. Durations come from the rehearsals.
- [Go-live readiness](https://implementer.ifs-erp.com/help/en/go-live.md): The paper the steering group reads before it authorises go-live. It scores the readiness criteria and ends in one decision.

## Phase 5: Go live

- [Guide: phase 5, Go live](https://implementer.ifs-erp.com/help/en/stage.golive.md): You run the cutover, retire the old system, hand over to support and close the project. The Go live complete gate closes the phase.
- [Handover to support](https://implementer.ifs-erp.com/help/en/handover.md): Give the support team everything it needs. They check the pack and accept it.
- [Project closure](https://implementer.ifs-erp.com/help/en/closure.md): Close the project cleanly. Give every open item an owner outside the project and record what you learned.

## Phase 6: Maintained after go-live

- [Guide: after go-live, keep the system current](https://implementer.ifs-erp.com/help/en/stage.maintain.md): IFS Cloud updates arrive on a regular rhythm. You plan each one so that tailored objects and interfaces keep working.
- [Updates (Evergreen)](https://implementer.ifs-erp.com/help/en/updates.md): IFS Cloud updates arrive on a regular rhythm. Plan each update so that your tailored objects keep working.

## Every stage

- [How an IFS Cloud project runs](https://implementer.ifs-erp.com/help/en/method.md): 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.
- [New project, rollout or BAU](https://implementer.ifs-erp.com/help/en/modes.md): The app supports three kinds of work. You choose one when you create the project. The kind decides which phases and screens you see.
- [Roles and who may do what](https://implementer.ifs-erp.com/help/en/roles.md): Your role decides what you can see and do. Some actions need a second person. Nobody approves their own work.
- [Dashboard](https://implementer.ifs-erp.com/help/en/dashboard.md): Your overview of the project. See where you are, what is late and what waits for you.
- [Registers and boards](https://implementer.ifs-erp.com/help/en/register.md): A register is the single list of one kind of object, such as risks or change requests. Show it as a board or as a list.
- [Object panel](https://implementer.ifs-erp.com/help/en/object.md): The side panel for one item. It has fields, links, attachments and the full history.
- [Risk register](https://implementer.ifs-erp.com/help/en/register.risk.md): Track what could go wrong, how likely it is and what you will do about it.
- [Issue log](https://implementer.ifs-erp.com/help/en/register.issue.md): An issue is a problem that exists now. Log it, give it an owner and close it with a result.
- [Change requests](https://implementer.ifs-erp.com/help/en/register.change_request.md): Use a change request when scope, date, budget or a modification must change. No work starts before approval.
- [Approvals inbox](https://implementer.ifs-erp.com/help/en/approvals.md): All decisions that wait for you, in one list. Approve, reject or send back with a reason.
- [Delegations](https://implementer.ifs-erp.com/help/en/approvals.delegations.md): Hand your approvals to someone else for a set time, for example during leave.
- [Qualification gates](https://implementer.ifs-erp.com/help/en/gates.md): A gate closes a phase. The team shows evidence for each checklist item. The steering group then approves, approves with conditions, or rejects.
- [Documents](https://implementer.ifs-erp.com/help/en/documents.md): IDK documents built from the registers. You do not type tables into them. You change the register, and the document follows.
- [Content search](https://implementer.ifs-erp.com/help/en/search.md): Find items by what their fields say, not only by their key. You see only the types you may read.
- [Audit log](https://implementer.ifs-erp.com/help/en/audit.md): Every change to project data, with who, when and where it came from.
- [Scheduling meetings](https://implementer.ifs-erp.com/help/en/scheduling.md): Find a time that suits the participants, for example for a user acceptance test session. The server proposes times and a person confirms one.
- [Import a register from CSV](https://implementer.ifs-erp.com/help/en/import.md): Load a list you already keep in Excel into a register. Nothing is saved until you confirm the last step.
- [Export project data](https://implementer.ifs-erp.com/help/en/export.md): Download the registers of the project as one zip archive. Excel and other tools can open it. Use it for your own analysis or for an exit.
- [Transport register](https://implementer.ifs-erp.com/help/en/register.transport.md): A transport is a package of IFS configuration that moves between environments. The app records it and checks the rules. It never applies anything to IFS.
- [Reports](https://implementer.ifs-erp.com/help/en/reports.md): Run ready-made reports or build your own. A report reads the registers, so it is always up to date.
- [Calendar](https://implementer.ifs-erp.com/help/en/calendar.md): Dated items of the project, day by day. Open an item to change its date in its own register.
- [Ask the project](https://implementer.ifs-erp.com/help/en/chat.md): Ask questions in plain words. Answers use only the documents and registers you may see, with sources.

Last updated: 13 November 2026
