Nobody gets flagged for one post. Accounts get into trouble for patterns: twenty posts in four minutes, the same link five times in an hour, activity at 3 a.m. from an account that has slept for a year. Scheduling is the craft of keeping your activity shaped like a person, even when a computer is doing the typing.

Spacing is the whole game

A queue is a promise about the future shape of your activity. Two settings decide whether that shape looks human:

  • The gap between posts in a troop. Real people do not post on the minute, every minute. Vary the spacing, and keep the average honest: if you would not read twenty posts in ten minutes, do not send them that way.
  • The overlap between troops. Two troops firing at once double your rate even when each one is reasonable on its own. Stagger start times so troops interleave instead of stacking.

Blowhorn shows you the combined picture across troops before anything runs, because the platform only ever sees the combined picture.

Timing: post for the audience's clock

The best time to post is when your readers are awake and scrolling, which is rarely the moment you wrote the post. Scheduling exists to separate writing time from posting time:

  • Write in batches, whenever you think clearly.
  • Post on the audience's schedule: their morning commute, their lunch scroll, their evening wind-down.
  • Keep a quiet period. An account that never sleeps reads as automation to platforms and as noise to followers. A daily gap of several hours costs nothing and buys a human rhythm.

Queues: short is safe, long is a liability

A long queue feels productive and ages badly. Links break, announcements go stale, and a platform rule can change between the day you queued a post and the day it fires. Practical rules that hold up:

  1. Queue days ahead, not months. A week is a good outer limit for most troops.
  2. Put anything time-sensitive at the front, and re-check the queue after any platform announcement.
  3. When a post fails, fix the cause before the retry reaches the front of the queue. A queue will happily repeat a mistake at scale.

A pre-flight check that takes one minute

Before a troop's first run, look at the whole day the way a platform would: total posts, biggest burst, longest gap, quiet hours. If that day looks like a person with something to say, ship it. If it looks like a script, it is one, and spacing is the fix.

This is the second article in the Product intelligence series. The first covered reading your results; the next takes up what happens when a platform changes the rules mid-schedule.