# Client handover — Fintech

The client handover with the items a regulated financial product cannot afford to lose: the review record and which creative sits under which reference, the market restrictions and where they are configured, the disclosures and their placements, and the register of what is live today.

Everything else is the general handover, unchanged. One row per item, named exactly, verified from the receiving side, with ownership distinguished from access.

## How to use it

1. Copy this file, or the CSV version if you would rather work in a sheet.
2. List by category first, so a whole class of thing cannot be forgotten.
3. Name items exactly, with identifiers, not by description.
4. Have the receiving side verify each item, and record who and when.
5. Distinguish ownership transferred from access granted.
6. Write the risk if missed on every row, so the list can be prioritised.
7. Keep the notes: the reasons behind decisions are the part that cannot be recovered.

## The columns

**Item** (Text). The specific thing being handed over, named exactly: the review register by its location, an ad account by its identifier, a landing page by its URL. In this category an item named loosely is an item nobody can audit.

**Category** (Text). The kind of thing it is: an account, an asset, data, a document, an access right, a relationship or an obligation. The document category carries the most weight here, because the review register and the refusal history are the two things that cannot be reconstructed.

**Where it lives** (Text). The system it is actually in: the shared review folder, the business account, the page's hosting, the reviewer's own records. Where anything lives only in an individual's mailbox, that is a finding as well as a row.

**Access before** (Text). Who could reach it before, and for the review register that is usually the account team and the reviewer. Recording it matters because the reviewer is the relationship the successor most needs.

**Access after** (Text). Who can reach it afterwards, by name, and deliberately narrower for anything that can edit live creative. A handover is the right moment to shorten that list rather than to copy it.

**Ownership transferred** (Text). Whether ownership itself transferred, or a permission was issued against somebody else's. For the ad account this is the question that decides whether the history survives the agency's own account being closed, and it takes days through a platform process.

**Verified by** (Text). The incoming owner who confirmed it, by name. For the review register that means reconciling it against every live ad rather than confirming the folder opens.

**Verified on** (Date (YYYY-MM-DD)). The day it was confirmed, which for this category is also the baseline date: on this day these ads were running under these references, verified by these people. Everything after it is the successor's.

**Risk if missed** (Text). What is exposed if this is missed, in one line. For the register it is that nobody can say what is running under which review, and the next rate change becomes an archaeology exercise rather than a filter.

**Outstanding** (Text). What is still to be done and by whom: the ownership transfer still queued with the platform, the page still to be moved off the agency's hosting, the screenshots still to be captured.

**Evidence** (Text). What shows the transfer happened: the reconciled list of live ads and references signed by both sides, screenshots of delivery settings, the rendered disclosures, a permissions screen after transfer.

**Status** (Text). Not started, transferred, or verified. Verified here carries more weight than elsewhere, because the verification date is what separates inherited problems from introduced ones.

**Notes** (Text). What the receiving side cannot infer: which setting holds a market restriction, which claims have been refused and why, the review turnaround to plan around, the page whose terms are updated by another team.

## The client handover

| Item | Category | Where it lives | Access before | Access after | Ownership transferred | Verified by | Verified on | Risk if missed | Outstanding | Evidence | Status | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|   |   |   |   |   |   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |   |   |   |   |   |

## Before you commit it

- Items are listed by category, so no whole class is forgotten.
- The review register is handed over and reconciled against every live ad.
- Market restrictions are documented with where each is configured.
- Disclosure placements are recorded as rendered, with screenshots.
- Every row was verified by somebody on the receiving side, with a date.
- Automated rules have been listed and transferred or stopped.
- The notes carry the reasons behind decisions, including refused claims.