---
mpf: '0.7'
title: What stays with you — ESFI Docs
url: https://docs.esfi.eu/our-approach/what-stays-with-you/
mpf-url: https://docs.esfi.eu/our-approach/what-stays-with-you/index.mpf
organization: European Strategy & Future Infrastructure
domain: docs.esfi.eu
lang: en
updated: '2026-11-03'
author: ESFI
provenance: human
source-hash: b5f85e66efd8c53bed08f92328ec14b9744efef621ddf70c0c4a014a691b266d
toc:
  - level: 1
    text: What stays with you
    id: what-stays-with-you
  - level: 2
    text: How a Task Force works
    id: how-a-task-force-works
  - level: 2
    text: What you keep
    id: what-you-keep
  - level: 2
    text: How you will know
    id: how-you-will-know
  - level: 2
    text: What we will not do
    id: what-we-will-not-do
  - level: 2
    text: On this page
    id: on-this-page
spec-origin: esfi.eu
content-origin: docs.esfi.eu
content-id: esfi:page:our-approach-what-stays-with-you
content-parity:
  html: true
  human-visible-source: true
  hidden-sections: false
summary: The engagement ends when the function no longer needs us.
index: true
confidence: probable
content-type: narrative
companion-footer: ESFI — civilization infrastructure · https://esfi.eu
companion-contact: mailto:hermes@esfi.eu
preferred-representation: mpf
companion-scope:
  cite: true
  summarize: true
  train: true
  index: true
  relay: true
language-variants:
  en: https://docs.esfi.eu/our-approach/what-stays-with-you/index.mpf
  fr: https://docs.esfi.eu/fr/our-approach/what-stays-with-you/index.mpf
  nl: https://docs.esfi.eu/nl/our-approach/what-stays-with-you/index.mpf
  de: https://docs.esfi.eu/de/our-approach/what-stays-with-you/index.mpf
  hr: https://docs.esfi.eu/hr/our-approach/what-stays-with-you/index.mpf
mpf-id: a12c2038893dd25b5a8d2ec1a93949975816af0e0c843980745c2d2af1557cc0
---

Language

✕

/our-approach/what-stays-with-you/index.mpf[open file ↗](/our-approach/what-stays-with-you/index.mpf)[spec ↗](/standards/mpf/0.7)✕

loading…

# What stays with you {#what-stays-with-you}

**The engagement ends when the function no longer needs us.**

Strategy, formal alignment and institutional intent do not guarantee execution. An ESFI Task Force enters at that gap, between what an institution has decided and what it is able to carry out, and leaves only when the capability remains inside the institution.

That exit is not a formality at the end of a contract. It is the purpose of the work.

## How a Task Force works {#how-a-task-force-works}

**Diagnose.** Start with the function, not the organigram. Locate where responsibility, capability and execution separate; establish the target state; define the evidence that will show whether the gap is actually closing.

**Build.** Translate the diagnosis into an operating programme. Design the intervention, assemble the necessary expertise, run delivery with institutional counterparts and test the system under actual constraints. Not recommendations. Working capability.

**Transfer.** Move procedures, tools, data, competencies and operating routines into the institution itself. External support recedes as internal capability expands. The objective is not permanent support. It is independent execution. Transfer is not a final phase; it runs through the whole engagement.

**Capability remains.** Success is reached when the function no longer needs the Task Force. Capability remains. The Task Force leaves.

## What you keep {#what-you-keep}

At the end of an engagement, a partner should hold more than a working system. We expect it to keep:

-   **People who can operate, maintain, change and judge the function**, not only run it on a normal day;
-   **Decision records** that explain why the function was built the way it was, and when those decisions should be revisited;
-   **Exercised procedures** that its own staff have carried out, including recovery from failure;
-   **Evidence** of what was tested, under which conditions, and what remains unverified;
-   **The freedom to replace** any component, any supplier, and us.

The last item is deliberate. An institution that could not replace its advisers has received a dependency, however well it is documented.

## How you will know {#how-you-will-know}

The clearest test comes after we leave: **the first change the institution makes on its own.** If it can adapt the function, explain the change and judge whether it was done well, the transfer worked. If it needs to call us back, it did not, whatever the final report said.

We say this in advance, and we hold ourselves to it.

## What we will not do {#what-we-will-not-do}

We do not stay longer than the function requires. We do not design engagements that keep an institution dependent on us. We do not measure success by hours of training, pages of documentation or number of workshops. And where capability has not moved, we say so, and at which level.

Why capability is so often lost, and what it takes to keep it, is set out in full in [Capability transfer](/topics/capability-transfer).

**Related:** [Capability transfer](/topics/capability-transfer) · [The sequence](/our-approach/the-sequence) · [Where the work begins](/our-approach/where-the-work-begins)

## On this page {#on-this-page}

ESFI — civilization infrastructure · https://esfi.eu