Use an explicit coverage rule
Define included postcodes, towns or agreed boundaries. Record exceptions and the person who can accept them. A town name alone may be too broad for a crew with limited travel time, so the intake process should allow a useful location check without collecting more detail than necessary.
Route for capacity as well as geography
A valid location does not mean the team can take the job. Service type, appointment availability and crew coverage can affect assignment. Begin with transparent manual rules before introducing more complex automation.
Scope can include
Agree the rules and failure handling before implementation.
- Coverage matrix and exception handling
- Location questions in forms
- Assigned owner by service or territory
- Fallback queue for unmatched enquiries
- Source-to-territory reporting
Location on the website
Publish a service-area statement that reflects real coverage. A dedicated city page needs specific useful information and evidence. Do not create dozens of near-identical city pages or claim a local office where none exists.
What remains planned
Automatic geographic enrichment and scheduling-aware routing require validated data and supported integrations. Browser location permissions are not requested here. The website does not infer a visitor’s precise location.
