Virtual Assistant Services Editing and Proofreading Services

Delegation fails at the handover, not at the doing. A business owner who has run their own inbox for nine years knows a hundred small rules they have never articulated — which suppliers get chased at seven days and which at thirty, which client's emails must never be answered by anyone else, that the Tuesday report goes out before eleven because a particular person reads it over coffee. None of that is written anywhere. The assistant is capable; the instructions are the problem.

We edit what virtual assistant businesses and remote support providers produce — task handover documents and process guides, standard operating procedures for recurring work, client onboarding questionnaires and discovery documents, service agreements and hours packages, scope and boundary documentation, communication and response time protocols, tool access and security procedures, inbox and calendar management protocols, client-facing service descriptions and packages, assistant training and induction material, escalation and decision authority documentation, and reporting and time tracking documentation. Our editors work on the document that decides whether delegation actually saves anyone time.

The task handover is the whole business in one document, and it fails by describing the task instead of the judgement inside it. "Manage the inbox" is not a handover; it is a hope. We write these so each recurring task is captured as a trigger, the steps, and the decision points where the assistant must choose — which is the only part that requires the owner's knowledge; so every decision point states the rule and the exception, with what to do when neither applies, since an assistant who guesses once too often gets their access reduced and an assistant who asks about everything has saved nobody any time; so the authority boundary is explicit in money and consequence — spend up to this without asking, reply on my behalf to these people but never to those, book without checking under these conditions; so the tone of any client-facing message is shown by example rather than described, because "friendly but professional" is invisible and three real sent emails are not; so the things the owner does not want touched are listed, given that this is where trust is actually lost; and so each procedure names how the owner will know it was done. Handovers written this way survive the assistant being replaced, which is the point at which most of these relationships collapse.

Everything you send is treated in confidence, including client procedures, business information and correspondence. We are editors rather than business, operational or security advisers, and we offer no view on processes, delegation or access arrangements. What we can do is capture the judgement that currently exists only in one person's head.