“Approved” should identify what someone saw, which decision they made and what may happen next. It should not mean that silence was interpreted as permission.
Separate drafts, previews and releases
A draft is work still being shaped. A preview shows that work in context without making it public. A release is a named set of approved changes prepared for a specific environment. Keeping those states separate makes it possible to move quickly without pretending every save is safe to publish.
Ask a specific question
“What do you think?” creates an open-ended review. Ask whether the structure answers the brief, whether factual details are correct or whether this exact version may move to production. Different questions belong at different stages.
Show the change, not only the result
A reviewer needs to know what is new, what was removed and what remains unchanged. A visible diff, short release note and working preview reduce guesswork—especially when several people contribute.
Record who approved what
The project should retain the version, approver, time and target environment. This is useful accountability, not ceremony. It also lets an editor return to the approved baseline when a later idea does not work.
Make publication a human action
Tools and agents can prepare content, run checks and assemble releases. A person with responsibility for the website should approve consequential publication. That boundary is central to Mavie Studio’s workflow.
