Guides · Growty

Scheduled or published? Make the final step visible

Publishing tasks do not all follow the same technical route. Make it clear what is prepared, approved and still awaiting action.

Define the intended outcome

Record what completed means as well as when a message should be ready. Is the draft reviewed, is a task waiting for someone, or is the post visible on the channel? Those are different outcomes. Use consistent wording in your process so a colleague does not infer that publication happened simply because a date appears in a calendar. Make the final verification someone’s responsibility.

Check the available route

The current Growty approach distinguishes connected publishing from manual completion. The usable route depends on the channel and its configuration. A channel name in a design does not mean every permission or requirement is ready. Check the configured connection and visible status before relying on an automatic next step. Keep unresolved access or configuration work separate from the content approval itself.

Treat manual work as a real task

When someone must publish manually, provide the final text, media and destination clearly. State when the task is due and who is responsible. Have the person check that the correct account is active. Agree how completion will be reported. A reminder helps organise the work but is not evidence that the content appeared. Keep the handover complete enough to avoid last-minute guessing.

Connect scheduling with availability

The local Growty version uses a scheduler in the running process. In that setup, availability of the app and associated server matters. For a different installation, ask explicitly how execution is managed. Do not assume continuous operation from the calendar view alone. A schedule is useful when the conditions for carrying it out are understood and someone can recognise when those conditions change.

Review a failed action before retrying

Inspect the feedback before trying the same post again. Check whether anything already appeared on the intended channel and whether you still have the correct variant. Resolve uncertainty about duplicate content first. The aim is a deliberate recovery step, not repeated execution without review. Record failures in the work overview so the responsible person knows what remains to be done and can make an informed choice.

Discuss the process with an example

Prepare a fictional brief with one brand, one draft and the intended outcome. Identify who writes, reviews and publishes. Then describe where handover or feedback is missing. This makes a Growty discussion concrete without promising every channel is fully connected or presenting future inbox, analytics and advertising features as available services. Access credentials are not needed to explain the workflow and should remain private.

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