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. When something stalls, the reason and the side that caused the wait are recorded.
Stage with owner and deadline · Plan converted into tasks · Delay with a named owner · 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 problem
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.
What changes
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.
- If work stalls, the reason and the responsible side are recorded.
- The material goes for approval and the client replies through Axis.
- Publishing is scheduled and the case stays consultable afterwards.
Features
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.
Delays with reason and owner
A pause records the reason and the side that caused the wait — client or team. Corrections have their own deadline and automatic follow-up.
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 specialistDemonstration
The stage open right now — and the case already closed
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
Recorded wait
4h waiting for client material — the stage deadline was recalculated and the reason stayed in the history.
View 2 — the case reconstructed
Illustrative dataRecovery campaign · closed last quarter
- Context — a drop in reach identified in the monthly report.
- Decision — switch the main format of the month to short video.
- Execution — 12 tasks created; two stalled waiting for the client.
- Result — delivery completed with 6 days of accumulated delay.
What worked
Brief filled in before opening production.
Internal review before showing the client.
What got in the way
Client material only requested at the design stage.
Reusable in similar cases
Ask for the client material right when the task opens.
Screens built for this page, with invented data. No real client, person or number appears here.
How it works
From plan to publishing, in eight steps
The highlighted step is the only one that leaves the team’s hands — and it happens outside Run.
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. Whoever approves or asks for a change is the client, in Axis.
Publishing
Once approved, the material is scheduled and published on the connected channels.
History
The task trail is preserved and the case can be reconstructed later.
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. Inside the team there are internal review and approval — which never replace the client’s word.
Where each one fits
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 a delay gets an owner.
Atlas — content
Concentrates creative production and the editorial calendar. Run does not replace creation: it 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.
In the ecosystem
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.
Away from the desk
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
Deadline and movement notifications arrive through the app, without depending on a message group.
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.
Control and limits
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 in a private area
Client files sit in private storage with validation on upload — not on an open public link.
Data subject rights
There is a data export routine and a defined retention period for the operational trail.
Run does not decide on its own: it does not move a stage, approve or publish without a person asking it to. It also does not evaluate anyone’s performance automatically.
Who it is for
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.
Starter
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
Pro
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
Max
EverythingEverything 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
- Chronological replay of closed cases
- Immutable audit trail for tasks and requests
- Android and iOS app with notifications
Questions
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, records delays with a named owner 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. That combination is what lets you reconstruct a case months later.
What is the difference between Run, Atlas and Axis?
Run handles execution: stage, owner, deadline and delivery. Atlas concentrates creative production and the editorial calendar. Axis is where the client talks, follows along and approves. The three complement each other, but do not replace each other.
Does the client approve material inside Run?
No. Run sends the material for approval and moves the task to the matching stage, but whoever approves or asks for a change is the client, in Axis — and the reply comes back to the task. Inside Run there are internal team review and approval, which do not replace the client’s word.
Does Run work on a phone?
Yes. There is an Android and iOS app that opens the same operation, with notifications. 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, velocity 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.
What is case replay?
It is the chronological reading of work that has already closed: context, decisions, the tasks created, where waits happened, the outcome and what was recorded as reusable in similar situations. It is not a screen recording or a video — it is the timeline assembled from what was registered.
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 and follow-up on pending corrections.
How is each organisation’s data separated?
Each organisation sees only its own data, and the separation is enforced in the database. Files sit in private storage with validation on upload, 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.