Scoring Website Proposals Fairly: A Weighted Framework

Fair website proposal evaluation rests on three things decided before you open a single response: the criteria, the weight each one carries, and a written description of what a strong, average and weak answer looks like. With those in place, a panel can score independently, compare notes on real differences, and reach a decision it can explain. This article gives you a weighted scoring matrix and the warning signs that separate a convincing answer from a confident one.

It assumes the RFP has already been issued and responses have passed a compliance check. If you are still at that stage, start with our guide to running a web agency RFP in the UAE.

Why unweighted scoring misleads

A common shortcut is to score every question out of five and add the totals. The problem is that every question then counts equally. A strong answer on project management templates can offset a weak answer on content migration, even though one of those decides whether the launch succeeds and the other barely matters.

Gut feel has the opposite problem. A panel that "just knows" which agency it prefers will usually favour the best presentation, not the best plan. Weighting forces the panel to agree, in advance, which parts of the work matter most to this particular project.

Building a proposal scoring matrix

A proposal scoring matrix has four columns: criterion, weight, score and weighted score. The work is in defining the first two well.

Step 1: Group criteria into a small number of areas

Keep the top level to five or six areas. More than that and the weights become too thin to separate bidders. A typical set of procurement evaluation criteria for a website project looks like this:

1. Understanding of the brief: does the response show it has grasped your goals, audiences and constraints?
2. Solution and technical approach: platform choice, architecture, integrations, performance, security, accessibility.
3. Design and user experience approach: research, information architecture, bilingual design, content strategy.
4. Team and delivery: named people, relevant experience, project method, risk management.
5. Support and ownership: post launch support, upgrades, documentation, what you own at the end.
6. Commercials: total cost over a fixed term, clarity of pricing, assumptions and exclusions.

Step 2: Assign weights that reflect this project

Weights should come from your project's risks, not from a template. A content heavy corporate site with a large migration might put more weight on technical approach and delivery. A brand led relaunch might put more on design. A tightly specified rebuild on a known platform might give commercials more influence.

A simple method is to give the panel 100 points to distribute across the areas, discuss the differences, and settle on a final split. Record the reasoning; it is the first thing an auditor or an unsuccessful bidder will ask about.

Step 3: Write the scoring scale

Use a scale of 0 to 5 and describe each level in plain words. This is the single most effective step for consistency between panel members.

Step 4: Calculate weighted scores

For each area, divide the score by 5 and multiply by the weight. Add the results to get a total out of 100.

Hypothetical example: a panel weights six areas as follows and scores two bidders.

Agency B produced the more impressive design work and a sharper price, and a panel scoring on impression might well have chosen it. The weighted view shows that Agency A is stronger in the areas this panel agreed matter most.

Vendor scoring for each area: strong answers and weak ones

Good vendor scoring depends on recognising the difference between detail and decoration. The indicators below help panel members score consistently.

Understanding of the brief

• Strong: restates your goals in its own words, identifies a risk or opportunity you did not mention, asks or answers a pointed question about your audiences.
• Weak: repeats your RFP text back to you, or opens with several pages about the agency before reaching your project.

Solution and technical approach

• Strong: recommends a platform and explains why it fits your requirements, names the trade offs, describes how migration and redirects will protect search visibility, and explains how performance and accessibility will be tested.
• Weak: lists every technology the agency has ever used, or proposes a platform without linking it to your requirements. Claims such as "fully secure" or "lightning fast" with no method behind them deserve a low score.

Design and user experience

• Strong: describes research with your actual users, explains how Arabic and English layouts will be designed rather than mirrored, and shows comparable past work with the reasoning behind it.
• Weak: relies on attractive unsolicited concepts with no research behind them. Polished visuals can hide a thin process.

Team and delivery

• Strong: names the people who will do the work, their roles and time allocation, and says clearly which parts, if any, are subcontracted. Gives a realistic plan with dependencies on your side spelled out.
• Weak: shows an organisation chart of the whole company, or promises a delivery date that ignores your own approval and content steps.

Support and ownership

• Strong: explains what support covers, how issues are prioritised, how updates are handled, and confirms you will own the code, designs, content and accounts.
• Weak: vague references to "ongoing partnership", or ownership terms that leave key assets with the agency. Check the draft contract against what the proposal says; the gap between them is where disputes start. Our guide to writing a scope of work that prevents disputes covers the clauses to look for.

Commercials

• Strong: uses your pricing template, lists assumptions and exclusions plainly, and separates one off from recurring costs over the term you asked for.
• Weak: a single headline figure, unexplained contingency, or large items marked "to be confirmed". A low price with many exclusions is often the most expensive option once the project runs.

How to score commercials fairly

Price causes more argument than any other criterion. Two practical rules help.

Normalise to a comparable total

Before scoring, adjust each price so it covers the same scope over the same term. Add back excluded items at a reasonable estimate, and note what you added. Then compare.

Score price relative to the lowest compliant bid

A common method gives the lowest compliant total the full commercial score, and every other bid a proportion of it: lowest total divided by this bid's total, multiplied by the weight. It is simple and transparent. Whatever formula you use, publish it in the RFP and apply it without exception.

Some panels score quality first, without seeing prices, and open commercial envelopes only for bidders above a quality threshold. That separation reduces the pull of a low number on everyone's judgement.

Running the panel

A sound matrix still fails if the panel process is loose.

Score independently first

Each member scores alone and writes a one line reason for every score. Group discussion before individual scoring tends to converge on the view of the most senior person in the room.

Moderate the differences

In a moderation meeting, look only at areas where scores differ by two points or more. Ask each member to explain their reasoning with reference to the response text. Agree a moderated score and record why.

Use presentations to test, not to rescore everything

Final presentations should test specific doubts from the written scoring, such as whether the named team really exists or whether the migration plan holds up. Decide in advance which areas the presentation can change, and by how much.

Keep a decision record

Store the matrix, individual scores, moderation notes and final decision together. In regulated sectors and in government related entities this record is often required; our article on government and semi government web projects covers that context. It also lets you give honest feedback to the agencies that did not win.

Adapting the framework to specialist platforms

Where the platform is already chosen, shift weight from solution choice to evidence of depth on that platform: certified skills where the vendor offers certification, comparable implementations, and how the partner handles upgrades. Our guide to evaluating Sitecore partners for listed companies shows how those criteria change for an enterprise platform decision.

Putting Codeeo through your scoring

Codeeo welcomes being judged on substance. The team provides website design and development, UI/UX design, ecommerce on Shopify, WooCommerce and headless builds, custom software and business systems, and digital marketing and SEO, with 200+ projects delivered across the UAE and the US and a team of 80+ across Dubai, Riyadh and Karachi. You can review our case studies before shortlisting, and because the office is in Dubai, your panel can meet the people who would work on the project. Contact the team to request a proposal for your evaluation.