Throughout the program there are a set of written reports that are due from each team. Each of these reports is intended to mimic real milestone reports that can be found across industry. Reports for updating and informing people of various backgrounds are common in industry, and developing this type of communication skill is valuable for professionals in any industry.
While the exact format of these reports varies by project, there are three major report types within the program.
The project plan is an introductory report typically due mid-way through fall semester. This report is intended to set out many of the objectives of the project and establish many of the strategies and project management tools that the team will use to be successful.
The elements of these types of reports are often found in industry in business plans, project proposals, project quotes/bids, strategic plans, preliminary design reviews, and other preparation and proposal documents. The ability to effectively communicate this type of information can prove vital for getting projects, properly anticipating how much work they will be, and executing them successfully.
Status reports are due at the end of fall semester and/or mid-way through spring semester depending on department and project. These reports are intended to provide an update to interested parties on the progress, issues, and outlook of the team. Such reports should point clearly to risks which may inhibit progress or impact the success of the project.
These types of reports are common in industry. Investors, managers, partners, stakeholders, and customers will regularly need to know how a project is progressing such that they can adapt their strategies and expectations to better align results. The ability to tactfully communicate good news, bad news, and no news is a critical skill for technical professionals and can mean the difference between a well informed organization and a misinformed one.
The final report is a technical document, due at the end of spring semester, which should encompass the total work of the team. This report should be able to stand alone as a one-stop-shop summary of the project along with firm technical details and design package for the project.
This type of report is typically an essential part of industry projects. It is a deliverable which documents what was completed, how it was performed, and what the results were including all technical design definition. When a firm, department, or contractor completes a job, a final report of the completed work tends to be an essential deliverable to the customer.
These types of reports end up being essential for future implementation, management, operation, re-creation, assessment, and troubleshooting of designs throughout industry.
The submission of a report on its due date should not be considered a draft. In industry, these reports correspond with project milestones and key communications with other parties such as customers, management, regulators, and partners. Having major errors can have serious repercussions on a career. Reports should be started early and reviewed by Project Advisors and Design Advisory Board members as early as possible to be able to address issues prior to the due date with margin.
To learn more about written reports and their requirements, see Report Requirements & Guidelines.
Some teams may find that other written reports become necessary throughout the project to communicate with the customer, receive certain resources, or satisfy project-specific milestones. Teams should work with their advisor and sponsor to determine if any of these types of reports may be appropriate for their project.
Examples of other reports which teams may encounter in their projects and in industry:
Milestone report: A report similar to a status report or final report that summarizes the efforts and results associated with a milestone within a larger project. E.g. A report due after completing a set of tests or tasks to summarize the results.
Preliminary design: A report intended to summarize the details of an early design such that it can be easily reviewed by stakeholders in a cohesive format. E.g. A technical drawing or schematic package with analysis results, commercial product data, and summary.
Test plan: A detailed document which outlines an upcoming set of tests in detail such that those involved can review them and execute them according to said plan. E.g. A set of procedures, diagrams, maps, contingencies, and safety protocol for an upcoming test.
Manufacturing plan: A document intended to outline how a part or assembly will be produced. E.g. A set of drawings, work-instructions, equipment summaries, logistics, supply chains, schedules, production work-flow diagrams, and inspections.