For memos:

Memos should be correctly formatted, addressed to the correct recipient, and with adequate margins and font size. Only one page permitted; I will not grade more than one page. Memo should have correct grammar and spelling. It's only one page, so proof it.

The bulk of the points come from content. The expected content is as follows:

Introduction:Briefly (1 sentence or less) describe project, and who requested it. Describe the deliverables, including their formats, titles, and what each represents.

Body: Describe process, in English. I want to know what the layers are and your data sources (originators and brief description, i.e. roads or watershed, not file name and not Z:/Greenfield/Projdata folder, please). I then want to know what you did with them (in a non-technical sense), why you did it that way, and what you produced from it. Basically, convince me you know what you did in lab other than follow directions to press buttons.

Describe results, including any significant statistics even if they are included in your deliverables elsewhere.

Discuss any potential problems or considerations (such as difference in apparent and actual scale, alignment difficulties) with the data or process that may affect the results in a way the client needs to be aware of. Human errors in completing a lab do not fall into this category, unless they went uncorrected.

Make some sort of conclusion about your results (northeastern region most affected, high temperatures would change patterns, whatever is notable about your products). Tell the client what they will find of interest about the maps and tables you spent so much time laboring to produce.

Note time spent. Imagine I were going to pay you for your work...


For maps:

Maps must include desired features. Missing layers or obviously incorrect results (it is obvious if I can tell on sight) will result in docked points. Extent of map should reasonably match scope of project. If detail is too small to be seen, the map cannot effectively convey your results. Each element should be visible and recognizable within map. The most significant element or elements (the point of the map) should be the most prominent. Use labels as necessary to clarify.

All maps must include a title, scale bar, north arrow, author name, date, and sources used. Title should be highly prominent, succinct, and descriptive. In other words, without seeing the lab, any viewer should be able to tell what the map is supposed to represent. Confusing or misleading titles are detrimental to viewer understanding. When citing sources, note it so that a viewer knows that, say, the U.S. Census produced the data, not the map. For scale bar, make sure the labels don't overlap. Ideally, your scale bar should give some round number, like 1 mile or 2000 meters.

Legends are frequently required. When key is included, the terms must be in English (not code/GIS-speak). Each element should be visible and each term legible. Key must match map symbology, and all elements within map must be included in legend (ask me about exceptions, but when in doubt, put it in).

Finally, composition must show reasonable effort. Carelessly composed maps show a disrespect for your own work and are not acceptable. Check the spelling of any words within the map; misspelling the title or contributing agency's names looks bad. Maps must include reasonable margins (at least 3/4 inch). Do not place "picture" within a neatline and other elements in the margins; when in doubt, place all elements within neatline. If map is requested in black and white, do not produce a color version.

Maps turned in must be original work. No photocopies.


For tables:

Tables must be formatted in a coherent, easily readable fashion. If a layout was specified by the client, use it. Units should be identified within the headings, or repeated for each entry, as necessary. Incorrect values will be marked down.

Typically, I create a checklist for each deliverable. Missing or poorly executed elements are deducted for. Extra effort may offset deducted points.