Back to Insights
    #0008Apr 26, 2026

    The Evaluator Scorecard: How Committees Actually Score Your Proposal

    Most architecture firms write proposals without a clear picture of how the scoring actually works. The committee that decides whether you win is using a structured rubric, and the way they apply it has predictable patterns most firms don't account for.

    How the scoring matrix works

    Public-sector RFPs use weighted evaluation criteria that must be disclosed in the RFP itself. Research from Responsive, Arphie, and Inventive on RFP scoring shows the typical weight breakdown for AEC proposals:

    • Technical Approach: 25 to 35 percent
    • Experience: 20 to 25 percent
    • Cost: 15 to 25 percent (lower for QBS / qualifications-based selection)
    • Team: 10 to 20 percent
    • Timeline / Management: 5 to 15 percent

    In Canada and the US, federal architectural services often follow Qualifications-Based Selection under the Brooks Act, where price is excluded from the initial evaluation. Qualifications carry the entire weight until a shortlist is chosen, then fee is negotiated separately. This is why a low fee proposal rarely wins a federal project.

    What the research says about how evaluators score

    A few patterns from research on proposal evaluation bias and cognitive load are worth knowing:

    • First impressions anchor the rest of the scoring. Research compiled by Arphie on proposal evaluation found that "once an evaluator forms an initial impression of a proposal, they unconsciously seek evidence supporting that judgment while discounting contradictory information." Strong opening sections lift later scores. Weak ones drag them down.
    • The halo effect is real. A compelling Project Understanding or impressive lead bio carries forward through the rest of the proposal, even on unrelated criteria.
    • Cognitive load makes evaluators score conservatively. Research published in cognitive science journals shows that under high cognitive load, reviewers exhibit stronger central-tendency bias. They cluster scores in the middle rather than giving extremes. Proposals that are easy to read get higher scores than equally good proposals that are dense.

    What this means for your proposals

    If your proposal forces the evaluator to hunt for the answer, you lose points even if the answer is there. The committee scoring your submission has a finite amount of attention, and they're scoring under time pressure with five other proposals on the desk.

    The firms that score best aren't the ones with the most content. They're the ones that map every section of their proposal to a specific evaluation criterion, lead with the strongest material, and make it impossible for the evaluator to miss the points you're earning.

    This is what ArchFP's submission review feature is built around. It scores your draft against the RFP's actual evaluation criteria the same way a committee would, flags sections where you're losing points, and identifies where one stronger paragraph would lift your overall score.

    If your firm wants to know how a committee would score your next submission before you send it, book a 15-minute demo and we'll walk you through it.

    © 2026 Project Rayder Inc. All rights reserved.