. Class and type of service designators must be validated. As the documentation and construction come closer and closer to reality, it may be necessary or appropriate to make additional PRACTICAL IP AND TELECOM FOR BROADCAST ENGINEERING AND OPERATIONS releases. These should be clearly labeled with a new version number, such as version 1.1, similar designator, dated, and maybe even timed, depending on circumstances and potential requirement to maintain coordinated work to continue. It is also advisable to maintain a change record summarizing the changes included in each release, why changes were necessary, and the specific section and page where the changes were made. FINAL DOCUMENTATION RELEASE Final documentation should be revised and updated upon comple- tion of all work and proof of performance of all equipment, software, facilities, and services. Ideally, there should be some form of post mortem akin to the design review that formally examines the oper- ational status, functions, features, and capabilities of the finished project in light of the original design goals outlined in the first drafts and succeeding versions of the overall documentation. Logically this should occur at a point in time where all capital expenditures have been recognized and all increases and reductions in operating ex- pense are known and stabilized. The final documentation should be archived as well as made avail- able on a website. As such it becomes the reference information for ongoing operations, including paying bills, trouble resolution, service restoration, facilities scheduling, and other day-to-day details re- quired by the business. CHANGE AND CHURN Moves, adds, and changes are a way of life in today's business world. Telephones, computers, and other equipment used to support con- tent transport must be in the right place at the right time given the business operation at hand. If the documentation covering the initial project is properly scoped and created, it can support day-to-day operations without change. For example, 