Skip to content
SciTechBiz Institute
I want to join
Blog · Forward Deployed Engineer

Handover: leaving AI running at the client without you

An AI project handover is the point at which the client company starts running the system without the person who built it. It is prepared from the start and checked with facts: someone at the client runs the tests alone, every task has a named owner and the builder's access has been revoked.

Updated: 5 November 2026 · Deibson Silva · Forward Deployed AI Engineer and Founder

What it is

What is an AI project handover?

It is the last stage of a Forward Deployed Engineer's work. An FDE builds AI inside the company, with its data and its team, and leaves once the company runs on its own. Their presence is always temporary.

Handover exists because an AI system does not stand still. The company's process changes, cases arrive that nobody had seen, and one day someone suggests changing the model. If the only person who knows how to touch the system has gone, the company depends on a phone call.

The other ending is more common and quieter. The project is delivered, the demo went down well and, months later, hardly anyone uses it. Nobody in the business owned it.

Under the EU AI Act, the company using a system under its own authority is the deployer. The person who built it leaves and the company keeps using it. So the company needs to know how to run it.

Comparison

What is the difference between delivering a project and handing it over?

Delivering leaves something finished. Handing over leaves someone able to maintain it.

DeliveringHanding over
What the company receivesThe system running and a final documentThe system, its rules, its tests and the people who know how to use them
Who can change a ruleWhoever built itSomeone in the company, with the rule in writing and its change history
Who runs the testsWhoever built it, from their own environmentThe client's team, from its own systems
When something failsYou ring the person who made itThe operations owner follows a written procedure
The builder's accessLeft open, just in caseTransferred, and their credentials revoked
When it closesOn the contract dateWhen the process owner signs the Handover Test
The kit

What goes in a handover kit?

In the Legathum AI-First Hybridisation Method v3, the kit has these pieces:

To operate

  1. 01A written runbook: how to start it, how to stop it, what to watch and what to do when something fails.
  2. 02The recurrence plan: what is reviewed, how often and by whom.
  3. 03Access transferred to the company and the FDE's credentials revoked.

To decide

  1. 01The exported Book of Criteria, with the rules the in-house expert approved and their version history.
  2. 02The regression suite, ready to run from the client's systems.

To carry on

  1. 01The owners named in writing, each with a deputy.
  2. 02The gap report: what the product did not solve, each point with its case.

The last lab of the programme is building this kit. The check requires the regression suite to run from a clean copy, without the environment of whoever wrote it.

The test

How do you check that the company can manage alone?

With the Handover Test, the last of the six the client signs. It is all or nothing.

The tests, without the FDE

Someone on the client's team runs the regression suite from their own systems, reads the result and decides. They explain each failure unaided.

The next case, without the FDE

The team picks another process from its list and scopes it: with an owner, a metric and a baseline. If it can prepare the next one, it has learnt the method as well as receiving a system.

Named owners

In writing and with a deputy: who maintains the evals, who operates the system, who keeps the AI Act register and who is the point of contact in each area.

The measurement, repeated

The measurement taken at the start is repeated at 90 days and shared with the team. That shows what has changed against the baseline.

If it does not pass

What happens if the company is not ready yet?

The FDE's presence is extended with a date and a plan. Never without a date. A handover that drags on with no limit ends in dependence.

The cause is usually one of two things. Either nobody has the time to own the evals, or the team uses the system less than it seemed. The first is solved by naming a person and giving them the hours. The second goes back to the previous stage, adoption, where the cause is corrected.

From the first day

When do you start preparing the handover?

At the beginning of the project. A handover left to the final week turns into a folder of documents. What is done at each stage:

  1. 1When the case is qualified, you settle who owns the process inside the company. That person will sign the tests.
  2. 2When the criterion is captured, the rules are written in plain language and approved by the in-house expert. Whoever comes later can read them and change them.
  3. 3During the build, the evals have an owner from the first day, and the code, the instructions and the model version are released together.
  4. 4At deployment, each person is trained for their role and a sample of runs is reviewed. Every failure that is noted goes into the regression suite.
  5. 5Throughout the project, gaps in the product are written down, each with its case.

In the certification's final project, the Adoption and Handover tests are left planned with the company.

Good to know

Honest limits

  • The system can still fail after a good handover. The difference is that the company sees it and knows how to correct it.
  • To deliver to client companies you need a valid FDE Certification and a signed Framework Contract and data protection agreements. The FDE annex to the contracts is being prepared.
  • In the real project, the company's data never leaves its systems, and the portfolio the FDE presents is anonymised.
  • This article describes a working method. It is not legal advice on your company's obligations.
  • Today the programme is taught in Spanish: 27 Spanish videos are published at the Academy, and the English videos arrive in November 2026.
  • The certification attests a competence, never a job or an income.
FAQ

What people ask most

01

When does a Forward Deployed Engineer's work end?

When the company runs on its own. In the method that is checked with the Handover Test, signed by the process owner: the team runs the tests without the FDE, there are named owners and the kit has been delivered.

02

What does the company keep when the FDE leaves?

The rules the system decides by, the tests and who approved them, all documented. Plus a runbook, the review plan, access in its own name and a report on what was left unsolved.

03

Who maintains the tests afterwards?

Someone in the company, named in writing and with a deputy. They own the evals: they run the regression suite before each new version and add a task for every failure that appears.

04

What happens to the access of the person who built the system?

It is transferred to the company and the FDE's credentials are revoked. That is part of the handover kit and one of the conditions of the test.

05

Is handover taught in the FDE Certification?

Yes. The programme has a module on handover and the final project, and a lab in which you build the kit. In the four-week project at a real company, the handover is left planned with the company.

Portrait of Deibson Silva
Deibson Silva · Forward Deployed AI Engineer and Founder

Founder of Legathum and iPersonality and Forward Deployed AI Engineer. He leads the SciTechBiz Community from Madrid and examines the FDE Certification defence.

Your licence

Start from your dashboard

On the licence page you request access; requesting access costs nothing. You then sign the contract and pay the annual licence from your dashboard.

iPersonality Global Institute, S.L. · NIF B27580042 · Madrid · Privacy policy

Prices in euros, exclusive of VAT. In Spain, Spanish VAT is added. In the rest of the EU, VAT is calculated at payment according to your country and VAT number. No Spanish VAT is charged to UK customers.