An approved plan is not delivered work. Here it becomes a task with an owner and a deadline.
Run takes the plan you closed with the client and turns it into tasks: every production stage with an assignee, its own deadline and a visible status.
Stage with owner and deadline · Plan converted into tasks · Requests in a queue · A trail nobody erases
Task in production
Illustrative dataTask
Anniversary campaign · feed carousel
Current stage
Design — stage deadline ends today at 5pm
Stage assignee
Account designer, set when the stage opened
Illustrative data — no real brand or person.
The work exists. The record of the work does not.
The bottleneck is not a missing to-do list. It is that the whole operation depends on people’s memory — and memory does not scale, cannot be audited and goes on holiday.
The request lives in the messaging app
The request arrives as a message, the change as a voice note and the reference as a link. When someone is away, the context goes with them — because it was in the conversation, not in the system. Then the team redoes what was already finished and the client repeats what they had already explained.
A deadline with no owner
The task has a delivery date, but nobody knows who should have produced the artwork on Tuesday. The delay only shows up when the client asks — and there is no way to say where the work stopped.
Nobody can reconstruct it
Three months later, "why did we do it this way?" has no answer. What is left is the final file, without the path to it: what was decided, what blocked it and what was worth repeating.
From an approved plan to a proven delivery
The path Run organises — without pretending the operation runs itself.
“Strategy without execution is just intention.”
- The monthly plan is closed with the client.
- The plan is converted into tasks, one per item with content.
- Each task enters the production flow for its type of work.
- Stages get an assignee and deadlines calculated from the delivery date.
- Priority, status and delivery date stay visible in the list.
- Brief, guidelines and files live inside the task itself.
- Whoever finishes a stage hands over to the next one.
- Review and internal approval are stages of their own, ahead of the client’s.
- The material goes for approval and the client replies through Axis.
- Publishing is scheduled and the task trail stays consultable afterwards.
What exists today, inside the product
Every item below is in operation. Whatever is not, does not appear on this page.
Production flow stages
Strategy, social media, copywriting, design, video, review, internal approval, client approval and publishing. The task walks through them in flow order.
A deadline per stage, not only per delivery
Each stage has a start, a deadline and a duration in hours, calculated from the delivery date. The warning arrives before it is missed.
An assignee on every stage
Responsibility is not for the whole task: it belongs to whoever holds it right now. The list shows who has what in hand.
Corrections with their own deadline
Corrections have their own deadline and automatic follow-up once that deadline is exceeded.
Queued requests and internal activities
Internal requests enter a queue with an owner and a status. Activities without a client stay separate from production.
Context inside the task
Brief, copy and call-to-action guidelines, comments, attachments and final files by format. The team does not search in five places.
Scheduled publishing
Date and time per connected channel, with the status and history of each post published from the task.
Link hub with QR codes
Link spaces per client, with QR codes and access statistics, inside the same operation.
Want to see this running with your own production flow?
Talk to a specialistThe stage open right now — and the trail of a delivered task
Two illustrative screens: how work looks while it happens and how it stays consultable after delivery.
View 1 — inside the task
Illustrative dataAnniversary carousel · delivery in 3 days
Task stages
- CopywritingCompleted
Account copywriter
- DesignIn progress · due today at 5pm
Account designer
- Internal reviewWaiting for the previous stage
Coordination
- Client approvalNot started
The client replies through Axis
Material in the task
Brief, guidelines and the client’s attached references sit inside the task itself, at hand for whoever holds the stage.
View 2 — the task history
Illustrative dataShort launch video · delivered last month
- Created the task — from the monthly plan.
- Assigned the video stage to the account videomaker.
- Attached the final file and moved the task to review.
- Moved from internal approval to client approval.
In every entry
The recorded action and who took it.
A server timestamp.
If an entry disappears
The removal attempt is recorded.
Editing or deleting later
The trail only accepts additions.
Screens built for this page, with invented data. No real client, person or number appears here.
From plan to publishing, in eight steps
The highlighted step is the only one whose decision is recorded outside Run, in Axis.
Flow of a production task
Illustrative dataApproved plan
The monthly plan is closed with the client and converted into tasks.
Task created
Each item gets a client, a type of work, a priority and a delivery date.
Stages with owners
The flow distributes the stages, with an assignee and a deadline on each.
Production
Copy, design and video work from the brief and the files inside the task.
Internal review
The team reviews before showing the client; a fix comes back with its own deadline.
Client approval
Run sends and moves the task to the approval stage. The decision is recorded in Axis — by the client or by someone on the team — along with who responded.
Publishing
Once approved, the material is scheduled and published on the connected channels.
History
The task trail is preserved, with a server timestamp on every entry.
Eight-step flow: approved plan, task created, stages with owners, production, internal review, client approval through Axis, publishing and preserved history.
No task is approved automatically. Run prepares and sends; the client decision happens in Axis and comes back to the task. Internal team review and approval are recorded separately from the client’s approval.
Run, Atlas, Axis and Oracle do not do the same thing
Confusing them is expensive: duplicated work on one side, ownerless decisions on the other.
“Each system answers a different question.”
Run — execution
Who does it, by when, at which stage and what has already been delivered. This is where work moves and where every stage has an owner and a deadline.
Atlas — content
Concentrates creative production. Each client’s planning and editorial calendar also exist in Run, which organises who produces what, at which stage and by when.
Axis — the client
Where the client talks, follows along and approves. Run sends material for approval, but whoever decides replies in Axis.
Oracle — consulting
Structures the diagnosis, the proposal and the follow-up of the consulting journey. What is decided there becomes work here — today with no automatic handover between the two.
A boundary this page respects: external client approval belongs to Axis. Run has internal team review and approval — never the client decision.
What already talks to Run
Three links that exist in code today — and what each one does, without overstating.
Only integrations verified in code, with the file checked, appear here. Complementarity without automatic exchange is not presented as an integration.
The operation also opens on the phone
The app exists for people who need to update a stage without going back to the desk — and it is honest about what it does not do.
See what is yours today
The task list with stage, deadline and priority opens on the phone as it does on the computer.
Update from wherever you are
Finishing a stage, commenting and attaching material can be done during a shoot, on the road or at the client.
Check the context
Brief, guidelines and task links are available on the same screen, without asking anyone to resend them.
Get the notice
On Android, deadline and movement notifications arrive through the app, without depending on a message group. On iOS, on-device notices do not exist yet.
Anniversary carousel · delivery in 3 days
Design
In progress · due today at 5pm
The Android and iOS app opens the same operation and requires an internet connection — there is no offline mode. The denser management screens are still better on a computer.
What Run guarantees and what it does not do
Execution without control becomes just one more place to lose information.
Each organisation sees only its own
Separation by organisation is enforced in the database itself, not only on screen.
A trail you cannot edit
Creation, stage change, assignment, attachment, sending for approval, client reply and publishing enter an append-only trail with server date and time.
Files validated on upload
File uploads are validated for type and size. Request attachments sit in private storage and open through a temporary link.
Data subject rights
There is a data export routine and a defined retention period for the operational trail.
Run does not approve on the client’s behalf. If the internal team turns on automatic scheduling for a client, that client’s approval in Axis schedules the post on its own, at the configured time on the connected channels, and moves the task to the posting stage.
Operations that gain from stage, owner and deadline
If work passes through several hands before it ships, Run has something to solve.
Agency with a social media flow
Copy, design, video, review and publishing in a chain, for several clients at once, with a deadline in every pair of hands.
In-house marketing team
Requests arriving from many areas that need a queue, an owner and a status — instead of scattered messages.
Coordination that needs the whole picture
Whoever answers for many clients sees what is late, what is waiting on the client and what is due today.
Teams that must prove delivery
Operations that need to show what was done, when and by whom — with a trail that does not depend on screenshots.
System plans
Three tiers that unlock more as you grow. On Max, you get access to everything.
Essentials to start
- Tasks per client with the stages of the production flow
- Assignee and deadline set for each stage
- Priority, status and delivery date per task
- Internal requests with a queue and an owner
Full operation
- Tasks per client with the stages of the production flow
- Assignee and deadline set for each stage
- Priority, status and delivery date per task
- Internal requests with a queue and an owner
- Monthly plan converted into tasks with calculated deadlines
- Send for client approval — the client replies through Axis
- Comments, attachments and final files by format
- Scheduling and publishing on connected channels
Everything unlocked
- Tasks per client with the stages of the production flow
- Assignee and deadline set for each stage
- Priority, status and delivery date per task
- Internal requests with a queue and an owner
- Monthly plan converted into tasks with calculated deadlines
- Send for client approval — the client replies through Axis
- Comments, attachments and final files by format
- Scheduling and publishing on connected channels
- Link hub with QR codes and access statistics
- Immutable audit trail for tasks and requests
- Android app with notifications, plus an iOS version
Frequently asked questions
What is Centriu Run?
It is Centriu’s operational execution system. It converts the plan closed with the client into tasks, distributes the production flow stages with an assignee and a deadline on each, and preserves the history of what was delivered.
Is Run just a task manager?
No. A to-do list keeps the item and the date. Run keeps the stage the work is at, who is responsible for it right now, that stage’s deadline, the context the person needs to execute it and the trail of what happened.
What is the difference between Run, Atlas and Axis?
Run handles execution: stage, owner, deadline and delivery, and also holds each client’s editorial planning. Atlas concentrates creative production. Axis is where the client talks, follows along and approves.
Does the client approve material inside Run?
No. Run sends the material for approval and moves the task to the matching stage; the decision is recorded in Axis and comes back to the task. Besides the client, members of the agency team can also record that decision in Axis, and who responded is stored. Inside Run there are internal team review and approval, recorded separately from the client’s approval.
Does Run work on a phone?
Yes. There is an Android and iOS app that opens the same operation; on-device notifications, for now, reach Android only. It needs an internet connection: there is no offline mode. The denser management screens are still more comfortable on a computer.
Can work be tracked by sprint?
No. Run does not work with sprints, story points or epics — and older material that promised this was wrong. Tracking is by stage, stage deadline, delivery date, priority and task status.
How does task history work?
Every relevant move — creation, stage change, assignment, comment, attachment, sending for approval, client reply, scheduling and publishing — enters an append-only trail with server date and time. It cannot be edited or deleted by the team and has a defined retention period.
How does the monthly plan become tasks?
When the plan is activated, each day with a channel and a format becomes a task with its stage deadlines already calculated; a day without a channel or format is skipped, with a warning. When the client requires approval of the plan, only days that were approved, or had no approval request, become tasks.
Does Run have automations?
There is no automation builder for users to create their own rules. What is automatic is already defined: converting the plan into tasks, calculating each stage’s deadline from the delivery date, deadline warnings, follow-up on pending corrections and, when the internal team turns this option on for a client, scheduling the post as soon as that client approves in Axis.
How is each organisation’s data separated?
Each organisation sees only its own data, and the separation is enforced in the database. Uploads are validated, request attachments sit in private storage behind a temporary link, and there is a data subject export routine.
See your production flow inside Run.
We build the demo around the type of work your operation delivers — the stages, the deadlines and the trail, with no commitment.