freelancersdigital legacy

Digital legacy planning for freelancers

By Imok Team ·

Digital legacy planning for freelancers comes down to one uncomfortable question: if you stopped responding tomorrow, would anyone be able to tell your clients what they are owed, where their work is, and what happens next? For most freelancers the honest answer is no — everything lives in your head, your inbox, and your personal accounts. This post walks through exactly what a freelance digital legacy plan must cover, and how to automate the delivery of it.

Why freelancers are uniquely exposed

Freelancers carry a concentration of risk that employees and even small agencies do not. Three factors make it acute:

  • Clients mid-project. You may be holding deposits, half-finished deliverables, or access to a client’s systems. If you vanish, that client is stuck — and your family inherits the angry emails.
  • Income tied to your availability. There is no HR department, no colleague who knows the project, no bus factor above one. Revenue stops the moment you do, but obligations do not.
  • Everything lives in personal accounts. Your contracts are in your email, invoices in your accounting app, files in your personal cloud drive, the portfolio on a domain registered to you personally.

Compare that with an employee who dies: the company reassigns their work the same week. A freelancer is the company. If you want the broader picture of what an unattended one-person business looks like, see what happens to your online business when you die.

The 5 things a freelance digital legacy plan must cover

A workable plan is shorter than you think. It needs five sections, each answering one question your successor will ask in the first 48 hours.

1. Active client list and project status

Answer first: who are you currently working for, and what state is each engagement in?

For each active client, record:

  • Client name, contact person, email
  • Project name and one-line description
  • Current status: “awaiting feedback,” “delivery due March 15,” “retainer, monthly”
  • Money position: deposit held, invoice outstanding, paid in full

This single list prevents the worst outcome — a client finding out you are gone by having their deadline silently pass.

2. Outstanding invoices and how to collect or refund

Answer first: what money is owed in each direction, and what should be done about it?

List unpaid invoices with amounts and where they were issued from (your invoicing tool, Stripe, PayPal). Just as important: list any prepayments or deposits for undelivered work, with a clear instruction — refund in full, refund pro-rata, or “the work is 90% done and the files are in location X, deliver and invoice.” Your successor should not have to make ethical judgment calls without guidance from you.

3. Files and deliverables locations

Answer first: where does the work product live, and how does someone get to it?

Name the systems, not the passwords: “All client deliverables in Google Drive, folder ‘Clients 2026’, organised by client name. Final exports also attached to the relevant invoice in my accounting tool.” Credentials belong in a password manager with emergency access; the handover plan points to them.

4. Domain and portfolio handling

Answer first: what happens to your website, portfolio, and professional identity?

Your domain will keep auto-renewing on your card until the card fails, then lapse — potentially into the hands of a domain parker wearing your professional name. Decide now: should your successor keep the portfolio up as a memorial/archive, redirect it, or let it expire deliberately? Note the registrar, the renewal date, and the decision.

5. Who notifies clients, and what they say

Answer first: name the person, and give them the words.

This is the section everyone skips, and it is the one that matters most. Your successor is grieving and has never run your business. Do not make them compose fifteen difficult emails from scratch — write the template for them.

A client-handover script your successor can send

Here is a short template you can adapt. It is deliberately calm, factual, and offers a clear next step:

Subject: Important notice regarding [Your Name]‘s studio

Dear [Client name],

I am writing on behalf of [Your Name]. I am very sorry to share that [he/she/they] [has passed away / is seriously unwell and unable to work].

Your project, [project name], was at the following stage: [status]. All files completed so far are available here: [link/location].

Regarding payment: [invoice #123 for $X remains outstanding and we would appreciate settlement to the estate / your deposit of $X for undelivered work will be refunded in full within 14 days].

Please reply to this email with any questions. I will do my best to help during this transition.

With condolences and thanks for your understanding, [Successor name]

Notice what it does: states the situation in one line, answers the client’s two immediate questions (where is my work, what about money), and closes politely. Having this pre-written turns a terrifying task for your successor into an afternoon of mail merges.

Recurring revenue and retainers

Answer first: retainers and subscriptions must be stopped or transferred explicitly, or they will keep billing.

If you bill monthly retainers, list every client on retainer, the billing mechanism (Stripe subscription, standing invoice, direct debit), and the instruction: cancel, or hand over to a named fellow freelancer. Left unattended, recurring charges to clients for work no one is doing become a legal and reputational mess for your estate. The same applies in reverse — note any subscriptions you pay for, so your successor can cancel them instead of discovering charges for years.

Where a dead man’s switch automates all of this

Everything above can live in a single encrypted handover packet. The remaining problem is delivery: how does the packet reach your successor at the right moment without you handing it over prematurely?

That is what Imok does. It is a dead man’s switch: you check in periodically, and if you stop, the system moves through reminders and a trusted-contact nudge, then releases your packet to your designated successor through a one-time link. The packet is encrypted in your browser before it ever reaches the server — Imok cannot read it — and it is free during early access (see pricing).

The result: your five-section plan, your invoice list, and your client-notification script all arrive in the right hands automatically, exactly when they are needed — and never before. For the full content checklist, see what to put in a business handover document.

Start your switch

Free while in early access. Set up in under 15 minutes.

Frequently asked questions

Is a freelance digital legacy plan legally binding?

No, and it should not try to be. A handover document is an operational map, not a legal will. Estate matters belong with a solicitor or estate attorney; your handover plan covers the practical day-one questions a helper faces.

Should I give my successor my passwords?

Not in the handover document itself. The document should say WHERE credentials live — typically your password manager with emergency access configured — rather than containing raw passwords. That keeps sensitive secrets in a system designed for them.

What happens to my unpaid invoices if I die?

They become part of your estate, but someone still has to know they exist, who owes what, and how to collect or refund. That is exactly what the invoice section of a handover plan documents, so your successor or executor is not reconstructing it from your inbox.

How does Imok help freelancers specifically?

Imok stores your encrypted handover packet and releases it to your chosen successor only if you stop checking in — no courts, no waiting period, no one able to read it meanwhile. See the details at Imok for freelancers and pricing (free during early access).

Protect your one-person business

Imok delivers your encrypted handover packet automatically if you ever stop checking in.

Your business shouldn't disappear with you.

Set up your dead man's switch in under 15 minutes. Your handover packet is encrypted in your browser — we can never read it.