Dustin Ogle**Cluster:** Set 2 hub (proof standard) — pairs with Set 1 architecture hub
**TL;DR:** Engineering buyers do not shortlist firms because of a “50-mile radius.” They shortlist when **scope + place + proof** line up. Service-area claims must be **region-shaped and evidence-backed**: projects or patterns, coverage, and jurisdictional honesty. Radius language is a sales sentence, not a trust strategy.
Who this is for
Environmental and geotechnical firms that:
- already know which counties or metros they want, and
- need a **proof standard** so marketing, BD, and principals stop arguing about location copy.
Architecture (when to build pages) lives in Stop Building Thin County Pages. This article is the **evidence standard** for every claim that survives onto those pages.
Why radius claims fail pre-RFP research
Before an RFP, buyers often:
- Search scope + geography,
- Open a few firm sites,
- Check whether experience looks real **here**,
- Build a mental shortlist.
A radius map fails step 3. It answers “how far we drive,” not “have you done work like ours under constraints like ours.”
| Claim style | What buyers hear | Risk |
|---|---|---|
| **Radius** (“within 75 miles”) | Coverage theater | Easy to write; hard to believe; weak for search specificity |
| **Region + proof** (county/metro + service lines + patterns) | Fit and risk reduction | Harder to write; shortlist-ready |
The service-area proof standard (four tests)
Every location claim should pass:
**1. Service-line specificity**
Name the **lines** in play (Phase I, Phase II, remediation, geotech investigation, etc.). “Full-service environmental” is not a line.
**2. Place honesty**
Name the **place layers** that are true: county/city, program context when it shapes scope, office/field coverage. Do not decorate with regs your staff will not stand behind.
**3. Pattern or project proof**
Publish **patterns** seniors approve (facility types, phases, deliverables) — or real projects when allowed. No invented metrics. See What Proof Makes a Service-Area Claim Believable?.
**4. Owner sign-off**
A named technical reviewer can initial the claim. If marketing owns it alone, it is not proof-ready.
If any test fails, demote the claim to a careful **mention** or silence — do not invent a county page. Scorecard: When Does a County Deserve Its Own Page?.
Region vs. radius (practical language)
**Prefer**
- “In [County], we support [line] and [line] for [buyer types].”
- “Comparable industrial sites in the metro” (when analogs are honest).
- “Staffed coverage for field work in …” (when true).
**Avoid**
- “Serving the greater X area and beyond.”
- “#1 in the county.”
- Find-and-replace county names on identical paragraphs.
Copy patterns: Stop Saying “We Serve the Area”.
Where proof lives on the site
| Asset | Job |
|---|---|
| **Practice-area / service-line pages** | Spine for scope; market modules attach here first |
| **County page (optional)** | Only if scorecard passes; satellite of service lines |
| **Location proof module** | Reusable block seniors approve — Location proof modules |
| **One-page service-area plan** | Operating artifact for owners — One-page plan |
Failure modes when proof is missing: Why County Pages Fail Without Jurisdictional Proof.
30-day proof program (without thrash)
| Week | Action |
|---|---|
| **1** | Inventory current location claims; mark pass / fail / unknown against the four tests |
| **2** | Build or fix proof modules for the top two **P** markets (from your service-line matrix) |
| **3** | Rewrite one service-line page market block using region + proof language |
| **4** | Re-score counties; promote **one per cycle; two only when both pass cleanly** |
Bridge workflow: From Market Map to Proof File.
Frequently Asked Questions
Our Editorial Process: Our expert team uses AI tools to help organize and structure our initial drafts. Every piece is then extensively rewritten, fact-checked, and enriched with first-hand insights and experiences by expert humans on our Insights Team to ensure accuracy and clarity.
By: About the BVM Insights Team
The BVM Insights Team is our dedicated engine for synthesizing complex topics into clear, helpful guides. While our content is thoroughly reviewed for clarity and accuracy, it is for informational purposes and should not replace professional advice.
