Avoid Commonly Used But Vague Terms

Some terms are so common that their use is not questioned by consultants, contractors or customers.

The assumption is that "somebody" knows what is meant by the term, even if the person reading the specification does not.

"Industry standard" is one such term. Technology changes too fast for that term to have meaning any longer. Where a standard actually does apply, the standard itself should be quoted or referenced.

"Typical" is another word to avoid. What scope is being used to determine what is typical? Replace " typical" with a specific example, or a specific description.

"Must be capable of" is a phrase that often generates quite a bit of disagreement. Does it mean that the system is capable of the function as installed, or only through the addition of options not included in the project?

Almost always the " capable of" item needs further explanation. Will it be a manual or automatic operation? Will training be required?

Where the "capable of" item is expected to be a part of the system as installed, replace be " capable of..." with " be installed and configured to provide..." and then give the additional details