12-Aug-2026 — rights-of-way volunteer management with a group-neutral import ref #355

build 823commit 566b3ec


A complete rights-of-way volunteer capability in NGX: a workspace for parishes, volunteers, contacts, reports and correspondence, an editable coverage map, and a group-neutral import that sets an area's data up from two documented Excel files, joined to live ONS parish boundaries by official parish code. Nothing about any one area, and no bespoke database format, is baked into the product.

This capability is modelled on an established rights-of-way volunteer database that has been built and refined over many years. Its parish, role and assignment model, its reports and much of its workflow follow that design closely.

Full write-up, with diagrams and the file layouts: 2026-08-10-rights-of-way-volunteer-import-model

How the system works

Three layers, joined only by the official ONS parish code:

Everything a volunteer operation needs is one sentence, filled in with real names and places: a person takes on a role (Local Footpath Officer, Parish Footpath Observer or Coordinator) for a parish, which sits in a rights-of-way group, an authority and a sector, and has a council you write to.

How to use it, step by step

  1. Prepare two standard Excel files (an area with a legacy system converts it into these files outside the product; the product never reads a bespoke format): a People file with one row per person (Member Ref, Contact Id, First/Last name, Email, Group Code, Team Status, Volunteer Roles); and a Structure workbook of three sheets - Parishes (by ONS code), Assignments (linked to people by email) and Contacts.
  2. Load the People file into the supporter feed. Uploading is additive by default, so you can build the dataset up rather than replacing it each time.
  3. Sync supporters into NGX members (Member Bulk Load -> Ramblers Team Emails -> Sync supporters now).
  4. Import the Structure workbook from the volunteer workspace Import tab: upload, check with a dry run and a review queue, then apply. Repeating an import updates the same records rather than duplicating them.

What's in the workspace

Parity with the legacy rights-of-way system

We went through every screen of the legacy application and checked it against this workspace. NGX already covered its parish, volunteer, group, role and cover model, its vacancy, role-holder, coverage and mapping reports, its mailing audiences, its bulk reassign and its appointment letter, and in most of these it goes further (effective dates, an audit trail, an idempotent dry-run import, a data-quality report, conflict and capacity warnings, an interactive map and a real email send). This release closes the last few gaps so that nothing the legacy application does is missing:

Also in this release