Dustin Ogle**TL;DR:** A **location proof module** is a reusable, principal-approved block that makes a service-area claim defensible. It is not generic “proof assets” and not a thin county page. Build modules for **service line × place**, store them as approved copy, and only then attach them to pages.
What a location proof module is
| Element | Required |
|---|---|
| Service line(s) | Yes |
| Place (county/metro) | Yes |
| Buyer types | Yes |
| Pattern / project language | Yes (approved) |
| Coverage note | Yes |
| Out-of-scope note | Recommended |
| Technical owner + date | Yes |
| Do-not-edit flags | Recommended |
Generic proof articles still help: Build proof assets. This piece is **only** the geo/service-area module.
Module template (copy/paste)
LOCATION PROOF MODULE · Line(s): _______________ · Place: _______________ · Buyer types: _______________ · Pattern (approved language): · _______________ · Coverage: · _______________ · Out of scope / will not claim: · _______________ · Owner (technical): ________ Date: ________ · BD confirm pursuit: ________ · Status: Draft | Approved | Expired (re-review after 6 months)
Example (composite — not a client)
Line(s): Phase I ESA · Place: Harris County, TX · Buyer types: commercial acquisition teams, lenders' environmental counsel · Pattern: Commercial and light-industrial due diligence phases with standard Phase I scope language seniors approve; no invented project counts. · Coverage: Houston-based staff routinely support Harris County sites for this line. · Out of scope: CMT; claims of “every submarket exclusive.” · Owner: J. Nguyen, PE Date: 2026-07-23 · Status: Approved
Where modules attach
- **Service-line page** market section (default)
- **County page** only if scorecard passes
- **Proposals / one-pagers** (same approved language — no freestyle)
Matrix drives which modules to build first: Map Service Lines Before You Add Markets.
Approval workflow (no thrash)
| Step | Owner | Timebox |
|---|---|---|
| 1. Draft from BD pursuit notes | Marketing | 30–45 min |
| 2. Redline patterns and coverage | Technical | 15–30 min |
| 3. Approve or reject (no soft maybe) | Technical | same session |
| 4. Publish to page(s) | Marketing | after approve |
| 5. Re-review | Both | 6 months or when coverage changes |
Cadence for new full county pages remains: **one per cycle; two only when both pass cleanly.**
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.
