MPO Policy and Procedures Manual - Indianapolis Metropolitan ...
MPO Policy and Procedures Manual - Indianapolis Metropolitan ...
MPO Policy and Procedures Manual - Indianapolis Metropolitan ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
scope, schedule, <strong>and</strong> budget, <strong>and</strong> review interim <strong>and</strong> final deliverables for content <strong>and</strong><br />
grammar.<br />
Particularly significant projects should include the development of an annotated outline as a<br />
specific task item.<br />
Document St<strong>and</strong>ards<br />
Draft documents should include the following items:<br />
44<br />
• Cover sheet with title of project, date of final submittal, <strong>and</strong> <strong>MPO</strong> logo<br />
• A version number <strong>and</strong> date history, including reviewer names.<br />
Final documents should include the following items:<br />
• Cover sheet with title of project, date of final submittal, <strong>and</strong> <strong>MPO</strong> logo<br />
• <strong>MPO</strong> logo in either the header or footer of the document<br />
• A table of contents, including page numbers<br />
• A credits page, which lists the <strong>MPO</strong> project manager, <strong>MPO</strong> staff, contractor address <strong>and</strong><br />
staff members (if applicable), <strong>and</strong> other pertinent stakeholders (e.g., study review<br />
committee)<br />
• An executive summary<br />
• A paragraph statement of the study’s purpose <strong>and</strong> need, including its relationship to the<br />
LRTP goals <strong>and</strong> objectives the UPWP<br />
• (Optional) A paragraph statement of the study’s relationship to the <strong>MPO</strong> Strategic Plan.<br />
Note that contractor logos are generally not allowed on any interim or final documents, including<br />
PowerPoint presentations, display boards, or h<strong>and</strong>outs. Contractors may be listed (text only) on<br />
the credits page (see above) <strong>and</strong> the rear cover (text <strong>and</strong> address only). All final deliverables<br />
should be developed with the viewing public in mind. While not required for all documents,<br />
projects of significant scope that have a large potential for public review should be developed<br />
using desktop publishing software.<br />
File size is an issue that should be considered in final document submittal. Generally,<br />
documents will be posted on the web, so file sizes should be commensurate with downloading.<br />
Images in particular (including maps) should be subject to special scrutiny. Images intended for<br />
direct display on a web page should be no larger than 50k <strong>and</strong> 90 dpi. Images embedded in<br />
PDF documents can have larger resolution, but the overall file size of the document should then<br />
be scrutinized. If it is not possible to have a manageable document file size with images, then a<br />
version without images should be submitted, along with separate files for individual image<br />
viewing. If there are any questions, please contact <strong>MPO</strong> staff for further guidance.<br />
Map St<strong>and</strong>ards<br />
All hardcopy <strong>and</strong> electronic map versions, regardless of interim or final status, should have the<br />
following elements:<br />
• Title<br />
• A listed scale, either by use of a scale bar or a text scale<br />
• North arrow