Step 3: Review, Revise and Approve Project Scope Document
Once the Project Scope Document has been completed, it should be distributed for review to all relevant stakeholders and decision makers. You should request that they read it thoroughly and provide comments and questions. This will help you ensure everything is clear to those who are going to be involved. If necessary, have a meeting to review the document.
Regardless of the how spectacular, intricate, and fascinating your Project Scope Document is, the question you will typically hear most often at this stage will be similar to this: "what will it look like?" Sometimes people will be able to articulate this clearly and ask: "Can I see the new design before I review this document, so I can see the context in which the content and functionality will fit?" Regardless of how they ask to see the designs first, it is important to explain that designing design of the GUI is not part of the planning phase; it is part of the production phase. While visually oriented people may not appreciate that, explaining it in terms they might (designing a product without approved definition will cost time & money) will help.
Discuss the Project Scope Document to whatever degree is required and make revisions until consensus is reached among stakeholders. This document will be the master plan for your efforts. If some aspect of your project is not explicitly captured inside, it will not be delivered. That being said, there will still be people who give their approval, then contact you shortly thereafter with requests for modifications and additions.