Daily article operations guide
Check brief readiness before a content VA starts drafting
A short pre-draft check keeps missing decisions from turning into avoidable rewrites.
Where the work breaks
A topic and word count are not a usable brief. The writer still needs the reader question, intended outcome, source rules, route identity, and a person who can answer exceptions.
A routine the team can repeat
Before research begins, read the brief without relying on background conversation. Mark each required field ready, unclear, or missing. Start only when the reader question and evidence boundary are clear.
What to keep in the record
Save the checked brief version, review time, open questions, and person asked. This explains delays without turning the log into a judgment about the writer.
Who decides
The assistant can identify gaps and suggest wording. The editor decides the article promise, claim scope, and whether a thin brief is safe to release.
Use this in the daily queue
Apply the check to one named article and keep the result with that article’s release record. A short, specific entry is more useful than a generic "done" status.
See the research library or plan a research support workflow.