Intro
Evaluators do not read proposals the way authors intend. They skim, search for tick-box evidence, and negotiate judgment across constrained time and competing priorities. A technical solution can be excellent but still fail if it imposes cognitive friction on the panel. This post explains how panels process submissions and translates that behaviour into concrete structure and drafting rules that make evaluators' jobs easier and increase your scoring probability.
How panels actually read submissions
Understanding evaluator behaviour is the first lever. Several consistent patterns appear across donor and government panels:
- Satisficing not optimising. Evaluators aim for a defensible score, not the absolute best value. Once a submission meets the defined markers, they move on.
- Search-driven reading. Most evaluators do targeted searches for required phrases, evidence items and numbers rather than reading end-to-end.
- Anchoring and order effects. Early impressions and the order of sections influence later judgments. A strong opening can anchor a higher overall score.
- Time pressure and fatigue. Panels often have days of dense review; clarity and brevity reduce errors and drift.
Design your document to work with these behaviours. That means predictable structure, clear signposting and evidence presented where the evaluator expects to find it.
Document layout and signal design
Format guides matter. A clean, consistent layout reduces the time it takes for an evaluator to locate a required element.
- Use the tender structure as your skeleton. Mirror the evaluation criteria headings exactly, with identical numbering where possible. This reduces search time and aligns your response to the scoring matrix.
- Lead with an evaluator-friendly executive summary. Two short pages that map criteria to the exact page numbers and annexes where supporting evidence lives will be used repeatedly by reviewers and panels.
- Create signalling devices: a one-line answer, followed by supporting bullets, followed by a tagged annex reference. Example structure for each criterion:
- One-line compliance statement (yes/no or short claim).
- Two to four bullet points of the required evidence with labels (evidence: CV; date; reference; outcome).
- Pointer to annex and exact page/table cell for verification.
- Use templates for recurring elements. Standardised CV cards, partner role cards and delivery timelines let evaluators compare entries quickly.
- Keep tables dense and consistent. Evaluator eyes prefer compact tables that place the criterion on the left and the evidence on the right. Avoid sprawling narrative in table cells.
Visual clarity matters as much as content. White space, consistent font sizes and heading hierarchy reduce cognitive load. But do not hide evidence in images or infographics without also providing a plain-text equivalent.
Crafting bite-sized evidence
Evaluators are looking for proof, not persuasion. Present evidence in a format that can be verified in a few seconds.
- Atomic claims. Break achievements into single-idea claims that each have one supporting evidence item. This avoids mixed claims that force evaluators to decide between discrete elements.
- Use evidence labels. Preface each supporting item with a label the evaluator expects such as: contract reference, client name, contract value, dates, deliverable and outcome. If a tender forbids client names, label the contact as "confirmed referee" and give the verification mechanism.
- Annotated annexes. Instead of a long annex, produce short annexes with a one-line header explaining what the document proves. For example: "Annex 3a: Completion certificate for water rehabilitation, confirms client acceptance and handover date 03/2023."
- Avoid jargon and passive voice. Plain sentences with active verbs cut reading time and reduce misinterpretation.
- Prioritise verifiability over flourish. A clear table with dates and outcomes beats a paragraph of praise from your marketing team.
Where multiple pieces of evidence support the same claim include a primary and secondary evidence item. Make the primary the easiest to verify.
Operational checklists and rehearsal
Submission layout must be validated before final upload. Rehearse how an evaluator would check your dossier.
- Create an evaluator walkthrough checklist. For each scored criterion, list: the exact line in your proposal that answers it, the annex file name and page number where supporting evidence appears, and the expected verifier (referee, published report). Use this checklist in internal QA and to prepare for clarifications.
- Run a timed review. Give a colleague or external reviewer 20 minutes per major criterion and ask them to score based only on the materials you have flagged. If they struggle to find proof, revise.
- Prepare a short adjudication note for the bid team. This is a two-page brief that explains how you expect evaluators to score the proposal and where to find any potentially contentious evidence. It is useful if evaluators ask clarifying questions.
- Check accessibility. Avoid embedded files that require custom software and ensure annex file names are meaningful and ordered to match references in the main text.
These operational checks reduce the risk of late-stage surprises and help you defend scores in clarification rounds.
When to simplify and when to expand
Not every section benefits from dense evidence. Use the following rule of thumb:
- Simplify when the criterion is pass/fail or procedural: a short direct claim and a single corroborating document is sufficient.
- Expand when the criterion is discretionary and comparative: provide granular evidence, metrics and a short comparative narrative that explains why your approach is superior.
Also tailor detail levels to the scoring weight. Spend proportional time and page space relative to the points available in the evaluation matrix.
Takeaways
- Mirror the tender structure exactly to reduce evaluator search time.
- Use a one-line claim, short supporting bullets and a precise annex pointer for every criterion.
- Present evidence in atomic, labelled items that can be verified in seconds.
- Test your dossier with a timed evaluator walkthrough and use the results to rework structure and signposting.
- Allocate detail proportionally to the scoring weight and simplify pass-fail sections.
Writing for the evaluator is not about diluting substance. It is about packaging substance so panels can find, verify and reward it consistently. Adopting these habits lowers cognitive friction, reduces scoring errors and increases your chance of success.