What is a content approval workflow and how does it work?
Updated
Quick answer
A content approval workflow is the path a post follows until the client says yes: the agency prepares it, the client reviews it, approves or requests changes, and only then does the content move on. In LUME Hub it has two checkpoints: the script, before shooting, and the video, after editing, with notifications and a recorded conversation.
A content approval workflow is the path every post follows until the client says "go ahead and publish". The creator prepares it, the decision-maker reviews and responds (approves or requests changes), and only then does the content move to the next stage. Without a workflow, approvals get lost in scattered messages, voice notes and screenshots.
Why have an approval workflow?
- Less rework: the client comments in the right place, on the right version.
- Clear ownership: everyone knows whose turn it is.
- A record: who approved, when, and what they asked to change.
- Safe publishing: nothing goes live without a yes from whoever is responsible for the brand.
For agencies, a clear workflow also protects the relationship: when a client says "I never approved that", the record answers for you.
What are the steps of an approval workflow?
A typical workflow has four moves that repeat until the yes:
- Send: the agency sends the piece with a note.
- Review: the client reads or watches it.
- Respond: approve, or request changes with a comment.
- Fix and resend: if changes were requested, a new version goes back for review.
How does the approval workflow work in LUME Hub?
LUME Hub splits approval into two checkpoints at the right moments of production:
| Checkpoint | When | Who sends | Where the client responds |
|---|---|---|---|
| Script | Before shooting | The agency, from the calendar post | Approvals screen |
| Video | After editing | The team, from the Videos screen | Approve videos screen |
At the script checkpoint, an approval moves the post to waiting to record; a change request sends it back to script pending. At the video checkpoint, the client can comment on an exact minute, and the video moves to approved or changes requested. In every case, whoever needs to act gets a notification in the Hub.
What makes approvals fast?
- Send the script before shooting, so you change text instead of video.
- Add a short note explaining the post's goal.
- Ask the client for specific comments, with the video minute when relevant.
- Watch deadlines: the Production board shows what is with the client and what is overdue.
If the team managing your account is an agency with several clients, also see the Console and white label section.
Frequently asked questions
Why approve the script before shooting?
Because changing text takes minutes and reshooting a video takes hours. Approving the script first avoids recording something the client will reject.
Does the client need a LUME Hub account?
Yes. Clients approve scripts on the Approvals screen of their account. Video reviewers get an email invitation and sign in to the Hub, without needing the Videos module.
Is there a record of who approved?
Yes. The post keeps the script conversation, and each video keeps its approval history and comments, even if the reviewer's access is turned off later.
Can something be published without approval?
For Reels, the agency can schedule by ticking the option to schedule without client approval. It is logged, and if the client requests changes before the time, the schedule is canceled.
Still need help?Ask the Community: other users and the LUME team answer.
Ask a question