A long-standing problem in the acquisition of flight simulators has been the clear communication of requirements through the specification process. There are numerous reasons for this, including obfuscation by technical jargon, fragmentation of requirements within a specification, and a human inclination to adopt "cut and paste" approaches which may reflect the requirements of a precedent system more than those of the current system. This paper discusses an Air Force initiative to develop a hypertext-based generic guidance specification for flight simulators that attempts to address these problems. Each generic specification paragraph includes hyperlinked recommendations and rationale for specification language, verification, and options. Knowledge - based upon systems engineering principles - is embedded in logic that guides the author through the development of specifications. Since this guidance specification is embodied in a software tool that makes it relatively easy to use, the expectation is that it will be used. If it is used, the documents produced will reflect the high degree of standardization imposed by this guidance specification. It will provide a clear alternative to less-disciplined cut-and-paste approaches, and emphasize sound systems engineering practice. Standardized format and vocabulary will help avoid misplaced information and inconsistent interpretations. Localization and integration of requirements will minimize conflicts.