CASE STUDY · MEDIA & PUBLISHING · BAHRAIN

Out of WhatsApp.Into One Workflow.

A media and publishing company was running video requests, approvals and corrections through chat. In about three months, Dtech turned its basic ClickUp workspace into one production workflow, from request to publication.

INDUSTRYMedia & publishing
LOCATIONMiddle East
SERVICEClickUp consulting & implementation
DURATIONAbout 3 months
PLATFORMClickUp
LANGUAGESEnglish and Arabic

The client is not named. Workspace screens on this page are recreated with sample data.

01Who they are

A Traditional Publisher,Now Making Video.

The client is a media and publishing company in the Middle East. Like many traditional publishers, it has moved into digital publishing and video production, and every new format adds more people to coordinate: reporters, marketing, approvers and the production team.

Reporters

Raise requests and follow their own assignments.

Marketing

Requests coverage and reviews it before production.

Marketing manager

First approval stage.

Video production head

Second approval stage, then assigns the crew.

Production team

Shoots, edits and delivers each piece.

The roles that every video request passes through.

02Where they started

Requests, Approvalsand Corrections in Chat.

There was no central process for media production. Requests, feedback, approvals and corrections moved across different channels, including WhatsApp. The company already had ClickUp, but it worked as a basic to-do list, so it was hard to track progress, know who was responsible or keep everyone aligned.

M
Media Team14 members
Sara · Marketing

Can we get a video from the business forum on Tuesday? 🙏

Ali · Reporter

I can cover it. Who approves?

Mona · Marketing manager

👍

1
Ali · Reporter

Footage is in the drive, folder “forum_final”

Khalid · Production

Which drive? Also need the logo version from last week

2
Sara · Marketing

Small change: can the title say “Highlights”? Also cut the second speaker

3
Ali · Reporter

Is this published yet??

4

1An approval given as an emoji, with no record of what was approved.

2Files and versions scattered across drives.

3Corrections buried in the conversation.

4Nobody can see where an assignment stands.

A group chat like the team’s, recreated with sample messages.

WHAT THE TEAM NEEDED

Centralise incoming media and video production requests.

Set clear approval stages and responsibilities.

Improve coordination between reporters, marketing and production.

Track each assignment from request to publication.

Give each team member a clear view of their own work.

03What we built

One List,Nine Stages, Every Role.

Dtech worked closely with the company’s main contact to understand how production really ran, then designed the ClickUp workspace around it. The setup went through two versions before landing on a single Video Productions List.

VERSION 1Two Lists
RequestsProduction

The first setup split incoming requests from production work.

VERSION 2One Video Productions List
Video Productions

After further discussion, the whole lifecycle moved into one List, so each request stays one task from start to finish.

Every request is one task that moves through the same stages. Two of them are approvals, so the marketing manager and the video production head each review the work at the right point.

01New Request
02Production Approval
03Team Assignment
04In Progress
05Shooting
06Editing
07Internal Review
08Client Review
Published
Rejected

On top of that List, each role gets its own view. Reporters see only their assignments, department heads see the whole pipeline, and the calendar and map keep upcoming events and locations in view.

Video Productions/Reporter ViewRole-based view
Assignee: Me
NameStatusEvent dateLocationDeadline
Business Forum Coverage – Highlights VideoSHOOTINGNov 18ManamaNov 20
Heritage Week FeatureTEAM ASSIGNMENTNov 22MuharraqNov 25
Tech Expo InterviewsEDITINGNov 12SakhirNov 15
Food Festival HighlightsINTERNAL REVIEWNov 9RiffaNov 13
BILINGUAL FIELDS
Event Dateتاريخ الفعاليةLocationالموقعDeadlineالموعد النهائي

Recreated with sample data. Switch tabs to see each view.

Custom fieldsApproval stagesWorkflow automationsRole-based viewsCalendar viewMap viewDashboardsBoard viewEnglish and Arabic labels

04How the team adopted it

Built AroundHow People Actually Work.

Technology must reflecthow people actually work.

The workflow was shaped with the company’s primary contact and refined through further discussions. At a later review, the media workflow was still running, and the client had added its own automations to post messages when specific events happened.

AT A LATER REVIEW
The media workflow was still in use.
The client had built its own automations that post messages when specific events happen.
Supporting CRM, client data and subscription tracking modules were set up, but not all were confirmed as fully adopted.
WHAT WE DID
Worked with the main contact

Mapped the real production process before configuring anything.

Iterated the structure

Moved from two Lists to one Video Productions List after review.

Built approvals into the flow

Separate stages for the marketing manager and the video production head.

Kept it bilingual

English and Arabic labels and fields wherever possible.

05What changed

From Chat Threadsto a Production Line.

The company now runs media production in one structured workflow. Requests, assignments, approvals and publishing sit in one place, each person can see their role and progress, and different views give different ways to follow the work.

STAGES9

from new request to published

APPROVALS2

review stages built into the flow

VIEWS4

Calendar, Map, Board and Dashboard

DURATION~3

months to implement

BEFORE
  • Requests sent through WhatsApp and other channels
  • Approvals given informally in chat
  • Corrections lost in long threads
  • ClickUp used as a basic to-do list
  • No view of where an assignment stood
AFTERLIVE
  • Every request is a task in one Video Productions List
  • Two approval stages built into the workflow
  • Clear roles from reporter to production head
  • Calendar, Map, Board and Dashboard views
  • Each assignment tracked from request to publication

Outcomes are described from the delivered workflow and a later review. Time savings were not measured.

06Lessons learned

What We Would Tellthe Next Newsroom.

01

Technology must reflect how people work

A workspace only sticks when it matches the way the team already produces work.

02

Map approvals before automating

Understanding who approves what, and when, had to come before building automations.

03

Involve end users early

Direct input from reporters, production staff and department heads makes workflows more practical for everyone.

IN SHORT

By moving beyond basic task management, the company gave its media production clearer responsibilities, structured approvals and full visibility from the first request to final publication.

NEXT CASE STUDYFrom Business Case to Live Project

How a gaming and esports organisation connected business case approvals, projects and reporting in one ClickUp PMO system.

Read the Story

BOOK THE FIRST HOUR

Let theResults Speak.

As a ClickUp Diamond Partner, we are measured on real adoption, not hours billed. If the first session works, your team will ask for more. If it does not, we stop there.

Book a Free Hour
Your free first hour60 minOnline
PICK A DAYRIYADH · GMT+3
AVAILABLE TIMES
Chat on WhatsApp