If you run an agency, you already know the real bottleneck isn't making the content — it's getting a client to actually look at it, react to it, and sign off before a posting deadline slips. BittuAI's approval pipeline is built around that reality, not around an idealized version of it.
Where content sits before it's "done"
Every content item you produce lives inside a Campaign, which lives inside a Channel, which lives inside a Domain — your agency's overall workspace. That hierarchy exists so a client only ever sees the Channels and Campaigns that belong to them, never your other clients' work, and so you can hand off review at whatever level makes sense: a single video, a week's batch, or a whole campaign at once.
The review step is a real gate, not a formality
A content item doesn't move to delivery on its own. It sits in a preview state where you (and your client, if you've given them access) can watch the actual rendered output — not a mockup, the real file — before it's marked approved. That preview/approval gate is what actually enforces quality control on an automated pipeline: automation only helps if there's still a checkpoint before something goes out with your client's name on it.
When a client wants a change
Clients don't need to email you a marked-up screenshot and hope you remember every note. There's a dedicated editing-request intake built for them: they leave a note against the specific content item, and that request becomes something you and BittuAI's video pipeline can act on directly, tied to that exact piece of content rather than floating in a separate thread.
What happens after approval
Once something is approved, it's ready for delivery through whatever channel that Campaign is set up for. Nothing renders or re-renders again outside that approval boundary — the same gate that caught issues before delivery is the same one your audit trail is built on, so you can always see who approved what, and when.
Why this matters more as volume goes up
A single video, you could review by eyeballing it in a shared folder. A pipeline built to run multiple channels and topics at real volume can't rely on that — it needs a structured place for review to happen and a structured place for feedback to land, or approvals become the actual production bottleneck instead of the editing itself. That's the problem this pipeline is built to solve.