Building in public. Follow along on X

Guide

Offboarding checklist when a cofounder or contractor leaves

Offboarding a person from a small project means moving ownership of every account away from them before you remove their access. Do it in this order: list what they touch, transfer what they own, revoke the rest, change shared secrets, then test that you can still recover everything.

By Matt Warcholinski, co-founder of Brainhub · Updated 16 November 2026

Not legal advice. This guide covers accounts and assets. It does not cover notice periods, final pay, equity, intellectual property or contracts, and those rules differ by country. If money, customers or a dispute is involved, talk to a lawyer before you act.

What is offboarding in a small project?

Offboarding is the set of steps you take when someone stops working on a project: a cofounder, a contractor, a freelancer, a volunteer. In a large company this is an HR process with a form and a laptop return. In a small project it is mostly about accounts.

Most offboarding guides online are written for HR teams. They talk about exit interviews and benefits. I care about a narrower question: after this person is gone, who owns the domain, who can log in to hosting, who can still charge the company card, and who can recover each of those if something breaks?

That question is the whole job when you have two to five people and no IT department. The shared glossary entry for offboarding gives the short definition. This page gives the working checklist.

Why the order matters more than the list

Every checklist tells you to "revoke access". If you do that first, you can break the project.

Suppose the person who leaves is the only owner of the domain registrar account. You remove their login. Now nobody owns the domain, and you cannot renew it, change DNS or prove it is yours. You made the problem worse by acting fast.

So I split offboarding into two kinds of access:

Transfer ownership, then remove participation. The bus factor guide covers the same idea from the other side: a single person holding a single key is a single point of failure, whether they leave on good terms or not.

Before you start: three questions

  1. Is the exit friendly? If yes, you can ask the person to help with transfers. If not, protect access first and ask for cooperation second. The if my cofounder leaves checklist is built for that case.
  2. Do they have a notice period or a handover duty? Check your agreement. If you have none, write a short one now and have both sides confirm it by message or signature.
  3. Who is the single point of contact? Pick one person on your side to run offboarding. Two people changing things at once is how an account gets locked.

The offboarding checklist, step by step

  1. Inventory everything the person touches. Do not rely on memory. Open your password manager, your shared inbox, your billing statements for the last three months, the member lists of your code host and cloud tools, and your registrar. Write each account in one row: what it is, who owns it, who pays, who else can get in.
  2. Sort each row: owner or participant. Mark every account where the leaving person is the owner, sole admin, billing contact or recovery email. Those go to the transfer list. Everything else goes to the removal list.
  3. Name a new owner for each transfer item. One named person per account, plus a second person who can recover it. An account owned by "the team" is owned by nobody.
  4. Transfer ownership while the person can still help. Add the new owner as an admin or owner first, confirm they can sign in, then ask the leaving person to step down. Where a service has an official ownership transfer, use it rather than sharing a login.
  5. Move billing. Replace the leaving person's payment card with a company or project card. Check the invoice email address. A cancelled card is the most common reason a domain or a hosting plan silently lapses.
  6. Remove their personal access. Take them out of member lists, shared folders, chat workspaces and calendars. Remove their keys from servers, deploy keys from repositories and their devices from any trusted list.
  7. Rotate anything they could have copied. That means shared passwords, API keys, tokens, webhook secrets, database passwords and the recovery codes for shared two-factor setups. If a secret lived in a message or a file they could read, assume they hold a copy.
  8. Check the recovery paths. Recovery emails, phone numbers and backup codes often point at a personal address of the person who left. Change each one to an address you control.
  9. Redirect communication. Forward or alias their project email to a named person for a set period, and update any public contact page, DNS records or invoices that name them.
  10. Test, read-only. Have the new owner sign in to each account from a clean browser and confirm they can see billing and the recovery settings. Do not change anything during the test. The bus factor guide has a read-only test you can reuse.
  11. Record the result. Date, who did it, what changed, what is still open. Keep it where all remaining founders can read it.

What to move, remove or rotate for each kind of account

The right action depends on what role the leaving person holds. This table is a decision aid. Service names are examples of categories, and each service's screens differ, so check the official help for the exact clicks.

Account typeIf they are the ownerIf they are a memberAlso check
Domain registrarTransfer account ownership or the domain itself to an account you controlRemove the loginAuto-renew, registrant email, contact record
DNS and email hostAdd a second owner, then hand over billingRemove the loginMail forwarding, SPF and DKIM records
Code hostMake another person owner of the organisation or repoRemove access, then revoke tokens and SSH keysDeploy keys, secrets in CI, third-party apps
Cloud and hostingAdd a second owner and move billingRemove the user and their keysAccess keys, service accounts, public buckets
Ad and social accountsAdd a second full-control admin before removalRemove the person's roleBusiness manager links, payment method
PaymentsMove to an owner role held by a remaining founderRemove the user, review payout bank detailsPayout account, API keys, webhooks
Password managerMake a remaining founder the owner of the shared vaultRemove from shared vaultsRotate every credential they could view
Chat and docsMake another owner, export what you needRemove, keep their files if the agreement allowsShared links that were public

The right-hand column is where offboarding usually fails. People remove the member but leave a token, a key or a deploy secret alive. Those keep working after the person's login is gone.

A worked example: a two-person project

This example is illustrative. The names and accounts are made up to show the method.

Mia and Jonas run a small subscription product. Jonas built it and is leaving in two weeks to take a full-time job. He holds the registrar account, the hosting account and the payment processor login. Mia holds the code organisation and the support inbox.

AccountOwner todayPaysActionNew ownerBackup
Domain registrarJonasJonas's cardTransfer, change cardMiaShared company email
HostingJonasJonas's cardAdd Mia as owner, change cardMiaJonas for two weeks
Payment processorJonasNot applicableAdd Mia as admin, change payout and recovery emailMiaAccountant
Code organisationMiaMiaRemove Jonas, revoke his tokensMiaJonas as read-only contractor, if agreed
Support inboxMiaMiaRemove Jonas from forwardingMiaNot applicable

Three of the five rows are transfers, and all three are in Jonas's name. If Mia had started by removing his access, she would have lost the domain, the server and the money in one afternoon.

Her plan runs over the two weeks. In week one she gets herself added as owner on all three accounts and swaps the cards. In week two she and Jonas rotate the secrets together, then she runs the read-only test alone. On his last day Jonas steps down from the accounts. The result is a one-page record, the same one you can fill in with the template below.

Copy this offboarding record

One page is enough. Paste it into a doc, fill it in, and have the leaving person and a remaining founder confirm it.

Offboarding record: [PROJECT]
Person leaving: [NAME]   Role: [cofounder / contractor / other]
Last working day: [DATE]   Run by: [NAME]

1. Inventory (one row per account)
   [ACCOUNT] | owner: [NAME] | pays: [NAME / CARD] | recovery: [EMAIL / PHONE]

2. Transfers (done before removal)
   [ACCOUNT] -> new owner [NAME], backup [NAME], done on [DATE]

3. Removals
   [ACCOUNT] member removed on [DATE]; tokens and keys revoked: [YES / NO]

4. Secrets rotated
   [SECRET] rotated on [DATE] by [NAME]; stored in [VAULT]

5. Recovery paths changed
   [ACCOUNT] recovery email now [ADDRESS], backup codes stored in [VAULT]

6. Test (read-only)
   [NAME] signed in to [ACCOUNT LIST] on [DATE]: billing visible [Y/N], recovery visible [Y/N]

7. Still open
   [ITEM], owner [NAME], due [DATE]

Confirmed by: [LEAVING PERSON] [DATE]   [REMAINING FOUNDER] [DATE]

If you want the same structure with checkboxes, the project handover checklist and the user access review checklist cover most rows. The project handover document template adds an asset register and a recipient sign-off.

How do I offboard a contractor differently from a cofounder?

The accounts are the same. The risk is different.

A contractor usually holds fewer owner roles, but often holds more tokens and keys, because they were given access for a task and nobody wrote it down. Focus on the removal and rotation steps. Ask them to list every credential they were given, then compare with your own list.

A cofounder often holds ownership. Focus on the transfer step and billing. Check the paperwork too: access is only one part of an exit, and what the person keeps (shares, rights to the code) is a legal question outside this guide. The page on what to do when a cofounder removes you from the domain or ads covers the case where the exit is already hostile.

What if the person will not cooperate?

Then do the part you control and document the rest.

  1. Use the owner or admin rights you already have to add a second owner wherever the service allows it.
  2. Change shared secrets and recovery contacts that you control.
  3. Save evidence: screenshots of member lists, the dates, and the messages where roles were agreed.
  4. For accounts only they own, use the service's own account recovery or ownership dispute process, and see a lawyer if the account holds something valuable. The domain ownership guide explains why the registrant matters.

Do not guess passwords or log in as the person. That can create legal trouble for you and is not needed when you follow the service's own process.

Prevent the next one: build offboarding into onboarding

The cheapest offboarding is the one you planned on day one. Three habits make it easy:

If you want the register to stay current without a spreadsheet, the app records who controls each account, who pays and who confirmed it.

Do it with AI

Draft your offboarding plan

Give an AI your account list and let it draft the order of steps. Check every step against the service's official help before you act.

Act as an operations assistant, not a lawyer. [NAME] is leaving our [NUMBER]-person project on [DATE]. They are a [cofounder / contractor].
Here is the list of accounts they touch, with owner, who pays and recovery contact: [PASTE LIST]
1) Mark each account as ownership-transfer or simple removal.
2) Put the steps in a safe order so we never remove the only owner.
3) List the secrets, tokens and keys we should rotate.
4) List the recovery emails and phone numbers to change.
5) Write a read-only test we can run afterwards.
6) Flag any step where I should check the service's official help or ask a lawyer in [COUNTRY].

Frequently asked questions

What is an offboarding checklist?

It is a written list of the steps to take when someone leaves a team: what to collect, what to transfer, what to remove and what to change. For a small project the most important rows are the accounts and assets the person owned or could reach.

What should be on an offboarding checklist for a small team?

An inventory of accounts, a list of ownership transfers, a list of access removals, secrets to rotate, recovery contacts to change, a read-only test and a signed record. HR items such as final pay and equipment return are separate and depend on your agreement and country.

Should I remove access before or after transferring ownership?

After. Transfer ownership first, confirm the new owner can sign in, then remove the leaving person. Doing it the other way round can leave an account with no owner.

How soon should access be removed when someone leaves?

On their last working day for participation access, and earlier for anything sensitive if the exit is hostile. Ownership transfers should be finished before that day, so plan them during the notice period if you have one.

Do I need to change passwords when a cofounder leaves?

Change any shared password, token or key they could have seen or copied. Their personal login is simply removed. If a secret sat in a shared note or message, treat it as known.

How is cofounder offboarding different from employee offboarding?

A cofounder usually owns accounts, holds shares and has a say in decisions, so transfers and written agreements matter more. An employee usually has a contract and a manager, so the process is closer to standard HR steps plus a clean account removal.

Can I do offboarding without a password manager?

Yes, but it is harder. You will need to list accounts from billing emails, member lists and the person's own account list. A shared vault makes the inventory and the rotation step much faster.

What this guide does not cover

Sources

Related

Record who owns, pays for and can recover every account, so the next person to leave is a checklist, not a crisis.

Start free in the app