Guides · Growty

Content approval: keep the exact version central

A clear approval concerns the text, media, account and schedule you actually intend to use.

Start with a concrete item

Gather the message, brand and intended audience before creating variants. Identify the image or video that belongs with it. Distinguish a loose idea from a draft that is ready for review. Approval of a topic is different from approval of the final wording. Naming those steps helps the owner recognise what remains undecided and avoids treating early enthusiasm as a publishing instruction.

Review the channel and context

A message may suit one channel and need changes for another. Review the actual variant, selected account and media together. Check links and the intended time as well. Do not ask a reviewer to approve an outdated screenshot after the draft has changed. Use the concrete version that is ready for the next step and make any remaining uncertainty visible before requesting a decision.

Changes require a new review

The current Growty source binds approval to the exact variant. When relevant variant data changes, existing approval is withdrawn. This supports a practical workflow: revised wording or a different schedule needs another look. Always check the visible status during use. An earlier approval is not general permission to change every detail later or to publish another version under the same topic.

Check before the planned action

Review the final variant when the date or campaign context has changed. A post prepared early can become outdated. Agree who is responsible for this final check. Have uncertain factual claims, prices and media rights reviewed before approving publication. Preparing the content makes those questions easier to identify, but does not automatically answer them or replace an accountable decision.

Separate intent from outcome

An approved variant records a decision about what may happen. After that, it still needs to be clear whether publication happened or a task remains open. Check the resulting status and any feedback. A schedule or an approval moment does not prove every external connection is configured or that a message actually appeared on the intended channel. Treat the outcome as a separate verification step.

Use a short handover

Keep the selected variant, account, schedule and person responsible for completion together. Record unanswered questions before passing the work on. When discussing a process with Growty, describe where preparation, review and execution currently become mixed up. Use a fictional example where possible. Passwords and access tokens do not belong in a contact message and are not needed to explain a workflow problem.

Editorial guide based on the current Growty source and README; connection availability remains configuration dependent. No live publishing action was performed for this guide.