Retire an application when its service can continue
Application rationalisation is often reduced to finding unused licences and cancelling subscriptions. Usage figures can provide a signal but cannot settle the decision. A rarely opened application may produce an essential annual report. A heavily used tool may merely compensate for poor data flow. The relevant object is the business service, including contracts, interfaces, data and its ability to function after closure.
This retrospective on 2023 was written in 2026. All applications, amounts and volumes below are fictional teaching examples, not CYTIZEN engagements. The method supports distinct choices: retain, improve, replace, consolidate uses or retire. It does not promise a universal savings percentage. Retirement must rest on continuity and understood obligations rather than a desire to reduce inventory rows.
The apparently inactive application
A fictional group has three commercial tools. One serves teams daily. A second has few logins but transfers billing data nightly. A third holds historic contracts and an export function used during audits. Login counts make the last two appear redundant. Task analysis reveals distinct dependencies. First establish which functions must survive and where they will run.
The inventory records business and technical owners, active users, employed functions, interfaces, data categories, contracts and costs. Product names and servers are insufficient: one application may support multiple journeys. Connect each tool to the point in the process where it matters. Finance confirms renewals; procurement checks notice conditions. A missed cancellation date may turn an announced saving into another year of expenditure.
A decision brief with visible unknowns
| Fictional application | Use and dependency | Contract and data | Proposed decision |
|---|---|---|---|
| Sales A | Daily entry; opportunity source | November renewal; active records | Retain; simplify duplicate fields |
| Relay B | Few logins; nightly billing feed | Three-month notice; transit data | Retire after replacement and reconciliation |
| Archive C | Rare searches; contractual evidence | Export untested; retention rules to establish | Migrate archive and provide controlled consultation |
Keep each decision open while an unknown could reverse it. For Relay B, test reconciliation between transmitted data and received invoices. For Archive C, demonstrate retrieval of a contract with its attachments from the export. A composite value score cannot replace these proofs. Scores can rank candidates; authorising retirement requires evidence matching the critical function.
Understand usage at task level
Purchased accounts, activated accounts and people completing useful work are different measures. Separate automatic logins, technical accounts and emergency access from human activity. Observation must cover relevant cycles: month-end, seasonal peaks, annual obligations or audits. Inactivity over a short interval does not prove absence of need. Ask staff about parallel tools used when the application no longer supports their work.
The business owner observes a complete case: input, processing, decision, output and recipient. Identify what can disappear, move or improve. Copying every feature into a replacement preserves unnecessary rules. Conversely, two tools showing customer lists may differ in permissions, evidence, pricing or exceptions. Compare delivered results rather than screen layouts.
Include the transition cost
Net recurring annual savings equal genuinely avoidable old-service costs minus additional target-service, archiving and operating costs. Simple payback equals transition cost divided by positive net annual savings. In a fictional example, 72,000 euros avoided minus 22,000 euros in new costs gives 50,000 euros annually. An 80,000-euro transition then has a simple payback of 1.6 years. This calculation does not by itself value risk or service quality.
Committed, unrecoverable costs do not become savings when an application closes. Released staff time is not automatically a cash reduction; it may be capacity for other work. Include parallel operation, testing, training, reinforced support and extraction. Finance distinguishes removed spending, deferred costs and capacity benefits. Moving a budget line to another team is not a saving.
Prepare the exit before cancellation
A retirement plan needs four proofs: essential functionality works elsewhere, necessary data remains usable, interfaces are replaced or removed with recipients' agreement, and the contract permits the intended exit. Assign observable tests. The business completes a task on the target. IT reconciles feed volumes and errors. Data owners check readability and access. Procurement confirms dates and exit costs against contractual documents.
Do not migrate every file indiscriminately. Separate active data, evidence requiring retention, information without a continuing justification and records subject to specific duties. Qualified owners validate retention periods and arrangements. An archive must be retrievable, intelligible and protected; an unreadable export is not continuity. Backups and residual copies also need coherent treatment. This article supplies no universal statutory retention period.
Close in controllable steps
Stopping new entries, moving to read-only access, removing accounts and closing the service can make transition observable. These stages are not mandatory everywhere. For fictional Relay B, reconcile old and new feeds over two financial closes. Explain discrepancies rather than averaging them away. Preserve a recovery procedure until reliability criteria are met and while contractual conditions allow it.
Suspend retirement if a critical task fails, exports lose essential information, an ownerless interface appears or a retention obligation remains unresolved. Reject a target whose operating burden persistently exceeds its expected benefit. Avoid indefinite retention based on vague caution: give each obstacle a requested proof, owner and review date. Record exceptions with their cost and closure condition.
Use the portfolio to support accountability
The portfolio forum arbitrates cross-functional use, transition resources and costly exceptions rather than reviewing every configuration. Business owners sign service continuity; technical owners sign operating conditions; relevant specialists examine data and contract obligations. None can authorise a cross-functional closure alone. The final decision identifies stopped and transferred functions, the beneficiary of savings and the people taking on new work.
After closure, reconcile forecast savings with costs actually removed at the next relevant billing event. Review incidents, restoration requests and parallel tools created by staff. Rapid recreation of a shared spreadsheet can reveal a forgotten function. Follow-up should correct the target and explain causes rather than defend the original decision. This improves the next portfolio wave.
Constraints change retirement order
Manufacturing software may depend on equipment and production qualification; replacement costs exceed licence costs. Financial services may need traceability and period-end controls, justifying an explicit temporary extension. Public services may prioritise archives and continued citizen access. Retail peaks can make a cutover imprudent. Dependencies, contract dates and transition capacity determine order.
A useful first wave combines understood uses, available owners, exportable data and verified exit conditions. Apparently lucrative cases with unknown dependencies first need investigation. Reduced complexity means clearer services, controlled costs and fewer fragile dependencies, without silently shifting work onto operational staff.
Sources and method
Official references checked in October 2026. Figures and worked decisions are teaching examples.
- Federal CIO Council, Application Rationalization Playbook, 2019: available before 2023, addressing inventory, business value and technical fit. The resource was verified through official CIO.GOV search results.
- CNIL and French interministerial archives service, Practical guide to retention periods, 2020: available before 2023, consulted in 2026 to distinguish active use from retention. It provides no single period for every portfolio.