Get started with Ambassy

Ambassy helps parkrun Regional Event Ambassadors (REAs) plan and allocate events. Upload your allocation CSV files to see events on a map and in a table.

Upload your CSV files

Select one or more files below. You can also use the sample templates to inspect the expected format.

Sample CSV templates

What you will see

Each parkrun event appears as a marker on the map, coloured by the Event Ambassador allocated to it. A Voronoi layer shows Regional Event Ambassador territories. The allocation tables summarise the same data in tabular form.

Privacy and data

Allocation data are parsed in your browser and kept in local storage on your device. They are not uploaded to johnsy.com, logged by Ambassy, or stored on our servers. Optional parkrunner IDs and imported visit histories are stored the same way.

There are no analytics: usage is not counted and adoption is not measured. Ambassy is shared in goodwill, not to boost traffic. The intent is close to Datensparsamkeit (data minimisation): carry only what you need for the job.

Network use is limited to OpenStreetMap map tiles, the public parkrun events catalogue, and — if you install the finish export userscript — fetching that script from johnsy.com for installation and updates. That script request does not include your allocation or finish data.

Visiting parkrun profile pages to import finishes is ordinary browsing on parkrun's own sites. When you geocode a place, the search text you enter is sent to Photon (OpenStreetMap data) to resolve coordinates; that request does not include your CSV or ambassador names.

Only the columns the tool uses are read from each file; extra columns are ignored. Export and Import only move files when you deliberately exchange them. Finish import may copy JSON to your clipboard, or pass through Tampermonkey on your device when moving from a parkrun profile tab to Ambassy. There is no central Ambassy service that stores what you are working on.

You may use aliases in your CSV if you prefer. The author uses real names because it makes conflicts of interest between volunteers easier to spot. The source code is on GitHub for inspection — improvements are welcome.

Screenshot of Ambassy showing a map with event markers and allocation tables

I found this useful (and a fun programming challenge) as an REA and I publish it in the hope you do too.

Ambassador visit history

Why this exists

The Event Teams tab can show last ambassador visit — who finished at an event most recently, and when. That helps REAs see oversight visits by ambassadors who are not allocated to the event.

Ambassy runs entirely in your browser. parkrun profiles live on per-country websites with bot protection, so Ambassy cannot fetch visit history directly. The finish export userscript runs on parkrun profile pages you already have permission to view, extracts finish dates from the /all/ table, and hands the data back to Ambassy on your device.

Only finishes that match live events in the parkrun catalogue are kept. Volunteer roles are not imported in this version.

Privacy

Visit history is imported only when you choose to. It is parsed in your browser from parkrun profile pages you already have permission to view, then stored in local storage with your other Ambassy data. It is not uploaded to johnsy.com or stored on our servers.

The userscript may use Tampermonkey to hand off data between tabs on your device. Clipboard import is available if you prefer not to use that bridge. Installing or updating the userscript fetches the script from GitHub; that request does not include your allocation or finish data. A copy also remains on johnsy.com for older installs.

Export and Import move a single JSON file containing allocations, ambassadors, prospective events, visit histories, and related settings (including parkrunner IDs when set).

Setup

Install Tampermonkey (or a compatible userscript manager) if you do not already have it.
Click Install Ambassy visit history export below and confirm in your userscript manager. It will check GitHub for updates automatically.
Set each ambassador's parkrunner ID on the Event Ambassadors or Regional Ambassadors tab, or via the optional parkrunner ID column in your CSV.

Importing finishes

Open the ambassador's parkrun profile /all/ page (use the link on their parkrunner ID when set).
Click Export finishes to Ambassy on that page.
Open or switch to Ambassy — the import runs automatically when the userscript bridge delivers the payload (no refresh needed if Ambassy is already open).
If you cancel ambassador assignment, use Resume on the main page banner or Import visit history from clipboard below.

Clipboard fallback: copy the JSON from the userscript notification, then use Import visit history from clipboard below.

Install Ambassy visit history export

← Back to Ambassy

Ambassador name filter

Regional Event Ambassador (REA)	Event Ambassador (EA)	Event Name	Event Director(s)	Coordinates	Event Series	Country	Last ambassador visit	Actions

Regional Ambassador	Name	State	Home parkrun	parkrunner ID	Number of Allocations	Events Assigned	Actions

Name	State	parkrunner ID	Number of Allocations	Event Ambassadors Supported	Actions

Prospect Event	Country	State	Prospect ED/s	Regional Event Ambassador (REA)	Event Ambassador	Date Made Contact	Course Found	Landowner Permission	Funding Confirmed	Geocoding Status	Coordinates	Event Ambassador assignment	Actions

Change Type	Event Name	Original Value	New Value	Timestamp

Event Name	Event Ambassador	Regional Ambassador	Issue Type	Actions

Ambassy