A map is only two things: areas and pins. Every map is a geographic boundary layer with addresses/activities plotted on top. Each is a "map element"—everything else is styling.

Build your area layer with or without assessment areas. CRA customers point the element at the Assessment Areas object (filter by year, or leave blank for all). Non-CRA customers use Other → public data source → census tracts or counties, set the variable to Tract Income Level, then use Create Auto Range and recolor low/moderate to high-contrast colors so LMI areas stand out.

Any address list can become a map layer via CSV report. Reports → New Report → New CSV Report geocodes an upload of branches, ATMs, or loan offices (needs a full address plus a date). It then works like any report—filterable, shareable, and selectable as a map data source, so only one teammate has to upload it.

Reuse one report across multiple elements with different styles, and drag to reorder layers. The same locations report can be a point layer and a radius pin layer (e.g., 5-mile max in 1-mile steps) to show reach. If a layer covers something up, drag it in the list or drop its opacity.

The map can only show what's on the report—so the report does the real work. Filters and columns control everything that appears. Filter by service date and CRA eligibility, add columns like tract income level, assessment area, county, and duration, and watch the association layers when picking fields. New reports let you disable a filter instead of deleting it.

Turn the gaps you spot into Goals. When a map reveals an underserved LMI area, create a Goal scoped by year, assessment area, and tract income with a target metric (e.g., 150 hours). Progress is dynamic, tasks and comments attach for accountability, and goals are reportable—drop a goals report on a dashboard.