Institutional news doesn’t ask permission

An award for a professor, an incident on campus, a visiting dignitary: none of it waits for a slot to open up in Marketing’s calendar or for the development team to find time to publish it. And behind each of those stories isn’t a single person, but a team of journalists spread across faculties, campuses and centers — each with their own agenda, their own source, their own pace.

The challenge isn’t writing fast. It’s publishing fast without the institutional voice dissolving across too many different hands.

Real autonomy for a distributed team

Griddo gives every writer full autonomy to create and publish, with real-time preview on any device before anything goes to production, native multi-language and multimedia publishing, and storytelling tools with digital-magazine quality. When the news can’t wait, the system is built for that too: urgent or crisis communications, not just an editorial calendar planned weeks in advance. That same immediacy comes with a safety net: every publication is versioned, and rolling back to the previous version for an urgent correction doesn’t put the rest of the site at risk.

The same autonomy covers language: a research story or an international recognition doesn’t have to wait for a second translation round to reach audiences outside Spain — it gets translated and reviewed inside the same editor.

At Universidad Pontificia Comillas, 60 people from 31 departments, faculties, institutes and chairs generated 2,262 publications in a single month, spread across 8 sites — with 2,101 page configurations made by the team itself. The revealing figure isn’t the volume: it’s that the team builds its own pages instead of queuing requests for someone else to build them. As Carmen Pedruelo, Head of Digital Communications at Comillas, sums it up: “A change that now takes us ten minutes used to take up a whole morning.”

And it isn’t an isolated pattern: across the instances Griddo measures, over 99% of that activity happens on business days — daily use of the system, not a one-off content push before a deadline.

Institutional consistency without manually reviewing every piece

Whether an intern or the Vice-Rector’s office publishes it, the visual result is the same: the Embedded Design System applies brand identity by design, before anyone reviews anything. On top of that base, approval flows are configured once, by site or by section — not piece by piece —, so oversight doesn’t depend on Communications leadership reading every story before it goes out.

As Lucía Tornero, Director of Communications and Institutional Relations at Comillas, sums it up: “We don’t have to be watching over consistency, the narrative, because Griddo already guarantees it.” Consistency stops being a daily review task and becomes a property of the system.

Visibility without being glued to a screen

Communications leadership doesn’t need to approve every publication from every campus — they need to know what’s been published, where and by whom, without chasing every team by email. Griddo’s mobile app offers the full ecosystem activity log from a phone: pages published, edited or deleted, drafts in progress, SEO changes, translations, image replacements — filterable by site, content type, date or action, in a timeline or per-person view. Built for marketing leadership, communications leads and digital transformation teams who need ecosystem visibility without being chained to a desk.

We already covered in detail how this traceability layer changes leadership work in beyond content management: leadership governance with Griddo App; here the focus is what it means for whoever runs communications for a distributed team, not for the university’s leadership as a whole.

How to talk about this with your CIO and your CMO

Operational limitations

Where this fits

This article is part of Griddo Journal’s Governance cluster.

Back to the Hub: Centralize Without Suffocating →

If you’re a CIO, start here → — why this same model reduces shadow IT instead of creating risk.

If you’re a CMO, start here → — why governance accelerates campaigns instead of slowing them down.

Your next step

If your team is still waiting its turn to publish a story that can’t wait, let’s talk about how much of that wait is avoidable.

Request a demo →