Multi-format brief intake
One platform, many front doors. Each type of creative request gets its own intake shape instead of being forced through one generic form, capturing exactly the fields and approvals that kind of work actually needs.
Broadcast creative teams were running briefs, production jobs and asset requests across spreadsheets, inboxes and a patchwork of point tools - while their real planning, the thing everyone actually looked at each morning, lived on Monday.com boards that nobody had the bandwidth to keep current by hand. Every status update meant someone remembering to copy it across three places at once, and reference material sat in yet another system entirely, disconnected from the brief it was meant to support. The team didn't need to be talked out of the boards they trusted - they needed everything feeding into and out of them automatically. We built a single system of record that takes a brief from intake all the way to delivered asset, and stays in two-way lockstep with Monday.com, so the board and the system of record always tell the same story.
One firehose, zero source of truth
A broadcast creative operation is a firehose of requests, and not a uniform one: editorial promos, commercial spots, kids' content, sports graphics and internal makelists each carry their own intake shape, approvers, and delivery deadline. Without a shared system of record, a brief's real status depended on who you asked, while the team's actual planning happened entirely on Monday.com boards updated by hand every time something changed elsewhere — creating drift the moment one copy of the truth changed and the others didn't catch up.
Reference material and existing assets lived in a separate silo entirely, disconnected from the brief they supported, and feedback on creative work tended to scatter across email threads instead of staying attached to the work itself. The actual creative wasn't the bottleneck — the coordination around it was. And any fix that asked the team to abandon the boards they already trusted was dead on arrival.
One home, still in sync with Monday
Creative Shop manages the full lifecycle of a creative request — brief intake, job creation, assignment, production tracking, delivery, and final asset hand-off - as one connected chain. Brief intake isn't one generic form: each type of creative request gets its own intake shape, tailored to that team's specific fields and approval chain, so a request arrives already structured for how it's actually reviewed instead of landing as free text someone has to decode. Once a brief becomes a job, it's assigned, tracked through production, and marked delivered, with briefs, jobs and assets linked together, so status resolves to one answer instead of three conflicting ones.
The system doesn't ask anyone to leave Monday.com — it keeps both sides current through bi-directional, webhook-driven sync, propagated as changes happen rather than on a batch delay. Underneath, database writes are atomic, uploaded assets land straight in S3, and the integration-heavy work — Monday sync, asset processing, SharePoint imports and disk scans, reminder emails — runs through durable queues and idempotent scheduled commands, so an interruption means work resumes rather than gets dropped or double-processed. Reference material and assets get pulled in directly from SharePoint, and feedback lives as threaded comments with @mentions on the brief itself, not in a parallel inbox.
Update a job in Creative Shop and the Monday board reflects it. Move a card or change a field on Monday and Creative Shop stays current. Neither side is a read-only mirror.
Four features, real staying power
One platform, many front doors. Each type of creative request gets its own intake shape instead of being forced through one generic form, capturing exactly the fields and approvals that kind of work actually needs.
A brief becomes a job; jobs are assigned, tracked through production, and marked delivered. Feedback lives on the work itself - threaded comments with @mentions pull the right person into the right conversation - so "what's the status of this promo?" has one answer instead of three half-answers, and creative direction never gets lost in a separate email chain.
Assets land durably in S3 from the moment they're uploaded, and the heavy lifting underneath - Monday sync, asset processing, reference imports, reminder emails - runs through durable queues and idempotent scheduled commands. If anything pauses, it resumes automatically; nothing is ever silently lost.
Reference material and existing assets are brought in via SharePoint disk scans and reference-material imports, so the team's existing libraries feed the workflow instead of sitting in a silo.
Less chasing, more creating
Creative Shop gave the broadcast creative team a single source of truth for every brief, job and asset — without making them give up the Monday.com boards they plan on. Requests arrive structured, status is always current on both sides, feedback stays attached to the work, and the integration-heavy machinery underneath is durable by design: queues drain and scheduled jobs catch up on their own, so an outage means a brief delay, never lost work.
The result is less time spent chasing status and reconciling tools, and more time spent on the creative itself.