Newsroom & broadcast systems
One newsroom,
from the pitch
to the lower third.
Everything a news channel needs, in one dashboard we designed and built end to end. Reporters file ideas, editors decide, stories are written and checked, the front page rebuilds itself, the ticker keeps itself current, six social platforms go out together, and the graphic on screen comes from the story it belongs to. The handovers in between happen on their own.
- screens
- 50screens
- story stages
- 5story stages
- platforms
- 6platforms
ঢাকার খাল পুনরুদ্ধার প্রকল্প
অনুসন্ধানী প্রতিবেদন · রাফিক আহমেদ
The lower third, the crawl and the channel bug above are built in the dashboard and go out at full HD, straight into the broadcast software the gallery already uses.
THE WHOLE THING, IN UNDER A MINUTE
Follow one story through the newsroom
A headline is typed once, and the film follows it across twelve screens of the dashboard — the pitch that becomes an assignment, the article desk, the photocard that builds itself, six social accounts, the front page, the prompter, the gallery, and the revenue it is booked against. Nothing in it is retyped between screens, which is the whole argument for the product.
- Story pitches
- Story pipeline
- Article desk
- News Management Desk
- Photocard studio
- Social publishing
- Homepage builder
- Teleprompter
- Studio
- Multimedia studio
- Attendance & leave
- Revenue dashboard
Silent, about a minute, and it starts itself. Screens shown with representative story content.
One
dashboard
the whole channel runs from it
50
screens inside it
a desk for every job
5
stages per story
idea to published, tracked
6
social platforms
published to in one action
5
graphics layers
live on screen at once
Full HD
to air
straight into your broadcast software
This is the dashboard
Six of the desks a newsroom uses every day. Pick one to see it.
Swipe the row for the other desks. Six more are in the gallery below, and there are fifty screens in all.
Open this and you know where the whole channel stands, without asking anyone.
- What published today, what is waiting on a decision, what is on air this minute
- The queue in deadline order, so the thing that is about to be late is at the top
- A running list of everything the system did on its own, with the time it did it
Screens shown with representative story content, in the English-and-Bangla mix the dashboard is built for.
The work that happens on its own
Each of these used to be a person remembering, at the end of a long shift, to go and do something in another system. Now the newsroom makes the decision and the rest follows — or, where a step exists to stop mistakes, it holds until someone has looked.
An editor approves a pitch
The assignment writes itself
Headline, section, reporter, editor, priority, deadline, the brief and every file the reporter attached all move across. Nobody opens a second screen and types it again.
A reporter files the story
The desk is told, and the clock starts
It lands in the news desk queue in deadline order, the people responsible are notified, and the story's own timeline records who did what and when.
Proofreading signs it off
Publishing unlocks
Not before. The checklist is enforced by the system, so a story cannot reach readers because somebody was in a hurry.
The story is published
The front page rebuilds
It takes the slot the editor arranged for its section, and stories already shown higher up are not repeated further down.
It was marked breaking
The ticker picks it up
It joins the scroll at the top of the site at the priority it was given, and drops off by itself when its time is up. Nobody has to remember to remove it.
The social card is needed
It is already made
The design was built once. Each story pours its own headline, photograph and reporter name into it, correctly set in Bangla, at the size each platform wants.
Someone picks the accounts
All six platforms go at once
Now or at a time you set. Each account is tracked separately, a clip that breaks a platform's rules is caught before it is sent, and if one account fails you resend that one alone.
The story goes on air
The lower third already matches
The graphic takes its words from the story itself, so what is on screen and what is on the site come from the same place rather than drifting apart. Timed graphics leave the screen on their own clock.
Agency copy arrives
It is translated and waiting
Wire items are pulled in, prepared in Bangla and queued beside the original wording — for an editor to approve. Nothing from a wire reaches the site unread.
A story was scheduled
It publishes itself
At the minute it was set for, with its social posts going out on the same schedule. No one has to be at a desk at six in the morning.
None of it removes the editor's decision. Approving, sending back, signing off and choosing where a story goes are all still a person's call — what the platform takes away is the typing that used to follow each of those calls.
One story, one identity, all the way through
This is where most newsrooms lose their day: every handover means someone retyping what the last person already wrote. Here the idea filed at 09:42 is the same story that goes to air at 17:00 — it is never re-entered, only moved forward.
- 0109:42
A reporter files the idea
Story pitchesTitle, section, why it matters, what they will investigate, who they expect to talk to, and any documents they already have. If something similar is already on the desk, they are shown it before they send.
- 0210:05
An editor decides
Story pitchesApprove it, ask for changes with a note the reporter can act on, or decline it with a reason that stays on the record. The reporter is told either way.
- 0310:06
The assignment appears
Story pipelineAlready filled in, with the brief and the attachments. The reporter opens it and starts writing. This is the handover that normally loses an hour.
- 0414:20
The story is written and filed
WritingIn Bangla, with photographs, captions and credits, the district it happened in, and its place on the front page chosen as it is written.
- 0516:48
The desk and proofreading clear it
News desk, then proofreadingThe checklist has to be complete before the publish button will work. Anything sent back comes with a note, and the reporter sees exactly what to fix.
- 0617:00
It goes everywhere at once
PublishedLive on the site, in its slot on the front page, in the ticker if it is breaking, out to the social accounts someone ticked, and up on the gallery wall as the graphic that announces it.
And the rest of the building
Six more desks. Open any of them to read the screen at full size.
Everything it covers
A news channel is more than a publish button. Twenty-four capabilities, grouped by who uses them — all built and delivered.
Getting the news out
The desks reporters and editors sit at every day.
- The article desk
- Headline, standfirst, body, photographs, video, tags, district and guest bylines — with a preview of exactly how a reader will see it.
- Sections and sub-sections
- Build the structure of the site, give each section its own place in the menu, and rename one without leaving old stories mislabelled.
- Scheduled publishing
- Set a story to go live at a chosen minute and it does, with its social posts on the same schedule.
- Photo and video galleries
- Picture sets and video collections published as their own pages, plus a straightforward desk for single clips.
- Reader polls
- Ask readers a question, close it on a schedule, and show the result on the page.
- Search across everything
- Staff find any story, picture or page from the top of the dashboard. Readers get search built for Bangla, not bolted on.
Putting it on screen
The gallery side of the building.
- A graphics library
- Build lower thirds, breaking plates, headline cards and the channel bug in a visual editor, and keep them ready to use.
- Five layers at once
- A new lower third replaces the old one and the channel bug stays put through all of it — the way a gallery expects it to behave.
- Graphics that fill themselves
- Point a field at the story and the reporter's name, the headline and the section arrive on screen without anyone typing them twice.
- Live data on screen
- Weather and market-style boards that refresh themselves, and keep showing the last good numbers rather than going blank if a source stops answering.
- Remote guests
- Send a link; the guest appears as a source in the mixer with nothing to install. Their picture goes straight to the gallery.
- Keyboard operation
- Space to take, one key per transition, number keys for sources. An operator works at the speed of a real gallery.
Reaching the audience
Everything that happens after publish.
- The front page builder
- Lead slot, section blocks, photo stories, videos, polls and most-read, arranged by dragging, previewed, then published.
- Six platforms, one action
- Any number of accounts on each, the right format for each, your own wording per platform if you want it, and a result you can see per account.
- Caught before it fails
- A clip that is the wrong length or shape for a platform is flagged before it is sent, rather than failing quietly afterwards.
- Accounts that need attention
- When a connection stops working you are told on the dashboard, not three days later when someone notices the posts stopped.
- Social cards on tap
- Design the card once; every story fills in its own headline and picture, properly set in Bangla.
- The wire desk
- Agency copy pulled in, prepared in your language, and held beside the original for an editor to approve before it is used.
Running the place
The parts a manager uses rather than a journalist.
- Staff accounts
- Create an account, hand over a temporary password once, and the person is made to change it the first time they sign in.
- Roles that actually hold
- A reporter reaches their own work and nobody else's. The rule is applied every time an action is taken, not merely hidden from the menu.
- Your org chart
- Company, branch, department and designation kept as proper lists, so the same desk cannot end up spelled three different ways.
- A task board
- Boards and columns for everything that is not a story — events, equipment, rotas, planning.
- Notifications
- Assigned, approved, changes requested, declined, mentioned — delivered to the person it concerns, about the thing it concerns.
- A record of everything
- Who moved a story, who approved it, who sent it to air and when. Readable months later, even after someone has left.
Six platforms, and what each one really allows
Posting is one action, and each platform receives it in the format it actually wants. The right-hand column is the part most proposals leave out.
| Platform | Formats built | Worth knowing |
|---|---|---|
| Posts, link cards, photos, video, Reels and StoriesEach format is sent on its own — a Reel can never go out as a Story by accident | Each format is sent on its own — a Reel can never go out as a Story by accident | |
| Photos, carousels, Reels and StoriesInstagram has no plain video post, so a video goes out as a Reel shared to the feed | Instagram has no plain video post, so a video goes out as a Reel shared to the feed | |
| X | Text, up to four images, or one videoX charges for posting through its service — the cost is yours, and the screen says so | X charges for posting through its service — the cost is yours, and the screen says so |
| Text, link cards and single imagesPosting as a company page needs LinkedIn's own approval first, which they grant on request | Posting as a company page needs LinkedIn's own approval first, which they grant on request | |
| YouTube | Full videos and Shorts, with playlistsCustom thumbnails need a verified channel, which is a one-off step on YouTube's side | Custom thumbnails need a verified channel, which is a one-off step on YouTube's side |
| TikTok | VideoTikTok keeps new apps' posts private until it reviews them — a one-off wait, stated plainly | TikTok keeps new apps' posts private until it reviews them — a one-off wait, stated plainly |
Where they started, and where they are now
What they were dealing with
A newsroom running on separate tools. Stories in one place, the front page edited by hand, the ticker updated by whoever remembered, posts copied into six apps one at a time, and the gallery on its own equipment entirely. Every handover meant typing the same thing again, and at any given moment nobody could say where a story had got to.
How we approached it
We built one newsroom instead of connecting several. A story keeps a single identity from the idea a reporter files to the graphic that announces it on air, and each step hands the next one real work rather than a copy of it. Where something genuinely could not be done honestly, the screen says so instead of pretending.
What they have now
A channel that one dashboard runs. Ideas come in, editors decide, stories are written and checked, the front page rebuilds itself, the ticker keeps itself current, the social accounts go out together, and the graphics on screen match the story they belong to — because they came from it.
Bangla set properly, not merely supported
Bangla set properly, which most platforms get wrong. The right typeface reaches every Bangla character even in a sentence that mixes Bangla and English, lines are given room so the marks above and below a letter are never clipped, and letters are never squeezed together where they would collide.
ঢাকার খাল পুনরুদ্ধার প্রকল্প: তিন বছরে কতটা এগোলো?
DSEX সূচক বৃদ্ধি পেয়েছে — একই বাক্যে বাংলা ও ল্যাটিন, প্রতিটি নিজস্ব ফন্টে।
Notice the line height: the vowel signs above and the ্র below both have room. Anything tighter clips them, which is why the platform never uses a tight leading or negative tracking anywhere Bangla renders.
We can build this for your channel
Tell us where your newsroom types the same thing twice — the handover between the desk and the gallery, the front page someone edits by hand, the posts copied into six apps one at a time. That is usually where the first version pays for itself.