The Candidate Evidence Menu: Front-Loading Clarity Without Front-Running Judgement
Photo: Campaigns & Technology, Dr. Reza Kazemi, CC BY-SA 4.0, via Wikimedia Commons
Most candidates do not set out to over-assess. They submit bulky portfolios because the evidence requirements were never made concrete at the point when they could still act on them. A candidate-facing evidence menu is a modest remedy: a short, assessor-approved document that sets out the kinds of evidence a programme accepts, what sufficiency looks like in practice, and where common submissions fall short. It is not a mark scheme, and it should not become one.
Start from the assessment plan, not from guesswork
An evidence menu should be derived from the assessment plan and the qualification criteria, not invented alongside them. The assessor team should review the plan, identify the evidence types that are genuinely permissible, and agree the language that will be used with candidates. The menu then becomes a translation layer: it makes the plan usable without replacing it. As providers review their assessment strategies in 2026, this is also a useful CPD exercise for assessors, because it forces the team to articulate what it means by sufficient evidence.
Approval matters. A lead assessor or internal quality assurer should sign off the menu, and the document should carry a version date and review point. If the assessment plan changes, the menu changes. If standardisation reveals a recurring misunderstanding, the menu is one of the first places to look.
What the menu should contain
Three layers are enough. First, acceptable evidence types: observation, witness testimony, product evidence, professional discussion, reflective account, work documents, and any other form the programme permits. Second, sufficiency criteria: the attributes that make a piece of evidence usable. Third, weak examples: short illustrations of common shortcomings, described without providing model answers.
A simple template is shown below.
| Section | Purpose | Example |
|---|---|---|
| Evidence type | Names the form and its limits | Single quotes used here: a witness testimony from a line manager or qualified colleague who observed the candidate carrying out the task. |
| What sufficient looks like | Sets out the attributes assessors will look for | Signed, dated, specific about what was observed, and clear about the witness relationship to the candidate. |
| Common weak example | Illustrates a recurring problem without supplying an answer | A statement that the candidate worked well under pressure, with no description of the task or the candidate actions. |
| If unsure | Routes questions to the right person | Ask your assessor or programme coordinator before commissioning new evidence; do not create retrospective accounts. |
Keep the language sector-agnostic where possible. The same principles apply whether the evidence comes from a workshop, a client-facing procedure, a laboratory task or a written product. The menu should not imply that one evidence type is always stronger than another; it should explain what each type can and cannot demonstrate.
Sufficiency in plain language
Assessors often know sufficiency when they see it, but candidates need it stated. A useful menu describes sufficiency through questions rather than slogans. Is the evidence attributable to the candidate? Is it current enough for the criteria being claimed? Does it cover the whole performance, or only the easy part? Is it consistent with other evidence in the portfolio? Can the assessor verify it without having to reconstruct the candidate intent?
Examples help. A product evidence item is sufficient when it can be linked to the candidate own work, carries a date or version, and includes a brief annotation explaining the candidate contribution. A reflective account is sufficient when it refers to specific episodes and decisions, not general statements about being professional. A witness testimony is sufficient when the witness describes what they saw or heard, not what they concluded about the candidate competence.
This is also where over-assessment begins to fall away. When candidates understand what sufficiency means, they are less likely to submit three pieces of evidence where one well-documented piece would do. The menu should say that explicitly: more evidence is not automatically better evidence.
Weak examples without model answers
Common weak examples are valuable, but they are also the easiest place to cross the line into coaching. Use them to illustrate a defect, not to supply a template. A photograph with no date, location or explanation of the candidate role is a weak example. A witness statement that says the candidate was competent, without describing the task or the candidate actions, is another. A logbook entry that records attendance but not the tasks performed is a third.
Notice what these examples do not do: they do not tell the candidate which photograph to take, which witness to approach or what words to use. They describe the quality of the evidence, not its content. That distinction should be stated in the menu itself, so that candidates do not read the examples as a checklist to be gamed.
Where informing ends and directing begins
The boundary is easier to hold if assessors apply a few practical tests. Would the menu read the same for every candidate on the programme? Does it describe evidence standards rather than expected answers? Does it leave the candidate to select and present their own evidence? Does it avoid promising an outcome? If the answer to any of these is no, the menu is probably doing too much.
Informing sounds like: we need evidence that shows you can carry out the task safely and explain your decisions. Directing sounds like: use the task on page 14 and write these three points. Informing points to the criteria. Directing pre-assesses the criterion. The first is transparency; the second is substitution.
Assessors should also be careful with verbal guidance. A menu is not a licence to coach candidates through the decision in pre-submission meetings. It is a reference point that both parties can use. When a candidate asks whether a piece of evidence is enough, the assessor can respond by referring to the sufficiency criteria and inviting the candidate to test their evidence against them. That preserves candidate ownership and assessor neutrality.
Governance, review and CPD
An evidence menu is a living document. Review it after standardisation sessions, after internal quality assurance sampling, and after any change to the assessment plan. Record the reason for changes. If a particular weak example keeps appearing, consider whether the menu is clear enough or whether the assessment plan itself needs revisiting.
There is a CPD benefit here too. Drafting and reviewing the menu gives assessors a shared language for sufficiency. It can be used in team meetings as a calibration exercise: ask assessors to sort a small set of anonymised evidence items against the menu and discuss the disagreements. That is a more productive use of time than producing another candidate handout that no one reads.
A short checklist before publication
Before the menu goes to candidates, check that it: is derived from the assessment plan; has been approved by the lead assessor or IQA; uses plain language; distinguishes evidence types without ranking them; describes sufficiency through attributes, not answers; includes weak examples that illustrate defects rather than templates; states where candidates should go with questions; and carries a version date and review date.
Done well, the menu does not make assessment easier or softer. It makes the requirements visible earlier. That reduces avoidable over-assessment, lowers the number of disappointing rejections based on misunderstanding, and supports consistency without turning assessor judgement into a script. The candidate still has to select and present evidence. The assessor still has to judge it. The menu simply gives both parties a clearer starting point.
