Decommission a digital product in 2026: properly close data, contracts, links and customer expectations

The subject “Decommissioning a digital product” must lead to proof, not just deployment: the expected effect must be measurable and reversible.
Frame the “date and criteria” point, control the “export and retention” point, then decide with an explicit reference measure.

1. Key figures

These benchmarks limit the decision on a planned digital service closure; they don't take it for you. A published value describes a precise perimeter, a date and sometimes a population different from yours. Read it as a constraint to be tested, not as the promise of an automatic effect. The roles are distinct.

Because the context evolves, the budgetary limit is noted: for this subject, the first source leads to the following operational reading: “Decommissioning requires data, redirections, support, contracts and proof of shutdown. » The second reference in the table must also be compared to your perimeter and a local measurement. This distinction between external reference and local measurement protects the analysis against easy extrapolations.

2. Read the sources without overinterpretation

Without a designated owner, the hypothesis can be contradicted: a source is useful when a reader simultaneously understands what it asserts, the scope it covers, and the limit of extrapolation. The five benchmarks below are therefore reread as decision markers, never as causal promises.

For the scope “a planned closure of a digital service”, external data can only be used to decide if its scope, date, unit and limit are explained. The review should separate what the source establishes, what the team infers, and what a local test still needs to demonstrate.

Concretely, the proof sheet preserves the organism, the title, the URL, the date of consultation, the population, the unit, the method and the reservation of interpretation. It then indicates the decision that the benchmark informs and the local observation capable of contradicting this benchmark. In this file, attach this register to “date and criteria” and entrust its review to “General Management”. Data without a documentary owner ages silently; data with a revision condition remains controllable and can be cited without losing its context.

2.1. Benchmark 1

The source GOV.UK Service Manual — Retiring your service locates the terminal “1 exit plan” in the field “public digital services, transposable principles”. It provides an external reference to the diagnosis; it does not replace either a local reference measurement or the analysis of exceptions. These mistakes are costly.

2.2. Bench 2

The “4 obligations” milestone, published by GOV.UK — Choose the right tools and technology, falls within the scope of “public digital services, transposable principles”. It helps to formulate a testable hypothesis, without transforming an external value into an automatic objective. Control remains human.

2.3. Bench 3

GOV.UK — Commercial off-the-shelf products document “2 phases before engagement”. The exact range is shown in the previous table; keep it when comparing this data to your own operations, populations and periods. Nuance matters here.

2.4. Benchmark 4

GOV.UK — What each role does provides the indication “5 key roles” here. This information informs a choice; it does not, by itself, demonstrate that the same effect will appear in your context. Each step leaves a trace.

2.5. Bench 5

The NIST Reference — Cybersecurity Framework 2.0 publishes “6 Functions”. Before making a decision, check the date, the population covered and the possibility of replicating the measure locally. The discrepancy deserves an explanation.

3. Reusable citation sheet

With incomplete data, the rights of action are documented: a robust citation must be able to be reproduced without losing its author, its date, its scope or its limit. The sheet below isolates these elements and links them to a specific decision; it prevents a correct figure from becoming misleading after extraction from its context.

4. Introduction: framework the primary risk

Four questions reveal the maturity of the system: how to deal with “date and criteria”, who carries “export and retention”, where to test “redirections” and when to review “proof of stopping”? Without a response, the deployment is reduced to a declaration.

The concrete risk takes the following form: an application turned off while its links, accounts and dependencies persist. This problem cannot be corrected either by an activated option or by an additional dashboard; it requires a perimeter, a person responsible and contradictory proof.

In the presence of a third party, the changes are versioned: our position is therefore clear: the system only has value if the announced effect is observable. The comparison must relate to the situation before the change, then to the same segments after the test. Deferred cost exists.

5. Actors and responsibilities

This distribution avoids confusing execution and responsibility. The first operational responsibility falls to the “General Management” function; the “Professionals” function provides separate control. The decision is only defensible if each actor knows what it measures, what it authorizes and what it takes back when the accepted limit is crossed. This border matters.

6. Definition: planned digital service closure

In this guide, the scope “a planned closure of a digital service” combines the points “date and criteria”, “export and retention”, “redirections” and “proof of shutdown”. The goal is to have the service retired without loss of data, trust or obligation; the decision is based on the coverage of users, data and integrations by the release plan.

After production, the fallback procedure is accessible: the definition is therefore operational: it names the components, the desired effect, the indicator and the limit. A reader can quote it without having to reconstruct the meaning from the rest of the page. The calendar serves as proof.

7. Why the subject becomes structuring

As long as doubt remains, the calculation unit does not change: the sources converge on three terminals: 1 exit plan, 4 obligations and 2 phases before commitment. They do not describe a universal average; they specify thresholds, obligations or operating conditions. In the present case, the third source leads to the following operational reading: “The choice of tool must follow the understanding of the problem and the testing of options. »

This reading transforms the figures into decision questions: what perimeter do they cover, what uncertainty remains and who can act when the measurement goes beyond the accepted threshold? On a planned closure of a digital service, this responsibility determines the desired effect. The outing is prepared early.

8. Compare four levels of engagement

Regarding a planned digital service closure, the comparison does not point to a universal winner. It makes visible the cost of an absent proof, an overly simple driver or a premature extension. The right level depends on the criticality of the flow, the quality of “export and retention” and the concrete possibility of resuming “proof of shutdown”. This evidence is local.

9. Recommended methodology: seven verifiable steps

Applied to a planned digital service closure, the following method is good public and operational practice. It is not presented as a proprietary method of Logiks: its value comes from the order of controls and the possibility, for a third party, to verify each deliverable.

9.1. Formulating the decision

To move forward without hiding the deferred cost, you must describe the expected result and link it to “date and criteria”. Compare before and after on the really open decision and the value which justifies it, then have a note from cadrage which names the decision, the limit and the person responsible reread by an actor who did not design the test.

9.2. Measuring the starting point

Between two reviews, operations can resume: expected action: observe the decision indicator before any modification. Start on a perimeter where the team can still get back. The expected proof concerns the initial situation and its variations between segments; record it in an initial measurement, dated and broken down by useful segment.

9.3. Trace Critical Path

The work is first to connect “export and retention” to the relevant data, teams and dependencies. Do not use an ideal demonstration or an overall average: observe the exceptions encountered by the teams using the system. The useful deliverable is a map of exceptions, dependencies and owners.

9.4. Laying down safeguards

At this stage, “redirects” must be framed by limits, rights and a recovery procedure. Involve the person who handles the exceptions, then confront the result with limitations, rights of action, and the possibility of going back. You must be able to provide a control matrix that makes cost and reversibility visible to a decision-maker absent from the project.

9.5. Test the difficult case

Here, the action consists of experiencing “proof of stopping” in a representative scenario, then in a degraded scenario. Run the check on a normal case and a degraded case, keeping the nominal behavior, the caused failure and the quality of the recovery as criteria. The concrete output takes the form of an account of the nominal scenario, failure and human recovery.

9.6. Build evidence

When a dependency changes, the date of measurement is recorded: this step transforms the intention into control: comparing result, errors, interventions and full cost at the starting point. Measure what actually changes in the gap between the initial promise and the recorded facts, including human replays. Document everything in a file of logs, deviations and decisions that can be read by a third party.

9.7. Decide and Review

If the metric diverges, the full cost appears: to move forward without hiding the deferred cost, you must assign the review and track the metric at an explicit cadence. Compare before and after on the threshold that triggers a correction, an extension or a stop, then have a review rule with correction and stop thresholds reread by an actor who did not design the test.

10. Logik tips: proof, mastery and reversibility

Our priority is the following risk: an application turned off while its links, accounts and dependencies persist. Start where this fragility already produces an expectation, a loss, or a contested decision; the prestigious perimeter can wait.

Depending on the assumption made, the threshold has an owner: keep the reference measurement at the level where a team can act. A quarterly average does not replace an observation by course, by cohort or by type of exception; the marker must remain actionable.

Treat “date and criteria” as a documented decision. A manager, a hypothesis, a limit and a review date are better than an adjustment whose origin no one knows.

Test "redirects" with "proof stop" and then with a degraded resume. The test should reveal operation and operating cost, not just confirm that the demonstration holds up.

Only extend the system if the observed facts support the desired effect and if “export and retention” remains controllable by a person outside the project.

In this file, the recommendations express a sequence judgment: make the risk observable, test the hypothesis relating to “redirections”, then commit the resources. Sophistication comes after the demonstration of the announced effect; it does not replace it. Reversibility decides.

11. Decision grid

The grid does not automatically produce arbitrage on a scheduled digital service shutdown. On the other hand, it forces the teams to show their hypotheses on “date and criteria”, their thresholds and their responsibilities; a disagreement is then explicit and can be resolved. The test must stand.

12. Frequent errors

12.1. Consolidate activation and result

Activating “date and criteria” does not prove that the expected effect is achieved. This error shifts the debate towards the tool while the decision concerns an observable change.

12.2. Optimize the first available indicator

Faced with a deviation, local verification can be reproduced: a convenient proxy can progress while the decisive measure deteriorates. Link each signal to a decision and a guardrail.

12.3. Ignore exceptions

On the critical path, exceptions are logged: the nominal path often hides the fragility described above. Test a borderline case, a failure and how the team regains control.

12.4. Leave an addiction without an owner

When “export and retention” is everyone’s responsibility, no one decides the incident or the cost. Assign the decision before deployment.

12.5. Present risk as a formality

Documenting “redirects” without correcting the system produces facade compliance. The record must show a check performed and its result.

12.6. Extend without exit rule

If “proof of stopping” does not allow a decision to be made, the pilot continues by inertia. Set continuation, correction and termination thresholds in advance.

13. Action Plan 30 / 60 / 90 days

13.1. Days 1 to 30: establishing the starting point

• describe the decision, the scope and the person responsible for it;
• record the initial value of the indicator before any modification;
• inventory dependencies and their exceptions;
• write the main risk and its detection condition.

Once the baseline is established, the stopping rule is known: the first phase serves to make the disagreement visible. At thirty days, management must know the baseline measurement, the missing data and the specific case on which progress will be judged.

13.2. Days 31 to 60: testing the critical path

• implement primary control over a representative flow;
• test the recovery in a normal then degraded situation;
• record errors, human interventions, delays and costs;
• compare the observations to the initial scenario.

In current operation, the trace remains auditable: this pilot does not only seek to demonstrate that the technology works. It must establish whether the system advances the selected indicator without shifting a disproportionate burden towards the operation, users or a supplier.

13.3. Days 61 to 90: decide and organize the continuation

• consolidate the evidence and have its limitations reread;
• assign each recurring control to a named function;
• confirm the next review date and discharge procedure;
• extend only if the facts support the effect initially announced.

From the first test, the initial value remains accessible: at ninety days, the initial hypothesis must be demonstrated or refuted. Three decisions remain legitimate: extend, correct or stop the perimeter; continuing without a threshold does not constitute a fourth option.

14. FAQ

14.1. How to define a planned digital service closure?

This is a decision framework applied to a planned digital service closure. The approach links “date and criteria” to “redirections” and “proof of stopping” controls, with a reference measurement, those responsible and an exit rule.

14.2. What to start with?

On the business side, the sample remains representative: start with a real decision, a reference measurement and an already observed manifestation of the main risk. The tool comes after this cadrage.

14.3. What budget should be retained?

When the pilot is launched, the evidence remains linked to the decision: add preparation, integration, operation, control, training, incidents and exit. Compare this full cost to the expected value, not just the license or campaign price.

14.4. How long should the test last?

The test must cover a full measurement cycle and at least one exception related to "redirects". Its duration derives from this observation, not from an arbitrary standard.

14.5. When to scale?

Scale up when progress remains stable, “proof of termination” is monitored, and responsibilities, costs, and exit conditions are documented.

15. Conclusion

During the audit, the next deadline is planned: the decision is solid when a common measure links the technical, business and financial choices. The number of options activated is less important than the ability to explain discrepancies, deal with exceptions and reverse a choice that has become costly.

The pivot is simple: the “planned closure of digital service” project must no longer be a project to deliver, but a capacity to govern to produce the announced effect. This benchmark does not decide.

16. Main sources

• GOV.UK Service Manual — Retiring your service — updated 26 August 2025, consulted 11 July 2026 — public digital services, transposable principles.
• GOV.UK — Choose the right tools and technology — consulted on 11 July 2026 — public digital services, transposable principles.
• GOV.UK — Commercial off-the-shelf products — updated on July 4 2025 — purchasing digital products and services.
• GOV.UK — What each role does — accessed on 11 July 2026 — digital product and services teams.
• NIST—Cybersecurity Framework 2.0 — 26 February 2024 — organizations of all sizes.