Skip to main content
FHAVI

Free resource

Hand over the work, not the passwords

The risk in hiring help is not competence. It is access: who can refund, who can publish a GTM container, who holds the payment credentials. And the second risk is knowledge — what happens when the person who knew how the store works leaves.

Access

Grant the narrowest thing that works

01

Before day one

  1. A business email account on your domain — never a personal address — with 2FA enforced.
  2. Role-based access to each tool, not the master login: Shopify staff accounts, Merchant Center user access, Ads manager roles, analytics read-only where editing is not needed.
  3. No shared passwords. If a tool only supports one login, that is a reason to change tools.
  4. Payment credentials never handed over; refunds issued by a role that logs who issued them.
  5. A written list of what they cannot do, which is as important as what they can.
  6. Offboarding plan agreed before onboarding begins: which accounts to revoke, and who owns that task.

Document

What must exist in writing

02

The operating file

  1. Order of operations for a normal day: what is checked, in what order, at what time.
  2. Exception paths — what to do for a failed delivery, a chargeback, a suspension, in steps.
  3. Where the numbers live, and which number is authoritative for each decision.
  4. The supplier list with contacts and current prices, not a memory of them.
  5. The change log conventions from the tracking change log, so their work is traceable.
  6. Tone and response templates for customer replies, with the boundary cases written out.

Handover

The first two weeks

03

Sequence that avoids damage

  1. Week one: read-only. They observe and write down what they do not understand.
  2. Week one: they update the operating file with what was missing. That document is the deliverable, not a formality.
  3. Week two: they act, with your review before anything customer-facing or feed-facing goes live.
  4. Week two: a deliberately destructive test — cancel a test order, pause a tag — to confirm they know where the switches are.
  5. End of week two: revoke anything unused, and write the access list into the operating file.

Keep going

The rest of the library

Every checklist here is free and ungated. The research pages carry the reasoning behind them.

All resources · Research library

Hiring your first ops person?

We will set up the access model and the operating file before they start, so the first month is productive rather than risky.

Prefer email? Write to md@fhavi.com