Based on reviewing past labs, here are some general recommendations related to writing reports / labs:

• You should always label every map, figure and table, and explicitly refer to them in your text. For example, “We can observe (Map 1) that the two paths are very different.”
• It is better to refer to the tables, figures and map as above (bracketed) rather than to use them as the subject of the sentence (e.g., it is poor grammar to state: Table 2 shows that …. Since ‘Tables’ are inanimate objects, they can’t ‘show’ us things!).
• You should caption elements appropriately—a table should be labeled as such (not as a figure or graph), and ensure that the rows / columns are labeled appropriately (that is, for example, use ‘Residential’ rather than Res in a header). If you do use acronyms, you should provide a footer that explains each acronym. This also applies to legend categories–do not use acronyms such as MedInc since the reader won’t know what the legend is specifically referring to. In this example, you should use Median Income rather than MedInc.
• Sorting the legend categories (e.g., land uses) alphabetically helps the reader find a specific entry (e.g., the Residential land use) in the tables and in the map legends.
• Where possible, tables (and figures) should be combined in order to make it easier for the reader to compare the values (e.g., two tables (or figures) showing the same metrics but for two different years should be combined into one table).
• You should rotate figures / tables if necessary in order to maximize their presentation on the printed page.
• Ensure that your maps are properly labeled, with your name, a date, data source, scale, north arrow, etc.  Legend entries should be checked for typos, and you should provide a proper title.  Watch out for the presentation of excessive (non)significant digits in the legend entries (that is, the ESRI default is to provide far too many digits when producing numeric legend entries). When adding an Inset Map, you need to ensure that the scale bar being used is the appropriate one.
• You must always consider what is an appropriate classification method for your data. You should not simply accept the default Jenk’s classification, as it often produces widely-variable classes (that is, some class may contain only a few values but have a very wide spread, while other classes may contain a large number of values but have a very narrow spread). It is impossible to judge the ‘significance’ of each class unless we know something of the underlying data distribution, and the classification method used. You should explore the data distribution and determine which of the various classification methods best represents the data (and explicitly identify on the map which classification method you used).
• Neat lines around maps help to ‘contain’ the content.
• You should try to use ‘standard’ colours on your maps whenever possible. You can access a wide variety of application-specific styles in ArcMap by selecting Style Manager… under Customize. In the Style Manager window, click on Styles (button on the right side), and scroll through the list of Style References provided by ESRI. If you select Civic and click on Okay, you should see the Civic style added to the list of style choices. If you click on the [+] to open the Civic menu, you’ll see that only some of the possible styles contain data (if the folder symbol is blank there are no civic-specific styles available). If you click on Colors (and Fill Symbols) you’ll be presented with a large selection of colour choices. Two other relevant styles are Conservation and Environmental.
• An Executive Summary, if required, should be presented immediately after the title page, and on a page by itself. Adding appropriate headers, such as Introduction, Discussion, Summary (or Conclusion or Recommendations), throughout the text also helps the reader follow your work.