Most publishing mistakes are not creative failures. They are the post that went to the wrong account, the link with no campaign tags, the image whose rights were never checked, the caption that was perfect in the composer and truncated on the platform. Every one of them is catchable in the sixty seconds before publish — and none of them are catchable after.

This is the checklist worth running before any post leaves your queue. It assumes you are using a scheduler; the same pass works manually, it just takes longer.

What the composer already catches

Before you run a manual pass, know what the tool is already checking. PostHub's composer shows a launch checklist on the right-hand panel as you draft, and it covers the mechanical failures:

• Destinations picked — at least one account selected for the post.
• Content length — the draft has to clear a five-character floor and fit the tightest limit among your selected destinations.
• Media attached — platforms that require media (Instagram, TikTok, Pinterest) will refuse a text-only draft, and the composer flags it before the schedule is attempted.
• Plan allowance — the post counts against your monthly per-platform limit on Starter and Professional.
• Platform-specific requirements — YouTube needs a video file; a poll needs options; a carousel needs slides.
• Hashtag volume — a warning when the count climbs high enough to look automated.
• Schedule slot — the time is in the future, inside your plan's scheduling window, and not in a slot that is already full.

The composer also runs a preflight before anything is scheduled: if a platform's own rules would refuse the post — a caption over the limit, a missing required field — the schedule is blocked with the reason, in plain language, before it enters the queue. That message is your first signal that something structural is wrong.

What the composer cannot check is everything that requires a human: whether the voice is right, the link is correct, the media is cleared for use, and the account is the one you meant.

The copy pass

Read the post as if you were the person seeing it in their feed, not the person who wrote it.

Voice check. Does this sound like the brand, or like a social media manager having a productive morning? The AI captions guide covers building a voice reference so drafts arrive in your register rather than generic; the check here is whether the finished post still sounds like you after the last edit.

First line. On most networks, the first line is the entire argument — everything after it is behind a "more" cut or a scroll. Read only the first sentence. If it does not earn the second, rewrite it before anything else.

Claim accuracy. Every number, date and name in the post. A wrong figure in a scheduled post is a wrong figure published to every network simultaneously; a wrong figure caught in the draft is a two-second fix.

Hashtag count. The composer warns when the number gets high. On Instagram, a handful of relevant tags outperforms a wall of them; on LinkedIn and Threads, hashtags carry less discovery weight than the first line does. Trim to what is functional.

Per-platform overrides. If the post is going to several networks with different character budgets, check that each override actually says what you meant it to say. The composer lets you set a different caption per destination — the check is that you used it, rather than letting the original travel everywhere unchanged.

The link pass

Links are where good posts go to die quietly.

Does the URL work? Open it. Check the destination is the page you meant, not a staging URL, not a redirect that has been changed since the draft was written, not a page that 404s on mobile.

Are the UTM parameters present? Every link in a scheduled post should carry campaign tags so the traffic lands in the right row of your analytics. A consistent naming scheme — same source, same medium, same campaign format across every post in a campaign — is what makes the monthly report possible. The scheduling guide walks through building the scheme once so every subsequent post inherits it.

Where does the link sit? Instagram does not clickable-link captions, so the post needs to say "link in bio" and point at a profile link that is itself tagged. LinkedIn and Threads carry links natively. X carries them, at a cost — a post containing a link is charged at a higher rate than a plain text post, which is worth knowing before you schedule a five-link thread.

The media pass

Rights and consent. Can you use this image, this clip, this screenshot? Licensed stock, own capture, or explicit permission — not "found it on Instagram." A rights complaint arrives after the post is live and is visible to everyone who saw the post.

Alt text. The composer offers alt text fields on the platforms that support them. Fill them in. It is the difference between a post that works for everyone and one that works for most people, and it takes thirty seconds per image.

Crop and aspect. PostHub auto-fits images to each platform's accepted window — the Meta crop range, Dribbble's exact dimensions — so a landscape photo is not rejected or badly cropped on arrival. Check the preview for each destination anyway: an auto-fit that cuts through a face is still a bad crop.

Format and size. The media requirements guide lists the current limits per platform: image counts, file types, size ceilings, video dimensions. A file that misses by a megabyte is refused at publish time, not at compose time.

Screenshots and confidential material. If the image contains an internal dashboard, a client's name, a figure that has not been announced, or a person who has not consented — do not schedule it. The queue is where that mistake is caught; after publish it is a screenshot of a screenshot.

The destination pass

Right accounts. The single most expensive mistake on this list. Open the destination rail and read the account names — not the platform icons. Two Instagram accounts connected to the same workspace are both selectable, and the post goes to every account you selected. Read the names.

Right group and timezone. If the post sits in a client group with a timezone attached, "9am" means 9am in that group's timezone, not yours. Check the slot renders at the time you actually meant.

Right slot. The calendar shows the post in context: what else is publishing that day, across which accounts, from which groups. A slot that looks free in the composer may be adjacent to three other posts competing for the same audience.

Connection health. If an account shows a reconnect prompt, the post will fail at publish time regardless of how good it is. Fix the connection before the slot, not after the failure notification. The login and account access guide covers the reconnect path.

The governance pass

Approval status. If the group runs an approval workflow, the post needs to pass review before it publishes. Check the status rather than assuming the request went out — and if the post is going to a client for sign-off, make sure the request reached them while the draft is still editable.

Lock state. If the workflow locks posts on approval, an approved post is locked against late edits. That is the point: what was signed off is what publishes. If you need to change an approved post, unlock it deliberately rather than editing around the lock.

Label. Does the post carry its campaign label? Applying it at compose time means the monthly report can filter by campaign; backfilling labels in the report week is a chore that does not get done.

Where PostHub fits, and where it does not

PostHub handles the mechanical half of this list: the launch checklist, the preflight that blocks a post the platform would refuse, auto-fitting for each destination's crop window, per-platform text overrides, the approval gate, and the calendar that shows every scheduled post in context. The first-week setup checklist covers getting the workspace into a state where this pass takes a minute rather than ten.

What it cannot do is the human half. Whether the voice is right, the claim is accurate, the media is cleared, the account is the one you meant — those require a person reading the post as if they were seeing it for the first time. The composer can tell you the post will publish; it cannot tell you that it should.

Key takeaways

• The composer's launch checklist catches the mechanical failures; the human pass catches voice, links, rights and the wrong account.
• Read the first line alone. If it does not earn the second sentence, rewrite it before touching anything else.
• Every scheduled link needs working destination, consistent UTM tags, and a placement that matches the platform — and X charges more when a link is included.
• Media: rights cleared, alt text filled, preview checked per destination, size within the platform's limit.
• Read the account names in the destination rail, not the platform icons. That single habit prevents the most expensive mistake on this list.

FAQ

How long should this pass take?

Under a minute per post once the workspace is set up: the mechanical checks are automated, the human checks are four questions. If it is taking ten minutes, the post probably needs a rewrite rather than a review.

Do I need to run this for every post, or just the important ones?

Every post. The wrong-account mistake does not distinguish between a product launch and a Tuesday filler post — and the filler posts are published with less attention, which is exactly when the mistake happens.

What do I do if the preflight blocks my schedule?

Read the message — it names the rule that would have refused the post at publish time, in plain language. The failed-publish guide covers the full set of preflight failures and how to resolve each one.