Before a serious platform is designed, someone has to answer a deceptively simple question: what kinds of information does this organization actually manage?
Most projects skip that question. They begin with pages: homepage, about, services, contact, blog. That feels familiar, but it often hides the real structure of the organization. A research initiative may manage reports, authors, funders, themes, regions, events, datasets, media mentions, and policy briefs. An NGO may manage programs, campaigns, impact stories, partners, staff, resources, grants, and volunteer opportunities. A service firm may manage services, sectors, case studies, insights, team members, lead magnets, client journeys, and proof points.
Content modelling is the process of identifying these content types and defining how they relate.
Content is not the same as pages
A page is a presentation. A content model is structure. The same content can appear in many presentations: a case study page, a homepage proof section, a sector landing page, a proposal, a newsletter, or a filtered archive. When content is trapped inside one page, reuse becomes manual. When it is modelled properly, reuse becomes natural.
This is especially important for organizations that publish repeatedly or operate across multiple programs. Without content modelling, teams slowly invent structure through copy-paste habits. One editor writes dates one way, another uses another format. One page uses “partner,” another uses “collaborator.” A program name changes in one place but remains outdated elsewhere.
Content modelling is how an organization turns scattered information into reusable infrastructure.
What a content model includes
A content model defines the objects, fields, relationships, rules, and workflows that govern content. For example, an event might include a title, description, start date, end date, location, format, speakers, registration link, capacity, topic, status, related resources, and post-event recording. A case study might include a client type, problem, solution, services used, outcomes, sector, testimonial, images, and related articles.
Good modelling is not about adding fields for the sake of fields. It is about giving the organization the structure it needs to publish faster, stay consistent, and make content useful across the whole system.
The UtterFocus modelling sequence
Why organizations skip it
Content modelling is often skipped because it is not as immediately visible as design. Stakeholders want to see pages. They want colors, typography, motion, and layouts. Those things matter, but without structure, design becomes a surface layer over future disorder.
It is also skipped because it requires decisions. Who owns this content? What counts as a resource? Should reports and articles be separate types? Do programs have sub-programs? Which fields are required? What should be archived? What should be searchable? These questions can reveal organizational ambiguity, and many teams would rather move quickly than resolve it.
What changes when modelling is done well
Editors gain confidence because they know where content belongs. Developers build faster because they have predictable data. Designers create reusable sections instead of one-off layouts. Leadership gets clearer reporting because content can be categorized and measured. Users find information more easily because filters, relationships, and archives are meaningful.
For growing organizations, content modelling also protects the future. A well-modelled system can support new languages, new programs, new audiences, new campaigns, and new integrations without rebuilding the entire site.
Content modelling questions to ask early
- What content types do we publish repeatedly?
- Which information is duplicated across pages?
- What content needs filtering, search, or categorization?
- Who owns each type of content and who approves it?
- Which content should connect to forms, CRM, newsletters, or reporting?
The hidden foundation of a better website
Content modelling is not an extra step for large organizations only. It is the foundation that determines whether a website will remain usable as it grows. A beautiful website without a content model can become difficult to maintain in months. A structured system can keep improving for years.
If your organization’s website is full of duplicated pages, inconsistent content, manual archives, unclear ownership, or slow publishing, the issue may not be design. It may be that the content was never modelled as a system.