Document 522 – Post-Assessment Report
Instructions for Report Preparation
Please go to the EWB-USA website to make sure that you are using the most current version of this document.
The information gathered during the assessment trip is archived, presented and summarized in this document. All information gathered should be included as appendices to this document. This includes notes, photographs, sketches, survey information, interview notes, measurements and any other pertinent data. The data should also be summarized as appropriate. For example survey data should be reduced and appropriate mapping should be prepared. This report should be prepared and submitted to EWB-USA National Staff within the first month (30 days) of return from your trip, while the information is fresh in your minds, before making progress on your design. The 522 – Post-Assessment Report will follow the same review cycle as the pre-trip reports and will be processed and reviewed within one month of the deadlines listed on the submittal deadlines table on our website (Member Pages – Project Process – Submittal Deadlines). For example, if a 522 – Post-Assessment Report is submitted on the Monday one day after the monthly Sunday deadline, the report will be processed and reviewed after the following month’s deadline.
Formatting – Please ensure correct page numbering in your document, and include a Table of Contents. Also, please minimize the number of documents submitted. Multiple documents are unprofessional and confusing.
Size Limit (10MB) – Please limit the size of the reports submitted to the National Office to a maximum size of 10MB. If you compress the photos within the document, this will help reduce the size of the entire document. If you do not know how to compress photos, please see our website for instructions. Please contact firstname.lastname@example.org if you have special circumstances that may require a larger report submittal.
There are two parts to the post-assessment trip report: Part 1 includes the administrative information for the trip and Part 2 includes the technical information.
Part 1 is a fill-in-the-blank exercise that provides the EWB-USA National Office with specific information about the chapter and program. The information should be provided in the exact format requested without deviation. If you have questions about completing Part 1 of the report contact your Chapter Relations Manager (CRM) at the EWB-USA National Office.
Part 2 of the report is not a fill-in-the-blank exercise. This is the portion of the report where your chapter provides all the technical information about the project. The outline of this portion of the report can be modified by the chapter if necessary to present the project more clearly. It is your chapter’s responsibility to clearly and thoroughly present your project and the results of your completed assessment trip. Note that you may need to include additional information that is not listed depending on the specifics of your project. If you have questions about completing Part 2 of the report, contact one of the Project Managers (PM) at the EWB-USA National Office.
Part 1: Administrative Information – Instructions
1.0 Contact Information – Fill in the table completely with updated contact information for current project leaders. This information will be used by EWB-USA National Office staff to contact your project team throughout the review process.
2.0 Travel History – Show every trip that your chapter has taken for this program.
3.0 Travel Team – Include information for all the travel team members that actually traveled on the trip.
4.0 Health and Safety
4.1 Incident Reports – If there were any health and safety incidents during the trip, check “Yes” and submit your completed Incident Report as a separate attachment with this report. If your HSO has not yet filled out the Incident Report, a blank form can be found on the EWB-USA website – Member Pages – Project Process – Health and Safety Program. If there were no incidents, check “No.”
5.1 Cost – This should be your actual budget including what team members paid. Please include in-kind contributions.
5.2 Professional Mentor/Technical Lead Hours – Note that EWB-USA can count the volunteer hours of Professional Mentors (student chapters) and Technical Leads (professional chapters) towards our in-kind donations. Therefore, it is helpful for us to know how many hours these volunteers have spent on the project for each trip. Please report the pre-trip, during trip, and post-trip hours in this table for each Professional Mentor/Technical Lead for this trip only.
6.0 Project Discipline(s) – The headings in bold are project types, the subheadings are project disciplines. Check all project disciplines addressed in this report. Note that each project type needs to be approved by an EWB-USA Project Manager. If this is a new project that has not previously been approved, your chapter may need to submit a 501B – New Project Within Existing Program Application.
7.0 Project Location – Provide the longitude and latitude of the project location so that the project site can be located using Google Earth.
Part 2: Technical Information – Instructions
1.0 Introduction – Explain the purpose of this document and provide a short description of the project and recently completed trip.
2.0 Program Background – Provide the background for the project. This can be taken directly from the pre-assessment form with modifications that incorporate information gathered during your trip and should be updated with each subsequent trip.
3.0 Trip Description – Provide a concise description of the trip sufficient for anyone who had not participated on the trip to understand what happened on the trip.
4.0 Community Information
4.1 Description of Community – Describe the community using information gathered during the assessment trip. Information should include those items that will have a bearing on the design of a project such as population, population density, infrastructure in the community (type and number of houses, water, power, industry, farming, roads, etc.), geographical size of the community, proximity to transportation, etc.
4.2 Community and Partnering Organization/NGO Resources and Constraints – This is similar to same section in the pre-assessment document but includes information gathered during the assessment trip.
4.3 Community Relations – This is similar to same section in the pre-assessment document but includes information gathered during the assessment trip.
4.4 Community Priorities –List the community’s top priority projects, in addition to any other major findings from your community meeting. Any notes from the community meeting should be included as an appendix and not in the text of the report.
5.0 Data Collection and Analysis
5.1 Summary of Data – Include a summary of all the data that was collected on the trip. This summary in general is best displayed using drawings, charts and graphs. The full data should be included in appendices. This includes notes, photographs, sketches, survey information, interview notes, measurements and any other pertinent data. For example, include the names and contact information for the key community members involved in the project in the text of the report. Interview notes for discussions with the individuals during the site visit should be included in an appendix.
5.2 Mapping – Provide the base mapping that will be used for the project. If your chapter does not have mapping that clearly illustrates the components of the project and the design issues that are associated with the project, this likely indicates a significant deficiency with the document and the project. If the mapping has not yet been finalized, present the current version of the data with an explanation of the additional items to be added to the mapping. The type, scale and scope of the mapping will be dictated by the requirements of the project. For example, topographic information will likely be essential for any water pipeline projects, whereas this is probably not important for a solar power project.
6.0 Monitoring— List at least three metrics by which you will measure the success of your project. List all data, both quantitative and qualitative, that will be required to develop those metrics. Also provide details on the methods used for data collection.
6.1 Monitoring of past-implemented projects: If you monitored the status of past-implemented projects on this trip, include all data, both quantitative and qualitative, that were used to measure the success of your project(s). Also provide details on the methods used for data collection. In addition, complete the following information for each project.
Project Discipline – State the discipline of the past-implemented project you monitored. Use only the terms listed in Part 1, Section 6.0 above.
Date of Completion – What was the date of the completion of the project implementation? (month/day/year)
Functionality – What percentage of the project implemented is functioning as designed? (0-50%, 50-75%, 75-100%)
Enhancement – Has the community enhanced the system implemented at all? (Yes or No)
Duplication – Has the community duplicated the design on their own in another location? (Yes or No)
7.0 Community Agreement/Contract – A community agreement/contract can take many forms including a memorandum of understanding, signed letter of intent, formal contract, etc. You will need to decide which is most appropriate based on feedback from your community partners. Provide an English version of the draft agreement/contract that your team has developed with the community leadership. If this was a first assessment trip, this document will likely still be conceptual in nature. If it is a second (or later) assessment trip, the community agreement/contract should be detailed in nature. See the EWB-USA website for an example agreement/contract.
8.0 Photo Documentation – Provide a few photographs of relevant parts of the project along with a description for the photograph. Additional photos taken during the project along with a photo log can be included in an appendix
9.0 Project Feasibility – Provide a discussion of the program feasibility and the decision of whether the chapter will continue with the project.
10.0 Lessons Learned – Provide a section on the lessons learned during this trip. The purpose of this section is to help the chapter in their future trips and also assist other EWB-USA chapters that may read this document. Each of the lessons learned should be concise and descriptive.
11.0 Project Status – Describe the project status of each project type that was included in your assessment trip. Use one of the following options for each project type:
Assessment Continues – Select this option if the assessment work is not complete and additional information is needed from the site to move forward with design development.
Design – Select this option if the assessment work is complete and the next phase will be to begin designing the project.
Cancelled – Select this option if the project type that you had planned to assess will not be implemented at any point in the future.
Note: If a new project type has been identified as a top priority of the community and your team plans to focus on this new project type, please submit a 501B – New Project Application within Existing Program Application.
12.0 Mentor Assessment – The Professional Mentor (for student chapters) or Technical Lead (for professional chapters) should write a short assessment of how the project team carried out the trip, what decisions were made during the trip and what the next phase of the project will be. You should discuss the requirement in this section with your Professional Mentor/Technical Lead ahead of time to accommodate their schedule in anticipating the submittal deadline. This section is required for review.
12.1 Professional Mentor/Technical Lead Name – List the name of the Professional Mentor/Technical Lead who wrote the assessment.
12.2 Professional Mentor/Technical Lead Affirmation – The Professional Mentor/Technical Lead should write one sentence here acknowledging their involvement in the trip preparation and their acceptance of responsibility for the course that the project is taking.