Go/no-go without a spreadsheet: a bid decision workflow for estimating teams

Stop running go/no-go as a one-time scorecard. Build the bid/no-bid decision into your pipeline so it uses your real hit rate and guides what your team pursues.

The most expensive decision in estimating isn't how you price a job. It's whether you bid it at all. Every hour spent on a pursuit you were never going to win is an hour stolen from one you would have. Most teams know this, which is why they build a go/no-go scorecard, usually in a spreadsheet that gets filled out once and then forgotten. The scoring isn't the problem. The problem is that a one-time score sitting in a spreadsheet doesn't change what your team does next.

Why the scorecard-in-a-spreadsheet fails

A go/no-go spreadsheet asks the right questions: Do we have the relationship? Is it our kind of work? Do we have the capacity? Can we win it at a margin worth having? But once you've scored a bid, the spreadsheet has done all it can. It doesn't carry the decision into your pipeline, and it lives apart from the bids themselves. So the score becomes a formality, and the real decision gets made on gut anyway.

Make go/no-go the first stage of the pipeline

Treat go/no-go as a step every bid moves through, not a document you fill out on the side. When a new opportunity lands on your board, it enters a review stage where the go/no-go question gets answered before any estimating time is spent. Pursue it and it advances. Pass on it and it's marked and set aside, not deleted, so you keep the record.

Decide with your own history, not just instinct

A go/no-go call is only as good as what you know about your own results. Because every past bid is a record with a stage and an outcome, your analytics show you what you actually win. When you can see your hit rate by type of work or client, the go/no-go question stops being does this feel right and becomes do we win this kind of job.

Keep the decision visible

When go/no-go is a stage on a shared board, the whole team sees what's being pursued and why the passed bids were passed. The principal doesn't have to ask. The estimator doesn't start work on a job that was already declined.

The workflow in practice

A new opportunity lands on the board and enters review. The team answers go/no-go using relationship, fit, capacity, and your real hit rate for that kind of work. Pursue advances the bid to estimating. Pass marks it and clears it from active work. Every outcome feeds the analytics that sharpen the next decision.