Explain technical terms with their meaning and the action available
A service description should connect a term to a practical use. For CMS, explain that it is a content-editing system, then state who can change which information.
GOV.UK's language guidance recommends retaining necessary specialist terms and explaining them on first use. Apply that principle by connecting terminology to the reader's task. (GOV.UK clear language)
Keep terms useful for search and comparison
Pair a term with an explanation when readers need it to compare proposals or other services. Use consistent names for the same feature throughout the page.
Explain more than the abbreviation
Define an abbreviation on first use and explain its context. A heading listing SSL, SEO, and CMS needs copy explaining their respective roles. Where precision matters, describe the actual action instead of relying on a loose everyday analogy.
Write the operation and scope behind the feature name
Specify what the service provides and what the user can do. Adapt these copy examples to the actual system being described.
| Term-only statement | Example of a specific explanation |
|---|
| CMS support | Staff can edit opening hours in the management screen |
| Responsive design | Text and image layout adjusts to the screen width |
| Booking form | Submit preferred dates; a reply from the shop confirms the booking |
Separate capabilities from predicted outcomes
Submitting preferred dates and reducing phone workload are different claims. A statement about operational improvement needs evidence about the workflow. Keep feature descriptions distinct from unsupported promises of more inquiries.
Test whether readers can make the intended decision
Ask readers to identify the available work, price, and next step. Record terms that cause confusion and misunderstood scope, then revise those explanations.
Use researched questions to improve the copy
Inquiry records and interviews can identify missing explanations. GOV.UK's research guidance combines existing evidence, interviews, and observation, while treating unsupported opinions as assumptions to test. (GOV.UK user-needs research)
See Customer personas and website copy for deciding what to publish. Record subsequent questions and align the terms and service scope across Japanese and English versions.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To build a website that explains service terminology and practical use, give SpreadSite a try!
Build a website with SpreadSite →