How to write a VA daily update your client can act on

Make the next decision easy to find

A useful work update helps your client understand what is complete, what needs attention and what will happen next. It does not need to describe every click or fill a page. Agree on the timing and channel with your client, then use a consistent structure they can recognize.

This is a Boogie editorial template for virtual assistants. Adjust it to your role, reporting requirements and agreed hours. A daily message may suit an active operations role; other work may need a different rhythm.

Start with outcomes, then explain the blocker

GitLab’s public engineering-communication guidance describes short asynchronous updates that summarize completed work, blockers or risks and link back to the relevant work item. That is a documented practice from a remote company, not evidence that a particular reporting cadence improves every VA relationship. Read the original GitLab guidance.

For your own update, replace a vague activity such as “worked on the CRM” with a verifiable outcome such as “updated the records assigned for today; two still need a service-area decision.” Link to the authorized task or record so your client can check the detail.

Copy this format

• Reporting period: Date and agreed time zone.
• Completed: The finished outcome and where to find it.
• Still open: What remains, with its current status.
• Decision needed: A specific question, who should answer and when the answer is needed.
• Next: Your next agreed priority and expected handoff.

If there is no blocker, say so. If a task is incomplete, keep it out of the completed section. State whether a delivery time is confirmed or an estimate. Use counts only when they come from the actual records.

An example from appointment support

Illustrative update; all counts below are example data.

Reporting period: Wednesday, agreed Pacific Time shift.

• Completed: Confirmed tomorrow’s three scheduled estimate visits and saved the notes in the linked CRM records.
• Still open: Two inquiries are waiting for service-area confirmation. No visit has been promised.
• Decision needed: Can we accept projects in the two listed ZIP codes? Please add the decision to the restricted task before my next calling block.
• Next: Once confirmed, I’ll follow up with those inquiries and continue the approved lead list.

The message makes a boundary visible: the VA has completed confirmations, while the client still owns the service-area decision. There is no need to repeat customer phone numbers or private details in the summary when an authorized record link provides the context.

Do not wait until the daily update for urgent issues

Agree which situations need immediate escalation and who is available to handle them during your working hours. A same-day schedule conflict may need a direct message through the approved channel. A routine improvement suggestion can wait for the weekly conversation.

After escalation, record what happened and the agreed next step in the relevant task. The daily update can point to that record without creating a second, conflicting account of the decision.

Keep the reporting process useful

After the first week, ask your client which parts helped and what was missing. If the report repeats a dashboard without adding decisions or context, shorten it. If recurring blockers keep appearing, use the next one-on-one to agree on a clearer rule or handoff.

For broader setup, use our remote-team onboarding guide. If you are exploring a role with Boogie, visit careers for the current application route. If you are hiring, start with the administrative-assistant role page to define the support your team needs.