The data handoff checklist every freelance analyst needs

The project wrapped in March. In May, an email lands from the client: "Our new analyst is trying to update the dashboard for Q2 and can't work out where the data comes from or how to refresh it — any chance you can jump on a call?" You barely remember the file structure, the refresh is buried in a Power Query step nobody documented, and now you're doing unpaid support on a project you closed two months ago. A clean deliverable that only you can operate isn't finished — it's a dependency. The handoff is the last mile that decides whether the client remembers you as the person who left them self-sufficient or the person they still have to chase.

A deliverable only you can run is not done

Analysts obsess over the quality of the output and forget that someone else has to live with it. The client's team will need to refresh the data next month, understand why a number is defined the way it is, and fix it when the source file changes shape. If all of that lives only in your head, every future month is a support call — bad for them, unpaid for you, and quietly corrosive to the relationship. A proper handoff transfers not just the files but the ability to operate them, so the work keeps running when you've moved on to the next client.

The handoff package, listed

Here's what actually changes hands, beyond the dashboard itself:

HANDOFF PACKAGE — Northbridge Q2 dashboard
  Files:        q2_clean.csv, clean_sales.pqx, region_map.xlsx
  Where it lives: /clients/northbridge/2026-q2/
  How to refresh: open workbook -> Data -> Refresh All
                  (source parameter = path to new monthly CSV)
  Definitions:  churn, active, revenue (see delivery report)
  Mappings:     region_map.xlsx — add new spellings here
  Known breaks: if refresh errors, check unmapped regions tab
  Credentials:  none — all local files, no logins
  Contact:      [you], support until 31 July

Notice the "how to refresh" and "known breaks" lines. Those two are the difference between the new analyst updating Q2 in five minutes and emailing you in a panic. You're not handing over a file; you're handing over the operating manual for it, and it fits on one screen.

The handoff checklist

1. Deliver the files, named plainly — the cleaned data, the cleaning steps or query, and any lookup tables, in one folder with an obvious structure.
2. Write the refresh procedure — the literal clicks to update with next month's file, including where the source path is set.
3. Hand over the definitions — what each metric means, so the client's team doesn't silently redefine "active" and break the trend.
4. Expose the mappings — the region and code lookup tables, with a note that new values go here, not into the logic.
5. Document the known breaks — what goes wrong when the file changes shape, and the one place to look first.
6. State credentials and access — any logins, source locations, or permissions the team will need, or confirm there are none.
7. Set a support boundary — "included support until 31 July, then billed at £X/hr" — so helping is generous, not endless.

Seven items, half a page, delivered on the last day of the project instead of reconstructed under pressure in May. It costs you twenty minutes and it ends the unpaid support calls before they start.

The handoff is where referrals are won

There's a reason to do this beyond avoiding May's phone call. The client who can run your work without you is the client who tells the next company, "we hired someone who left us completely set up." A clean handoff is the most undersold marketing an analyst has — it turns a finished project into a reference that sells itself, precisely because you made yourself unnecessary. Counterintuitively, the way to get hired again is to prove the client doesn't need you, and the handoff checklist is how you prove it in writing on the very last day.