RE: Business Glossary

Subject: RE: Business Glossary
From: Rochelle McAndrews <rmcandrews -at- csiu -dot- org>
To: 'wondersofone' <wondersofone -at- gmail -dot- com>, 'TECHWR-L Writing' <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 14 Aug 2015 11:35:06 -0400

Basically, do what is suitable for your information consumers.

Our glossary needs are simple, for internal use (not client-facing), and not mired in legalities. Support documents are maintained on a server to which support staff have access, so I link to the central glossary from other support documents. Staff can easily click the glossary link to open a read-only PDF.

Several instances of the same initialisms/acronyms have dual meanings depending on our software context. It's important that our staff are aware of the differences in definition when clients have support needs, so I include each meaning as a separate record. For example:

Term Software Meaning

LOA Human Resources Contextual: Leave of Absence

LOA Financial Systems Contextual: Level of Approval

Keep in mind the users' needs, and whenever possible, get their reviews/input.

Rochelle McAndrews

-----Original Message-----
From: wondersofone [mailto:wondersofone -at- gmail -dot- com]
Sent: Thursday, August 13, 2015 3:57 PM
To: TECHWR-L Writing
Subject: Business Glossary

Hi All. We currently have terms and definitions scattered within individual policy & procedure docs. The company is looking to create a central glossary to eliminate contradicting definitions.

What is best practice in terms of using and maintaining a glossary like this? May end up as an Excel file.

Should all terms within a P&P doc simply reference the glossary going forward?

And what if there are differences in the definition of a term due to context? We do have different lines of businesses within the company. Just define only using the most common "denominator" in the glossary?

Appreciate any insight.

This message may contain privileged, confidential information that is exempt from disclosure under applicable law. If you are not the addressee indicated in this message or if it does not apply to you or your organization, you may not copy or deliver this message to anyone. In such a case, please delete this message and reply to the sender immediately. Thank you.
Learn more about Adobe Technical Communication Suite (2015 Release) |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Business Glossary: From: wondersofone

Previous by Author: Re: Recommendations for programmer's guides
Next by Author: Re: "Software Technical Writing is a Dying Career"
Previous by Thread: RE: Business Glossary
Next by Thread: "Software Technical Writing is a Dying Career"

What this post helpful? Share it with friends and colleagues:

Sponsored Ads