The documentation process for DDC systems can be complex because of software flexibility provided in the design of control sequence languages. The software must be documented to provide users with a clear understanding of the control sequence. The documentation process becomes even more complex when a programmer uses flow diagrams to generate control sequence line code. Too often the programmer fails to ensure that the code exactly follows the flow diagram logic so that others are able to read the line code. If this is not accomplished it will be difficult and costly for others to make future modifications. One concept for preventing this documentation problem is the use of block sequence language techniques, This procedure eliminates the conversion step from flow diagram to line code. The blocks defined on the diagram become the blocks defined in software. This technique results in one document for design, installation, and future modifications, thus simplifying and reducing costs of the DDC documentation procedure, The foflowing paper will explain this concept.