Dtech — Case Study: 20 IT Teams, One Workspace

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.

Media Operations/ Video Productions

Reporter View Calendar Map

Assignee: Me

Name Status Event date Location Deadline
Business Forum Coverage – Highlights Video SHOOTING Nov 18 Manama Nov 20
Heritage Week Feature TEAM ASSIGNMENT Nov 22 Muharraq Nov 25
Tech Expo Interviews EDITING Nov 12 Sakhir Nov 15
Food Festival Highlights INTERNAL REVIEW Nov 9 Riffa Nov 13

Reporters see only their own assignments and the details they need.

INDUSTRY Media & publishing
LOCATION Middle East
SERVICE ClickUp consulting & implementation
DURATION About 3 months
PLATFORM ClickUp
LANGUAGES English and Arabic

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.

Roles in the Workflow

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.

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.

WHAT THE TEAM NEEDED

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 1 Two Lists

Requests | Production

The first setup split incoming requests from production work.

VERSION 2 One 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.

01 New Request
02 Production Approval
03 Team Assignment
04 In Progress
05 Shooting
06 Editing
07 Internal Review
08 Client 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.

BILINGUAL FIELDS

Video Productions/ Calendar

November 2026

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

WHAT WE DID

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.

STAGES 9

from new request to published

APPROVALS 2

review stages built into the flow

VIEWS 4

Calendar, Map, Board and Dashboard

DURATION ~3

months to implement

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.