# When a Service Website Needs a Glossary and When a Simple Rewrite Works

A practical guide for Malaysian service businesses deciding whether a confusing term should be rewritten, defined in context, or kept in a shared glossary, with a reusable decision table and a fictional content review.

Published by Blackstone Intelligence.

## Start With the Reader's Question, Not the Term

A service website usually carries vocabulary that made sense inside the business before it reached the page. A term can be perfectly accurate and still leave a visitor unsure what happens next. The useful first question is not "is this word correct?" but "what is the reader trying to decide when they meet it?"

Take a fictional Kuching-based interior fit-out company, which we will call Rumah Fitout for this guide. Its services page lists "design intent coordination" between the concept description and the enquiry button. The phrase is not wrong. It is simply doing no work for a reader who wants to know whether drawings, site measurements and installation are included. That is a rewrite case, not a glossary case.

A second fictional example: a KL-based managed IT support provider lists "endpoint hardening" in a service tier. A reader comparing tiers may genuinely need the term to understand the difference between packages. Rewriting it away could remove a real distinction. That is a define-in-context case.

A third: a Malaysian logistics software vendor uses "SLA" across its pricing page, support page and contract summary. The abbreviation is standard in its market and appears in documents the buyer will sign. That is a glossary case, because the same term must mean the same thing everywhere.

Sorting terms this way keeps the work proportionate. Most pages do not need a glossary. Some need one or two sentences of plain explanation. A smaller number need a shared definition that survives across pages, teams and sales conversations. The rest of this guide gives you a way to tell them apart, then shows the method applied to a fictional review.

## A Three-Case Decision Table You Can Reuse

The table below is an author heuristic, not a published standard. Treat the thresholds as prompts for discussion rather than rules. It is designed to be copied into a content review document and filled in per term.

Case 1: Rewrite. Use this when the term has a plain equivalent that loses no meaning, when it appears once or twice, and when the reader does not need to recognise it later. Example: replacing "design intent coordination" with a sentence naming the drawings, site checks and installation steps included. The test is whether a reader could act on the sentence without asking a follow-up question.

Case 2: Define in context. Use this when the term carries a real distinction the reader is comparing, when it appears in a specific section only, and when a short parenthetical or following sentence would resolve it. Example: "endpoint hardening (the baseline security settings we apply to each laptop and server before handover)". The definition lives next to the term, not on a separate page.

Case 3: Shared glossary. Use this when the same term appears across several pages, when different team members write about it, when it appears in documents the customer will sign or receive, or when two internal teams use it slightly differently. Example: "SLA" used on pricing, support and contract pages. A glossary entry is only worth creating if it will be referenced more than once and kept current.

A simple scoring prompt for each term: How many pages does it appear on? Does the reader need to recognise it later? Would a plain phrase lose a distinction the buyer cares about? Does more than one person write about it? Two or more yes answers point toward a glossary; one points toward defining in context; none points toward a rewrite.

## Why a Glossary Is a Maintenance Commitment

A glossary is not a one-off writing task. It is a small reference system that has to stay aligned with the pages that use it. If a service page changes its package structure and the glossary still describes the old tiers, the glossary becomes a source of contradiction rather than clarity.

That maintenance burden is the main reason to be conservative about creating one. A glossary works best when it is short, owned by a named person, reviewed on a schedule, and linked from the pages that rely on it. It works badly when it is launched as a comprehensive dictionary of every technical word the business knows.

This is also where the choice of web design services matters more than it first appears. A glossary needs a stable page structure, a way to link terms from body copy, and a review step that survives a redesign. If the site is rebuilt every year with new templates and no content ownership, glossary entries tend to drift or disappear. Planning the glossary as part of the site's content structure, rather than as a page added at the end, makes it more likely to stay accurate.

A practical middle path is a short "terms we use" section on a single page, limited to terms that genuinely recur. Anything that appears once belongs in the sentence where it is used. Anything that appears in a signed document should be defined in that document as well, not only on the website.

## When a Simple Rewrite Beats a Definition

Rewriting is usually the cheapest and most durable fix, and it is often skipped because teams treat their existing wording as settled. A rewrite is the right move when the term is internal shorthand, when it was borrowed from a supplier's documentation, or when it describes a step the reader does not need to name.

A useful rewrite test: read the sentence aloud to someone outside the business and ask them what happens next. If they can describe the next step in their own words, the sentence is doing its job. If they ask what a word means, you have found a rewrite candidate.

Rewriting also helps when a term has picked up several meanings inside the business. If "onboarding" means account setup to the sales team and training to the delivery team, no glossary entry will fix the page, because the underlying disagreement is operational. The page needs one clear sentence about what actually happens in the first two weeks, and the internal teams need to agree on it first.

Keep rewrites small and reviewable. Changing one sentence at a time makes it easier to confirm that the page still matches what the business delivers. Large simultaneous rewrites of a whole service section tend to introduce new ambiguity while removing old ambiguity, and nobody can tell which change caused which problem.

## A Fictional Content Review, Step by Step

Here is the method applied to Rumah Fitout, the fictional fit-out company introduced earlier. The review covers one services page and one pricing page. No real client, result or review is involved.

Step 1: Collect the terms. The reviewer lists every phrase on the two pages that a non-specialist might not recognise. In this example: design intent coordination, site survey, variation order, handover pack, and defect liability period.

Step 2: Count where each term appears. Design intent coordination appears once. Site survey appears three times across both pages. Variation order appears on the pricing page and in the sample quotation linked from it. Handover pack appears once. Defect liability period appears on the pricing page and in the contract summary.

Step 3: Apply the table. Design intent coordination is rewritten into a plain sentence about drawings, site checks and installation. Site survey is defined in context on first use, then used consistently. Variation order goes into a short shared glossary because it appears in a document the customer receives. Handover pack is rewritten as a list of what the customer gets at the end. Defect liability period goes into the glossary and is also defined in the contract summary.

Step 4: Assign ownership. One person owns the glossary, one person approves changes to the pricing page, and the reviewer records the date of the last check. This is the step most often skipped, and it is the one that determines whether the work survives the next six months.

Step 5: Re-read the pages as a buyer. The reviewer reads the services page and pricing page in sequence and notes any remaining question. In this fictional review, the remaining question is about payment timing, which is a content gap rather than a terminology problem. That distinction matters: not every confusing page needs a glossary or a rewrite. Some need a missing paragraph.

## Where Terminology Work Sits in a Wider Website Project

Terminology decisions are small, but they interact with the rest of a website project. A glossary page needs a place in the navigation, a link pattern from body copy, and a review step in the publishing process. A rewrite needs an owner who can approve the new wording. Neither works well as an afterthought once the design is signed off.

This is the kind of structural question that a web design services engagement can address alongside page templates and content structure, particularly when the site has several service pages that share vocabulary. For businesses in Sarawak, a web design Kuching engagement may also involve local service descriptions and location pages, where consistent terms help readers compare offerings without re-reading definitions on every page. Teams working across Peninsular Malaysia sometimes look at web design KL options for the same reason: the terminology problem is rarely confined to one page.

Blackstone Intelligence, operated by Blackstone Consultancy Sdn Bhd, lists website development among its services alongside AI automation, workflow automation, software development and AI consulting. That service list is context for who is offering the work, not evidence that any particular terminology approach produces a particular outcome. The decision about whether to rewrite, define or gloss remains an editorial judgement about your readers.

A sensible sequence is: settle the terms first, then design the pages around the settled wording. Doing it the other way round tends to produce polished layouts filled with phrases nobody has agreed on.

## A Short Checklist Before You Publish

Use this checklist as a final pass on any page that has been through a terminology review. It is a set of prompts, not a certification.

One: every term that survived the review has a reason to be there. If nobody can explain why a term is kept, rewrite it.

Two: each defined term is defined where the reader first meets it, not only on a separate page.

Three: the glossary, if one exists, is short enough that someone will actually maintain it, and it names an owner.

Four: the same term means the same thing on the services page, the pricing page and any document the customer receives.

Five: rewrites have been read aloud to someone outside the business, and that person could describe the next step.

Six: the page has been checked for gaps that look like terminology problems but are actually missing information, such as payment timing or what happens after an enquiry.

Seven: the review date and the reviewer are recorded, so the next pass has a starting point.

None of these steps requires a large budget. They require a decision about each term and a named person to keep the decision current. That is the whole discipline: rewrite what is merely internal, define what the reader is comparing, and reserve the glossary for terms that must stay consistent across pages and documents.

## Further reading

See [Blackstone Intelligence’s web design services](https://www.blackstoneintelligence.com.my/web-design-services) for the provider’s published information.

Blackstone Intelligence is a technology consultancy based in Kuching, Sarawak, and operated by Blackstone Consultancy Sdn Bhd. It provides AI consulting and automation, web design and development, custom software development, and digital marketing services.

Official website: [Blackstone Intelligence](https://www.blackstoneintelligence.com.my/).