# Before and after Implementer: documents versus registers

Without Implementer an IFS Cloud project runs on documents that know nothing about each other, and with Implementer the same facts live once in registers that compute gate verdicts, regression packs and approvals.

## What changes in daily work?

| Topic | Without | With Implementer |
| --- | --- | --- |
| Readiness | Opinions in a meeting | A gate verdict computed from evidence |
| Scope | Requests in mail and slides | One CRIM register with impact and history |
| Migration | Spreadsheet checks, surprises at month end | Reconciled by object, signed by data group |
| Testing | Evidence rebuilt at audit time | Step results and cycle verdicts on record |
| Updates | Regression invented per release | A pinned regression pack per update cycle |
| Accountability | “I think it was approved” | Approvals bound to a version, fully audited |

## What is the difference in one sentence?

Documents hold copies of facts, and registers hold the facts. In a document-based project the CRIM log, the interface list and the steering report each get edited alone and drift apart. In Implementer a CRIM object, a risk or a gate item exists once, with an owner, a state and a history, and every report reads it from there. See the eight [problems](https://implementer.ifs-erp.com/en/problems.md) behind the table.

## When are Word and Excel on SharePoint enough?

For writing a document, they are enough. Keep SharePoint for everything that is a document. The trouble starts when the same fact sits in three files and nobody can say which is current. If your project is small, short and has one owner of all files, Excel may be all you need.

## Which tools does Implementer replace?

| Tool you use | Keep it for | What Implementer adds |
| --- | --- | --- |
| Word, Excel, SharePoint | Writing and storing documents | One source of truth for risks, CRIM, interfaces, tests, gates and approvals, and generated documents as PDF or DOCX |
| Jira or Azure DevOps | Development and ticket work | Project governance those tools do not model: five gates with 61 items, the CRIM decision with the standard alternative, change requests with an approval ladder, the go-live review. There is no integration today. |
| MS Project | Detailed schedules | A read-only Gantt view of phases, milestones and cutover tasks with a baseline overlay, and baselines recorded at gate decisions |
| Your partner's tools | Delivery work | A shared record of decisions in the customer's infrastructure, with separate customer and supplier roles |

## What stays the same?

You still run the project with your own people, templates and judgment. Implementer does not decide for you. A gate decision is an approval by named people, and [AI](https://implementer.ifs-erp.com/en/ai-assistant.md) only drafts. Read the limits on [security and trust](https://implementer.ifs-erp.com/en/security-and-trust.md).

## How do the three journeys differ?

[New implementation](https://implementer.ifs-erp.com/en/new-implementation.md) uses five phases and gates. [Rollout](https://implementer.ifs-erp.com/en/rollout.md) works on the delta for the next site. [BAU and Evergreen](https://implementer.ifs-erp.com/en/bau-evergreen.md) runs updates as managed cycles. The registers are the same, so the team learns one way of working.

## How do you check it on your project?

Run a [pilot](https://implementer.ifs-erp.com/en/pilot.md) and measure on your next gate, see [pricing](https://implementer.ifs-erp.com/en/pricing.md), 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.

[Open the live demo](https://implementer.ifs-erp.com/login)
