Virtual assistant website content update requests

Key takeaways

• Use a written brief and definition of done.
• Keep approvals and escalation rules visible.
• Review quality before expanding the workflow.

# Virtual assistant website content update requests

Capture source, audience, exact change, URL, owner, approval state, and date. Separate factual correction from editorial, legal, and technical changes, then retain before-and-after evidence.

Applying virtual assistant website content update requests

A content request should identify the exact URL, changed claim, source, audience, approval state, and desired publish window. Separate a factual correction from copy editing, legal review, accessibility work, or a technical change. Before-and-after captures make a small update auditable.

Role boundary and review

The assistant can locate the page, prepare a proposed edit, and check that the supplied source supports it. The site owner approves public claims and changes with legal, brand, or accessibility implications. Keep the request and approval together instead of letting a completed edit imply that every reviewer agreed. the [services library](/services) helps define content support boundaries, while the [[provider vetting guide](/provider-vetting)](/provider-vetting) frames review ownership. [NIST guidance](https://www.nist.gov/itl/smallbusinesscyber) is a useful general reference when editors receive site access. ### Update record Keep URL, requested claim, source, before-and-after evidence, approval state, reviewer, and follow-up.