Principle
Give technical terms one local definition
Shared words can hide unshared models.
When it fits
- A specialist message uses a term that different teams interpret differently.
When to avoid it
- Local definitions should not silently redefine regulated or system-standard terminology; use authoritative definitions where they exist.
Why it matters
When a term is necessary and potentially ambiguous, define it once where first used or point to the authoritative glossary. Prefer the team's actual domain term over a simpler but inaccurate substitute. Do not expand every familiar acronym mechanically.
An example
'Activated = change request completed and BP data written to active area; it does not mean DRF replication finished.'
Check your result
The term has one operational meaning for this message.
Keep this limit in mind
- Local definitions should not silently redefine regulated or system-standard terminology; use authoritative definitions where they exist.
Connected ideas
Useful withWrite known, unknown and assumed as different states
Evidence and sources
Supports
CDC guidance recommends active voice and familiar audience language, with technical terms explained where needed.
Technical precision should not be removed when it is necessary for the task.
Description and Examples of Index Items · Core items 6 and 7