Back

How to define catchment area in Sloc Local

Catchment areas represent geographic zones, defined by time or distance, that the vast majority of a site's customers are willing to travel for that site's services. Typically, authorities set this to an area covering the closest 80% of customers to each site. In practice, catchment areas are often derived from precedent in similar merger control cases when such data is difficult to source.

As the pragmatic proxy for local market boundaries, the findings of competitive assessments hinge on catchment area definitions. Sloc Local makes it easy to flex and test different catchment scenarios for your local merger, so you can be confident in your results and prepared for any outcome.

Where to set your catchment

On the Scenarios page, choose your subset and parties, then use Define catchment areas in the left panel. You can combine a type (distance or time), a method of transport and a size. This guide explains each option and how to balance realism with speed.

Type
The catchment Type list: Straight-line distance under Simple routing, and Street-wise distance and Travel-time duration under Complex routing

Choose the type of catchment that best reflects your case:

Type

Description

Catchment shape

Run speed

Straight-line distance

"As-the-crow-flies" distance, in kilometres

A circle around each party site

Fastest

Street-wise distance

Distance along the best route by road or path, in metres

An isodistance: everywhere reachable within a set distance (e.g. 5,000 m)

Slower

Travel-time duration

Travel time along the best route, in minutes

An isochrone: everywhere reachable within a set time (e.g. 15 minutes)

Slowest

Straight-line catchments (Simple routing) are very fast and useful for quick estimates, but don't account for real-world features such as rivers, winding roads or difficult terrain. Street-wise and travel-time catchments (Complex routing) follow the actual road network - the more realistic approach - but take longer to calculate.

Method of transport (street-wise and travel-time only)

Choose how customers are assumed to travel to sites:

  • Driving

  • Trucking - for heavy-goods or delivery-based markets

  • Walking

Each method uses the routes and speeds that apply to it. Choose the one that matches how customers usually reach sites in the industry you're looking at.

Traffic assumption (travel time by driving or trucking)

For travel-time catchments by road, choose how traffic is modelled:

  • Typical (default) - uses average speeds based on historical road speeds where available, and speed limits where not. Best for stable, like-for-like comparisons.

  • Specific time - uses road speeds for a Departure date and time that you choose. Use it for peak, off-peak or time-sensitive analysis.

Travel-time duration settings: Method of transport set to Driving, and Traffic assumption set to Specific time with a departure date and time field

If you use a specific time, choose the time when customers most typically travel to sites in your industry.

Size

Under Size, choose Symmetric to use the same catchment for every local market, and enter the distance or time.

Catchment Size set to Symmetric, 3 kilometres

Each type has a maximum size:

Type

Unit

Maximum - driving or trucking

Maximum - walking

Straight-line distance

Kilometres

No maximum

-

Street-wise distance

Metres

482,800 m

43,450 m

Travel-time duration

Minutes

300 min

540 min

Choose a size that reflects a realistic travel range for the market you're analysing.

Different sizes for different markets (Asymmetric)

Customers may travel further in rural areas than in towns, or further to a large superstore than to a convenience store. To reflect this, choose Asymmetric under Size. The Asymmetric catchments window opens:

  • By market - tick one or more local markets, enter a Catchment value and click Assign. Repeat until every market has a value; the counter at the bottom shows your progress.

  • By category - choose a column such as Fascia, Urbanicity or another text field in your data (e.g. store size), then set a catchment for each value, for example 1 km for urban sites and 5 km for rural ones.

The Asymmetric catchments window, with three local markets assigned 2 kilometres

Click Update to apply your catchments. Every market needs a value before you can run the analysis.

Performance considerations

The more complex the setup, the longer the scenario takes to run. Run time depends on:

  • The number of local markets analysed (party sites)

  • The size of the catchments

  • Using street-wise or travel-time catchments

  • Using a specific departure time

🧠 Tip: Sloc remembers routes it has already calculated, so re-running similar scenarios is much faster the second time. Start with straight-line catchments to explore, then switch to street-wise or travel-time for your final results.