About the firm
A major international professional services company specialising in real estate, infrastructure, energy and natural resources with more than 22,000 employees across 60+ countries, create a high volume of global publications, reports and thought leadership.
Intro
Updating old content should take about 50% of your time when done correctly. Which means that if you’re a content creator, you should spend half of your time reviewing the content you’ve already published to check if the information is still accurate. That’s a lot of manual work. Especially when the same content is repeated across multiple assets: boilerplates, customer logos, quotes, footers… It can quickly get out of hand.
We spoke with Chris who works in design at the company about this. For them, updating +100 assets had become a real headache until they implemented Global Content Modules across their content.
The firm ran into three familiar challenges:
- Content quickly became outdated once it was published.
- Brand and legal consistency were hard to maintain across regions.
- Updating Docs meant hours of repetitive, manual work.
So far, to date, they have:
"With Global Content Modules, we don't have to go back in and change multiple docs time and time again."
Chris Bicker, Graphic Design Manager
The challenge: Repetition, inconsistency and time lost to updates
Before using Global Content Modules, the company relied on duplicated content blocks for things like footers and boilerplate messaging. Each update meant manually revisiting previously published documents and hoping nothing was missed.
“It was a lot of replicating the same blocks,” Chris explains. “We’d publish documents, then have to remind ourselves to go back and update them later. It was very time-consuming.”
Over time, this led to inconsistencies, especially in footers, where copyright dates, legal text and links varied depending on when a document was created.
“We’d been creating documents for so long that our design route had changed. That’s where inconsistencies started creeping in.”
The solution: a single source of truth with Global Content Modules
As soon as Global Content Modules became available in Foleon, the team saw an opportunity.
“We knew straight away it would be a massive time-saving feature. So we just dived straight in.”
The team started by modularising their footers, splitting them into multiple blocks. Core elements like copyright text, privacy policy links and brand statements were turned into Global Content Modules, centrally managed and automatically updated across all documents.
“All our current and future documents now use these modules. It means we can keep information up to date much more easily.”
Scaling consistency across regions and legal entities
Beyond footers, the company also uses Global Content Modules for boilerplate content, including different legal entity versions per region.
“We’ve got different versions of our boilerplate depending on where the document is published. Canada has a different legal entity to the UK, for example. Having modules makes that much easier to manage.”
This modular setup allows the team to scale content production without sacrificing accuracy or brand governance.
The impact: less manual work, more confidence
By moving critical content into Global Content Modules, the firm has:
- Reduced time spent manually updating Docs
- Improved consistency across global content
- Minimized the risk of outdated legal or brand information
- Created reusable templates that teams can trust
The bottom line
With Global Content Modules, the business has replaced repetitive manual updates with a scalable, future-proof content system. Which resulted in greater consistency, less rework, and more time for the design team to focus on creating high-quality, global Foleon Doc.
And they’re not stopping there.
“Seeing how other organisations use Global Content has definitely inspired us. It’s something we’ll continue to build on as we scale.”
Ready to stop updating the same content over and over?
Book a demo and see Global Content Modules in action.
.png)
.png)
