Module 7: Reliability Systems
Skills get you the trial task; reliability gets you the retainer. This module is the operating system of a VA clients keep: updates that land before the client thinks to ask, hours tracked so honestly they never get questioned, and a mistake protocol that turns your worst day into proof they hired the right person.
Async updates clients love
Every client carries the same quiet fear: they are paying for silence. Async updates kill that fear on a schedule — a short note, in the agreed channel, at the agreed time, whether or not there is drama to report. Most clients settle on a brief daily note or a fuller weekly one; what matters is that it never slips, because the update's real message is not the content. It is “you will always know where things stand without asking me.”
Use a fixed format so the client learns to scan it in two minutes. Done — with links to the actual work, not descriptions of it. In progress — one line each, with an expected finish. Blocked / needs a decision — the exact question, stated so it can be answered in one reply (“approve subject line A or B?” beats “waiting on the email thing”). Next — what you will pick up tomorrow or next week. When nothing is blocked, write “nothing blocked” — the empty field is information too, and it closes the loop clients otherwise close by messaging you.
Keep the whole trail in one place: the same Slack thread, the same email subject line, the same board — wherever onboarding established it. Scattered updates across four apps read as no updates. Do this well and something pleasant happens within a month: the “just checking in” messages stop, because the answer always arrives before the question. That is the core truth of this course in one habit — the VA who never has to be chased is the VA who gets renewed.
A client keeps messaging “any update?” in the middle of tasks, even though you're working steadily and delivering on time. What's the root cause, and the fix?
Time tracking and honest hours
Track time as it happens, with a timer, per task and per client — never reconstructed from memory on Friday. Memory inflates, rounds up, and quietly blends one client's work into another's, and clients can smell reconstructed timesheets the way you can smell a padded research list. The timer is not surveillance; it is your evidence and your protection. When every hour on the invoice maps to a timed, named task, hour disputes simply stop occurring.
Honesty runs in both directions. If a task took 20 minutes, log 20 minutes — even when the estimate said an hour. Padding that invoice buys you one quiet win and costs you the entire relationship the day it's noticed. The other direction matters just as much: when a task is running long, surface it early. At roughly 80% of the estimated hours with real work still left, tell the client now, with options — extend the hours, trim the scope, or park the remainder — rather than letting the overrun debut on the invoice, where it reads as a surprise charge.
Finally, know which hours are yours to absorb. Freelance VAs typically bill only about 70–80% of their working time; the rest is your own admin, communication, and business development. That gap is real, and it belongs in your rate math (Module 9 builds the floor from exactly this number) — not smuggled into a client's timer by stretching tasks. Share the task-level time report alongside your invoice as a matter of routine. A client who can see the work never argues about the hours.
A brief estimated three hours for a list-verification task. The list was cleaner than expected and you finished in ninety minutes. The invoice goes out tomorrow. What do you log and bill?
When something breaks: the mistake protocol
It will happen. A campaign goes out with the wrong link. A post publishes with last year's date. A file gets overwritten by the newer, emptier version. Your client's business will survive any of these; what it will not survive gracefully is finding out from a customer, a screenshot, or a week later from you. The protocol is four moves, in order: contain, report, fix, document.
Contain what you can, immediately, within your standing instructions: pause the campaign, unpublish or correct the post, restore the file from its previous version. Report fast — the same hour for anything customer-facing — in the agreed channel, in plain words: what happened, who it reached, what you have already done about it. No burying it in Friday's weekly note, no softening it into “a small hiccup.” Fix completely, including the follow-through (the corrected link resent to the client for approval, the affected list checked twice). Then document: one line added to the relevant checklist or SOP — “click every link in the test send, not just the first one” — so the system, not your memory, prevents the repeat.
Calibrate by severity. A typo in a caption you can still edit: fix it quietly and mention it in the weekly update. A wrong price in a sent email: immediate report, same hour, no waiting for a convenient moment. When you genuinely can't tell which it is, report — no client has ever fired a VA for hearing about a small problem too early. What actually happens to VAs who run this protocol is counterintuitive: they become more trusted after a mistake, because the client watched them catch it, own it, and engineer it out of the future. Cover-ups end engagements. Fast honesty extends them.
You spot that a post you scheduled goes live in an hour with the wrong event date. Your shift ends in ten minutes, and the client hasn't seen it yet. What do you do?
What you can now do
- Send async updates on the agreed schedule, daily or weekly, so a client never sits wondering whether they're paying for silence.
- Track time with a live timer, per task and per client, so every hour on your invoice maps to a record nobody has to question.
- Run the mistake protocol when something breaks: contain it, report it before the client hears it from anyone else, fix it, and document it.