---
title: "Go-Live Readiness Decision Template (IDK-21)"
date: 2026-09-21
description: "Ready-to-use template IDK-21: Go-Live Readiness Decision for IFS Cloud implementation projects, aligned with the IFS implementation methodology."
author: "Dariusz Mysliwiec"
categories:
  - name: "Implementation docs kit"
    url: "https://www.ifs-erp.com/implementation-docs-kit.md"
---

# Go-Live Readiness Decision Template (IDK-21)

Template IDK-21, version 1.0. Phase: Implement Solution.

 ## How to use this template

 
- This is the paper the steering group reads before it authorises go-live. Send it in advance, not on the day.
- Every criterion needs evidence that someone can open and read: a signed report, a log, a list. "We believe so" is not evidence.
- Area owners fill in their own status. The project managers challenge it. The steering group decides.
- Rows marked `Example:` show the expected level of detail. Delete them from your working copy.
- Three outcomes are possible: go, go with conditions, no-go. A no-go taken on evidence is a sound decision. Record it with the same care as a go.

 | Field | Value |
| --- | --- |
| Template ID | IDK-21 |
| Phase | Implement Solution |
| Owner | Customer project manager |
| Approver | Steering group |
| Qualification gate | Go Live Authorised |
| Version | 1.0 |

 ## Contents

 
- [Document control](#document-control)
- [1. Summary for the steering group](#1-summary-for-the-steering-group)
- [2. Readiness criteria by area](#2-readiness-criteria-by-area)
- [3. Open items](#3-open-items)
- [4. Timing considerations](#4-timing-considerations)
- [5. Decision record](#5-decision-record)
- [Approval](#approval)

 ## Document control

 | Field | Value |
| --- | --- |
| Project | [Project name] |
| Customer | [Legal entity] |
| Go-live scope | [Companies, sites, processes] |
| Proposed go-live date | [YYYY-MM-DD] |
| Decision meeting date | [YYYY-MM-DD] |
| Document owner | [Name, customer project manager] |
| Status | [Draft / Submitted / Decided] |
| Version | [x.y] |
| Storage location | [Link] |
| Related documents | [SAT and ORT sign-off (template [IDK-18](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/18-sat-ort-test-script-and-signoff)), training record (template [IDK-19](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/19-training-plan-and-course-description)), cutover plan (template [IDK-20](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/20-cutover-plan-checklist-and-contingency)), handover to support (template [IDK-22](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/22-handover-to-support))] |

 | Version | Date | Author | Change |
| --- | --- | --- | --- |
| [0.1] | [YYYY-MM-DD] | [name] | [First draft] |

 ## 1. Summary for the steering group

 | Item | Value |
| --- | --- |
| Recommendation of the project managers | [Go / Go with conditions / No-go] |
| Areas ready | [list] |
| Areas ready with conditions | [list] |
| Areas not ready | [list] |
| Main remaining risk | [One sentence] |
| Decision needed by | [date, because: reason] |

 Status legend used below: Ready / Ready with conditions / Not ready / Not applicable.

 ## 2. Readiness criteria by area

 
### 2.1 Solution

 | # | Criterion | Evidence | Owner | Status |
| --- | --- | --- | --- | --- |
| S1 | SAT completed, documented and approved by the steering group | [Link to SAT completion report] | [Test lead] |   |
| S2 | All CRIM objects delivered to production and tested | [CRIM log with status] | [Supplier PM] |   |
| S3 | No open defect that blocks deployment | [Defect log filter] | [Test lead] |   |
| S4 | Production functional and technical configuration complete and matches the accepted baseline | [Configuration checklist] | [Solution architect] |   |
| S5 | Load test signed off, if required by the test strategy | [Report or "Not required" decision] | [Customer IT lead] |   |
| Example: S2 | Example: Custom fields on purchase order line, supplier order report layout and bank payment file format are in production at the version tested in SAT | Example: Handover to Support (template [IDK-22](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/22-handover-to-support)), section 6, production version per CRIM object | Example: Supplier PM | Example: Ready |

 
### 2.2 Data

 | # | Criterion | Evidence | Owner | Status |
| --- | --- | --- | --- | --- |
| D1 | Migration routines validated with full volumes | [Rehearsal log] | [Data migration lead] |   |
| D2 | Each data set validated and signed by its data owner in the latest load | [Validation sign-offs] | [Data owners] |   |
| D3 | Cleansing of legacy data complete or remaining work accepted | [Cleansing tracker] | [Data owners] |   |
| D4 | Reconciliation method for balances agreed with finance | [Reconciliation procedure] | [Finance lead] |   |
| D5 | Manual data entry tasks planned with owners and time | [Cutover checklist] | [Cutover manager] |   |

 
### 2.3 Users and training

 | # | Criterion | Evidence | Owner | Status |
| --- | --- | --- | --- | --- |
| U1 | ORT completed; expert users signed the confirmation statement | [Link to ORT statement] | [Test lead] |   |
| U2 | End-user training delivered; absentees have a catch-up date before go-live | [Attendance record] | [Training lead] |   |
| U3 | Step-by-step guides final and available to all users | [Guide library link] | [Training lead] |   |
| U4 | Expert users named per site and area, and known to users | [Expert user list] | [Customer PM] |   |

 
### 2.4 Security

 | # | Criterion | Evidence | Owner | Status |
| --- | --- | --- | --- | --- |
| X1 | Roles and permission sets built and tested with role-based logins | [Role matrix, SAT evidence] | [Security lead] |   |
| X2 | Users attached to roles in production | [User and permission set export] | [Security lead] |   |
| X3 | Segregation of duties conflicts reviewed and accepted | [Review record] | [Finance lead, auditor contact] |   |
| X4 | Project and consultant accounts reviewed; elevated access has an end date | [Account list] | [Customer IT lead] |   |
| X5 | Integration and service accounts hold only the access they need | [Account list with permission sets] | [Integration lead] |   |

 
### 2.5 Infrastructure and environments

 | # | Criterion | Evidence | Owner | Status |
| --- | --- | --- | --- | --- |
| I1 | Production environment at the agreed release and service update level | [Environment record] | [Customer IT lead] |   |
| I2 | Network access, single sign-on and identity provider tested from every site | [Test record per site] | [Customer IT lead] |   |
| I3 | Printers, label printers, scanners and mobile devices tested at each site | [Device checklist] | [Site leads] |   |
| I4 | Backup before release to users arranged and confirmed | [Cutover plan section 11] | [Customer IT lead] |   |
| I5 | Update freeze agreed around go-live | [Update strategy (template [IDK-23](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/23-update-strategy-evergreen))] | [Customer IT lead] |   |

 
### 2.6 Integrations

 | # | Criterion | Evidence | Owner | Status |
| --- | --- | --- | --- | --- |
| N1 | Every interface in the interface register tested end to end with the external party | [Interface register with test status] | [Integration lead] |   |
| N2 | Production endpoints, certificates and credentials in place and verified | [Checklist] | [Integration lead] |   |
| N3 | Monitoring and error handling for each interface has a named owner | [Interface register] | [Integration lead] |   |
| N4 | Legacy interfaces to be stopped are listed in the cutover checklist | [Cutover checklist] | [Cutover manager] |   |
| Example: N1 | Example: Bank payment file accepted by the bank in its test channel; supplier order output received and confirmed by the pilot suppliers | Example: Interface register, column "External confirmation" | Example: Integration lead | Example: Ready with conditions |

 
### 2.7 Cutover

 | # | Criterion | Evidence | Owner | Status |
| --- | --- | --- | --- | --- |
| C1 | Cutover plan and checklist approved | [Link] | [Cutover manager] |   |
| C2 | Full-volume rehearsal completed; durations fit the available window | [Rehearsal log] | [Cutover manager] |   |
| C3 | Contingency plan approved; point of no return and decision maker named | [Cutover plan section 9] | [Cutover manager] |   |
| C4 | Cutover team confirmed available, including backups | [Cutover organisation table] | [Both PMs] |   |
| C5 | Communications to users, business, suppliers and customers scheduled | [Cutover plan section 6] | [Customer PM] |   |

 
### 2.8 Support

 | # | Criterion | Evidence | Owner | Status |
| --- | --- | --- | --- | --- |
| P1 | Go-live support resourced on site for the agreed period | [Resource plan] | [Supplier PM] |   |
| P2 | Issue logging and triage process for the go-live period agreed | [Cutover plan section 8] | [Customer PM] |   |
| P3 | Service desk trained in basic administration | [Training record] | [Customer IT lead] |   |
| P4 | Handover to support scheduled | [Template [IDK-22](https://www.ifs-erp.com/en/marketplace/implementation-docs-kit/22-handover-to-support), planned date] | [Supplier PM] |   |

 
### 2.9 Business readiness

 | # | Criterion | Evidence | Owner | Status |
| --- | --- | --- | --- | --- |
| B1 | Line managers confirm their teams are staffed for go-live and the period after | [Confirmations] | [Business leads] |   |
| B2 | Changed policies and procedures published | [Procedure list] | [Change lead] |   |
| B3 | Organisation changes linked to the new processes in effect | [Change plan] | [Change lead] |   |
| B4 | Manual procedures for the freeze period known to the affected teams | [Cutover plan section 2] | [Business leads] |   |
| B5 | Sponsor and steering group members visible to the business during go-live | [Communication plan] | [Sponsor] |   |

 ## 3. Open items

 | # | Area | Item | Impact if not closed | Owner | Due | Needed before go-live |
| --- | --- | --- | --- | --- | --- | --- |
| [n] | [area] | [text] | [text] | [name] | [YYYY-MM-DD] | [Yes / No] |
| Example: 4 | Example: Integrations | Example: One pilot supplier has not confirmed receipt of the new order format | Example: Orders to this supplier sent manually by email until confirmed | Example: Procurement manager | [YYYY-MM-DD] | Example: No, workaround accepted |

 ## 4. Timing considerations

 | Consideration | Assessment | Conclusion |
| --- | --- | --- |
| Business peaks | [Seasonal peaks, campaigns, large deliveries around the proposed date] | [OK / Conflict: text] |
| Holidays and absences | [Public holidays per country, school holidays, planned absence of key people on both sides] | [OK / Conflict: text] |
| Financial period | [Period or year end, closing activities, opening balances, audit dates] | [OK / Conflict: text] |
| External parties | [Bank, authority or partner deadlines; supplier and customer shutdowns] | [OK / Conflict: text] |
| Update calendar | [Planned service or release update near go-live] | [OK / Conflict: text] |
| Competing projects | [Other changes landing on the same users] | [OK / Conflict: text] |
| Fallback date | [Next possible date if this one is missed, and what it costs] | [YYYY-MM-DD] |

 ## 5. Decision record

 | Field | Value |
| --- | --- |
| Meeting date | [YYYY-MM-DD] |
| Present | [names, roles] |
| Papers sent in advance on | [YYYY-MM-DD] |
| Decision | [Go / Go with conditions / No-go] |
| Go-live date confirmed | [YYYY-MM-DD] |
| Reason for the decision | [text] |

 Conditions (for "go with conditions"):

 | # | Condition | Owner | Must be met by | Verified by | If not met |
| --- | --- | --- | --- | --- | --- |
| [n] | [text] | [name] | [date, time] | [name] | [Go-live is postponed / Escalate to: name] |

 For a no-go:

 | Field | Value |
| --- | --- |
| Criteria not met | [IDs from section 2] |
| Actions to reach readiness | [text, owners] |
| Next decision date | [YYYY-MM-DD] |
| Communication of the postponement | [Who informs whom, by when] |

 ## Approval

 | Role | Name | Decision | Date | Signature |
| --- | --- | --- | --- | --- |
| Customer project manager (owner) | [name] | [Submitted] | [YYYY-MM-DD] |   |
| Supplier project manager | [name] | [Recommends go / go with conditions / no-go] | [YYYY-MM-DD] |   |
| Project sponsor | [name] | [Go / Go with conditions / No-go] | [YYYY-MM-DD] |   |
| Steering group chair | [name] | [Go / Go with conditions / No-go] | [YYYY-MM-DD] |   |

 Independent template aligned with the IFS implementation methodology. Not an official IFS document. IFS is a registered trademark of IFS AB.

 Independent template aligned with the IFS implementation methodology. Not an official IFS document. IFS is a registered trademark of IFS AB.