Template

Sample weekly report for managed VA support.

A weekly report should make accepted work, blockers, QA notes, pending approvals, and next actions easy to review.

Volume, accepted tasks, notable deliverables, and where evidence can be reviewed.

Sampled work, corrections, repeated issues, and SOP updates.

Client decisions, access requests, scope changes, and sensitive actions waiting on review.

Download a simple copy-ready version to set the weekly review habit before work expands.

Use the Markdown version when you want a cleaner recurring status document with tables.

Use the RTF version when you want an editable report that opens cleanly in Word or Google Docs.

Report rows

A simple weekly operating rhythm.

Adapt these rows to the buyer workflow so completed work, blockers, quality notes, and approvals stay reviewable.

Section	Buyer question answered	Sample content
Reporting period	Which dates does this report cover?	September 7-13, 2026.
Owner / due date / status	Who owns each open item, when is it due, and what is its current state?	Ops Manager, due September 16, status: waiting on access approval.
Work completed	What was actually done this week?	42 tickets triaged, 18 reply drafts prepared, 3 help-center edits queued.
Accepted work	What met the agreed criteria?	35 items accepted; 7 returned for missing context or policy confirmation.
QA sample	What did the delivery owner inspect?	Five drafts and two escalations sampled against tone, facts, and approval rules.
Rework and SOP updates	What changed because of mistakes or learning?	Added refund-language checklist and new escalation tag.
Blockers	What stopped progress?	Missing HubSpot field access; unclear approval owner for billing exceptions.
Pending approvals	What does the client need to decide?	Approve reply template, grant report export access, confirm holiday coverage.
Next actions	What happens before next report?	Complete template update, run first approved reply batch, review queue volume.

Next step

Choose a quick inquiry or a saved assessment with this workflow summarized for follow-up.