approval gates
2
posts without sign-off
0
The project in facts
FormatA content pipeline
Control2 human approval gates
Outputa private client channel
Translationinto the clients' language
Our own system
Vendor updates should reach the clients.
The platform vendor keeps publishing updates and how-tos, but they never reach the clients: wrong channel, wrong language. Tracking and retelling them by hand is the work that always gets postponed.
We built a pipeline: it watches the vendor's site for new material, picks what's relevant, prepares a translation and publishes to a private client channel. A human controls the release at two points — nothing goes out without sign-off.
Context
What was in the way
- ✗Vendor updates never reached the clients — wrong channel, wrong language
- ✗Tracking the news by hand is the work that always gets postponed
- ✗There was no one to retell the updates to clients
Diagram
An update’s path to the client.
Vendor sitemonitoring
Selectionrelevance
Gate 1human: topics
Translationclients' language
Gate 2human: text
Client channelpublication
What's inside
Principles.
Principle
A human in the loop
The pipeline prepares, a human decides: two approval points before publication.
Autonomy
No reminders needed
New material is spotted without manual checks.
Replication
Any source
The same scheme repeats for another vendor or another client channel.
Results
Before → after
Before
After
Updates got lost on the vendor’s site
They reach a channel clients actually read
Monitoring and retelling by hand
The pipeline does it itself
Uncontrolled auto-posting is a risk
Two human approval points