# Taking over a service: what to ask in the handover meeting

> You have one hour with the person who knows the service. The questions that matter: what it does, where it runs, how it breaks, how you find out, and what they never fixed.

Source: https://hintvo.com/blog/taking-over-a-service-handover-questions | Last updated: November 20, 2026 | Reviewed: 2026-11-20

A handover is one hour with the person who knows the service, and after it they are busy with something else or gone. Do not spend it on a tour of the code. You can read the code later. Ask for the things that are not written down anywhere: how it breaks, how you find out, and what they never got around to fixing.

## What it does and who depends on it

- Who uses it, and what happens to them when it is down?
- Which other services call it, and which does it call?
- What is the one thing it must never get wrong?

## Where it runs

- How does a change get to production? Show me one, start to finish.
- What settings and secrets does it need, and where are they kept?
- What runs on a schedule, and what happens if a run is missed?

## How it breaks

- What were the last three incidents?
- Which alert do I take seriously, and which one is noise?
- What do you check first when something looks wrong?
- Is there anything that has to be done by hand, every week or every month?

## What was never fixed

- Which part of the code are you afraid to touch?
- What would you rewrite if you had a month?
- What does the documentation say that is no longer true?

People answer these honestly in a handover in a way they never do in documentation.

## Do one thing together

Before the hour ends, deploy one tiny change with them watching. The first deploy is where the missing permission, the undocumented step and the script on their laptop show up. Better now than at two in the morning.

## Your first week alone

1. Write up the handover while you remember it, and send it to them to correct.
2. Read the entry points: routes, jobs and the schema.
3. Find the dashboards and the logs, and look at a normal day so you can recognize a bad one.

> **Where Hintvo fits:** add the service's folder and Hintvo maps its files, functions, endpoints and data tables on your computer. During the handover call, a term you have not met is explained in one sentence in the context of that project, and Prepare me writes a one-page briefing before it. Prepare me briefings need a pack of hours. See [the first week scenario](https://hintvo.com/scenarios).

## Related

- [Hintvo AI in real meetings and interviews: 9 scenarios](https://hintvo.com/scenarios.md): What does Hintvo AI actually do in a real meeting or interview?
- [Your first weeks on a new codebase: follow the meetings before you know the code](https://hintvo.com/blog/first-weeks-on-a-new-codebase.md): How do I keep up in meetings during my first weeks on a new team?
- [Incident calls: find the code path while people are talking](https://hintvo.com/blog/incident-call-find-the-code-path-fast.md): How do I find the failing code path quickly during an incident call?
