How to Create a StoryMap That Gets Funding Approved

The Problem With Most Funding Requests

GIS teams build excellent analysis. Then they pour that analysis into a 40-slide PowerPoint, present it to a finance committee or grant panel, and wonder why the funding request gets tabled for “further review.”

The problem is never the data. It is the delivery format. A presentation deck forces the audience to watch passively while someone narrates data they cannot explore. By slide 12, attention has fragmented. By slide 25, the committee is thinking about lunch.

A well-built ArcGIS StoryMap flips this dynamic. The audience engages with the narrative at their own pace. Maps respond to their interactions. The spatial patterns that are invisible in a spreadsheet become obvious on a map. And the funding ask is the logical conclusion of a story they just experienced, not a number dropped at the end of a monotone presentation.

Before You Open StoryMaps Builder

The most important work happens before you touch the tool.

Define Your Audience in Specific Terms

Who reads this StoryMap, and what do they care about?

• City Council / Board of Directors: They care about constituent impact, cost, and risk. They do not care about your data model, your analysis methodology, or your map symbology choices. Lead with outcomes.
• Grant Review Panel: They care about alignment with grant criteria, feasibility, and measurable outcomes. They need to see that you understand their priorities and have a credible plan.
• Internal Finance Committee: They care about ROI, cost avoidance, and budget impact. They want to know what happens if they fund this and what happens if they do not.
• State/Federal Agency Reviewers: They care about compliance with program requirements, geographic targeting, and evidence of need.

Build for one audience. If multiple audiences will see it, build multiple StoryMaps — each one tuned to the audience’s decision criteria.

Start with the Ask

Write your funding request as a single sentence before you design anything:

“We are requesting $2.4M over three years to replace 47 structurally deficient bridges in District 7, preventing an estimated $18M in emergency repair costs and eliminating weight restrictions that add 22 minutes to school bus routes.”

That sentence has: the amount, the scope, the timeline, the risk mitigation, and the human impact. Your StoryMap exists to make that sentence feel inevitable by the time the reader reaches it.

Gather Your Evidence Stack

Every effective funding StoryMap builds on four evidence layers:

1. The problem: Spatial data showing the need (where, how much, how severe)
2. The impact: Who is affected and what it costs them (residents, businesses, operations)
3. The solution: What you propose, where, and why those locations
4. The alternative: What happens if you do nothing (the cost of inaction)

Structuring the Narrative

Section 1: The Hook (1-2 StoryMap Blocks)

Open with a single, specific, vivid instance of the problem. Not aggregate statistics — one incident, one location, one real consequence.

Example: “On March 14, 2024, a 6-inch cast iron water main installed in 1952 failed at the intersection of Oak Street and 3rd Avenue. The resulting break flooded a city block, closed a four-lane road for 72 hours, and cost $340,000 in emergency repairs. Three businesses reported damage claims totaling $89,000.”

Use a map zoomed to that specific location. Include a photo if available. This anchors the abstract problem in a real place the audience might recognize.

Section 2: The Pattern (2-3 StoryMap Blocks)

Zoom out from the single incident to the system-wide pattern. This is where your GIS analysis shines.

Show the audience:

• How many similar assets exist in the system
• Where they are concentrated (a map with heat maps or graduated symbols)
• How the problem has progressed over time (if you have temporal data)
• What the failure probability or risk score looks like across the service area

Use a sidecar layout here. Each narrative panel zooms the map to a different area or toggles a different analysis layer. The reader scrolls through the evidence without needing to interact with map controls.

Section 3: The Impact (1-2 StoryMap Blocks)

Translate the spatial pattern into consequences the audience cares about:

• For elected officials: Number of constituents affected, demographic composition, complaints filed
• For finance committees: Annual cost of reactive maintenance vs. proactive replacement, cost trends over 5-10 years
• For grant panels: Alignment with grant priorities (equity, resilience, environmental justice scores)

Embed charts and infographics alongside the map. A bar chart showing escalating repair costs over five years next to a map of aging infrastructure creates reinforcing evidence from two directions.

Section 4: The Solution (2-3 StoryMap Blocks)

Present your proposed project with spatial specificity:

• Exactly which assets or areas will be addressed
• The prioritization methodology (how you decided what to fix first)
• The project timeline mapped to geography (Phase 1 in Year 1 covers these areas, Phase 2 covers these)
• The expected outcomes — what the map looks like after the project is complete

The swipe tool works powerfully here. Let the reader swipe between “current condition” and “projected condition after investment.” The visual before/after is more persuasive than any table of projected metrics.

Section 5: The Ask and the Alternative (1-2 StoryMap Blocks)

Present two futures:

1. With funding: Summarize the investment amount, the outcomes, the timeline, and the return. Use the same map but with the proposed improvements overlaid.
2. Without funding: Project the status quo forward. More failures, higher costs, greater risk. If you have modeled projections, show the deterioration on the map — what the system looks like in 2030 without intervention.

End with a clear call to action: “We request that the Council approve $2.4M in the FY2026 capital budget for Phase 1 of the bridge rehabilitation program, beginning with the 12 bridges rated below sufficiency threshold in Districts 7 and 3.”

Design and Layout Best Practices

Map Design for Non-GIS Audiences

• Simplify symbology. Three colors maximum for thematic maps. Red/yellow/green is universally understood for bad/caution/good.
• Label key features. Decision-makers need to recognize streets, landmarks, and district boundaries without being GIS-literate.
• Use a clean basemap. The Light Gray Canvas or Human Geography basemap work well — they provide context without visual noise.
• Limit layers. Each map should make one point. If you need to show multiple analyses, use multiple maps rather than a single map with 8 toggleable layers.

Content Design

• Keep narrative text short. 100-150 words per sidecar panel. The map does the heavy lifting.
• Front-load key numbers. Put the important figure in the first sentence of each section: “$340,000 in emergency repairs.” “47 bridges rated structurally deficient.” “22 additional minutes per school bus route.”
• Use pull quotes. If you have a quote from a stakeholder, resident, or field crew — use it. “I’ve been with the department 23 years and we are patching patches.” — Operations Director
• Embed multimedia sparingly. One video or photo gallery adds credibility. Five makes the StoryMap slow to load and signals that you are padding content.

Accessibility

• Add alt text to every image and map
• Ensure color schemes are colorblind-safe (avoid red/green as the only differentiator)
• Keep text at 12pt minimum in embedded infographics
• Test the StoryMap on mobile — many reviewers will open the link on their phone first

After Publication: Maximizing Impact

A StoryMap published and emailed as a link gets about 30% of its potential impact. To maximize:

1. Present it live first. Walk through the StoryMap in the funding meeting. Use it as your presentation instead of slides. Hand out the link so committee members can revisit it later.
2. Follow up with the link. Send the StoryMap URL to every decision-maker within 24 hours of the presentation. Include a one-paragraph summary and the specific ask.
3. Track engagement. ArcGIS StoryMaps provides view counts. If you need more detail, use a URL shortener with analytics (Bitly, UTM parameters) to track click-through from different distribution channels.
4. Update annually. If the funding is multi-year or the request will recur, update the StoryMap with current data each cycle. A StoryMap that shows progress (“last year we funded Phase 1 and here are the results”) is even more powerful than the original ask.

Common Mistakes That Kill Funding StoryMaps

• Leading with methodology. Nobody on a finance committee cares about your weighted overlay model until they understand why they should care about the problem.
• Too many maps. Eight maps dilute the message. Three maps with clear progression (problem, pattern, solution) drive it home.
• No specific ask. A StoryMap that ends with “we need more investment in infrastructure” goes nowhere. A StoryMap that ends with “$2.4M for 47 bridges” gets put on the agenda.
• Burying the lead. If the most compelling data point is on map 6 of 8, move it to map 2.
• Assuming GIS literacy. Every map legend should be self-explanatory. Every technical term should be defined in context.

At GeoLever, we build funding-grade StoryMaps for government agencies, utilities, and nonprofits. Our StoryMap consulting services cover the full process — from evidence gathering to narrative design to presentation coaching.

Frequently Asked Questions

How far in advance should I start building a funding StoryMap?

Begin 6-8 weeks before the funding decision. The data preparation and analysis phase takes 2-3 weeks. Narrative design and StoryMap construction takes 1-2 weeks. Stakeholder review and revisions take 1-2 weeks. Rushing produces a data dump, not a persuasive narrative.

Can I use a StoryMap for federal grant applications?

Yes, with caveats. Many federal programs (FEMA BRIC, EPA WIFIA, DOT RAISE) accept or encourage supplementary spatial materials. Include the StoryMap URL as a supplementary attachment. However, do not rely on the StoryMap alone — the formal application narrative must stand independently because reviewers may not open external links.

Should the StoryMap be public or require a login?

For government funding requests, make it public. Council members will share it with staff, colleagues, and constituents. Login barriers reduce circulation. For internal corporate funding requests, organization-level sharing is appropriate. For grant applications, public sharing ensures reviewers can access it without ArcGIS credentials.

What if my data is sensitive and I cannot share it publicly?

Aggregate sensitive data to a level appropriate for your audience. Instead of showing individual parcel values, show block-group averages. Instead of exact infrastructure locations, show density by district. The narrative impact comes from the pattern, not the individual data point. You can always offer to share detailed data in a closed session after the StoryMap piques interest.

Can I track whether specific people viewed the StoryMap?

Not directly through ArcGIS StoryMaps, which only provides aggregate view counts. Use unique shortened URLs per recipient (Bitly allows this) if you need to track individual engagement. This helps you gauge who has reviewed the material before a vote or decision meeting.

Need a StoryMap built to secure funding? Book a discovery call with GeoLever — we have helped clients secure over $50M in approved funding using spatial narratives.