Updated Sep 2026
Why every post starts pending
You wrote a post. You like it. And still the app makes you approve it before it can go anywhere. If that feels like a pointless extra click, this page is for you, because the click is the product.
Creation and publication are separate acts
Every post lands in Pending the moment it’s created, whether AI wrote it or you typed every word yourself. There’s no fast lane and no exception for posts you obviously meant. That’s deliberate. An audit trail with exceptions isn’t an audit trail.
Here’s what that means in practice. When a post publishes, PostSignoff records who approved it and when, and the published copy is locked exactly as it went out. That record is only worth something if there’s no path around it. The moment some posts could skip review, “every published post was approved” quietly becomes “most of them were, probably”, and the whole thing stops being evidence of anything.
So the rule is absolute. A pending post never publishes on its own, no matter how long it sits. Even approving isn’t publishing. Approving says the content is right. Publishing happens later, at a scheduled time or when you choose Post Now. Two different questions, two different decisions.
Why a missed scheduled time expires a post
If nothing publishes without a decision, drafts can wait. And they do: a pending post doesn’t expire from age. It can sit for a day or a year, and it’s still there when you come back to it, because the thing keeping it from publishing is your decision, not a timer.
There’s one case where a post expires anyway. If you gave it a scheduled time and that time arrived while it was still unapproved, it missed its publication, and it moves to Expired rather than going out late.
The reason is that an approval is a judgment about a moment. A post written for Tuesday morning that quietly went out on Friday would be publishing against a world that no longer exists. The deadline it mentions has passed. The offer changed. The news moved on. Expiring the miss forces a fresh look instead of letting a stale post coast out the door on momentum.
An expired post isn’t gone, and you can bring it back. Reactivating returns it to Pending, where it waits for your decision like any other draft. The mechanics of reactivation live in the reference pages linked below.
Why disconnecting an account reopens approvals
There’s one more place this shows up, and it surprises people. If you disconnect or remove a social account, any posts already approved for that platform move back to Pending instead of being left to fail at publish time. Each one carries a note explaining why.
The logic is the same as expiry. Your approval was given under specific conditions: this content, going to that connected account. When the account goes away, the conditions the approval rested on go with it. Rather than letting an old yes carry over into a new situation, PostSignoff asks you to make the decision again once things are reconnected. Unapproved drafts aren’t touched, since they never had a decision to invalidate.
What this assumes about how you work
Right now you’re probably both the creator and the approver. That’s fine, and it’s how most people start. The gate still earns its keep, because the pause between writing something and approving it is the review, even when both hats are on the same head.
Nothing in the model requires them to be. The record names whoever approved each post, and the approver doesn’t have to be the person who wrote it. A draft can even be approved by someone else before you get to it.
Either way, the point stands. The gate is what makes your approval history mean something. It’s designed to support your supervision process, and it can only do that if it applies to everything, including the post you wrote yourself thirty seconds ago.