Mn/DOT Market Research Reporting General Guidelines for Qualitative and Quantitative Market Research Reports Revised: August 2, 2011

Similar documents
MARKET RESEARCH AND EVALUATION2017. Reporting Guidelines

Usability Report for Online Writing Portfolio

GT48232/ME4182 First Progress Report & Presentation (Fall 2016)

Creating a data file and entering data

IEEE Transactions on Fuzzy Systems (TFS) is published bi-monthly (February, April, June, August, October and December).

Evaluation Department, Danida. Layout guidelines for evaluation reports

FORMATTING GUIDELINES FOR RESEARCH REPORTS (for 2011submissions)

Evaluation Department, Danida. Layout guidelines for evaluation reports

[Maria Jackson Hittle] Thanks, Michael. Since the RSR was implemented in 2009, HAB has been slowing shifting its focus from data submission to data

Data to Story Project: SPSS Cheat Sheet for Analyzing General Social Survey Data

Background Information TPL Transmission System Planning Performance Requirements

Report Template. Joe B. Student and Dan Simon * Department of Electrical and Computer Engineering Cleveland State University Cleveland, Ohio 44115

Lesson 2 Writing Business Reports. Henan University of Technology Sino-British College Transfer Abroad Undergraduate Programme

Notes For Making an NTI Toolkit revised

Accountable Care Organizations: Testing Their Impact

Style guide for Department for Education research reports and briefs

7/11/14. Presented by: Overview. Writing effective subject lines Creating good body copy Choosing HTML vs. Plain Text s

Documenting Your Design

8 Organizing and Displaying

A GUIDE TO WRITING TECHNICAL REPORTS

Create Custom Tables in No Time

CHAPTER 2 Information processing (Units 3 and 4)

Excel Tips and FAQs - MS 2010

8. MINITAB COMMANDS WEEK-BY-WEEK

Software Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author(s)> <Organization> <Date created>

Abbreviated Title of Report. Table of Contents USING THIS DOCUMENT...2 SDWP REPORT FORMATTING...2 Charts...3 Tables...9 APPENDIX A...

Getting Started with Qualtrics

Usability Testing. November 14, 2016

Survey Questions and Methodology

Evaluating the Effectiveness of Using an Additional Mailing Piece in the American Community Survey 1

Software Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author> <organization> <date created>

OpenFlow Trademark Policy

Making Tables and Figures

GT48232/ME4182 Final Progress Report & Presentation (Fall 2015)

CPSC 444 Project Milestone III: Prototyping & Experiment Design Feb 6, 2018

Dissertation Formatting Rules. Basic Format

ME 4054W: SENIOR DESIGN PROJECTS

Mega International Commercial bank (Canada)

WEB ANALYTICS A REPORTING APPROACH

Presented by Dr. Mariah Judd February 15, 2013

The first thing we ll need is some numbers. I m going to use the set of times and drug concentration levels in a patient s bloodstream given below.

SyncFirst Standard. Quick Start Guide User Guide Step-By-Step Guide

Table of contents. TOOLKIT for Making Written Material Clear and Effective

THE TITLE OF THE THESIS IN 12-POINT CAPITAL LETTERS, CENTERED, SINGLE SPACED, 2-INCH FORM TOP MARGIN YOUR NAME ALL CAPITAL LETTERS A THESIS

Making Your Word Documents Accessible

Notes for authors preparing technical guidelines for the IPCC Task Group on Data and Scenario Support for Impact and Climate Analysis (TGICA)

Report on the usability test of [name]

For many people, learning any new computer software can be an anxietyproducing

Business Requirements Document (BRD) Template

<Project Name> Use Case Specification: <Use-Case Name> Version <1.0>

POFT 2301 INTERMEDIATE KEYBOARDING LECTURE NOTES

WPPD Senior Pharmaceutical Care (PC) Paper Evaluation Student Name:

Technical Paper Style Guide

Survey Questions and Methodology

Follow this and additional works at: Part of the Technical and Professional Writing Commons

Handling Your Data in SPSS. Columns, and Labels, and Values... Oh My! The Structure of SPSS. You should think about SPSS as having three major parts.

Montgomery College. Writing for the Web. Created by Paula Carrasquillo, Web Editor

Instructions & Procedures for Using Scan Forms

Projected Message Design Principles

Developing successful posters using Microsoft PowerPoint

Short Guide to using the Report Template (Version 3)

Creating Great Visual Aids

Guidelines on How to Structure & Format URBP 298 Planning Reports

It is written in plain language: no jargon, nor formality. Information gets across faster when it s written in words that our users actually use.

RAD Posters & Preparation Overview. Research Appreciation Day Education Session February 2017

YOUR LOGO HERE TITLE HERE: SUBTITLE HERE. Document No. HERE. Prepared for Put Name and Client Logo Here

DOCUMENTS AND THEIR FORMATS: REPORTS AND PROPOSALS. A Short Proposal or Report? Deciding Between Letter and Memo Format

Word Processing for a Thesis, based on UEA instructions

Cognitive Disability and Technology: Universal Design Considerations

University of Moratuwa

Standards Designation and Organization Manual

Creating Universally Designed Word 2010 Documents - Quick Start Guide

Resource Center & Messaging System

The Demographics of Mobile News Habits

FedRAMP General Document Acceptance Criteria. Version 1.0

GOING IN STYLE (#3): ON TYPOGRAPHY, PART 2

Constructing a Qualtrics survey Before you = start

Qualitative Data Analysis: Coding. Qualitative Methods: Interviews Chickasaw Nation September 12, 2017

What are the elements of website design?

User Story Workshop. BA-Squared, LLC

Let s get started with the module Getting Data from Existing Sources.

Design Proposal: Outline

Federal Plain Language Guidelines

Safety Perception Survey s: Interviewing & Sampling Method Considerations

To make sense of data, you can start by answering the following questions:

COMP 388/441 HCI: 09 - Balancing Function and Fashion Balancing Function and Fashion

Contents. Before you begin. Topic 1: Plan documents 1. Topic 2: Draft text 41. Topic 3: Prepare final text 63. Topic 4: Produce a document 79

RAD Posters & Preparation Overview. Research Appreciation Day Education Session February & March 2018

Readers are wary of out of date content, so it's important to actively manage the information you publish.

Technical Writing Process An Overview

Developed by: Beth Gibbs

Presentational aids should be used for the right reasons in the right ways

NETIQUETTE GUIDE FOR ONLINE LEARNING GADSDEN STATE COMMUNITY COLLEGE TEACHING & LEARNING CENTER

Tips to design your proxy statement and implement graphics in Wdesk. Your Message. Understood.

USABILITY REPORT A REPORT OF USABILITY FINDINGS FOR OFF THE BEATEN PATH WEBSITE

Images for Easy English

Web Evaluation Report Guidelines

APPENDIX 1 7 APPENDIX 2 8 APPENDIX 3 10 APPENDIX 4 11

Business Letters. Business letters are formal letters used for business-to-business, business-to-client, or client-tobusiness

Quality Site Visit Report

Transcription:

Mn/DOT Market Research Reporting General Guidelines for Qualitative and Quantitative Market Research Reports Revised: August 2, 2011 The following guidelines have been developed to help our vendors understand our reporting requirements. These guidelines apply to all kinds of studies, unless specifically noted. Content Areas: The report should contain, at minimum, the following sections: Cover Page Table of Contents Executive Summary Background Objectives Methodology Readers Notes Summary of Findings/Key Findings Conclusions and Recommendations Detailed Findings Appendix These sections may be combined, if appropriate, at the writer s discretion (though subject to final approval from Mn/DOT Market Research). Each is further defined below: Cover Page: The cover page should include o Project title o Study date (i.e., month and year the bulk of the data were collected) o Date report was written o Report prepared by [vendor] o Report prepared by If the project manager is part of Mn/DOT Market Research, the report is prepared for Mn/DOT Market Research If the project manager is not a part of Market Research, do not include Mn/DOT Market Research in this area. o The cover page may include: logos Table of contents: Include all key report sections and list what is included in each appendix. If the report is in two volumes, make sure both are included in the Appendix. Do not include other materials provided (i.e., data tables) unless they are a part of the report. - 1

Executive Summary: The report writer will be asked to write a 2-3 page Executive Summary. The Executive Summary is a short non-technical synopsis of the study, and includes a short description of the project, key findings and recommendations. Background: Describe the background of the situation that leads to the study. If this study is a follow up to earlier research, briefly describe that research as well. If this is a tracking study, include information about previous administrations (i.e., when it was administered previously and key differences, if there are any). Objectives: Why the project was done, what was to be learned and how information will be used. All objectives should be covered in the detailed findings section of the report. Methodology: How the research was conducted, including the sampling plan, and basic screening criteria. Also include information regarding the design and include all key dates. Include any limitations in design and whether the results are projectable and, if so, to what group, or who is being represented. Note: This section should be relatively brief nuances or details regarding sampling, weighting, etc. (i.e., things of interest to other researchers) should be included in an Appendix. o Quantitative research: include margin of error on the total sample, and any key sub-groups, and weighting information, if weighting was done. Note that additional methodology information (for example, extended information about weighting) may be included as an Appendix. o Qualitative research: include a caveat regarding the use of the data Readers Notes: This section should include all information that will aid the reader in understanding the report. This may be included with Methodology at the writer s discretion. This may include: o Definitions of terms o Definitions of subgroups o Report organization information o Information regarding trend calculations o Information regarding significance testing and a note indicating that any differences mentioned in the report are significant and/or meaningful. (In quantitative reports, this is required to be in the report in some location.) o Information regarding highlighting used within tables or graphs. Summary of Findings/ Summary of Key Findings: The findings that directly address the objectives. Mn/DOT prefers that this summary not contain too many numbers, and instead use proportions or other semantic terms to relay the message. These should be worded so that they will be clear to the non-research readers. Mn/DOT would not expect to see graphics in the key findings section as a rule; however, if a summary table or graph is the best way to communicate the information (for example in tracking studies), that is acceptable. Ideally, this - 2

section will be very easy to read, formatted in bullets and short paragraphs. Do not include demographics, unless that is one of the key objectives. The Summary of Findings is similar to the Executive Summary, but should include more depth and should only address findings (not background, etc.). Conclusions/Conclusions and Recommendations: This section is optional, depending on the study. Conclusions take the key findings a step further. That is, if two or three findings formulate an idea, Mn/DOT would call that a conclusion (sometimes this is only a possible conclusion). Conclusions are not just a restatement of the findings. And although Mn/DOT does not require consultants to make recommendations, it is a plus when you can make well-founded and defensible ones. This section may be combined with Summary of Findings at the writer s discretion. Note that all recommendations should able to be traced back to this study, though may include information drawn from other sources or previous research. (For example, if no one in the survey has mentioned congestion, Mn/DOT would not expect a recommendation regarding this issue.) Detailed findings: Present the results of the study. Use charts and graphs to enhance the readability of this section. Structure the presentation of the data to tell the story, rather than presenting the data in questionnaire order. Note that some questions may not be included in the detailed findings (example: screening questions, demographics), but every question should be in the report in some way. In quantitative studies, report only those differences which are statistically significant. If differences are not significant, don t report them. Please avoid comparisons, such as higher, lower, significant, and so on, except in reporting statistical differences. Appendix: The appendices should include any material necessary for interpretation of the report. This may include: o Survey documents: questionnaires, screeners, discussion guides, handouts, etc. o Demographics: in studies of the general public, where possible, include census data to show how the study parallels the general public o Sample resolution data: incidence, hours on phone, completion ratio, number of calls, etc. o Detailed information regarding advanced statistical testing o Sample of comments included in codes Tracking studies: The point of a tracking study is to understand changes over time. As such, the body of the report should focus on trends and the interaction of the current year data with past data (i.e., if females rate something higher than males in the current year, is this similar to the past or is it unique to this year?). Additional current year information the writer feels should - 3

be included in the report, should be included in an Appendix (unless, of course, the questionnaire was changed). Remember to include a note in the body of the report referring the reader to the Appendix. Layout: It is important that each page of the report be able to stand alone. As such, every page should include the following: Report or Study Title Date (date = month and year in which the bulk of the data were collected) Page number Because of the requirement that each page stand alone, it is particularly important that charts and graphs be formatted as follows. Each chart or graph should include the following (footnotes are okay or elsewhere on the page, as long as they are obviously/clearly related): The full text of the given question. [If the question is too long to include, it can be abbreviated and the reader referred to the questionnaire in the Appendix.] Base sizes (n= ) Whenever possible, avoid splitting tables or graphs across pages. Others for open-ended questions should represent only 5% of responses, with 10% being the maximum. (Mn/DOT Market Research can grant exceptions to this rule.) Remember, all code lists need to be approved before using. Color: Be careful when using colors. For example, the color red generally connotes negative or bad results and should not be used as a highlight for positive results. Also, be sure that colors will be able to be distinguished between readers, though try not to make color differences so extreme as to be garish or distracting. Mn/DOT do not dictate the layout or graphics to be used; however, expect that the writer/analyst will present the data in ways that are most reader friendly, and follow generally accepted graphic/reporting standards. (For example, vertical bar charts are preferred for time series data.) In addition, Mn/DOT appreciates well-edited prose and proper grammar. A few reminders: Write concisely. Please self-edit and have someone who is unfamiliar (or less familiar) with the study read for clarity. Watch for common usage errors (affect vs. effect, etc.), and remember that data takes the plural ( data are not data is ). Also avoid the use of persons unless you re writing legal text, people is appropriate. And, when you re talking about people, use the word who rather than that, (i.e., respondents who participated not respondents that participated ). Watch for common grammatical errors (commas and periods go inside quotation marks always). Titles should be short and to the point. Formatting should be consistent throughout the report. This applies to text and titles as well as graphs and charts. - 4

Also, please note that a report or page may be printed in black and white. Please try to make sure colors used in graphs show some distinction when not printed in color. Deliverables: Unless otherwise stated in the contract or agreed upon with your project manager, deliverables should include: Clean data file (in Excel or SPSS) with a data map or layout and codes Data tables with statistical testing An electronic version of the report, in MS Word Three bound copies of the final report - 5