How to Present GIS Data to a Board of Directors

The Presentation Problem

You have spent three weeks on a spatial analysis that reveals a clear pattern: infrastructure in the southeast quadrant is deteriorating faster than projected, and without intervention, the city faces $14M in emergency repairs over the next five years. The data is solid. The methodology is sound. The map tells the story perfectly.

Then you present it to the board of directors, and five minutes in, someone asks “Can you go back to the slide with the numbers?” and another director is checking email on their phone. The analysis dies in committee.

The failure is not analytical. It is translational. GIS professionals are trained to create maps. They are not trained to present spatial analysis to senior leaders who think in budgets, risks, and strategic priorities — not in feature classes, projections, and symbology.

Here is how to bridge that gap.

Know Your Board’s Decision Framework

Before designing a single slide or map, understand how your board processes information and makes decisions.

What Boards Care About

Boards of directors — whether municipal councils, utility boards, nonprofit boards, or corporate boards — evaluate proposals against a remarkably consistent set of criteria:

• Financial impact: What does it cost? What does it save? What is the payback period?
• Risk: What happens if we do this? What happens if we do not?
• Constituent/customer impact: Who benefits? Who is harmed? How many people are affected?
• Timeline: When do we see results? What are the milestones?
• Alternatives: What else could we do with this money? Why is this option better?

Notice what is not on the list: data sources, analysis methodology, software platforms, or cartographic technique. These are critical to the work but irrelevant to the decision.

Reading the Room in Advance

Before the presentation:

• Ask the board secretary or chief of staff what format presentations typically follow
• Learn how long presentations usually run (most boards allocate 10-15 minutes; plan for 8)
• Identify any board members with strong opinions on your topic
• Find out if the board packet is distributed in advance — if so, your printed material needs to stand alone without verbal narration
• Ask whether questions happen during or after the presentation

Structuring the Presentation

The 3-Map Rule

Most GIS analyses produce dozens of map outputs. For a board presentation, use exactly three:

1. The problem map: Shows the spatial distribution of the issue (aging infrastructure, coverage gaps, risk concentrations). This establishes why the board should care.
2. The impact map: Shows who is affected (population density, customer locations, critical facilities in the impact zone). This makes the abstract problem personal.
3. The solution map: Shows the proposed action — where investment will go, phased over time. This answers “what are you asking us to do?”

Three maps, each with one clear message. A director can follow the logic: here is the problem, here is who it affects, here is the fix. More than three maps and you lose the narrative thread. Fewer than three and you lack sufficient evidence.

The 10-Minute Framework

Structure your presentation into four segments:

Minutes 1-2: The hook (no map)

Open with a specific incident, a dollar figure, or a constituent impact. “On September 3rd, a water main failure on Elm Street left 2,400 homes without service for 14 hours and cost $340,000 in emergency repairs.” This grabs attention before you show any spatial data.

Minutes 3-5: The problem map + the impact map

Show the problem map. “That Elm Street main was one of 287 segments in our system rated critical. Here is where they are.” Pause. Let the spatial pattern register. Then show the impact map. “These critical segments serve 47,000 residential customers and 14 critical facilities including two hospitals and three schools.”

Minutes 6-8: The solution map + the financials

Show the solution map. “Our proposed CIP addresses the 85 highest-risk segments over three years. Phase 1 covers District 3 and District 7 — the areas with the highest concentration of critical segments and the largest served population.” Then present the financial summary: total cost, cost per year, projected savings, and what-if-we-do-nothing cost.

Minutes 9-10: The ask + the alternative

“We request $4.2M in the FY2026 capital budget for Phase 1. Without action, we project 12-15 main breaks per year in these segments, costing an estimated $5.1M annually in emergency repairs and service disruptions.”

Map Design for Board Presentations

Simplify Ruthlessly

Your analysis map in ArcGIS Pro might have 15 layers, a custom color ramp, and detailed labeling at every zoom level. Your board map should have 3-4 layers maximum:

• A clean, muted basemap (Light Gray Canvas or a custom minimal basemap)
• Your primary thematic layer with simple, high-contrast symbology
• Reference layers for context (district boundaries, major roads, landmarks)
• Labels only on features the board will reference in discussion

Use Board-Friendly Symbology

• Red/yellow/green for condition or risk ratings — universally understood without a legend explanation
• Graduated sizes for magnitude (larger circles = more people affected, more money at risk)
• Bold district or zone boundaries so board members can locate their constituency
• No classification breaks that require statistical literacy. “Natural breaks (Jenks)” means nothing to a director. “Poor / Fair / Good” means everything.

Label What Matters to the Board

Board members think in terms of neighborhoods, districts, and landmarks — not parcel IDs, feature GUIDs, or asset numbers. Label maps with:

• Neighborhood or district names
• Major intersection names (not street segment IDs)
• Well-known landmarks (schools, hospitals, government buildings)
• Dollar figures or population counts where relevant

Aspect Ratio and Resolution

If presenting on a projector or large screen, design maps at 16:9 aspect ratio. Leave the bottom 15% of the slide for a one-line takeaway statement, not a legend. If the map needs a legend, the symbology is too complex.

Export maps at 150+ DPI for screen presentation. For board packets (printed), use 300 DPI and CMYK color space.

Handling Questions

Board questions about GIS presentations fall into predictable categories:

“What does this mean for my district?”

Prepare a backup map or table that breaks down the analysis by board member’s geographic constituency. Know the numbers for each district cold: count of affected assets, population served, estimated cost. If asked, pull up the district-specific view immediately.

“How confident are you in these numbers?”

Be honest about data quality and methodology limitations. “The condition ratings are based on 2023 inspection data covering 94% of the system. The 6% uninspected segments are estimated based on age and material curves. The cost projections use a 3% annual inflation factor and are based on our actual repair costs from the past five years.” Specificity builds confidence; vagueness erodes it.

“What if we only fund half?”

Have a contingency scenario prepared. Show which projects would be deferred, what the risk exposure would be for the unfunded portion, and how the timeline shifts. This is where a prioritized project map with phases is invaluable — you can simply draw the line between “funded” and “deferred.”

“Can you show me [something not in your presentation]?”

If possible, have ArcGIS Pro or a web map open on a backup device. Being able to zoom, toggle layers, and explore data in real time during Q&A demonstrates command of the data and builds credibility. Practice navigating to the most likely on-the-fly requests beforehand.

“Why GIS? Could we do this with a spreadsheet?”

This question challenges the value of spatial analysis itself. Answer with what the map revealed that a table could not: spatial clusters, proximity relationships, geographic equity, infrastructure connectivity. “The spreadsheet shows 287 critical segments. The map shows that 140 of them serve the same two neighborhoods — which means a single event could cascade into a district-wide service failure. That geographic concentration is invisible in a table.”

Board Packet Materials

Most boards receive a packet before the meeting. Your submission should include:

1. Executive summary (1 page): Problem, solution, cost, benefit, recommendation. No maps on this page.
2. Three maps (1 page each): Problem, impact, solution. Each map has a one-sentence caption explaining what it shows and why it matters.
3. Financial summary (1 page): Table showing costs, projected savings, and net benefit over the project timeline.
4. Technical appendix (optional, clearly labeled): Methodology, data sources, detailed tables. Only for directors who want to go deeper. Most will not read it, but its existence signals rigor.

Total: 4-5 pages plus an optional appendix. Directors read hundreds of pages of board materials per meeting. Conciseness is a courtesy they will remember.

Common Presentation Mistakes

• Starting with methodology. “We used a weighted overlay analysis with five criteria normalized to a 1-10 scale…” — the board stopped listening at “weighted overlay.” Start with the finding, not the process.
• Showing the full analysis. You produced 30 maps in the analysis. The board sees three. Save the rest for the technical appendix or staff follow-up meetings.
• Reading from the map. Do not narrate what the audience can see. “The red dots are the critical assets.” They can see that. Instead, explain what it means: “Those 287 red dots represent $680M in replacement value serving half the city’s population.”
• Defending GIS instead of presenting findings. If a director questions the technology, redirect to the outcome. “The specific tools matter less than the finding: we have a $14M exposure concentrated in two districts, and we can address the highest-risk segments for $4.2M over three years.”
• Not having a printed backup. Projectors fail. Laptops crash. HDMI cables are missing. Always bring printed copies of your three key maps and the executive summary.

After the Presentation

Follow up within 48 hours:

• Send the board packet materials digitally to the board secretary for the official record
• Respond to any questions raised during the meeting that you could not answer on the spot
• If the board requested modifications, provide an updated analysis within two weeks
• If approved, reference the board presentation in your project kickoff — closing the loop builds institutional memory of GIS value

At GeoLever, we help GIS teams prepare board-ready presentations and materials. Our advisory services include presentation design, map production for non-technical audiences, and coaching for high-stakes presentations.

Frequently Asked Questions

Should I use a StoryMap instead of PowerPoint for board presentations?

For the live presentation, a StoryMap works well because it eliminates slide transitions and lets you scroll through the narrative naturally. However, always provide a board packet in PDF/print format — StoryMaps require internet and a browser, and some directors prefer paper. Many GIS professionals use a StoryMap for the live presentation and PDF exports for the board packet.

How technical should I get if a board member has a GIS background?

Stay at the decision-maker level for the formal presentation. After the meeting, offer a separate technical briefing for the interested director. Tailoring the main presentation to the most technical person in the room alienates every other director.

What if the board asks for changes and I need to redo the analysis?

This is expected. Budget for 1-2 revision cycles after the initial presentation. Common requests: “Can you run this for a different area?” “What if we change the priority weights?” “Add a scenario with a lower budget.” Having your analysis workflow scripted (Python notebooks or ModelBuilder) makes revisions fast instead of painful.

How do I handle a hostile board member who opposes GIS spending?

Do not debate the technology. Reframe every challenge in terms of the business outcome: “This analysis is about whether we can predict and prevent $14M in infrastructure failures. The tools we used to reach that conclusion are a means to that end.” If the opposition is ideological rather than evidence-based, the other directors will recognize that.

Should I present alone or bring my GIS team?

Present as the lead, but bring one technical team member who can answer detailed questions about data sources, methodology, or system specifics. Brief them beforehand on which questions to expect and how to keep answers concise (under 60 seconds). Two voices in a presentation add credibility; four voices create confusion.

Preparing a GIS presentation for your board? Book a discovery call with GeoLever — we help GIS teams translate spatial analysis into language that boards understand and fund.