How the handover runs
A careful start makes the later weeks much easier.
- Agree scope and terms with the service partner after your request is passed on.
- Write down the tasks you are handing over, with examples of done-right work.
- Give access through delegation or a password manager, never by sending passwords in email.
- Spend the first week answering questions and correcting small things early.
Before day one
The work goes better when these are ready in advance.
- Decide which tasks move first and which wait
- Write each process down, even roughly
- Gather the logins the assistant will need and plan how to share them safely
- Set up a separate user account where the tool allows it
- Agree how urgent items should be flagged
- Set approval limits for refunds, price changes, payments and outgoing invoices
Least access, clearly logged
Give an assistant the access a task needs and no more. Someone entering orders does not need permission to issue refunds. Someone answering chat does not need admin rights in the help desk.
Delegation and individual user accounts make this easy and keep a record of activity under the assistant's own name. Where a shared login cannot be avoided, keep it in a password manager and leave two-factor authentication on. Avoid sending passwords in email, text or chat.
Plan the exit at the start: a list of every system the assistant can reach, so you can remove access and change shared passwords the day the arrangement ends.
Keeping track once work begins
The first month is when habits form, so stay close to the work. Read the end-of-day summaries, answer questions quickly and note any correction you make so it can go into the procedures.
After that, most owners move to a weekly summary and a short check-in. That is usually enough to see what is getting done and to decide whether hours should change. If the workload grows, you can ask the service partner about adding hours or tasks. If it shrinks, ask about reducing them. Either way, changes are agreed with the partner, not assumed.
Sending a request commits you to nothing. It starts a conversation about scope.
Ask for a quote