A colourful mineral-project map can appear immediately understandable while combining observed features, interpreted geology and planned work. The legend determines which is which, making a small part of the page consequential to the conclusions a reader draws from it.

Different kinds of line

A boundary may represent a surveyed feature, a commercial area or a technical interpretation. Those meanings should remain distinct. The map should identify its purpose and source information so readers do not treat every precise-looking line as equally established. Visual clarity is valuable only when it preserves the differences that matter to the decision being discussed.

Scale and apparent certainty

A presentation map may simplify detail for readability. That is often reasonable, but it should not be used for a task requiring more precise information. The owner should connect the illustration with the appropriate underlying records and make its intended use clear. Enlarging an image does not create additional evidence about the feature it depicts or the accuracy of its position.

A date on the landscape

Project boundaries, infrastructure and interpretations can change. The map's date and revision should therefore travel with it when reused in a report or data room. A familiar diagram can survive long after the technical team has updated its understanding, leaving commercial discussions anchored to a picture that no longer describes the current project position.

Visuals that support scrutiny

The strongest project maps help readers ask better questions and find the source behind a claim. For investors, that is more useful than a dramatic image with ambiguous symbols. A well-designed legend allows the visual story to remain concise while preserving technical honesty, giving the map a practical role in discussion without asking it to establish more than its underlying information can support.

References
  1. ALFA whitepaper ↗
  2. JORC Code, 2012 edition ↗