--- title: "IFS Cloud Implementation Documentation Kit: 24 Templates" date: 2026-09-21 description: "24 ready-to-use IFS Cloud implementation templates grouped by the five phases of the IFS implementation methodology, with owner and gate for each." author: "Dariusz Mysliwiec" intro_image: "https://www.ifs-erp.com/images/implementation_docs_kit.webp" fulltext_image: "https://www.ifs-erp.com/images/implementation_docs_kit.webp" categories: - name: "Implementation Docs" url: "https://www.ifs-erp.com/implementation-docs.md" --- # IFS Cloud Implementation Documentation Kit: 24 Templates ![IFS Cloud Implementation Documentation Kit: 24 Templates](https://www.ifs-erp.com/images/implementation_docs_kit.webp) ## Contents - [How the kit is organised](#how-the-kit-is-organised) - [Index by phase](#index-by-phase) - [Minimum set if time is short](#minimum-set-if-time-is-short) - [Where read-only integrations fit](#where-read-only-integrations-fit) - [Related reading](#related-reading) - [Before you hand a filled template to anyone](#before-you-hand-a-filled-template-to-anyone) 24 ready-to-use templates for an IFS Cloud implementation project, grouped by the five phases of the IFS implementation methodology. Copy a file, replace the bracketed fields, remove the rows marked `Example:`, and the document is ready for review. Independent templates aligned with the IFS implementation methodology. Not official IFS documents. IFS is a registered trademark of IFS AB. ## How the kit is organised Every template has the same frame and an ID (`IDK-01` to `IDK-24`) used for cross-references: a front matter block (phase, owner, approver, the qualification gate that needs it), a short "How to use this template", a document control table, the body, and an approval block. Fields in `[square brackets]` are project-specific. The kit contains no project figures on purpose: durations, thresholds, cycle counts and effort are decisions of your project, so they are fill-in fields. ## Index by phase | # | Template | Phase | Owner | Needed at gate | | --- | --- | --- | --- | --- | | 01 | [Project Management Plan](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/01-project-management-plan) | Initiate Project | Supplier project manager (with customer project manager support) | Project Initiated | | 02 | [Project Scope Statement](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/02-project-scope-statement) | Initiate Project | Supplier project manager (with customer project manager support) | Project Initiated | | 03 | [Project Organisation and RACI](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/03-project-organisation-and-raci) | Initiate Project | Customer project manager and supplier project manager (joint) | Project Initiated | | 04 | [Risk Register and Issue Log](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/04-risk-register-and-issue-log) | All phases | Customer project manager (with supplier project manager support) | Project Initiated (register and process in place); reviewed at every later gate | | 05 | [Communication Plan and Stakeholder Analysis](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/05-communication-plan-and-stakeholder-analysis) | Initiate Project | Customer project manager (with supplier project manager support) | Project Initiated | | 06 | [Steering Group Pack](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/06-steering-group-pack) | All phases | Customer project manager and supplier project manager (joint) | Project Initiated (terms of reference approved); used at every gate for the status report and gate decision | | 07 | [Change Request and Change Control Procedure](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/07-change-request-and-change-control-procedure) | All phases | Customer project manager and supplier project manager (joint) | Project Initiated (procedure approved); applied until Go Live Complete | | 08 | [Qualification Gate Checklists](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/08-qualification-gate-checklists) | All phases | Customer project manager and supplier project manager (joint) | All five gates (Project Initiated, Solution Confirmed, Solution Established, Go Live Authorised, Go Live Complete) | | 09 | [Book of Rules](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/09-book-of-rules) | Confirm Prototype (revised during Establish Solution) | Customer functional team lead, supported by the application consultant | Solution Confirmed | | 10 | [CRIM Log](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/10-crim-log) | Confirm Prototype (needs identified), Establish Solution (specified, built, tested) | Supplier project manager, with the technical solution manager | Solution Confirmed (needs identified), Solution Established (objects delivered) | | 11 | [Functional Specification for an Integration or Modification](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/11-functional-specification-integration-modification) | Establish Solution | Application consultant, with the technical solution manager | Solution Established | | 12 | [Configuration and Report Specification](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/12-configuration-and-report-specification) | Establish Solution | Application consultant or customer technical analyst | Solution Established | | 13 | [Interface Register](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/13-interface-register) | Confirm Prototype (must exist before build starts), maintained through Go Live and into support | Customer technical analyst for integrations, supported by the technical solution manager | Solution Confirmed | | 14 | [Data Migration Strategy](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/14-data-migration-strategy) | Initiate Project | Customer project manager, supported by the supplier project manager | Project Initiated | | 15 | [Data Migration Plan and Customer Data Readiness Checklist](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/15-data-migration-plan-and-readiness-checklist) | Confirm Prototype (plan established), maintained through Establish Solution and Implement Solution | Customer data migration lead, supported by the data migration consultant | Solution Confirmed | | 16 | [Step-by-Step Guide (End-User Work Instruction)](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/16-step-by-step-guide) | Establish Solution (drafted in solution workshops, final at SAT), revised in Implement Solution after ORT | Customer functional team member or expert user for the process | Solution Established | | 17 | [Test Strategy](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/17-test-strategy) | Initiate Project (drafted), maintained through Implement Solution | Customer test lead | Project Initiated | | 18 | [SAT and ORT Test Script and Sign-off](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/18-sat-ort-test-script-and-signoff) | Establish Solution (SAT), Implement Solution (ORT) | Customer test lead | Solution Established (SAT), Go Live Authorised (ORT) | | 19 | [Training Plan and Course Description](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/19-training-plan-and-course-description) | Establish Solution (prepared), Implement Solution (delivered) | Customer training lead | Solution Established (plan approved), Go Live Authorised (training delivered) | | 20 | [Cutover Plan, Checklist and Contingency](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/20-cutover-plan-checklist-and-contingency) | Implement Solution (prepared and rehearsed), Go Live (executed) | Cutover manager | Go Live Authorised | | 21 | [Go-Live Readiness Decision](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/21-go-live-readiness-decision) | Implement Solution | Customer project manager | Go Live Authorised | | 22 | [Handover to Support](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/22-handover-to-support) | Go Live | Supplier project manager | Go Live Complete | | 23 | [Update Strategy (Evergreen)](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/23-update-strategy-evergreen) | Initiate Project (first decision), maintained after Go Live | Customer system owner | Project Initiated (cadence decided), Go Live Complete (operating model confirmed) | | 24 | [Project Closure and Lessons Learned](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/24-project-closure-and-lessons-learned) | Go Live | Customer project manager | Go Live Complete | ## Minimum set if time is short If the project is already running and nothing is written down, start with five: [IDK-08](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/08-qualification-gate-checklists) (gate checklists, to see what is missing), [IDK-04](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/04-risk-register-and-issue-log) (risks and issues), [IDK-07](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/07-change-request-and-change-control-procedure) (change control), [IDK-13](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/13-interface-register) (interface register) and [IDK-10](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/10-crim-log) (CRIM log). These five stop the most expensive surprises: unapproved scope, untracked modifications and interfaces nobody owns. ## Where read-only integrations fit An external service that only reads IFS Cloud through OData and installs nothing in the tenant creates no CRIM object to specify in template [IDK-11](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/11-functional-specification-integration-modification) or [IDK-12](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/12-configuration-and-report-specification). It still holds credentials against production, so it is listed in the Interface Register ([IDK-13](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/13-interface-register)), in the third-party integrations section of Handover to Support ([IDK-22](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/22-handover-to-support)), and in the projections check of the Update Strategy ([IDK-23](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/23-update-strategy-evergreen)). Templates [IDK-13](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/13-interface-register), [IDK-22](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/22-handover-to-support) and [IDK-23](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/23-update-strategy-evergreen) carry an example row for this case. ## Related reading - Pillar article: https://www.ifs-erp.com/en/marketplace/implementation-docs - Questions about the kit or about applying it to a running project: https://www.ifs-erp.com/en/contact ## Before you hand a filled template to anyone Rows marked `Example:` illustrate the expected level of detail. Page names, statuses and feature names in them are illustrative: confirm each against your own IFS Cloud release, then delete the `Example:` rows. Independent template aligned with the IFS implementation methodology. Not an official IFS document. IFS is a registered trademark of IFS AB.