Social media approval status tracker

Choose states that represent real handoffs

Start with drafting, awaiting review, changes requested, approved, held, scheduled, and published. If your team needs fewer states, combine them only when the owner and exit condition remain clear. “In progress” is usually too broad: it can mean someone is writing, waiting, revising, or troubleshooting.

For each state, record the next owner and action. Awaiting review belongs to the decision owner; changes requested returns to the creator; held belongs to whoever can resolve the blocker. Scheduled and published describe execution after approval. A failed publication should be visible as a separate exception rather than leaving the item marked published.

Track the item and its approved version

Give each item a stable identifier and record brand, destination account, publication window, current version, decision reference, and blocker. A spreadsheet can hold this information, but it needs a consistent update convention. A status alone does not prove that the asset currently linked in the row is the asset someone approved.

When a material edit occurs after approval, update the version and move the item back to the affected review stage. Keep the prior decision reference for context. Do not overwrite the old approval text with a new date or copy it to another target. Where audit retention is required, choose a system appropriate to that requirement; a manually edited sheet is not an immutable audit log.

Worked example: one campaign with two targets

Campaign SUMMER-14 has a LinkedIn variant LI-14 and an Instagram variant IG-14. LI-14 v2 is approved with its own link and asset. IG-14 v3 remains changes requested because the image uses the wrong date. The campaign summary says “one of two variants approved” rather than a single green status.

The scheduler updates LI-14 to scheduled after confirming the target and window. If its publication fails, the tracker records the error and recovery owner. It does not revert the whole campaign to drafting. When IG-14 is revised, its new version is reviewed independently unless the shared campaign message has also changed. This preserves a useful distinction between content decisions and delivery problems.

Keep the register trustworthy with a short reconciliation

Before the weekly planning meeting, compare upcoming rows with the decision records and scheduling system. Find approved rows without a version, overdue review states without an owner, and published rows without confirmation. Correct the source of each mismatch instead of assuming the more optimistic status is right.

Avoid maintaining several competing trackers. Declare which system owns the item state, and use summaries only as views or manually dated snapshots. If an exported sheet is shared with a client, label when it was produced and where current decisions live. A smaller register maintained consistently is more useful than a detailed one whose timestamps and owners cannot be trusted.

Use the tracker to prioritize the next action

Sort upcoming work by decision deadline and blocker, not only publication date. A post due later may require an earlier specialist decision than one publishing tomorrow. At handoff, name the person who will update the state after acting. If updates lag behind reality, simplify fields and repair the update convention before adding another dashboard.

Where this fits in Slash Social

See approval workflows in Slash Social. These resources describe operating practices you can adapt to your team. Review current product availability before choosing a rollout.