For teams where every post needs approval

Rules the tool enforces

Policies that depend on people remembering them fail on the busiest day. These are enforced by the software, for every post, whoever is working:

• Only approved posts publish. There is no route from draft to live that skips review
• Approved posts are locked. Changing one means unlocking it, which sends it back for a fresh decision
• An approval window can stop a post whose review didn’t finish in time — it expires instead of publishing
• Creators can’t approve their own work; editors are excluded from deciding
• Every decision is recorded with the person, the time and what they decided

The reviewer sees exactly what will publish

A compliance reviewer approving a caption in a document is approving something that doesn’t exist yet. Here they review the post itself, as it will appear on its network — the image, the full caption, where it will be cut off, the first comment and any link — so the thing they sign off is the thing that goes out.

Feedback goes on the post: “remove ‘guaranteed’”, “add the risk warning”, attached to the exact post or image it refers to. The team’s own working notes sit in a separate tab reviewers from outside the team never see.

A record for every post

For each post, the history shows who approved it, who requested changes and what they asked for, and when. Decisions a team member recorded on someone’s behalf — a reviewer who approved in a meeting — are labelled as such, with who actually clicked. When someone asks months later who agreed to a post, the answer is on the post.

How a regulated post moves through review

1. 01The marketing team writes the post; the preview and the network checks run as it is written
2. 02It is sent for review with the rest of the month, to the named compliance or legal approver
3. 03The reviewer approves it, requests changes with a note, or rejects it
4. 04Changes are made and the post goes straight back for another decision
5. 05Once approved it is locked, and publishes at its scheduled time
6. 06If anything needs changing after approval, it is unlocked and reviewed again

What this is — and isn’t

This is a sign-off workflow: it makes sure the right person approves each post before it publishes, and it records that they did. It is not a compliance archive. Record-keeping rules in regulated industries often require archiving every public communication, including comments and replies, in a dedicated system — keep using the archiving tool your compliance team relies on for that.

Nothing here is legal advice, and no tool can make a post compliant by itself. What it can do is make sure the people who decide compliance see every post, in its final form, before it goes out.