The challenge
Campus communication ran on printed posters, a crowded email list, and a handful of unmanaged TVs that stayed on all night. Every notice, a seminar, an exam-hall change, a placement drive, had to route through one central communications office, which became the bottleneck. Departments and student clubs improvised their own signage, and nobody knew which screens were even switched on.
What we deployed
Screens were organised into nested groups per building and department in the Digisigns CMS, with roles scoped so each department's team publishes only to its own screens. Student club submissions land in the approval queue, where the communications office reviews before anything airs. Studio layouts carry the campus feed: an announcements ticker, event countdown widgets, a clock, and a YouTube zone for lecture and event videos. Recurring notices run on daily and weekly schedules, remote power schedules shut every screen outside teaching hours, and offline email alerts plus the uptime timeline flag any screen that drops off. Bulk rename via a spreadsheet kept the 140-screen rollout organised.
Self-service without chaos
The rollout stood on three platform features: nested screen groups per building, roles scoped so a department can publish only to its own screens, and an approval queue for student submissions. Studio layouts carry the rest, a ticker for announcements, countdowns to exams and fests, a YouTube zone for event videos. Power schedules shut every screen after hours, and offline alerts catch the ones that do not come back. See education signage, the feature list, or pricing for per-screen costs.
“Clubs and departments publish their own notices now. We approve, we don't produce.”
A representative deployment story based on typical Digisigns rollouts. Details are anonymized and consolidated; metrics reflect ranges observed across comparable deployments.