Every EDO that has pursued and lost a manufacturing project carries an explanation. Usually it involves incentives. Sometimes the governor's office, sometimes a shift in the company's timing. Whatever it is, it circulates through board presentations, staff turnover, and legislative testimony, and within two or three years it functions as institutional fact.
Most of those explanations were never confirmed by anyone outside the organization. A substantial share are wrong. The cost shows up on a lag, because a wrong diagnosis directs infrastructure spending, workforce investment, and political capital at constraints that were not the ones that eliminated the community.
A city that misattributes a power-capacity disqualification to incentives will spend the next three years lobbying for expanded abatement authority instead of funding a substation study. A city that converts a specific workforce-pipeline gap into a general belief that it cannot compete for advanced manufacturing will sit out future competitions where its site, utility, and logistics attributes would have survived screening.
The Feedback Arrives Incomplete, or Not at All
Site selectors and corporate real estate teams have no obligation to explain an elimination. Most of the time they explain less than the full picture.
Missouri Partnership's published analysis of projects opened from FY2016 through FY2023 states that clients and consultants "only sometimes share" the elimination reason. In some cases the organization never learned where the project located. In others, the stated reason came from a project manager's interpretation rather than from the selector. What does arrive ranges from operationally specific — two submitted sites required electric and water upgrades that could not be completed within the company's schedule — to vague, as in a site described only as "too raw and too risky," to language that folds criticism into encouragement. When a selector says the site's shape, readiness, and metropolitan proximity didn't fit the project but the property "has potential," the community keeps the second clause.
Nelson Lindsay of Parker Poe Consulting has described projects where communities asked consultants to delay proceedings until after an election, companies moved to second-choice locations, and most affected communities never fully understood why they lost. Devin Hillsdon-Smith of Hyphen Strategies has noted that data-assisted pre-screening now eliminates communities before an RFI is drafted, which means the community never knew the project existed and no interaction occurred from which feedback could arise.
Three information conditions follow an elimination. In the rarest, the selector communicates a specific and actionable reason, though even then the stated reason may be one factor inside a multi-factor judgment. More commonly, the community participated and received nothing complete. Increasingly, the community was screened out before it knew there was a competition. The IEDC 2025 State of the Field found that 56.9% of respondents use a CRM system. The questionnaire did not ask whether those systems record elimination reasons, or whether they distinguish a confirmed reason from a staff inference. The profession has not standardized how a loss gets written down.
Four Substitutions
Each of these swaps an explanation that is comfortable or politically useful for one that is operationally accurate.
Incentive blame absorbing infrastructure disqualification. This one moves capital budgets, which makes it the expensive one. A community loses a project where its site lacked adequate power capacity, or its water system couldn't meet industrial fire-flow requirements, or its wastewater treatment plant had no committed headroom. The constraint was infrastructure. The 2026 Guild Pulse Check identifies utility and infrastructure capacity as the top elimination factor, cited by 61% of respondents. But the internal narrative gravitates toward incentives, because the winning state's package was announced publicly and carries a number the community can compare itself against, and because "we were outbid" is easier to say in a board meeting than "our infrastructure wasn't adequate."
Utility and infrastructure capacity is the top elimination factor for 61% of site selectors surveyed. Incentives are the top elimination factor for 2%. Community explanations of lost deals track the second figure far more closely than the first.
As I covered in Issue #1's incentive authority matrix, incentives were named the top elimination factor by 2% of that same respondent group. Daniel Young, formerly of the South Carolina Coordinating Council for Economic Development, has described projects where incentive maximization pulled investment toward locations without the infrastructure or operating fit to support it, including a major international project sited on land lacking required public infrastructure, with hundreds of millions committed and a wetlands permit still affecting the schedule. The distortion runs both ways. Incentives pull projects to the wrong site, and incentive explanations obscure why the right project went somewhere else.
Political blame absorbing evidence-quality failure. A community loses and attributes it to thin engagement from the governor's office, a council that moved too slowly, a mayor who didn't make the call. Political dynamics do cost deals. Political blame is also the easiest narrative to assemble when the failure was in the RFI response itself: a site sheet citing power capacity without a utility service letter, a workforce claim naming a training program without documenting annual completions, a "shovel-ready" designation on acreage that hadn't completed Phase II environmental.
As I've covered in prior issues on counterparty mapping, many of the claims an EDO submits are controlled by utilities, treatment authorities, railroads, and regulators the EDO does not speak for. When one of those counterparties misses the project's clock, the EDO often identifies the delay correctly and then attributes it to a political relationship rather than to the structural fact that the commitment was never the EDO's to make.
Market-timing blame absorbing site-readiness gaps. "The company wasn't really serious" and "the market shifted" require no internal accountability, and they are sometimes true. Missouri Partnership's records also show projects lost because sites were too raw, because buildings couldn't be expanded inside the project schedule, or because infrastructure upgrades fell outside the required calendar. Those are readiness failures. The company's timeline was real; the site wasn't ready for it. Recoding that as bad timing keeps the organization from funding the gap that would make it competitive for the next project with the same requirements.
Single-factor folklore from multi-factor losses. This is the version that lasts longest. A community loses a project where workforce scale, site acreage, and utility capacity all fell short, and the internal account collapses into one line: we can never compete on workforce. Missouri's records include a project requiring a 1,200-person opening workforce, 200 to 300 of them engineers, which placed the community in the bottom quartile of more than 20 submissions. That is a real workforce screen. But if the acreage or the power capacity would have disqualified the community independently, the workforce gap was not the binding constraint, and treating it as the only lesson sends the next three budget cycles into pipeline development while the site and utility gaps stay where they were.
How One Misattribution Becomes a Strategic Plan
A community loses a manufacturing project in 2022. The director tells the board the incentive package wasn't competitive, partly because it's the only variable with a public comparison point and partly because "I don't know why we lost" sounds, in a board meeting, like an admission of not doing the job. The board accepts it. It enters the minutes. When the strategic plan is updated for 2023–2025, the incentive gap appears as a documented finding. Staff begin targeting sectors and projects where existing incentive authority looks sufficient, which means steering away from the higher-capital competitions where infrastructure and site readiness are the screening gates. The organization enters fewer of the competitions that would have told it what its actual constraints are. The next loss gets read through the lens the strategic plan already established.
By 2026 the organization has a four-year record saying its problem is incentive competitiveness. The director who made the original attribution has moved on. The current director inherited it as a documented finding, without the caveat that no selector ever confirmed it. The board has approved two cycles of legislative advocacy for expanded abatement authority. The substation study went unfunded because power capacity was never identified as a constraint.
"We're not competitive for advanced manufacturing" can survive a decade and three leadership transitions if nobody returns to the original loss record and asks what evidence supports it. Frequently there is no original loss record.
The dynamics that produce this are structural rather than negligent. The director explains the loss to the board before the selector's feedback arrives, if it arrives, because the board asks at the next meeting and the elimination happened two weeks ago. The staff reconstructing what went wrong are the staff who prepared the response, and they are poorly positioned to conclude that their own evidence quality was the problem. When a new hire asks why the organization doesn't pursue a given sector, the answer comes back as settled knowledge: we looked at that in 2022, we can't compete. The qualifier that belongs with it — one loss, elimination reason never confirmed — was dropped somewhere between the second and third retelling.
Invest Northern Ireland's 2026 executive minutes document the same erosion from the inside. The agency found that its CRM closure fields emphasized internal factors, that early-stage losses weren't consistently captured, and that reporting relied on spreadsheets and anecdote. It also identified behavioral barriers to recording failed opportunities, meaning staff reluctance to enter losses into the system at all. INI is a large, well-resourced national investment agency. A three-person EDO working without a CRM is not doing better, and whatever its memory contains is setting infrastructure priorities this budget cycle.
The Capture Point Is Earlier Than the Post-Mortem
By the time a post-mortem happens, weeks or months after elimination, the account has already set. Staff have discussed it informally. Board members have asked what happened. The version that gets written down is the version that has already been told several times.
The capture point is the moment the organization learns it has been eliminated, and each earlier point in the pursuit where a constraint became visible.
Record the date of elimination; the source of the explanation, labeled as selector-confirmed, counterparty-reported, or staff-inferred; the stated reason in the source's own words rather than the organization's paraphrase; and the infrastructure, site, workforce, and evidence-quality deficiencies that were known during the pursuit whether or not the selector mentioned them. The distinction most likely to erode over time is between what the selector said and what staff concluded. It is also what determines whether the record is worth anything in year four.
In Issue #4 I introduced a structured non-pursuit record: an entry created when an organization evaluates a sector opportunity and decides it cannot compete, naming the sector, the disqualifying dimension, whether the gap is closable, and on what timeline. The same discipline applies to pursuits entered and lost. The record exists to hold the caveats next to the conclusion, so that the next director can tell what was confirmed from what was guessed.
Without it, institutional memory is whatever the current director recalls of what the previous director said about a project lost three years ago. That memory is already allocating capital. In most organizations nobody has gone back to check what it was built from.
- Missouri's loss taxonomy: Missouri Partnership's published project-loss analysis is the most granular public record of elimination reasons, feedback quality, and CRM provenance available from a U.S. statewide recruitment organization.
- Pre-RFI desktop screening: Devin Hillsdon-Smith's account of data-assisted pre-screening eliminating communities before any RFI is issued describes a growing class of losses where no feedback channel exists because the community never knew the project was real.
- INI's CRM reform effort: Invest Northern Ireland's 2026 executive minutes document an internal effort to standardize closure coding, capture early-stage losses, and address behavioral barriers to recording failed opportunities inside an existing CRM system.
- Election-related deal disruption: Nelson Lindsay of Parker Poe Consulting described projects where communities requested delays until after elections, with companies moving to second-choice locations and affected communities never fully understanding the cause.

