For a bank or insurance company, which a supervisory authority oversees, a website works better when every page has an owner, the terms are the same everywhere and the navigation never changes. The study shows how this structure is built and what it costs.
| Industry | Supervised businesses |
|---|---|
| Challenge | Accountability |
| Decision environment | Supervised |
| Complexity | High |
| Service | Business website |
This study is for businesses that a supervisory authority oversees, such as a bank or an insurance company. The auditor, the partner and the customer want to see who is responsible for a piece of information before they trust it. In such a business this is solved by how the site is organized, not by the style of the writing. This study describes a method of organizing. It is not a certification.
The organization works in a field where information must be correct, have a known source and match how the organization really works. The website is read by legal advisers, the risk management team, auditors and external partners. Each reads it for a different reason. The lawyer looks for the exact wording. The partner looks for the person to call. The auditor checks that what is published matches what is done.
Here the website is not a brochure. It is one of the places where the organization shows in public who does what. When a page says something different from the policy document, a question comes up and someone has to answer it.
The site has grown over the years. Different people added pages at different times, usually in a hurry and without a shared plan. Everyone did their job with care. What was missing was one person responsible for the whole.
The site uses different words for the same thing. One page says "procedures", another "policies", a third "guidelines". The reader cannot tell whether these are three documents or one. Responsibilities are not visible: many pages have no owner, and it is hard to find out who approved a paragraph.
The statements are hard to check. They have no date, they do not say which document they come from, and they do not say when they were last reviewed. For an auditor this is a real obstacle.
So the website needs explaining. In an audit, the organization explains its own site instead of showing it as evidence. That takes time and weakens the picture of order the organization works hard to build elsewhere.
Four constraints shape every decision. The sector has strict requirements, and the legal team has the last word on wording. Every piece of information links to a document, a date and a role. Responsibilities are written as they are in reality. A misreading is expensive, so every ambiguity counts as an error.
The website shows the organization exactly as it works and leaves nothing open to interpretation.
There is also a practical constraint. The site will be maintained by busy professionals, not web specialists. The structure has to be simple enough for a new colleague to keep it correct without a manual.
That is why a shorter, friendlier text is not always the answer. When you simplify a responsibility, its meaning can change. The goal is for everything to be clear and correct at the same time.
First, terminology. When the same idea has three names, each reader reaches their own conclusion. One shared vocabulary fixes that. Second, accountability: every piece of information has a visible owner, so you know who stands behind it. Third, complex duties are written more simply without changing the meaning of the policy they summarize.
The fourth is the most important. The website is part of how the organization works, not only a marketing tool. A promotional site is written to attract. The site of a bank or insurer is written to be checked.
The same goes for a redesign. A new style only helps when the content has been organized first. Otherwise the old inconsistencies just look nicer and the auditor's questions stay the same. That is why we finish the structure before the design. Our process starts there.
We start from the organization, not from the pages. First we write down in plain words who is responsible for what: which role owns which topic, which documents exist, who reviews them. Then we organize the website around that map. The pages follow the roles and the recorded procedures, not the order in which they were published.
The steps are few and simple:
We list every topic the site covers and name the role responsible for it.
We agree on one shared vocabulary and write it in a short glossary for the team.
We group the content by responsibility and give each group a fixed place in the navigation.
For every important statement we write where it comes from and when it was last reviewed.
The legal staff and the risk owners approve the structure before the visual design starts.
The navigation is always the same. Anyone who finds one responsibility page knows at once where the next one is. The auditor moves through the site as through a tidy archive of documents.
Four decisions carry the most weight, and each has a cost we accept knowingly. We write them down one by one, together with what is given up. A decision taken openly at the start causes no trouble later, when the site is already published.
Decision | What it means in practice | What is given up |
|---|---|---|
One vocabulary | The same idea always has the same name, on every page | Some friendlier but less precise wording |
Structure by owner | Pages are grouped by owner, not by display topic | A more promotional home page |
Fixed navigation | Same layout and same labels for similar pages | The freedom for each page to be different |
Statements that can be checked | Every key statement has a source and a review date | Speed of publishing; each update has one more step |
The last line is the most demanding and the most useful. Every extra check makes publishing a little slower. In return, the organization has a website it can stand behind in every audit. We agree on this trade openly from the start.
The website makes checks easier. The terms are the same everywhere and the responsibilities are visible, so fewer points cause confusion. Anyone assessing the organization finds what they look for more easily. The site reads as a faithful picture of the internal procedures.
The role of the website is specific: it makes responsibility easy to see and to check. The organization's documents remain the foundation, and compliance with each requirement depends on them. The website does not replace them.
The structure is also easier to maintain. When every topic has an owner, every update has an obvious place and an obvious person to approve it. That keeps the site organized in the years ahead.
If your organization recognizes this picture, a useful first step is a short talk about who is responsible for what. You can send a project request or see how we work in different industries. A related study: aligning many teams.
No client is named. The structure matters, not the name, and a bank or insurer rarely publishes details about its own work.
Compliance depends on the practices and documents of the organization. A clear structure makes those responsibilities easier to see and to check. A good website presents them accurately and does not claim to replace them.
The organization itself. We help to organize the site, agree the terms and show the source of each statement. The wording on legal or regulatory matters is written by those who have the expertise and the responsibility.
Yes, usually. First we list what exists and who is responsible for each part. Some pages are merged, some are removed and some are written again from scratch.
It depends on the amount of content and on how fast the people doing the review answer. The business websites we build are usually finished in four to ten weeks. The pace is usually set by the first listing of responsibilities.
A clinic's website earns trust when it explains services, specialties and what happens from the first contact in plain, accurate words, and shows clearly how to book.
When an organization speaks to leadership, working teams and outside partners at once, its website works well if each audience has its own path.
A consulting firm's website works when every visitor first finds a short explanation of what the firm does, then the details.
Send a project request, or check your current website for free. We read every message ourselves.