---
title: "The Playbook"
canonical: "https://anchor.is/groundbreak/issue/5/the-playbook"
publication: "Groundbreak"
publisher: "Groundbreak"
language: "en-US"
guide: "https://anchor.is/groundbreak/llms.txt"
permalink: "https://anchor.is/groundbreak/issue/5/the-playbook"
issue: 5
section: "the-playbook"
description: "The tier-3 site selector preparation guide"
authors: ["Ruth Anne Bridwell"]
published: 2026-08-17
updated: 2026-08-15
articles: 7
---

# Groundbreak

> Groundbreak exists to close the intelligence gap that costs tier-3 American cities manufacturing deals they are structurally positioned to win. The reshoring wave is delivering hundreds of thousands of industrial jobs back to domestic soil, but the analysis helping cities compete for that investment has been written for tier-1 metros, site selection consultants, and corporate real estate teams. Groundbreak is built for the practitioners at the other end: economic development directors in mid-sized cities who have the land, the workforce, and the infrastructure, but not the market intelligence to know which industries are looking for exactly what they have. The publication is a subscription intelligence product. Success is not measured one reader at a time — it is measured in aggregate deal flow: a national readership of ED teams, each using the publication to build a sharper sector target list, collectively closing a disproportionate share of the manufacturing deals that tier-3 markets can win.

[Read on the website](<https://anchor.is/groundbreak/issue/5/the-playbook>)

## Issue 5 — The Playbook

The tier-3 site selector preparation guide

### Diagnostic Readiness

- [Know Where You Fail Before the RFI Arrives](<https://anchor.is/groundbreak/issue/5/the-playbook/article/35181/markdown>) — By [Ruth Anne Bridwell](<https://anchor.is/groundbreak/team/101/markdown>) · Published 2026-08-15

The [2026 Guild pulse survey](https://siteselectorsguild.com/wp-content/uploads/2026/03/SoSS-2026-PulseCheck_3.20.26.pdf) found 61% of site selectors named utility and infrastructure capacity as the leading elimination factor. Cities get cut before incentives or quality of life enter the scoring.

### Incentive Screening Teardown

- [What the Incentive Question Actually Screens For](<https://anchor.is/groundbreak/issue/5/the-playbook/article/35183/markdown>) — By [Ruth Anne Bridwell](<https://anchor.is/groundbreak/team/101/markdown>) · Published 2026-08-15 · Format: Screening Question Teardown

Incentives eliminated 2% of communities in the 2026 Guild pulse. Utility and infrastructure capacity eliminated 61%. The selector asking "what incentives can you offer" is not scoring the package yet; they are scoring the person answering. A vague response ("we can put together something competitive") suggests the director may not know their own approval pathway, their council's calendar, or their statutory limits, and that doubt travels back through every other answer they gave. This piece specifies what a passing response requires: named instruments with enabling statutes, approval calendars built from actual meeting schedules, precedent agreements with performance terms, and the GASB 77 disclosures the selector may have already pulled.

### Disqualification Ledger

- [Recording No-Bids and First-Cut Losses So the Pattern Reaches the Budget](<https://anchor.is/groundbreak/issue/5/the-playbook/article/35182/markdown>) — By [Ruth Anne Bridwell](<https://anchor.is/groundbreak/team/101/markdown>) · Published 2026-08-15 · Format: Disqualification Ledger

A tier-3 ED office might see 30 or 40 projects a year through state RFIs, utility leads, and broker calls. Most don't fit. Whatever the staff learned about why ends up in an email thread or a conversation note. Three losses on wastewater pretreatment capacity over 18 months are one infrastructure constraint surfacing three times, and they're the capital case for a POTW upgrade. Filed in three separate email chains with three separate state project managers, they look like bad luck. A structured record is what turns them back into evidence.

- [The No-Bid Decision on an Industrial RFI](<https://anchor.is/groundbreak/issue/5/the-playbook/article/35184/markdown>) — By [Ruth Anne Bridwell](<https://anchor.is/groundbreak/team/101/markdown>) · Published 2026-08-15 · Format: Deliberate No-Bid

South Dakota GOED is the only state agency in the public record that tells its own communities not to submit an RFI response when a critical driver is missing. The 2026 Guild/DCI survey confirms why: utility and infrastructure capacity eliminates at 61%. A three-person ED team that sends a package collapsing on the power question in first-round screening has spent its scarcest resource on telling the state contact it will chase projects it cannot land. This piece covers the decision framework, the communication mechanics, and what to document when the competent move is to decline.

- [The Same Screening Failure Has Four Causes and Four Price Tags](<https://anchor.is/groundbreak/issue/5/the-playbook/article/35185/markdown>) — By [Ruth Anne Bridwell](<https://anchor.is/groundbreak/team/101/markdown>) · Published 2026-08-15 · Format: Four-Cause Diagnosis

Your city was eliminated for "insufficient electric capacity." The fix might be a $5M substation upgrade or a $5,000 utility study you could have had in hand before the RFI arrived. Which one depends on a diagnosis most ED offices never make. This piece classifies screening failures into four root causes — asset gap, evidence gap, coordination gap, transaction gap — each with its own cost profile, timeline, and owner. Each section ends with a forwardable summary you can send to the utility director, POTW superintendent, or city manager who needs to act on it.

- [Turning Screening Failures Into Infrastructure Investment Cases](<https://anchor.is/groundbreak/issue/5/the-playbook/article/35186/markdown>) — By [Ruth Anne Bridwell](<https://anchor.is/groundbreak/team/101/markdown>) · Published 2026-08-15 · Format: Pattern-Based Investment Cases

Four food-and-beverage prospects eliminated in 18 months at the same wastewater discharge threshold. The disqualification record exists and the infrastructure gap is documented. What happens next depends on four separate approvers who evaluate on different criteria: the city manager needs a CIP project justification with lifecycle cost, the utility director needs a load profile with location and demand shape, the grant application needs a need narrative held to the program's evidentiary standard, and the council needs a budget line item with cost, funding sources, and consequence of deferral. This piece covers what each one requires, at the format level, to move pattern evidence toward a funded project.

- [Your Last Deal Loss Is Probably Misdiagnosed. Your Next Infrastructure Budget Reflects It.](<https://anchor.is/groundbreak/issue/5/the-playbook/article/35187/markdown>) — By [Ruth Anne Bridwell](<https://anchor.is/groundbreak/team/101/markdown>) · Published 2026-08-15 · Format: Institutional Memory Protection

Site selectors name utility and infrastructure capacity as the top elimination factor at 61%. Incentives register at 2%. But when a community loses a manufacturing project, the internal explanation gravitates toward incentive gaps, political failures, or bad timing. The misattribution compounds: a power-capacity disqualification recorded as an incentive loss sends the next three budget cycles into abatement advocacy while the substation study goes unfunded. This piece traces how unconfirmed loss explanations harden into strategic-plan findings, survive leadership transitions, and set infrastructure priorities years after anyone can identify where the diagnosis came from.

## Other sections in Issue 5

- [The Opportunity](<https://anchor.is/groundbreak/issue/5/the-opportunity/markdown>)
- [Deal Anatomy](<https://anchor.is/groundbreak/issue/5/deal-anatomy/markdown>)
- [City Intelligence](<https://anchor.is/groundbreak/issue/5/city-intelligence/markdown>)

## More

- [Publication guide](<https://anchor.is/groundbreak/llms.txt>)
- [Issue archive](<https://anchor.is/groundbreak/issues/markdown>)
