> For the complete documentation index, see [llms.txt](https://docs.range-mate.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.range-mate.co.uk/for-club-admins/reach-compliance/site-environmental-profile.md).

# Site Environmental Profile

The environmental profile is your record of **where the range is, what its boundaries are, and what sensitive water features are nearby**. It's the most laborious part to compile by hand, so the module does as much of the research for you as it can.

It lives on the **Site profile** tab of the range's compliance hub.

## Drawing the map

Click **Edit profile**. If the range is geocoded you'll see a map with a mode picker:

* **Boundary** — click to drop points around the edge of the complex; after three or more a shaded boundary appears.
* **Firing points** — each click drops a marker where shooters fire from.
* **Grazing area** — draw the area grazing animals or wildlife can reach, the same way as the boundary.

**Clear this layer** wipes whichever mode you're in and leaves the others alone. What you draw is what gets saved; the raw map data sits in a collapsed **Technical details** section you don't need to touch.

**Backstops aren't drawn here** — each [backstop](#range-layout--backstops) carries its own drawn outline, set on the backstop's form: tap the corners on the map, or walk the backstop pressing **Add point at my location** at each corner. Backstop outlines appear on the profile map automatically, labelled by name.

{% hint style="info" %}
If you can't draw the boundary right now, just record the wildlife notes — the boundary can be added later. A boundary or wildlife notes are enough for the profile to count as "captured" on the dashboard.
{% endhint %}

## Range layout & backstops

The **Range layout & backstops** card describes the physical shape of the range:

* **Layout** — number of lanes, the firing arrangement (fixed firing points, different lanes into different backstops, or variable/practical), and the marked firing distances. These are set on the range's settings page and describe the range on your declaration and evidence pack.
* **Backstops** — add each backstop or impact area: what it's built from (earth bund, sand trap, granulate, stop butt or open impact area), how tall it is, the distance, and **which lanes it serves**. Photos of the construction make strong evidence.

Once backstops exist, [reclamations](/for-club-admins/reach-compliance/lead-reclamation.md) and [samples](/for-club-admins/reach-compliance/soil-and-water-monitoring.md) can be recorded against a specific backstop, and the lead inventory shows a per-backstop breakdown.

{% hint style="info" %}
A simple range with one bund needs one backstop — or none at all. Everything keeps working at whatever level of detail your club wants to record.
{% endhint %}

## The wildlife risk-minimisation statement

In the **Wildlife risk-minimisation statement** box, describe how risks to ruminants, grazing wildlife and wild birds are minimised at the site (for example, fencing grazing animals away from the impact area).

{% hint style="info" %}
Every time you change this statement, Range Mate keeps a dated version of the previous wording, so you have a history of how your approach has evolved.
{% endhint %}

## Nearby water features & designations

The "soil and water" record needs you to identify nearby lakes, ponds, rivers, streams, canals, drainage ditches, aquifers, Source Protection Zones (or Protected Areas in Scotland) and known abstraction points.

Click **Look up nearby water data**. Range Mate queries the relevant free public datasets for your nation:

* **England** — DEFRA MAGIC / Environment Agency (groundwater zones and named watercourses, including canals)
* **Wales** — Natural Resources Wales (DataMapWales)
* **Scotland** — SEPA

Anything it finds is added to the table as a **Candidate**. For each one you can:

* **Confirm** it — once you've checked it's real and relevant, it becomes part of your evidence.
* **Remove** it — if it's not relevant.

You can also add features the datasets don't know about.

{% hint style="warning" %}
**Private water supplies** are not held in any national dataset — local authorities hold that information. If your range is near a private water supply or borehole, you'll need to add it yourself. The declaration treats these as operator-confirmed.
{% endhint %}

{% hint style="info" %}
The look-up surfaces candidates for **you to confirm** — it doesn't replace a consultant's site assessment. If it returns nothing, that means the public datasets show nothing nearby for your nation; it's still worth a manual check for local features. The look-up needs the range's **nation** set (see [Getting started](/for-club-admins/reach-compliance/getting-started.md)).
{% endhint %}