Your team is about to spend an hour in a conference room deciding whether to pursue a project the principal already committed to over dinner last week.
That's what most AEC go/no-go meetings actually are. Not a decision gate— a formality. A performance scheduled after the real decision already happened informally, or a room full of people trying to reverse-engineer a yes out of criteria designed to say no. When the go/no-go meeting is theater, everyone in the room knows it— but nobody says so.
The problem isn't the process. According to CRM Software Blog6, 83% of AEC firms have a formal go/no-go framework in place. Most override it when volume pressure hits. Industry average win rates stay flat at roughly 40%2, which tells you that having a process and running a real decision are not the same thing.
The math on this is brutal. According to Canadian Consulting Engineer4, 38 architecture firms each spent $20,000 to write proposals for a single project worth $50,000 in fees— $760,000 collectively to produce one winner. When you're running theater, you're not just wasting meeting time. You're burning real money on pursuits that were never winnable.
The firms that fix this don't fix the scorecard. They fix who's deciding and when. This article names the three theater patterns, the five structural failure modes behind them, and the framework that actually works.
Three Types of Go/No-Go Meeting Theater
Theater in go/no-go meetings falls into three patterns, and most AEC firms run at least one of them.
1. Retroactive rubber-stamp. The most common type. Section headers are drafted, the PM is mentally committed, the principal is excited about the relationship— and then the go/no-go meeting gets scheduled. Kantiv1, an AEC business development research firm, puts it plainly: "The go/no-go meeting is scheduled, but the pursuit coordinator has already drafted section headers. Commitment is already made." Sunk-cost dynamics mean nobody in that room wants to be the one to kill it.
2. Untracked outcomes. The team meets, scores the opportunity, and makes a call. But the decision quality never gets measured. Did the go decisions win at the rate the team predicted? Did any of the no-go pursuits turn out to be winnable projects that went to a competitor? Without a feedback loop, criteria drift from reality year by year until the scorecard stops predicting anything at all.
3. Wrong-criteria theater. The most dangerous type. The scoring sheet asks about strategic fit and team capacity, but the room is actually responding to principal gut feel, recency bias, and the fear of missing a high-fee opportunity. Tom Porter of Barton Malow Company5 (a major construction management firm) names the dynamic directly: "Be wary of end runs around the go no go process...the odds of getting stuck with a losing, or expensive, project increase if requirements are too easily sidestepped." The framework becomes an elaborate suggestion box.
Each of these patterns produces the same result: a process that costs time and money while adding no decision quality. Behind each of them is a structural failure mode.
Why Go/No-Go Meetings Break Down
Go/no-go meetings become theater through five structural failures— any one of them is enough to undermine even a well-designed process.
1. Authority vacuum. The framework exists, but there's no real power to decline. If the answer to "who can say no?" is "the committee collectively," then in practice the most senior or most vocal voice determines the outcome— not the criteria. A committee with no named authority produces the same result as no authority at all.
2. Gut feel substituting for data. Principals and project managers read the same client relationship differently. The meeting averages those gut reads instead of consulting factual inputs: client payment history, win probability against known competitors in this sector, proposal cost as a percentage of potential revenue. Those numbers exist in most firms' CRMs. They're rarely the first thing pulled up in the meeting1.
3. Sunk costs preventing no decisions. Once someone has sketched a pursuit plan or drafted a scope outline— even a lightweight one— killing the pursuit feels like wasting that investment. The real question isn't "what have we already spent?" It's "what will we spend from here, at what probability of winning?"
The first three are behavioral: they're about how the room responds to a pursuit in the moment. The last two are structural: they're about information that was never built into the process.
4. Unused historical data. Win/loss history exists in most CRMs6, but it's rarely consulted during go/no-go decisions. Firms don't ask: "Against this competitor in this market sector, what's our actual win rate?" They guess. The data that would make the decision defensible sits unread.
5. Misaligned capacity visibility. Capacity gets assessed globally— "Is the firm busy?"— rather than by discipline. A firm can be overloaded in structural design while sitting idle in MEP (mechanical, electrical, and plumbing disciplines). Monograph3 (an engineering project management platform) notes that capacity fit by discipline is the criterion most often guessed when staffing data lives in separate spreadsheets.
Most AEC firms respond to these failures by redesigning the scorecard. That's the wrong fix. Treating the process as an innovation problem— when the actual fix is naming one person who can say no— is how firms end up with elaborate frameworks that produce the same results year after year.
What Real Go/No-Go Discipline Looks Like
Real go/no-go discipline requires three structural changes: weighted criteria set before RFPs arrive, a named person with authority to decline, and quarterly outcome audits that refine the weights.
Monograph3 publishes one of the clearest AEC-specific frameworks available:
| Criterion | Weight | Rationale |
|---|---|---|
| Expected margin vs. firm median | 20% | Do the economics work? |
| Capacity fit by discipline | 15% | Can we staff this well? |
| Strategic value | 15% | Does this fit our growth plan? |
| Client quality | 10% | Financial stability and reasonableness |
| Payment history | 10% | Do they pay on time? |
| Scope certainty | 15% | Can we price this accurately? |
| Schedule risk | 15% | Can we do good work on this timeline? |
Decision bands: Go (80%+), Conditional go (70–80%), No-go (below 70%).
The critical requirement: weights must be set before RFPs arrive. Monograph3 is explicit— "Weights must be set before RFPs arrive to prevent post-hoc justification of desirable fees or familiar clients." Criteria set after the RFP lands are almost always a ratification of a decision already made on fee size or familiarity.
Three hard deal-breakers override the scoring entirely:
- Pursuit cost exceeds 10% of potential revenue (especially when other criteria are already marginal)
- Client has a history of late or non-payment
- Contract terms are uninsurable (duty-to-defend language or unlimited liability clauses)
Kantiv's1 research on hundreds of AEC pursuits adds one consistent finding: firms that pass on 40–50% of opportunities consistently outperform firms that chase everything. That's not just a process insight— it's a business model. Selectivity sustains the operational capacity to do excellent work on the pursuits you do take. SMPS Foundation research2 surveying 303 U.S. AEC firms shows engineering firms average a 44.2% hit rate. The firms clustering above that benchmark share one characteristic: they say no more often than their peers.
For any major strategic decision, a structured decision framework beats a room full of competing intuitions.
What AI Actually Adds to Go/No-Go Decisions
AI can improve go/no-go decisions, but only once the criteria are real. If the framework is theater, automating it just makes the theater run faster.
Unanet's7 2026 research on AEC business development identifies pursuit selection as the single highest-leverage BD decision AEC firms make— and notes an emerging practice of feeding RFPs to AI tools like ChatGPT or Claude against a defined scoring rubric. When the criteria are solid, an AI automation workflow can:
- Score an RFP objectively against weighted criteria in minutes rather than 30
- Surface pattern mismatches— flagging that a client profile resembles past pursuits you lost to a specific competitor— when you provide your firm's historical pursuit data as context
- Generate a written decision summary documenting why a no-go decision was made— which your team then saves to your CRM or project record
- Remove the social pressure that makes committees reluctant to decline visibly
What AI cannot do: replace relationship intelligence, read unwritten client dynamics, or substitute for the named authority who makes the call. That distinction matters. CRM Software Blog6 notes that automation can enforce go/no-go criteria consistently across the firm— but "consistently" only helps if the criteria themselves are predictive.
The right framing is AI as discipline enforcer, not decision-maker. It holds the criteria constant so that weekly RFP volume doesn't quietly erode the standards. AI governance works the same way for any system where humans are tempted to override structure under pressure.
Three questions come up consistently when AEC firms start building real go/no-go discipline.
FAQ
What is a go/no-go meeting in AEC?
A go/no-go meeting is a formal decision point where an AEC firm evaluates whether to respond to an RFP or pursue a project opportunity. The meeting is meant to apply weighted criteria and make a genuine go or no-go call before proposal resources are committed. In practice, the decision is often made informally before the meeting— making the formal session a ratification rather than a real gate.
What is a good win rate for an AEC firm?
SMPS Foundation research2 surveying 303 U.S. AEC firms shows engineering firms average a 44.2% hit rate— the highest among AEC sectors. Construction firms average 37.9%. Firms using formal pursuit discipline with selective criteria cluster above that benchmark; firms that pursue everything tend to land at the low end. The gap between selective and non-selective firms is where the real ROI of go/no-go discipline lives.
How long does a go/no-go meeting take?
The meeting itself can run 15–30 minutes. The problem isn't duration— it's that the real decision is often made informally before the meeting, making the formal session redundant. According to Unanet7, AI-assisted scoring against pre-defined criteria can reduce structured evaluation time to under five minutes. But meeting length is a secondary issue. The primary issue is whether anyone in the room has the authority to actually say no.
What criteria matter most in a go/no-go decision?
Client relationship strength is the single strongest predictor, representing 20–30% of the scoring weight in Kantiv's1 AEC-tested framework. Other high-weight factors include team availability by discipline (15–20%), sector experience depth (15–20%), and competitive landscape (10–15%). The data is consistent across hundreds of AEC pursuits: no other factor compensates for a weak client relationship. Without a warm relationship, win probability is consistently low regardless of every other criterion.
Auditing Your Own Go/No-Go Process
Start with three diagnostic questions:
- Do you know who had the authority to say no on your last three losses?
- Did you track whether your go decisions won at the rate you predicted?
- Are your criteria set before you see the RFP— or after?
If you can't answer those three questions, your go/no-go is theater.
The fix isn't procedural. Another scorecard won't move the needle if the same authority vacuum persists, if outcomes are still untracked, if criteria still get set after the fee size is already visible. Building real discipline means making one structural decision— naming the person— and protecting it from override.
When that audit reveals theater, AI strategy for your firm is a starting point for building the right decision infrastructure. Measuring win rate improvement quarterly is how you know the fix is working.
The goal isn't a better scorecard. It's real discipline.
References
- Kantiv, "Go No Go: How AEC Firms That Win More Make the Decision"— https://www.kantiv.com/blog/go-no-go-in-aec
- Building Design + Construction Magazine, "How does your firm's hit rate stack up to the AEC competition?" (2017)— https://www.bdcnetwork.com/how-does-your-firms-hit-rate-stack-aec-competition
- Monograph, "Which Engineering Projects Should You Say No To? A Go/No-Go Framework"— https://monograph.com/blog/engineering-go-no-go-framework
- Canadian Consulting Engineer Magazine, "Preparing Proposals Is A Costly Business— And Not Just For Consultants"— https://www.canadianconsultingengineer.com/preparing-proposals-is-a-costly-business-and-not-just-for-consultants/
- Unanet, "Expert Advice: How to Make the Right Go/No Go Decision"— https://unanet.com/blog/expert-advice-how-to-make-the-right-go-no-go-decision/
- CRM Software Blog, "AEC go/no-go automation for better pursuit decision making" (2024)— https://www.crmsoftwareblog.com/2024/01/aec-firms-can-make-smarter-decisions-about-pursuing-work-by-automating-the-go-no-go-process/
- Unanet, "How AI is reshaping AEC business development and marketing"— https://unanet.com/blog/how-ai-is-reshaping-aec-business-development-and-marketing/
