Understanding your QA score

Your QA score is shown for every answer and aggregated for the whole bid. It's an estimate of how an evaluator is likely to score the response based on past evaluator behaviour on comparable questions.

How it's calculated

• Specificity (25%), named projects, named partners, dated examples, numbered commitments.
• Evidence (25%), claims backed by documents in your vault.
• Vocabulary fit (15%), using the contract's language (Scope vs Spec, CE vs variation).
• Word limit utilisation (10%), neither under nor wildly over.
• Structure (10%), clear introduction, body, commitment, evidence.
• Compliance (15%), addresses every part of the question and any mandatory elements.

What 'benchmark' means

Each answer is also compared to the benchmark score, the average score that comparable answers have achieved on past tenders in the same sector and contract form. If you're above benchmark, you're competitive. Below benchmark, you have a specific improvement opportunity.

Improving a low-scoring section

The QA panel surfaces the specific dimension hurting the score. Most low scores are caused by either insufficient specificity (no named projects/numbers) or insufficient evidence (claims with no backing). Adding two specific examples typically lifts a score by 15–25 points.