Formatting content that leaves your hands clean

Formatting is not decoration. It is the difference between a draft and a publishable asset: one heading structure, working links, images that belong, and a page a reader can scan without effort. Clients hand you raw material — a Google Doc, a transcript, a voice note typed up by someone in a hurry — and what comes back from you has to be consistent with everything else they have ever published. That consistency is the product.

Work in passes, never in one heroic read-through. Structure pass: apply the heading hierarchy (one H1, H2s for sections, H3s under them — never bold text pretending to be a heading). Cleanup pass: paste from Word or Docs as plain text first, then apply formatting inside the editor, so stray fonts and mystery spacing never reach the page. Link pass: every link clicked, every link pointed at the live page, not a draft or a staging URL. Media pass: images in the right places, alt text written, file names following the client's convention. Then one slow proofread, out loud if you can.

Two judgment rules protect you. First, you format what you are given — you do not silently rewrite claims, prices, or dates. If a number looks wrong, flag it to the client in your update and let them decide; a VA who quietly “fixes” a price owns the mistake when it was actually correct. Obvious typos are the exception if the client has told you to fix them on sight — get that instruction once, in writing, and it becomes part of your system. Second, if the client has no style sheet, start one: heading case, comma habits, words they always spell their way. A one-page style sheet you built is early proof you think in systems.

Email platform work: build from the brief, send nothing unchecked

Building a campaign starts with the brief, and the brief is a contract: audience segment, subject line, preview text, send time, the offer, the one call to action, the assets. Your job is exact execution — the right segment, not the whole list; the approved subject, not a better one you thought of; tracking switched on; personalization tokens tested with a real test send to yourself before the client ever sees it.

One rule outranks all others: you do not press send on your own authority unless the client has granted that in writing. The default flow is build, test, approval, schedule. Most campaign disasters are not writing failures — they are build failures: the buyers-only email that went to the full list, the button linking to a staging page, the send time set in the wrong time zone, the reply-to address nobody monitors. The checklist below is how professionals catch them while they are still free to fix. Run it on every send, including the “quick ones.”

• Correct list or segment selected — and it matches the brief, not the default
• Subject line and preview text match the approved version exactly
• Every link clicked in the test send; each lands on the live page, not a draft or staging URL
• Personalization fields render correctly, with a sensible fallback when a name is missing
• Images have alt text, and the email still makes sense with images blocked
• Plain-text version reviewed — no broken tokens, links readable
• Send date, time, and time zone confirmed against the brief
• Test send reviewed and approved per the client's standing approval rule before scheduling

Website updates without breaking anything

Website work scares new VAs because the page is live and the client is watching. The fear goes away with one habit: never make your first attempt on the live page when a safer surface exists. Duplicate the page or use the CMS draft and preview modes, do the edit there, compare it against the original, then publish. Before you touch anything, check what depends on that page — menu links, buttons on other pages, an ad or an email pointing at it — because your small edit lives inside a web of other people's links.

Image swaps cause more quiet damage than any other update. Match the replacement to the original's dimensions and shape before uploading; a tall photo dropped into a wide banner slot will crop someone's head off on mobile. Compress large files first — a 6 MB hero image slows the whole page for every visitor. Keep the client's file-naming pattern, write fresh alt text that describes the new image, and do not delete the old media file until you have checked nothing else on the site still uses it.

Text edits follow the same discipline: read the entire paragraph, not just the sentence you are changing, so the edit doesn't contradict the line after it. After publishing, view the page the way a stranger does — logged out, and at phone width — and click every link in the sections you touched. Finally, keep a change log: date, page, what changed, who asked. It takes thirty seconds, and the first time a client asks “when did this change?” you will be the person who simply knows.