Summarize the following:
Once you have gathered the information for each part and written it up, you need to pull the whole thing together into one big report. Divide it into major processes and sub-processes, so it is easy to read. Use visuals where possible to clarify understanding. In addition, be sure to be as concise as possible, as many people will need to read this report. This statement does not need to be pages long. It can be a paragraph or two, as it just expresses the problem. In fact, the main part of the problem should be able to be expressed in a single sentence. Confirm your findings with team members and department sources. This step is a quality control check to ensure nothing has been omitted or misrepresented. Ask if any revisions need to be made. If you need to make revisions, change the document. Once you have made revisions, you need to send it out again, making sure to highlight the differences so your readers don't need to read the whole document again. Write out a short summary of your major findings so that they can be easily understood by readers. In most cases, the summary should be no more than two pages. Make sure to include references or links if you have created an electronic report. Create a presentation and presentation materials so that you can show your findings to the sponsoring party. If an oral report is necessary, prepare for that meeting by reviewing your findings.
Pull the information into a report. Keep it concise. Confer with your team members. Make the needed revisions. Summarize your findings. Present your report to sponsoring party.