how to write methodology in engineering report

• U of T Home
• Faculty Home

Engineering Communication Program

Methodologies

The Methodology is one of the most important and neglected sections in engineering writing. In some documents, such as an undergraduate lab report, the methodology section can be as short as a one-sentence reference to relevant section of the lab manual. But in more advanced labs, the methodology can be a very significant part of the report. In fact, the methodology is often the product of engineering related research: researchers are often looking for appropriate ways of testing or evaluating products, forces, etc., or new methods for accomplishing a required task. In a proposal, the methodology can even be the most important part of the document – the proposal argues that its method for achieving a certain task is the best.

The methodology section of report should accomplish two tasks:

• Should allow readers to, if necessary, reproduce your experiment, design, or method for achieving a task
• Should help readers to anticipate your results

Writing a methodology that does both requires attention to detail and precision. In the following example from a lab report, key elements of the method are missing:

We poured out some distilled water into the container. We then added some of mixture A. We shook the mixture and observed what happened, taking some measurements.

This statement of method is missing some essential elements:

• How much distilled water did you pour?
• How much of the mixture did you add?
• How did you shake it (length, technique)?
• What did you observe, measure?

It is also missing some key details that may or may not be relevant to the experiment:

• What was the container made of?
• How big was it?
• Did you let it settle?

The composition of the container ma be significant because the mixture may react with certain materials; its size is significant, because it may tell us how accurate your measurements were (for example, measuring 5ml in a 1000 ml container would probably result in less accurate measurements than measuring 5ml in a 100ml container). Whether or not the mixture was allowed to settle, and how much time was required, may also determine the results of the reaction.

In revising this statement of method, we want to ensure that we include all of these details to help the reader reproduce the experiment and to anticipate a set of results:

We poured 250ml of distilled water into the 1000ml glass beaker. We then added 50mg of Mixture A. We shook the mixture by gently twirling the beaker around for two minutes. We observed and recorded the changes in mixture color and transparency during our mixing process. Immediately after stopping the mixing process, we recorded the color, translucency, and temperature of the new solution; we repeated these measurements after letting the solution settle for five minutes.

After reading this method, readers should already have expectations for the results: specifically, readers should see three key readings, color, transparency, and temperature taken at three different times, during, immediately after shaking, and after settling (but no temp reading for during stage).

Passive versus Active Voice: The methods section of your report should not be written in an imperative mode – that is, you are not giving people instructions or commands, but describing what was done. But the choice between active and passive voice in your methods is a contentious one. Some readers will prefer the active voice, while others prefer the passive. Both are acceptable; deciding on what voice to use will require some audience analysis (i.e. ask your professor or supervisor). The above passage can easily and unobtrusively be converted to passive:

250ml of distilled water was poured into a 1000ml glass beaker. 50mg of Mixture A was then added to the water. The mixture was gently shaken for two minutes. Changes in mixture color and transparency during our mixing process were observed and recorded. The color, translucency, and temperature of the new solution were recorded immediately after shaking, and after five minutes of settling.

Writing Methods for Other Types of Reports: The above example was taken from a student lab report: you should apply the same attention to detail in writing methods sections for proposals and other types of reports.

The key difference between the methodology in lab report and other types of reports is that in the lab report, the method is often given in the procedure from the manual. In research reports and proposals, the method is something you devise on your own. This adds two tasks to writing the methods: organization and justification.

1. Organization: Organization of the methodology section seems simple enough: the most obvious structure is chronological. However, while organization by chronology is usually the dominant mode of organization, you may not want to describe everything in the order that you did them. For example, you might start a different stage of the methods while waiting for the previous one to finish. Trying to adhere to a strict chronological mode of organization here would not be a good idea. Organizing a methodology section well involves:

Dividing and subdividing the steps into the appropriate key stages/sub-stages Choosing headings / key words that reflect the nature of the stages (i.e. Sample Preparation) Providing an overview of the entire methodology at the beginning of the section

2. Justification: If your method is of your own making, you may also need to justify your choices. Explain clearly why you chose the method that you did – for accuracy, simplicity, etc. – and also identify the implications of using your methods. For example, there may be some limitations that you were forced to accept because of time, cost, or other constraints. Identify these, state why they are acceptable or necessary, and explain the effect they may have on your results (take these into account in your Discussion as well).

© 2024 Faculty of Applied Science and Engineering

• Accessibility
• Student Data Practices
• Website Feedback

Technical Report Writing for Engineers: A Comprehensive Guide

As an engineer, if you are looking at technical report writing for engineers? And learn how to write effective technical reports? If yes, then this article is for you.

After completing our comprehensive guide, you can improve your communication skills and stand out in your industry with our expert tips. It will meet your needs too.

Technical report writing is an essentials skill for engineers to communicates their finding, design, and recommendation to clients, colleagues, and other stakeholders. However, despite its importance, many engineers have difficulty writing effective technical reports. This is a critical issue because poorly written technical reports can results in misunderstanding, errors, and delays that can have serious consequences for project and organization.

Fortunately, research has shown that with the right training and supports, engineers can significantly improves their technical writing skill and produces high-quality report that meet the need of their audience.

As an engineer, you know that technical report are a crucial part of your jobs. They provides a detailed account of your finding, recommendation, and conclusion based on your researches and analysis. However, technical reports writing is not always easy, especially for those who are not familiar with the formats and styles. In this article, we will provides you with a comprehensive guides on technical reports writing for engineers, including tips, best practices, and common mistake to avoid.

• Understanding Technical Report Writing
• Types of Technical Reports
• Preparing for Technical Report Writing
• Structure of Technical Reports
• Writing a Technical Report
• Editing and Revising Technical Reports
• Mistakes to Avoid in Technical Report Writing

1. Understanding Technical Report Writing

Technical report writing is a specialized form of writing that is used to communicate technical information to a specific audience. Technical reports are typically used to document research findings, provide recommendations, and make conclusions based on data analysis. These reports are often used in engineering, science, and other technical fields.

1. What is an engineering report?

An engineering report is a documents that presents technical information related to an engineering projects, researches, or analysis. The report typically includes a description of the problem or objective, the methodology used to conduct the analysis, the result and conclusion, and recommendation for further action.

2. Why write an engineering report?

There are several reasons why someone may need to write an engineering report. One common reason is to communicate technical information to stakeholders such as clients, colleagues, regulatory agencies, or the public. The reports will provides a comprehensive understanding of the problems and the proposed solutions, helping to build consensus and support for the projects.

Additionally, an engineering report can serves as a record of the work done and the result obtained, which can be used for future references or to support claim or decision. It can also helps to identify area for improvements or further researches.

Overall, an engineering report is an essential tool for engineers to effectively communicate technical information and findings related to their work.

Also read:  Technical Writing vs Business Writing: Understanding the Nuances for Professional Growth

2. Types of Technical Reports:

Feasibility reports, progress reports, design reports, research reports, inspection reports, evaluation reports.

These reports assess the feasibility of a project or a proposed solution. They evaluate the technical, economic , and social viability of the proposed solution and provides recommendations on whether to proceed with the project.

These reports provide updates on the promotion of a project. They outline the accomplishments, challenges, and remaining tasks of the project and provide recommendations for addressing any issues.

These reports document the design process of a product or system. They outlined the design criteria, constraint, and specification, as well as the rationale for design decision.

These reports presents the finding of a research study. They outline the research questions, methodology, data analyse, and conclusion.

These reports document the findings of an inspection of a product, system, or facility. They identify any defects, hazards, or non-compliance with standards and provide recommendations for corrective action.

These reports assess the effectiveness of a program, project, or policy. They evaluate the objective, outcome, and impact of the programs, projects, or policy and provides recommendation for improvements.

3. Preparing for Technical Report Writing:

Before you start writing your technical report, it’s important to gather and organize all the necessary information. This includes identify the purpose of the reports, the audience, and the scope of the reports. You should also consider the formats, structures, and styles of the reports. Some tips for preparing for technical report writing includes:

• Identify the purpose of the report
• Determine the audience
• Determine the scope of the report
• Consider the format, structure, and style of the report
• Gather all necessary information
• Organize your ideas and information

Identify the purpose of the reports: Before you start writing your technical reports, you need to identify its purposes. Are you writing a feasibility reports, progress reports, design reports, research reports, inspection reports, or evaluation reports? Understanding the purpose of the reports will helps you to focus your writing and ensure that you includes all necessary information.

Determine the audience: It is essential to consider the intended audience of your technical report. Who will be reading your report? Who will read your report? What is their technical knowledge and skill level? Tailor your writing style and language to your intended audience to ensure that your report is easily understood.

Determines the scope of the reports: Determine the scope of your reports by identifying the boundaries of the topics or problems that you will be addressing. This will helps you narrow down the focus of your reports and ensure that you stay on track.

Consider the format, structure, and style of the report: Technical reports should be well-structured and formatted. Consider using headings, subheadings, and lists to organize your ideas and information. Ensure that your report follows the required format and style guidelines.

Gather all necessary information: Collect all necessary information related to your topic, including data, research, and supporting documentation. Ensures that you have all the necessary information before you start writing your reports.

Organize your idea and information: Organize your idea and information in a logical and coherent manners. Ensure that your reports flows well and that your ideas are presented in a clear and concise manners.

4. Structure of Technical Reports:

• Table of contents
• Abstract or executive summary

Introduction

• Background and literature review

Methodology

• Results and findings
• Discussion and analysis
• Conclusion and recommendations
• References or bibliography

Appendices (optional)

Technical report are formal documents that follows a standard structure to ensure that they are well-organized, informative, and easy to understand. The following sections are typically included in the technical report:

The title page includes the title of the reports, the name(s) of the author(s), the date, and any other relevant information, such as the name of the organization or project.

Table of Contents

The tables of contents lists the main sections of the reports and their page numbers. It helps the reader to navigate through the report quickly and easily.

Abstract or Executive summary

An abstract or executive summary provide a brief overview of the reports, including the purpose, scope, methodology, and key finding. It is typically one to two paragraph in length and is often included on a separate pages.

The introduction provides background information on the topic of the report, explains the purpose and scope of the report, and outlines the main objectives or research questions.

Background and Literature Review

The background and literature review section provides an overview of the existing knowledge and research related to the topic of the report. It helps to establish the context and significance of the report.

The methodology section describe the method used to collect and analyze data, conduct experiment, or carry out research. It include information on sample size, data collections technique, and statistical analysis method.

Results and Findings

The results and findings section presents the data and research findings in a clear and concise manner. It may includes table, graph and other visual aids to helps illustrate the data.

Discussion and Analysis

The discussion and analysis section interprets the results and findings in light of the research questions and objectives. It may also compare the results to previous research or industry standards.

Conclusion and Recommendation

The conclusion and recommendation section summarize the main finding and conclusion of the reports and provide recommendation for future researches or action.

References and Bibliography

The references and bibliography section lists all the sources cited in the report. It should be formatted according to the required citation style, such as APA or MLA.

Appendices may be included to provides additional information that is not included in the main body of the reports, such as technical drawing, calculation, or survey questionnaires.

By following this standardized structure, technical reports can effectively communicate complex information to a range of stakeholders and decision-makers.

5. Writing Technical Report:

Technical reports are formal documents that require clear and concise writing to effectively communicate complex information to the intended audience. Some tips for writing a technical report include:

• Use clear and concise language
• Avoid jargon and technical terms
• Use headings and subheadings
• Use relevant data and visuals to support your findings
• Include a conclusion that summarizes your findings and recommendations

Use clear and concise languages: Avoid using unnecessary technical jargon or complex terminologies that may be difficult for the audience to understand. Use always clear and concise language to convey the message.

Avoid jargon and technical term that the audience may not understand: If you need to use technical term, provides clear definition or explanation to ensure that the audience can understand the meaning.

Use headings and subheadings: Use descriptive headings and subheadings to organize the content of the report into meaningful sections. This make it easier for the readers to navigate the reports and find relevant information.

Use relevant data and visual to support your finding: Use table, chart, graph, and other visual aids to presents your data in a clear and concise manners. This helps the reader to quickly understand and interpret the information.

Include a conclusion that summarizes your findings and recommendations: Summarize the main findings of your report and provide recommendations for future action or research. This help the readers to understand the significance of the reports and its implication.

6. Editing and Revising Technical Reports:

Editing and revising are important steps in the technical report writing process. Please review your report for clarity, accuracy, and consistency. You should also check for spellings and grammar error and ensure that your reports meets the required format and style guidelines. Some tips for editing and revising technical reports include:

• Review your report for clarity, accuracy, and consistency.
• Check for spellings and grammar error.
• Ensure that your report meets the required format and style guidelines.
• Get feedback from colleagues or experts in your field.
• Revise your report accordingly based on the feedback received.

Review your reports for clarity, accuracy, and consistency: Read through your reports carefully to ensure that your ideas are presented in a logical and coherent manners. Ensure that your report is accurate and consistent throughout.

Check for spelling and grammar error: Use a spell checkers and proofread your reports thoroughly to eliminate any spellings or grammar error that could distract from the content.

Ensure that your reports meets the required format and style guidelines: Follow the guidelines provided by your organizations or professors to ensure that your reports is formatted and styled appropriately.

Get feedback from colleague or expert in your field: Share your reports with colleague or expert in your field to get feedback on its content, structures, and clarity.

Revise your report accordingly based on the feedback received: Use the feedback received to revise your report, making changes where necessary to improve its clarity, accuracy, and overall effectiveness.

7. Common Mistakes to Avoid in Technical Reports Writing:

In technical reports writing, there are common mistake that engineer often make that can impact the overall quality of the reports. Some of these mistakes includes:

• Failing to identify the purpose and audience of the report.
• Use technical jargon or acronym that are not understand by the intended audience.
• Include irrelevant information that does not support the purpose of the report.
• Neglect to cite sources or provide references for information used in the report.
• Failed to proofread and edit the reports for error in grammar, spellings, and formatting.

Failing to identify the purpose and audience of the report: Before beginning to write a technical report, it’s important to identify the purpose of the report and the intended audience. This will helps ensure that the reports is written in a way that effectively communicate the information to the audience.

Using technical jargon or acronym that are not understand by the intended audience: Technical term and acronym can be confusing for reader who are not familiar with the terminology. It’s important to use clear and concise languages that can be easily understand by the intended audience.

Includes irrelevant information that does not supports the purpose of the reports: The information presented in a technical reports should be directly relevants to the purpose of the reports. Including irrelevant information can detract from the overall effectiveness of the report.

Neglecting to cite sources or provide references for information used in the report: Technical reports often requires the use of data and information from external source. It’s important to provides proper citation and reference for this information to give credit to the original sources and avoid plagiarism.

Failing to proofread and edit the report for errors in grammar, spelling, and formatting: Technical reports should be well-written and error-free to effectively communicate the intended message. Neglecting to proofread and edit the reports can result in error that can impact the overall quality and effectiveness of the reports.

By avoiding these common mistakes, engineers can ensure that their technical reports are effective, well-written, and accurately convey the intended message to the audience.

 Conclusion

Technical report writing is a crucial skill for engineers, and with the help of our expert tips and comprehensive guide, you can improve your technical report writing skills and stand out in your industry. Remember to keeps your audience in mind, use clear and concise languages, and always review and edit your reports before submitting it. By following the tips and best practices in this guide, you can write effective technical reports that communicate your findings, recommendations, and conclusions to a specific audience. With these skills, you can excel in your fields and make a significant impacts.

 Frequently Asked Questions

What is the purpose of the technical reports?

The purpose of a technical reports is to communicates technical information or data to a specific audience in a clear and concise manners.

What is the structure of the technical report?

The structure of a technical report typically includes a title page, table of contents, abstract or executive summary, introduction, background or literature review, methodology, results and findings, discussion and analysis, conclusion and recommendations, references or bibliography, and appendices (optional).

How do I determine the audience for my technical report?

To determine the audience for your technical reports, consider who will be reading the reports and what their level of technical knowledge is. Tailor your language and style to best communicate with this audience.

What are some common types of technical reports?

Common types of technical reports includes feasibility report, progress report, design report, research report, inspection report, and evaluations report.

How can I avoid common mistakes in technical report writing?

To avoid common mistakes in technical report writing, be sure to clearly identify the purpose and audience of the report, avoid technical jargon that is not understood by the intended audience, include relevant information and data, properly cite sources, and thoroughly proofread and edit the report.

How important is the revision and editing process in technical report writing?

The revision and editing process is critical in technical report writing to ensure clarity, accuracy, and consistency in the report. It is important to review and review the report multiple times to ensure it meets the required format and style guidelines and effectively communicates the intended message.

What are some tips for presenting technical reports to an audience?

When presenting a technical reports to an audience, use clear and concise languages, incorporate visuals to support your finding, and be prepared to answer questions and provides additional information as needed.

2 thoughts on “Technical Report Writing for Engineers: A Comprehensive Guide”

• Pingback: What is Technical Writing in Criminology? Learn Right Now - Technical Rede - Learn Techniques of Writing
• Pingback: What are some examples of technical writing in creative writing? - Technical Rede - Learn Techniques of Writing

Leave a Comment Cancel reply

Save my name, email, and website in this browser for the next time I comment.

• How to Join
• ProComm Leadership Team
• Our Vision and Mission
• Membership Information
• Constitution
• ProComm Conferences
• ProComm 2024
• Past Conferences
• Future Conference Locations
• About the Journal
• Submitting a Manuscript
• Search Articles on IEEE Xplore
• Videos for Transactions Peer Reviewers
• English, Chinese, and Spanish Abstracts
• IEEE Transactions on Professional Communication Editorial Staff
• Classics in Communication
• The Wiley-IEEE PCS Book Series
• IPCC Proceedings (IEEE Xplore)
• About the Communication Resources
• Interpersonal
• Style and Grammar
• Written Reporting
• Oral Presentation
• Career Development
• Rhetorical Strategies
• Become a ProComm Expert
• ProComm Network Events
• Find a ProComm Expert
• About Division VI
• IEEE Education Society
• IEEE Industrial Electronics Society
• IEEE Product Safety Engineering Society
• IEEE Reliability Society
• IEEE Society on Social Implications of Technology
• IEEE Technology and Engineering Management Society

As a professional engineer, you have myriad experiences solving problems. Your reports, both formal and informal, help your client, supervisor, or other stakeholders make actionable decisions about those problems. Explore these resources to learn how to write more effective reports for greater project and career success:

• How do I write an effective report?

How do I use Microsoft Word to my advantage?

• Where can I find more information about writing reports?

Whether formal or informal, interim or final, your report is an essential part of the problem-solving process. Begin by analyzing your communication situation (note: link to Communication Situation) and reviewing communication basics?? (note: link to Communication Basics), then find out how to structure and format your report as effectively as possible:

What elements should my report contain?

What is the best way to present those elements.

Whether you’re writing for a client, your supervisor, or some other project stakeholder, your audience will likely want to know [adapted from P.V. Anderson’s Technical Communication (1)]:

• What will we gain?
• Are your facts reliable?
• What do you know that is useful to us?
• How do you interpret those facts from our point of view?
• How are those facts significant to us?
• What do you think we should do?

An effective report will be structured to answer these questions clearly and specifically. Depending on its level of formality, your report structure will include all or some of these elements [adapted from the Purdue Online Writing Lab (2)]:

• Front matter This report element includes the title or cover page, letter of transmittal, acknowledgments, table of contents, and lists of figures and tables.
• Executive summary and abstract These report elements provide an overview of what you’ll discuss in the body of the report.
• Body This report element includes the introduction, summary/background, methods/procedures, results, discussion of results, conclusion, and recommendations.
• Back matter This report element includes references, appendices, and attachments.

Front matter refers to the preliminary, supporting components of a report. It appears where you might expect: at the front of the report. You will typically attend to this element last and in conjunction with back matter, after you have written the body and executive summary and abstract.

Your report’s front matter includes [adapted from the Purdue Online Writing Lab (3)]:

• Title or cover page Include a title, the name of the person authorizing the report, your name, your company’s name and contact information, and the date you submit the report.
• Letter of transmittal Describe the problem you’re solving for, the purpose of the work you’ve done, the time period for the work, and your results and recommendations.
• Acknowledgments Credit anyone who contributed substantially to the project, and include any permissions for copyrighted materials use.
• Table of contents Provide a guide that includes every report element and the page on which it occurs. Page number front matter with lower-case Roman numerals (i, ii, iii, etc.); page number the rest of the report with Arabic numerals (1, 2, 3, etc.). You can use Word to automatically generate your table of contents.
• Lists of figures and tables Provide a separate guide, like a secondary table of contents, that includes the name and page location of every figure in your report, and another for tables.

Formal reports include every component listed above; an informal report may only include some of them. In some cases, your company may specify which of these components to use and how.

Executive summary and abstract

Your engineering report may include both an executive summary and an abstract, or it may only include one or the other. These elements appear between the front matter and the report body. Write these after you have written and revised the report body.

What is an executive summary?

An executive summary is an overview of the key points in your report. It should summarize the purpose and scope of your work, the methods you used, and your key findings, conclusions, and recommendations [4].

What is an abstract?

An abstract is a short but specific summary of the details you cover in the report’s body. It should briefly mention the purpose and scope of your work, the methods you used, and your key findings, conclusions, and recommendations [5].

What’s the difference between the two?

The difference lies primarily in their purpose and length. The abstract provides a preview of the report’s content meant to entice readers to read the entire report. It is typically less than a page long. The executive summary, on the other hand, provides enough information to allow stakeholders to make a decision without reading the full report. It is typically as long as 10% of the full report [6].

The body of your report is where you provide the details of your work. It is the longest part of your report and falls after the front matter and executive summary and abstract. You will produce the body before any other element of your report, with the possible exception of graphics, like figures and tables.

Your report’s body includes [1] [7]:

• Introduction Summarize your major conclusions and recommendations. Also describe the organization of your report and its scope.
• Summary/background Describe the existing research or activity you relied on to guide your work.
• Methods/procedures Describe what you did and how you did it. Include the equipment you used.
• Results Reveal your research findings. This report component may be combined with the discussion of results.
• Discussion of results Describe what your results demonstrate and why that is important to your audience. Highlight notable trends the results reveal, as well as the limitations and assumptions in your work. This report component may be combined with the results.
• Conclusion Make meaningful statements based on the discussion of results. This report component may be combined with the recommendations.
• Recommendations Provide actionable recommendations based on your conclusions. This report component may be combined with the conclusion.

Back matter

The back matter of a report is its succeeding, supporting components. As its name implies, it appears at the back of the report. You will typically attend to this element last and in conjunction with front matter , after you have written the body and executive summary and abstract .

Your report’s back matter includes [1]:

• References List the references you cited throughout your report. Use your company’s or engineering field’s style guide (note: link to What is a style guide? Which one should I use?) to determine the appropriate format for your reference list.
• Appendices Present detailed information related, but not essential, to your report in the appendices. Some examples of materials appropriate for the appendices, includes data, analysis methods, and equipment details [3]. In some cases, you’ll include all your tables and figures here rather than in the body of the report. Put the appendices in order by their mention in the body of the report.
• Attachments Attach materials appropriate for the appendices that are too large in size to fit the report format. For instance, you may have oversize blueprints that would be unreadable if reduced to the typical 8.5×11 size of a report.

According to Paul Anderson in his book Technical Communication: A Reader-Centered Approach , “Good [formatting] helps readers understand your information, locate information, and notice highly important content” [8]. A successful report is formatted well.

What components should I consider while formatting?

When formatting your report, pay attention to these common components [8]:

• Body text Sentences and paragraphs
• Headings Titles, headings, subheadings
• Headers and footers Recurring components at the top and/or bottom of every page, like page numbers and report title
• Graphics Tables, figures, photos
• Space Empty areas between headers, paragraphs, graphics, and captions

How do I format those components?

Consider these basic principles adapted from graphic design theory when formatting your report [9]. Scroll to the bottom of this page for a rough example of these principles applied to the above components:

• Contrast Use contrasting size, weight, and typeface to establish focus and hierarchy on your pages. For instance, set your top-level headings in a bold, sans-serif, 14 point typeface like Arial; set your body text in a regular weight, serif, 10 to 12 point typeface like Times New Roman.
• Repetition Use the same formatting for every page and similar components on that page. For instance, include page numbers in the same place, with the same formatting on every page (10 point, bold, Arial, at the bottom, center of the pages, for example). Style your body text and headings the same throughout the report (Microsoft Word styles can help you do this easily).
• Alignment Connect every component on a page with a strong visual alignment. For instance, place graphics, like tables or figures, on the left side of the page in alignment with the left edge of the text. Align headings to the left like the body text.
• Proximity Use space to group related items together and separate unrelated items. For instance, place graphics near their mention in the body text. Put less space between a subhead and its related body text; put more space between the bottom of body text and the next, unrelated subhead.

Reference Report examples

Your company likely has numerous examples of reports that include some or all of these elements and their individual components. In addition, examples of formal reports abound in professional journals in your field.

Microsoft Word includes numerous tools and functions that will save you time and hassle, and allow you to consistently format your reports. Visit the links from Where can I find more information about writing effective reports? to learn how to use these time-saving tools and functions:

• Styles Rather than manually styling text, use styles to change the formatting of the same type of text (body, headings, captions, etc.) from one formatting dialog at one time.
• Page numbering and sectioning Instead of manually numbering your pages one at a time, use automatic page numbering and sectioning to organize your report.
• Table of contents creation Instead of manually creating and numbering your report’s table of contents, use automatic table of contents creation to provide access to the organization and contents of your report.
• Graphics Place and resize graphics from programs like Excel or from other text documents to fit your report’s format.

Where can I find more information about writing effective reports?

The IEEE Professional Communication Society’s site provides you with a basic understanding of writing effective reports. Explore other resources to gain more knowledge about this topic.

• Writing an executive summary for engineering reports (vidcast) Watch this 6-minute video that demonstrates how to write an effective executive summary for an engineering report.
• Writing a title page for engineering reports (vidcast) Watch this 4-minute video that demonstrates how to put together an effective title page for engineering reports.
• Report checklist Use this checklist to make sure you’ve addressed every element in your engineering report.
• How to use styles in Microsoft Word to save a lot of work Read this resource that teaches you how to use styles in Word to make your report formatting consistent and efficient.
• Create an automatic table of contents in Word (video) Watch this 4-minute video to learn how to generate an automatic table of contents using styles in Word.
• How to create a table of contents in Microsoft Word Read this thorough resource that shows you how to automatically create a table of contents in Word.
• Table of Contents tips Consult this source that points out some fine points of creating and modifying tables of contents in Word.
• Add page numbers to documents in Word 2007 and 2010 Read this resource that shows you how to add page numbers in both Word 2007 and 2010.
• Word 2003 page numbers Watch this 3-minute video to learn how to insert page numbers in Word 2003.
• How to insert page numbers in Microsoft Word 2003 Read this quick set of instructions for inserting page numbers in Word 2003.
• How to restart page numbers in a Word document section Read this quick set of instructions for sectioning Word documents and page numbering each section differently.
• How to copy a chart from Excel into a Word document Consult this resource to learn how to place and modify Excel charts in Word documents.
• Move Excel graph to Word tutorial (video) Watch this 13-minute tutorial to learn how to place and modify Excel charts in Word documents.
• How to crop and resize an image in Word 2010 (video) Watch this 2-minute video to learn how to crop and resize images in Word.
• Insert and position graphics in Word documents Read this resource to learn how to insert and position graphics in Word.

[1] P.V. Anderson, “Writing reader-centered reports,” in Technical Communication: A Reader-Centered Approach. Boston, MA: Thomson Wadsworth, 2007, pp. 539-556.

[2] E. Cember, A. Heavilon, M. Seip, L. Shi, and A. Brizee. Sections of reports. Purdue Online Writing Lab. [Online]. Available: http://owl.english.purdue.edu/owl/resource/726/05

[3] E. Cember, A. Heavilon, M. Seip, L. Shi, and A. Brizee. Mechanical elements of reports.  Purdue Online Writing Lab.  [Online]. Available: http://owl.english.purdue.edu/owl/resource/726/0 8

[4] Processes for writing an executive summary.  Writing at Colorado State University.  [Online]. Available: http://writing.colostate.edu/guides/page.cfm?pageid=1508

[5] E. Cember, A. Heavilon, M. Seip, L. Shi, and A. Brizee. The report abstract and executive summary.  Purdue Online Writing Lab . [Online]. Available: http://owl.english.purdue.edu/owl/resource/726/07

[6] K. Khan. (2008, Sept. 19). Difference between executive summary, abstract and synopsis. University of Balochistan. [Online]. Available: http://www.scribd.com/doc/55954574/Difference-Between-Executive-Summary-Abstract-and-Synopsis

[7] E. Cember, A. Heavilon, M. Seip, L. Shi, and A. Brizee. The report body.  Purdue Online Writing Lab.  [Online]. Available: http://owl.english.purdue.edu/owl/resource/726/06

[8] P.V. Anderson, “Designing reader-centered pages and documents,” in  Technical Communication: A Reader-Centered Approach.  Boston, MA: Thomson Wadsworth, 2007, pp. 372-398.

[9] R. Williams,  The Non-Designer’s Design Book.  Berkeley, CA: Peachpit Press, 2004.

How To Write The Methodology Chapter

The what, why & how explained simply (with examples).

By: Jenna Crossley (PhD) | Reviewed By: Dr. Eunice Rautenbach | September 2021 (Updated April 2023)

So, you’ve pinned down your research topic and undertaken a review of the literature – now it’s time to write up the methodology section of your dissertation, thesis or research paper . But what exactly is the methodology chapter all about – and how do you go about writing one? In this post, we’ll unpack the topic, step by step .

Overview: The Methodology Chapter

• The purpose  of the methodology chapter
• Why you need to craft this chapter (really) well
• How to write and structure the chapter
• Methodology chapter example
• Essential takeaways

What (exactly) is the methodology chapter?

The methodology chapter is where you outline the philosophical underpinnings of your research and outline the specific methodological choices you’ve made. The point of the methodology chapter is to tell the reader exactly how you designed your study and, just as importantly, why you did it this way.

Importantly, this chapter should comprehensively describe and justify all the methodological choices you made in your study. For example, the approach you took to your research (i.e., qualitative, quantitative or mixed), who  you collected data from (i.e., your sampling strategy), how you collected your data and, of course, how you analysed it. If that sounds a little intimidating, don’t worry – we’ll explain all these methodological choices in this post .

Why is the methodology chapter important?

The methodology chapter plays two important roles in your dissertation or thesis:

Firstly, it demonstrates your understanding of research theory, which is what earns you marks. A flawed research design or methodology would mean flawed results. So, this chapter is vital as it allows you to show the marker that you know what you’re doing and that your results are credible .

Secondly, the methodology chapter is what helps to make your study replicable. In other words, it allows other researchers to undertake your study using the same methodological approach, and compare their findings to yours. This is very important within academic research, as each study builds on previous studies.

The methodology chapter is also important in that it allows you to identify and discuss any methodological issues or problems you encountered (i.e., research limitations ), and to explain how you mitigated the impacts of these. Every research project has its limitations , so it’s important to acknowledge these openly and highlight your study’s value despite its limitations . Doing so demonstrates your understanding of research design, which will earn you marks. We’ll discuss limitations in a bit more detail later in this post, so stay tuned!

Need a helping hand?

How to write up the methodology chapter

First off, it’s worth noting that the exact structure and contents of the methodology chapter will vary depending on the field of research (e.g., humanities, chemistry or engineering) as well as the university . So, be sure to always check the guidelines provided by your institution for clarity and, if possible, review past dissertations from your university. Here we’re going to discuss a generic structure for a methodology chapter typically found in the sciences.

Before you start writing, it’s always a good idea to draw up a rough outline to guide your writing. Don’t just start writing without knowing what you’ll discuss where. If you do, you’ll likely end up with a disjointed, ill-flowing narrative . You’ll then waste a lot of time rewriting in an attempt to try to stitch all the pieces together. Do yourself a favour and start with the end in mind .

Section 1 – Introduction

As with all chapters in your dissertation or thesis, the methodology chapter should have a brief introduction. In this section, you should remind your readers what the focus of your study is, especially the research aims . As we’ve discussed many times on the blog, your methodology needs to align with your research aims, objectives and research questions. Therefore, it’s useful to frontload this component to remind the reader (and yourself!) what you’re trying to achieve.

In this section, you can also briefly mention how you’ll structure the chapter. This will help orient the reader and provide a bit of a roadmap so that they know what to expect. You don’t need a lot of detail here – just a brief outline will do.

Section 2 – The Methodology

The next section of your chapter is where you’ll present the actual methodology. In this section, you need to detail and justify the key methodological choices you’ve made in a logical, intuitive fashion. Importantly, this is the heart of your methodology chapter, so you need to get specific – don’t hold back on the details here. This is not one of those “less is more” situations.

Let’s take a look at the most common components you’ll likely need to cover. 

Methodological Choice #1 – Research Philosophy

Research philosophy refers to the underlying beliefs (i.e., the worldview) regarding how data about a phenomenon should be gathered , analysed and used . The research philosophy will serve as the core of your study and underpin all of the other research design choices, so it’s critically important that you understand which philosophy you’ll adopt and why you made that choice. If you’re not clear on this, take the time to get clarity before you make any further methodological choices.

While several research philosophies exist, two commonly adopted ones are positivism and interpretivism . These two sit roughly on opposite sides of the research philosophy spectrum.

Positivism states that the researcher can observe reality objectively and that there is only one reality, which exists independently of the observer. As a consequence, it is quite commonly the underlying research philosophy in quantitative studies and is oftentimes the assumed philosophy in the physical sciences.

Contrasted with this, interpretivism , which is often the underlying research philosophy in qualitative studies, assumes that the researcher performs a role in observing the world around them and that reality is unique to each observer . In other words, reality is observed subjectively .

These are just two philosophies (there are many more), but they demonstrate significantly different approaches to research and have a significant impact on all the methodological choices. Therefore, it’s vital that you clearly outline and justify your research philosophy at the beginning of your methodology chapter, as it sets the scene for everything that follows.

Methodological Choice #2 – Research Type

The next thing you would typically discuss in your methodology section is the research type. The starting point for this is to indicate whether the research you conducted is inductive or deductive .

Inductive research takes a bottom-up approach , where the researcher begins with specific observations or data and then draws general conclusions or theories from those observations. Therefore these studies tend to be exploratory in terms of approach.

Conversely , d eductive research takes a top-down approach , where the researcher starts with a theory or hypothesis and then tests it using specific observations or data. Therefore these studies tend to be confirmatory in approach.

Related to this, you’ll need to indicate whether your study adopts a qualitative, quantitative or mixed  approach. As we’ve mentioned, there’s a strong link between this choice and your research philosophy, so make sure that your choices are tightly aligned . When you write this section up, remember to clearly justify your choices, as they form the foundation of your study.

Methodological Choice #3 – Research Strategy

Next, you’ll need to discuss your research strategy (also referred to as a research design ). This methodological choice refers to the broader strategy in terms of how you’ll conduct your research, based on the aims of your study.

Several research strategies exist, including experimental , case studies , ethnography , grounded theory, action research , and phenomenology . Let’s take a look at two of these, experimental and ethnographic, to see how they contrast.

Experimental research makes use of the scientific method , where one group is the control group (in which no variables are manipulated ) and another is the experimental group (in which a specific variable is manipulated). This type of research is undertaken under strict conditions in a controlled, artificial environment (e.g., a laboratory). By having firm control over the environment, experimental research typically allows the researcher to establish causation between variables. Therefore, it can be a good choice if you have research aims that involve identifying causal relationships.

Ethnographic research , on the other hand, involves observing and capturing the experiences and perceptions of participants in their natural environment (for example, at home or in the office). In other words, in an uncontrolled environment.  Naturally, this means that this research strategy would be far less suitable if your research aims involve identifying causation, but it would be very valuable if you’re looking to explore and examine a group culture, for example.

As you can see, the right research strategy will depend largely on your research aims and research questions – in other words, what you’re trying to figure out. Therefore, as with every other methodological choice, it’s essential to justify why you chose the research strategy you did.

Methodological Choice #4 – Time Horizon

The next thing you’ll need to detail in your methodology chapter is the time horizon. There are two options here: cross-sectional and longitudinal . In other words, whether the data for your study were all collected at one point in time (cross-sectional) or at multiple points in time (longitudinal).

The choice you make here depends again on your research aims, objectives and research questions. If, for example, you aim to assess how a specific group of people’s perspectives regarding a topic change over time , you’d likely adopt a longitudinal time horizon.

Another important factor to consider is simply whether you have the time necessary to adopt a longitudinal approach (which could involve collecting data over multiple months or even years). Oftentimes, the time pressures of your degree program will force your hand into adopting a cross-sectional time horizon, so keep this in mind.

Methodological Choice #5 – Sampling Strategy

Next, you’ll need to discuss your sampling strategy . There are two main categories of sampling, probability and non-probability sampling.

Probability sampling involves a random (and therefore representative) selection of participants from a population, whereas non-probability sampling entails selecting participants in a non-random  (and therefore non-representative) manner. For example, selecting participants based on ease of access (this is called a convenience sample).

The right sampling approach depends largely on what you’re trying to achieve in your study. Specifically, whether you trying to develop findings that are generalisable to a population or not. Practicalities and resource constraints also play a large role here, as it can oftentimes be challenging to gain access to a truly random sample. In the video below, we explore some of the most common sampling strategies.

Methodological Choice #6 – Data Collection Method

Next up, you’ll need to explain how you’ll go about collecting the necessary data for your study. Your data collection method (or methods) will depend on the type of data that you plan to collect – in other words, qualitative or quantitative data.

Typically, quantitative research relies on surveys , data generated by lab equipment, analytics software or existing datasets. Qualitative research, on the other hand, often makes use of collection methods such as interviews , focus groups , participant observations, and ethnography.

So, as you can see, there is a tight link between this section and the design choices you outlined in earlier sections. Strong alignment between these sections, as well as your research aims and questions is therefore very important.

Methodological Choice #7 – Data Analysis Methods/Techniques

The final major methodological choice that you need to address is that of analysis techniques . In other words, how you’ll go about analysing your date once you’ve collected it. Here it’s important to be very specific about your analysis methods and/or techniques – don’t leave any room for interpretation. Also, as with all choices in this chapter, you need to justify each choice you make.

What exactly you discuss here will depend largely on the type of study you’re conducting (i.e., qualitative, quantitative, or mixed methods). For qualitative studies, common analysis methods include content analysis , thematic analysis and discourse analysis . In the video below, we explain each of these in plain language.

For quantitative studies, you’ll almost always make use of descriptive statistics , and in many cases, you’ll also use inferential statistical techniques (e.g., correlation and regression analysis). In the video below, we unpack some of the core concepts involved in descriptive and inferential statistics.

In this section of your methodology chapter, it’s also important to discuss how you prepared your data for analysis, and what software you used (if any). For example, quantitative data will often require some initial preparation such as removing duplicates or incomplete responses . Similarly, qualitative data will often require transcription and perhaps even translation. As always, remember to state both what you did and why you did it.

Section 3 – The Methodological Limitations

With the key methodological choices outlined and justified, the next step is to discuss the limitations of your design. No research methodology is perfect – there will always be trade-offs between the “ideal” methodology and what’s practical and viable, given your constraints. Therefore, this section of your methodology chapter is where you’ll discuss the trade-offs you had to make, and why these were justified given the context.

Methodological limitations can vary greatly from study to study, ranging from common issues such as time and budget constraints to issues of sample or selection bias . For example, you may find that you didn’t manage to draw in enough respondents to achieve the desired sample size (and therefore, statistically significant results), or your sample may be skewed heavily towards a certain demographic, thereby negatively impacting representativeness .

In this section, it’s important to be critical of the shortcomings of your study. There’s no use trying to hide them (your marker will be aware of them regardless). By being critical, you’ll demonstrate to your marker that you have a strong understanding of research theory, so don’t be shy here. At the same time, don’t beat your study to death . State the limitations, why these were justified, how you mitigated their impacts to the best degree possible, and how your study still provides value despite these limitations .

Section 4 – Concluding Summary

Finally, it’s time to wrap up the methodology chapter with a brief concluding summary. In this section, you’ll want to concisely summarise what you’ve presented in the chapter. Here, it can be a good idea to use a figure to summarise the key decisions, especially if your university recommends using a specific model (for example, Saunders’ Research Onion ).

Importantly, this section needs to be brief – a paragraph or two maximum (it’s a summary, after all). Also, make sure that when you write up your concluding summary, you include only what you’ve already discussed in your chapter; don’t add any new information.

Methodology Chapter Example

In the video below, we walk you through an example of a high-quality research methodology chapter from a dissertation. We also unpack our free methodology chapter template so that you can see how best to structure your chapter.

Wrapping Up

And there you have it – the methodology chapter in a nutshell. As we’ve mentioned, the exact contents and structure of this chapter can vary between universities , so be sure to check in with your institution before you start writing. If possible, try to find dissertations or theses from former students of your specific degree program – this will give you a strong indication of the expectations and norms when it comes to the methodology chapter (and all the other chapters!).

Also, remember the golden rule of the methodology chapter – justify every choice ! Make sure that you clearly explain the “why” for every “what”, and reference credible methodology textbooks or academic sources to back up your justifications.

If you need a helping hand with your research methodology (or any other component of your research), be sure to check out our private coaching service , where we hold your hand through every step of the research journey. Until next time, good luck!

Psst... there’s more!

This post was based on one of our popular Research Bootcamps . If you're working on a research project, you'll definitely want to check this out ...

You Might Also Like:

51 Comments

highly appreciated.

This was very helpful!

This was helpful

Thanks ,it is a very useful idea.

Thanks ,it is very useful idea.

Thank you so much, this information is very useful.

Thank you very much. I must say the information presented was succinct, coherent and invaluable. It is well put together and easy to comprehend. I have a great guide to create the research methodology for my dissertation.

Highly clear and useful.

I understand a bit on the explanation above. I want to have some coach but I’m still student and don’t have any budget to hire one. A lot of question I want to ask.

Thank you so much. This concluded my day plan. Thank you so much.

Thanks it was helpful

Great information. It would be great though if you could show us practical examples.

Thanks so much for this information. God bless and be with you

Thank you so so much. Indeed it was helpful

This is EXCELLENT!

I was totally confused by other explanations. Thank you so much!.

justdoing my research now , thanks for the guidance.

Thank uuuu! These contents are really valued for me!

This is powerful …I really like it

Highly useful and clear, thank you so much.

Highly appreciated. Good guide

That was helpful. Thanks

This is very useful.Thank you

Very helpful information. Thank you

This is exactly what I was looking for. The explanation is so detailed and easy to comprehend. Well done and thank you.

Great job. You just summarised everything in the easiest and most comprehensible way possible. Thanks a lot.

Thank you very much for the ideas you have given this will really help me a lot. Thank you and God Bless.

Such great effort …….very grateful thank you

Please accept my sincere gratitude. I have to say that the information that was delivered was congruent, concise, and quite helpful. It is clear and straightforward, making it simple to understand. I am in possession of an excellent manual that will assist me in developing the research methods for my dissertation.

Thank you for your great explanation. It really helped me construct my methodology paper.

thank you for simplifieng the methodoly, It was realy helpful

Very helpful!

Thank you for your great explanation.

The explanation I have been looking for. So clear Thank you

Thank you very much .this was more enlightening.

helped me create the in depth and thorough methodology for my dissertation

Thank you for the great explaination.please construct one methodology for me

I appreciate you for the explanation of methodology. Please construct one methodology on the topic: The effects influencing students dropout among schools for my thesis

This helped me complete my methods section of my dissertation with ease. I have managed to write a thorough and concise methodology!

its so good in deed

wow …what an easy to follow presentation. very invaluable content shared. utmost important.

Peace be upon you, I am Dr. Ahmed Khedr, a former part-time professor at Al-Azhar University in Cairo, Egypt. I am currently teaching research methods, and I have been dealing with your esteemed site for several years, and I found that despite my long experience with research methods sites, it is one of the smoothest sites for evaluating the material for students, For this reason, I relied on it a lot in teaching and translated most of what was written into Arabic and published it on my own page on Facebook. Thank you all… Everything I posted on my page is provided with the names of the writers of Grad coach, the title of the article, and the site. My best regards.

A remarkably simple and useful guide, thank you kindly.

I real appriciate your short and remarkable chapter summary

Bravo! Very helpful guide.

Only true experts could provide such helpful, fantastic, and inspiring knowledge about Methodology. Thank you very much! God be with you and us all!

highly appreciate your effort.

This is a very well thought out post. Very informative and a great read.

THANKS SO MUCH FOR SHARING YOUR NICE IDEA

I love you Emma, you are simply amazing with clear explanations with complete information. GradCoach really helped me to do my assignment here in Auckland. Mostly, Emma make it so simple and enjoyable

Submit a Comment Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

• Print Friendly

Tips for Writing an Engineering Project Report

July 17, 2013 by Bernie Roseke, P.Eng., PMP 1 Comment

All of us have written technical reports for clients or other stakeholders.  It is one of the tasks that are central to an engineer’s job.  In this edition of the technical brief, I will provide a checklist that should be relatively comprehensive.  This has been taken from several of my old reports, and each of these were their own section (1.0, 2.0, etc.)

Introduction

This is a good place to state the basic premise of the project.  Who is the owner?  Why is the project being undertaken?  What are the parameters of the project?

Existing Condition

What is the existing structure and what is its condition?  Are the any residual effects because of this condition?  What inventory information exists from the owner?  This is also a good place to put survey or similar information.

Design Considerations

This is where you itemize the parameters that the design must conform to.  In the case of a bridge project, you could have sections called roadway alignment, cross-section, stream alignment, environmental permitting, debris, and any other items of significance affecting the design.  We don’t necessarily need to provide all of the mitigative solutions at this point, but it’s good to include this section because of the opportunity to analyze all of the issues.  There’s nothing worse than having a discussion after the report is submitted about an issue that was not mentioned or thoroughly analyzed.

Design Sections

Obviously each project is technically different but for a bridge project you might have sections entitled Hydrology, Substructure Design, or Superstructure Design.  Here you would detail the design methodology.  It’s time to state what the design was and why that design was chosen.

Alternatives

Most engineering reports are initiated because there are multiple alternatives available and the owner must decide on a course of action.  The alternatives section should itemize each alternative with the primary design features (for example, abutment type, bridge length) and an associated cost.  This is usually best in a table format.  A net present value analysis is often important to compare life cycle costs between options that have different life spans.

Regulatory and other Secondary Stakeholder Issues

Most engineering projects have some sort of secondary stakeholder issues like government regulators, adjacent landowners and so forth.  What is required to keep the project on track with these stakeholders?  State each one and make sure you are comprehensive in addressing their concerns, or the client might wonder if you’ve done enough to ensure a smooth project.

Recommendation

Of course, we have to provide a recommendation to make it worth the money.  The option with the lowest net present value is the cheapest and should be chosen unless there are compelling reasons to choose another option.  Sometimes when the recommendation is complicated I have found it helpful to contact the client and have some discussions before submitting a recommendation.  This ensures a speedy resolution and makes you look better because your recommendation was adopted.

Good luck with your projects!

Related posts:

No related posts.

About Bernie Roseke, P.Eng., PMP

Bernie Roseke, P.Eng., PMP, is the president of Roseke Engineering . As a bridge engineer and project manager, he manages projects ranging from small, local bridges to multi-million dollar projects. He is also the technical brains behind ProjectEngineer , the online project management system for engineers. He is a licensed professional engineer, certified project manager, and six sigma black belt. He lives in Lethbridge, Alberta, Canada, with his wife and two kids.

I appreciate your tip to take into account design considerations and the existing condition of a structure when doing a report on the foundation. I also like what you said about considering all the alternatives when looking into engineering reports. I’ve heard that engineering reports can also lead to better insurance rates to insure a structure, but I’ll have to do more research. Thanks for the tips!

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

• Project Initiation
• Project Planning
• Project Execution
• Monitoring and Controlling
• Project Closure
• Project Management Tutorial
• Project Scheduling Tutorial
• Earned Value Tutorial
• PMP Exam Tutorial
• Find Talent         
• PRINCE2 Foundation
• PRINCE2 Practitioner
• PRINCE2 Professional
• IPMA Level A
• IPMA Level B
• IPMA Level C
• IPMA Level D
• Learning Videos

Certification

Recent posts.

• PMI Project Knowledge Areas, Intro
• PMI Project Knowledge Areas, Video 1: Project Integration
• Project Risk Checklist
• Creating a Risk Register
• 50 SMART Goals
• Reporting Earned Value
• Analogous Estimating
• Variance at Completion (Earned Value Analysis)
• TCPI (Earned Value Analysis)

FIND IT HERE

Subscibe to ProjectEngineer.NET channel – YouTube

• WordPress.org
• Documentation
• Support Forums

Join our team

View our current job opportunities.

System Integration Partner

Vista Projects specializes in the implementation, configuration, administration, and support of AVEVA’s Asset Information Management suite.

Long-Term Success

We approach each project with the same outlook. Our goal is always to help clients meet their short-term project objectives while also preparing the asset for long-term success.

Intelligent Data Starts with Engineering

Download our brochure about Data-Centric Execution Architecture to learn more.

Media Contact

Are you interested in interviewing someone from Vista, using our logo, or talking to us about speaking opportunities?

Latest Post

How to Write an Engineering Report

• Adam Singfield
• Last Updated August 18, 2016
• Category Technical Writing

No matter what kind of engineer you are, you will eventually need to write an engineering report. This type of technical writing means knowing how to share information about research and analysis and then present it clearly in writing.

Writing a report about engineering services, like those we provide at Vista Projects, means communicating ideas in addition to furthering innovation and improvements. This skill makes you an even more significant asset to your company and allows you to solve problems and create solutions.

What Is an Engineering Report?

An engineering report is a type of technical editing that presents a problem, analyzes it, and offers solutions. It involves collecting and compiling data and ideas, conducting testing, and organizing the information you gained into comprehensible results for the reader.

Students learn to write these reports when they go through their education program, but writing them well involves knowing why you’re writing the technical report. While your purpose for writing technical reports will vary based on your specific field, the structure of all engineering reports remains the same: a summary, the body, and your conclusions.

Writing a report involves communicating a process for fixing a problem to a customer, community, business, or investor. Some engineers copyright their processes. Above all, your report should convey information clearly, offer information backed by evidence, and show why your solution stands out from the competition.

Why Write an Engineering Report?

Engineering report-writing should always focus on helping your firm achieve an objective. That may mean convincing a client to take action based on your solution or showing them how a project will benefit the public.

It may also help persuade your client to choose your company’s design or solution, get funding from investors, or encourage another business to partner with your firm on a project.

Other times, you may only want to inform your audience. For example, you may give your government the information it needs to decide on implementing a policy, show other engineers how to work from your proposed plan, or illustrate project outcomes for stakeholders.

Many students make the mistake of writing reports to show their personal knowledge. You do not want to teach your reader but instead, to offer a summary in writing to help them choose between two companies or engineers.

The body of technical reports should show your reader how your process affects them, include evidence to support your conclusions, and make a case for why your reader should support your ideas.

Do You Write an Engineering Report?

Before you start writing your report, consider the information you want to convey. Are you writing a trend report, an analytical report, or a trip report? Knowing the best way to share your information will help your audience understand your objectives.

Engineering students typically learn to write technical reports in their program, but different types of reports have different approaches. When it comes to report writing, remember these factors:

• Consider your audience
• Keep the proper structure and organization
• Make your writing easy to skim
• Only include pertinent information

The information and sources that you’ll need to compile your technical report will change based on the project. For example, a research report requires detailed information about your topic and the theory surrounding it. It involves citing textbooks, journals, and similar documents.

On the other hand, a site visit report should include the company history and operations, citing annual reports and the company prospectus. Fault reports also have different requirements, as they involve looking into a problem, determining the cause, and recommending an action to fix it.

Report writing means doing research, conducting tests, compiling evidence, and using that information to draw conclusions based on each previous section. Additionally, a strong introduction and summary will draw in your reader, and let them know what to expect.

Engineering reports should allow for selective reading and effective communication. Use headers, numbered lists, bullet points, and figures and tables to do more than explain your points in words. Readers will skim your writing, so make the important parts easy for them to find, such as in these technical report examples .

The Structure of Engineering Reports

Engineering reports follow the same structure. Your technical report should have these components:

• Executive Summary
• Table of contents
• Introduction
• Conclusions and recommendations
• References and appendices

The first few pages of your report are some of the most critical. They show your reader where they can find information throughout the document. Remember, some investors will not read past your executive summary .

Title pages should clearly state the purpose of your writing. Your executive summary should be no longer than two pages, and it acts as a condensed version of your research, conclusions, and recommendations. If your reader wants more information, the table of contents should allow them to find the correct section in seconds.

You have some freedom in structuring the body, but it must make sense and inform the reader while justifying your claims and ensuring that your reader understands the purpose of the writing. By sticking to this structure, you make writing reports simpler and focus on the following content.

Technical Report Overview

Technical reports always contain an introduction that states your report’s purpose and the leading question your research answers. Does it offer information about why your city needs a new bridge or highway? Are you showing an investor why they should put money into your project?

Your technical report overview should also hook your reader. Tell your audience what you investigate and why it’s important. Refer to your client’s request and scope of work in your writing, and relate the information back to the needs of your client, stakeholder, or executive.

Methodology

Your methodology section is often the most involved piece of writing in your report. Here, you talk about how you performed your study and why you approached it the way you did.

This section should show that you have done thorough research and should present your research protocol clearly. Your writing should detail how you got your information and how your methods offer something new to your field. This section should convey confidence in your company’s work so that your reader will, too.

If you used unique or original methods to gain your information and conclusions, you might  consider copyrigh t  for your work. That way, you keep your methods your own, which may help you in future reports and persuade other professionals to work with you.

When writing up the findings and results of technical reports, make sure not to make this section your conclusion. At this point, you should only state the outcome of your research, analyses, and tests. Include graphics to illustrate your results,

Your writing and structure should offer results conducive to the type of report. For example, design reports may evaluate the design of a new building and why it proves more stable than others. Other types of engineering reports, like proposals, will not require you to write a results section, as you are only offering a potential solution at this point.

Your writing will show the reader how you arrived at your final solution to their problem. Technical reports often require you to communicate dense information, so you should use similar language to that which you used in the technical report overview. That allows readers to make connections in your writing and understand how they relate to your report.

Recommendations and Conclusions

Your final section before writing your references and appendices includes your recommendations and conclusions . Here, you expand upon your results and tell the reader what they mean, how they affect the audience or community, and their benefits.

Align this section with your introduction, so your writing allows the reader to again make connections throughout your report. Let your reader know what you plan to do with the new information, and show them why they should care. Your writing may enlighten them to potential benefits like a greater profit, more convenience, higher productivity, or increased efficiency.

Above all, your writing sets out to answer a question. Your recommendations and conclusions are the final pieces in answering that question through research, allowing you to present how your client should respond to the situation.

Check out more  technical writing tips  in our resources section.

Vista Projects is an integrated engineering The process of integrated engineering involves multiple engineering disciplines working in conjunction with other project disciplines to e… services firm able to assist with your pipeline projects. With offices in Calgary, Alberta, Houston, Texas and Muscat, Oman, we help clients with customized system integration and engineering consulting across all core disciplines.

Data-centric Execution

How to Write Engineering Report

• First Online: 11 November 2021

Cite this chapter

• Yongsheng Ma 3 &
• Yiming Rong 3  

743 Accesses

An engineer’s work requires their mastery of the art of effective technical communication. An engineering report is a key form of written communication that is a direct reflection of the engineer’s knowledge of a particular subject. A well written report cannot cover up poor engineering; however, a poorly written report can be detrimental to otherwise excellent engineering work.

Technical writing is a continuous process of learning, carefully gathering, sifting, organizing, and assessing, all while trying to craft something that makes sense for a user. —Krista Van Laan, The Insider’s Guide to Technical Writing [Goodreads 2020] Contextualization lies in bringing out the right messages from the abundant content; in sandwiching the subject between the background of information and the foreground of its utility. —Suyog Ketkar, The Write Stride [Goodreads 2020]

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

• Available as EPUB and PDF
• Read on any device
• Instant download
• Own it forever
• Compact, lightweight edition
• Dispatched in 3 to 5 business days
• Free shipping worldwide - see info
• Durable hardcover edition

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Author information

Authors and affiliations.

Department of Mechanical and Energy Engineering, Southern University of Science and Technology, Shenzhen, Guangdong, China

Yongsheng Ma & Yiming Rong

You can also search for this author in PubMed   Google Scholar

Corresponding author

Correspondence to Yongsheng Ma .

Rights and permissions

Reprints and permissions

Copyright information

© 2022 The Author(s), under exclusive license to Springer Nature Switzerland AG

About this chapter

Ma, Y., Rong, Y. (2022). How to Write Engineering Report. In: Senior Design Projects in Mechanical Engineering. Springer, Cham. https://doi.org/10.1007/978-3-030-85390-7_15

Download citation

DOI : https://doi.org/10.1007/978-3-030-85390-7_15

Published : 11 November 2021

Publisher Name : Springer, Cham

Print ISBN : 978-3-030-85389-1

Online ISBN : 978-3-030-85390-7

eBook Packages : Engineering Engineering (R0)

Share this chapter

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

• Publish with us

Policies and ethics

• Find a journal
• Track your research

• Semiconductors
• $2 for 1-8 layer PCBs

How to Write an Engineering Report

• Table of Contents

 Structure of Engineering Reports: Structure of Engineering Reports

Engineering reports are based on the same format. Technical reports should contain the following components:

• Executive Summary
• Introduction
• Conclusions and recommendations
• Appendices and references

The first page of the report will be the most important. They inform the reader where to find the important information throughout the document. Keep in mind that investors might not go through the executive summary.

The title pages must clearly explain the reason for your writing. 

The executive summary should be no more than two pages and serve as a condensed summary of your research, conclusions, and suggestions. 

If your reader would like more details, your content list should permit readers to locate the appropriate section within minutes.

You are in the right to choose how you will design the body. However, it must be coherent and provide the reader with information while justifying your assertions and making sure the reader is aware of the intention behind the report. 

Adhering to this structure makes report writing easier, and you can focus on the content that follows.

 Technical Report Summary

Technical reports must include an introduction that explains the report’s objective and the main question the research will answer. Do they provide information on the need for your city to have an upgrade to a highway or bridge? Do you explain to an investor the reason to invest in your plan?

The summary of your technical report should be able to entice your readers. Explain to your reader what you’ve researched and why it’s relevant. Incorporate your client’s request and the scope of work in your writing and connect the information to the requirements of your stakeholder, client, or executive.

Methodology

The section on methodology is typically the most complicated section of your report. In this section, you discuss the process you used to conduct your research and the reasons you conducted the subject in the way you did.

The section you write in should demonstrate the depth of your research and should outline the research plan in a clear manner. The writing should explain the sources you used to gather your data and also how your research methods can bring something that is new to the area of expertise. The section you write about should show confidence in the work of your business in order that your readers will feel confident as well.

When you write about the results and findings of your technical reports, be sure not to make this part your final statement. In this section, you must only write down the results of your studies, analyses, and tests. Include pictures to show your findings,

Your report will inform readers how you came to the solution you came up with to their issue. Technical reports typically require you to convey complex information. Therefore, it is important to use the same language similar to the language you used in the overview of your technical report. This will allow readers to draw connections between your writing and comprehend how they connect to your report.

<H2> Recommendations and Conclusions

The final part of your report prior to making your references and appendices contains your conclusions and recommendations. This section should be aligned with your introduction so your writing makes it possible for the reader to connect with your document. 

Your writing is designed to provide a solution to a question. 

Your conclusions and recommendations are the final pieces to answer that question via investigation, which allows you to explain how your client must respond to the circumstance.

 Still need help with your report? Click it out here for assistance from professional writers!

Share this:

Wholesale PCBs SMT Stencil & PCBA Service Provider

Special offer:$2 for 1-8 layer PCBs 

Sign Up & Get 54$ Coupon

Author:  Henry

I am a professional engineer and graduate from a reputed engineering university also have experience of working as an engineer in different famous industries. I am also a technical content writer my hobby is to explore new things and share with the world. Through this platform, I am also sharing my professional and technical knowledge to engineering students. Follow me on: Twitter and Facebook .

Related Posts

When to Consider Tree Lopping: Signs Your Trees Need Attention March 25, 2024

Unlocking Opportunities: How to Choose Effective Digital Marketing Strategy for Car Hire Businesses in Leeds February 22, 2024

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

Post comment

Purdue Online Writing Lab Purdue OWL® College of Liberal Arts

Welcome to the Purdue Online Writing Lab

Welcome to the Purdue OWL

This page is brought to you by the OWL at Purdue University. When printing this page, you must include the entire legal notice.

Copyright ©1995-2018 by The Writing Lab & The OWL at Purdue and Purdue University. All rights reserved. This material may not be published, reproduced, broadcast, rewritten, or redistributed without permission. Use of this site constitutes acceptance of our terms and conditions of fair use.

The Online Writing Lab at Purdue University houses writing resources and instructional material, and we provide these as a free service of the Writing Lab at Purdue. Students, members of the community, and users worldwide will find information to assist with many writing projects. Teachers and trainers may use this material for in-class and out-of-class instruction.

The Purdue On-Campus Writing Lab and Purdue Online Writing Lab assist clients in their development as writers—no matter what their skill level—with on-campus consultations, online participation, and community engagement. The Purdue Writing Lab serves the Purdue, West Lafayette, campus and coordinates with local literacy initiatives. The Purdue OWL offers global support through online reference materials and services.

A Message From the Assistant Director of Content Development 

The Purdue OWL® is committed to supporting  students, instructors, and writers by offering a wide range of resources that are developed and revised with them in mind. To do this, the OWL team is always exploring possibilties for a better design, allowing accessibility and user experience to guide our process. As the OWL undergoes some changes, we welcome your feedback and suggestions by email at any time.

Please don't hesitate to contact us via our contact page  if you have any questions or comments.

All the best,

Social Media

Facebook twitter.

We've detected unusual activity from your computer network

To continue, please click the box below to let us know you're not a robot.

Why did this happen?

Please make sure your browser supports JavaScript and cookies and that you are not blocking them from loading. For more information you can review our Terms of Service and Cookie Policy .

For inquiries related to this message please contact our support team and provide the reference ID below.

BRIEF RESEARCH REPORT article

This article is part of the research topic.

Industry 4.0: The Impact and Implications for Transitioning Process Industries

Matchmaking for Industrial Symbiosis: a digital tool for the identification, quantification and optimisation of symbiotic potential in Industrial Ecosystems Provisionally Accepted

• 1 National Technical University of Athens, Greece

The final, formatted version of the article will be published soon.

Effective waste management is crucial for sustainable industrial operations. This paper introduces a state-of-the-art digital tool designed for the circular economy. Primarily it pinpoints and quantifies symbiotic possibilities between industries with liquid waste streams, emphasising the most lucrative inter-industry connections. In practice, the tool takes in data such as waste stream volumes, material concentrations within these streams, market prices of materials, and industries' raw material consumption rates. Utilising these, its algorithm identifies and assesses the most profitable material exchanges among the specified industries. This assessment considers the market value of materials and the costs associated with recovering those materials from liquid waste streams. One of the major challenges, the estimation of recovery costs, is addressed using an innovative Sherwood plot analysis. This analysis draws a correlation between a material's recovery cost and its concentration within a liquid medium. The tool's output provides a detailed list of potential transactions complemented by illustrative graphs that detail mass flows, profit margins, and environmental advantages for each industry. Collectively, these details offer insights both for individual industries and the industrial ecosystem as a whole. One of the tool's most significant revelations is its ability to uncover potential 'bridges' linking industrial waste streams to resource needs, unearthing previously unnoticed economic and ecological gains. By calculating economic and environmental benefits of "waste" reuse, this tool offers a compelling rationale for the adoption of industrial symbiosis. Ultimately, it uncovers the transformative potential of aligning industrial activities with a balance that fosters both economic growth and ecological responsibility.

Keywords: industrial symbiosis 1, circular economy 2, sustainability 3, material reclamation 4, waste valorisation 5, digital tool 6, optimisation 7, Sherwood plot 8 . (Min.5-Max. 8)

Received: 31 Dec 2023; Accepted: 16 May 2024.

Copyright: © 2024 Makropoulos, Kritikos and Pantazis. This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY) . The use, distribution or reproduction in other forums is permitted, provided the original author(s) or licensor are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.

* Correspondence: Mr. Nikolaos Alexandros Kritikos, National Technical University of Athens, Athens, 15780, Greece

People also looked at