Skip to content
TrendSuite

Publishing

Posting times and cadence

What the cadence editor actually governs (the default time for a post you compose) and why it deliberately does not drive content-plan timing.

The cadence editor sets the default time offered when you compose a post yourself. That is what it does, and this page exists because the obvious assumption about it is wrong.

What it governs

A handful of weekly slots (three by default) and a timezone. When you open Posts → New post, the next open slot is what the composer offers you. Change it per post whenever you like.

What it does not govern

It does not set the times inside a content plan. This surprises people, so here is the reasoning rather than just the rule.

A fortnight plan places well over a dozen posts across six platforms under per-platform daily caps. A cadence is a handful of weekly slots: three by default. Those slots cannot hold that many posts: honouring the cadence literally would either drop most of the plan or stack it up on the same hour.

And the fan-out's per-platform times are a deliberate stagger: LinkedIn in the morning, X at midday, Instagram in the evening. Collapsing those onto one shared time produces exactly the identical-cross-post pattern the stagger exists to avoid.

So the two are genuinely different mechanisms. Plan times stay editable per post on the plan's Schedule tab and on the calendar.

Choosing slots

Pick times you could plausibly be awake for. The value of a cadence is not algorithmic optimisation; it is that you stop re-deciding "when should this go out" forty times a month.

Timezone

The cadence carries its own timezone, so a schedule built on a trip does not quietly shift. Check it if times look an hour off.

Last updated September 11, 2026