Software vendors have spent two decades telling construction executives that spreadsheets are the enemy—that every workbook is a liability waiting to be replaced by a proper system. We sell automation software, so you might expect us to join the chorus. For bid-risk scorecards, we won't, because the spreadsheet is not what's broken. This article makes the case for keeping Excel at the center of your risk assessment process, and for fixing the part that actually fails.
The case for Excel is stronger than the industry admits
Consider what a bid-risk scorecard has to do. It has to collect judgments from several busy people—a BD lead, a risk manager, an operations executive, sometimes precon—in a form that can be scored the same way every time. It has to make the scoring math visible, because a go/no-go recommendation that emerges from a black box will be argued with, and should be. And it has to be legible to the CFO and the auditors years later, when someone asks why the firm chased a project that went sideways.
Excel does all of this well. Every reviewer in your company already knows how to use it, which means a new scorecard costs nothing in training and meets no adoption resistance. The formulas that turn raw answers into weighted scores sit in the workbook where anyone can inspect them, so the math is transparent rather than proprietary. Structured cells enforce the discipline that free-text forms never achieve: a reviewer who must choose a value from 1 to 5 in cell D14 produces data you can score deterministically, while a reviewer typing into a comment box produces prose you can only interpret. Finance departments trust workbooks precisely because they can open them, trace them, and archive them.
There's a reason the industry standardized on this tool for decision support, and it isn't inertia. It's that a scorecard is fundamentally a small structured document, and Excel is the best structured-document editor ever shipped.
What actually breaks: everything around the workbook
The failures attributed to spreadsheets are, almost without exception, failures of coordination. Someone has to send the right scorecard to the right five people for this gate of this pursuit. Someone has to notice that two of the five haven't responded and nudge them, then nudge them again, then find out one is on vacation and figure out who covers. Someone has to collect five returned attachments—one of which is last quarter's template, one of which has the formulas overwritten—reconcile them, transfer the numbers into a master workbook, and check the roll-up math. Then someone has to package the result for the decision-maker, who by now has three versions in their inbox and no certainty about which is current.
That someone is usually a capable person doing clerical work, and the process stalls whenever they're busy, which is always. When firms say "our go/no-go process broke down," this is nearly always what they mean. The scorecard didn't fail; the circus around it did.
Why replacing the spreadsheet doesn't fix it
The standard remedy is a portal: move the scorecard into a web application, give every reviewer a login, and let the system tally. This trades a coordination problem you understand for an adoption problem you don't. Reviewers who respond to an emailed workbook in minutes will postpone logging into an unfamiliar system, password resets become a real fraction of your cycle time, and the transparent formula bar gives way to scoring logic that lives in a vendor's code. The coordination work doesn't disappear either—someone still chases non-responders, except now they're chasing people to use software as well as to render judgment.
Our general view, laid out in meeting users where they are, is that automation succeeds when it adopts the tools people already use rather than demanding new ones. Bid-risk review is the clearest example we know.
Keep the scorecard, automate the coordinator
Bex Risk is built on exactly this division of labor. Your scorecard stays an Excel workbook, designed to your criteria and your weights. What Bex takes over is the ceremony: when a pursuit kicks off—with a single email like "AcmeCo wants us to bid the Oakdale renovation, ~$12M, RFP due 11/14"—Bex builds the workbooks, sends each reviewer a scorecard locked down to exactly the cells assigned to their role, and waits. It parses each return, scores it according to your weighted rules, sends reminders when a reviewer goes quiet, routes to an alternate when someone is out of office, and escalates when a timeout hits. At each gate, the decision-maker receives one clean package with the math already done, and replies "let's go" or "pass" to move the pursuit along.
The human judgment stays exactly where it was: reviewers score, executives decide. Bex never renders an opinion on whether to chase a project—a boundary we hold across every module, for reasons described in how Bex keeps humans in the loop. What disappears is the merging, the chasing, and the version confusion, which is to say the parts of the process that were never judgment in the first place.
The uncomfortable question for portal vendors
If a firm's reviewers are answering structured questions in a familiar tool, the scoring is deterministic and inspectable, and the coordination runs itself, what exactly would a purpose-built risk platform add? Usually the answer is dashboards, and Bex provides a live pursuit dashboard for those who want one. But the core insight stands: the spreadsheet was never the weak link. It was the strongest part of the process, surrounded by manual labor that nobody priced.
If your go/no-go process runs on scorecards that work and coordination that doesn't, we'd like to show you what it feels like when the coordination is automatic. The contact link is below—or read more about how Bex Risk runs multi-gate reviews first.