An event turnout map may be needed only through the final report, while a volunteer map for an ongoing program may need updates throughout the year. That difference matters when a coordinator is setting a limited mapping budget. The roster and sign-in records may already be available. The remaining question is how long staff will need access to map them, review the results, and keep them current.
| Mapping need | Row unit | View | Source record |
|---|---|---|---|
| Available volunteers | One volunteer | Role groups or Marker Density | Current availability roster |
| Registered participants | One person per event | Status groups or Marker Density | Registration list |
| Actual attendance | One checked person per event | Attended filter and Marker Density | Reconciled sign-in list |
| Area totals | One area with a numeric count | Represents Numerical Data | Prepared attendance summary |
Match the mapping project to your budget
Plan a short event analysis
A checked spreadsheet can support a useful role map or attendance view without buying another system to collect the same records.
Decide when you need access, including preparation, staff review, and the final event report. Maptive's prices checked October 10, 2026 include a 45 Day Pass at $250 for one user. Pro costs $110 per month when billed monthly. Compare both against your actual project dates before choosing a short-term option.
The pass gives you a defined 45-day period. Monthly Pro may cost less for a shorter project, but check the billing and cancellation terms before budgeting it. Don't assume that a one-time pass is always the cheapest choice just because you're mapping one event.
Maptive also offers a 10-day trial without a credit card. Use that evaluation period to test your prepared list and the view your team needs. Budget for paid access if the work will continue beyond it. The trial doesn't provide permanent free mapping.
Keep the first project focused on one event or one volunteer planning question. That reduces the preparation work and makes it easier to judge how much mapping access you'll use.
Plan recurring volunteer maps
For a recurring program, count the months when someone will maintain the roster, map new events, and review attendance. Pro costs $1,250 per year as of October 10, 2026, alongside the $110 monthly option. Compare the complete cost over your planned use rather than the monthly equivalent of an annual payment.
Budget time for the coordinator's preparation as well as the software. Reusing the same person IDs, event fields, and status values reduces repeated cleanup. Keep a blank copy of the checked spreadsheet layout for the next event, along with a note explaining which attendance definition it uses.
Assign one person to maintain the map and the source file. If several people need to edit, include their access needs in the plan choice. Budget from the published prices unless Maptive has given your organization a different quote, and confirm the current terms before buying.
Reconcile volunteers, registrations and sign-ins
For volunteer availability, prepare one row per volunteer with a stable person ID, location, role or skills, and a current availability field. Check that the availability date is relevant to the assignment. A volunteer who joined last year may no longer be available for the event you're planning.
For turnout, keep Event ID, event date, person ID, and an attendance-status field. Join the registration list with the actual sign-ins before importing. Preserve walk-ins who attended without registering, and inspect repeated scans or duplicate sign-in entries. Those extra entries shouldn't turn one attendee into several people.
Define attendance before you reconcile the sign-ins. Checking in once may be enough for an event headcount. For a volunteer shift report, you may need to confirm completed shifts or hours served. Keep those measures separate, and don't mark a person as completing a shift simply because they appeared at the entrance. Record the cutoff date for this check so later corrections can be traced.
Decide how repeated participation should count. One row per volunteer counts people in the prepared roster. One row per person per event counts attendance instances across events. Someone who attended several events counts once for each event in that second view. Keep a separate summary that counts each person once when that's the question.
Choose the location that fits the analysis. To map where people come from, use each person's relevant home area or the origin they've supplied. An event-site map needs the venue. Putting every attendee at the venue will show an event concentration rather than where the people came from.
Keep only the detail the staff task needs. A city or ZIP-level origin may be enough for a broad attendance review. Use a checked street address only when the staff purpose calls for that detail. Label the location type so no one mistakes an approximate area origin for an exact residence.
Import the prepared attendance list
In Maptive, choose Create New Map, name it for the roster or event period, then click Continue. Upload the Excel file under Your Data or paste the table with its headers. Select Map Now after loading the records.
Use Categorize Data to check which columns supply the location. Keep address information separate from the person ID, role, and attendance status. The extra business fields can remain unmatched and still appear in marker pop-ups. Review what you've imported before allowing a wider audience to see those fields.
Inspect known locations and any points that look displaced. Compare the Data rows with your prepared roster or attendance file. For a correction in the Data tab, edit the cell and press Enter to save. Update the original roster when it contains the same error.
Keep unresolved locations in a separate review group or list. They still belong in your event accounting even if you can't use them in the geographic comparison. Before reading the map, record how many checked attendees have origin details you can use.
Show the participation question you need
Color roles and turnout status
Open Map Tools, choose Grouping Tool / Colored Pins Tool, and select the role column as Primary Group for volunteer planning. The groups receive different marker colors. The small white icon beside a group lets you change its appearance. Open several records to check that their role agrees with the roster.
For turnout, group by attendance status instead. Keep registered, attended, and unresolved statuses clear in the source. If you're comparing registrations with attendance, retain a registration field as well, since a walk-in can attend without appearing in the original registration count.
Use the Filter Tool to select the group you need. Choose Create Filters on first use, or the gear for an existing setup. Group handles role and status categories. Date can restrict the event period. Attribute can separate the listed skills when semicolons divide their values. Check the active filters before counting or exporting records.
Map concentrations or area totals
For a view of where people cluster, open the Heat Mapping Tool, choose Marker Density, and click Add Heat Map. Use the attended subset when the question is actual turnout. A Specific Group sample can restrict the heat layer to a supplied category. Confirm the sample describes the same group as the pins you're reviewing.
For attendance already totaled by area, select Represents Numerical Data, choose the numeric total column, select the sample, and click Add Heat Map. The selected column must contain only numbers. One marker per neighborhood with Marker Density would give every neighborhood row a contribution regardless of how many attendees it contains.
Keep the same period, location precision, map extent, and heat settings when comparing registrations and attendance. A registration map and an attendance map can suggest different regional patterns, but colors alone don't give you a turnout rate.
Calculate that rate in the source spreadsheet when you need it. For registered-participant turnout, divide the number of registered people who attended by the number registered for that same event and area. Report walk-ins separately. Across several events, decide whether you're comparing attendance instances or unique people and use that unit throughout.
Before changing recruitment or venue plans, inspect the underlying counts. A bright patch could reflect a few people who attended many events. A weak patch could reflect missing addresses. Check those explanations against the roster and sign-ins, then ask the coordinator what needs follow-up.
Keep participant locations appropriate for sharing
Prepare a separate file of totals by area when a committee needs regional turnout instead of records for each person. Remove names, contact details, and exact addresses from that summary. Review small groups that might still identify someone, and keep the detailed attendance file available only to the staff who need it.
For a shared map, open Share on the left, then Share Externally. Choose Password Protected or Public, select the starting view, and use Copy for the link. Anyone with a public link can view it. Review the shared tools, record fields, and export choices, then test what a recipient can see.
For a staff file, use Export Data, select Export Filtered Data, choose the format, and click Export Now. Verify that the exported IDs belong to the intended event and attendance subset. Keep the reconciled sign-in source, event period, and mapping rules with the output so the next event can be compared on the same terms.
