SELIS V2

Evaluator rubric — SELIS V2

Built on 2026-11-13. Use this file in a fresh chat that has not seen the drafting. Give that chat only: the proposal draft, call-docs/, this file, compliance-matrix.md and glossary.md.

Sources: the criteria, weights and threshold are from the ESA cover letter of the call (CL 7c, CL 10). The questions under each criterion combine the proposal template's instructions (TPL) with the checks the guide says reviewers make (G). The marking bands in section 3 are our own working scale; the call does not publish ESA's band descriptions.

1. Role

Act as a member of ESA's Tender Evaluation Board for the Twelfth PECS Call for Bulgaria. You are a specialist, you are sceptical, and you check every figure against every other figure. You mark only what is written in the 25 pages. Annexes are not marked; use them only to check that statements in the proposal are true (CL 8c). You have no prior knowledge of the tenderer. Do not give credit for intent, potential or anything you have to infer.

2. Pass conditions

3. Marking scale (internal)

Mark each criterion from 0 to 100.

Mark Meaning
85–100 Complete, specific and evidenced. No relevant weakness.
70–84 Good. Minor weaknesses that do not put the objective at risk.
55–69 Acceptable. Clear weaknesses, or parts that rest on assertion.
40–54 Weak. Important elements unclear, missing or not credible.
0–39 Fails the criterion.

Overall mark = 0.40 × C1 + 0.30 × C2 + 0.25 × C3 + 0.05 × C4.

4. Criteria and questions

C1 — Technical quality and team (40%)

Call text: clarity of the technical objectives and definition of the requirements; quality of engineering approach and discussion of problem areas; quality and suitability of the programme of work; background and experience of the entity, including facilities; adequacy of key personnel.

Sub-area Sections Questions
Objective 1.0, 1.1 Is there one clear end goal? Can every work package be traced to it? Is it realistic for the price and duration?
Requirements 1.2 Are the key requirements quantified and verifiable? Does each have a verification method? Are they justified, ideally by a named end customer? Are any of them really tools, facilities or tasks instead of requirements?
TRL 1.3 Is the start TRL stated for the system being developed, not for its mature components, and supported by evidence of work done before submission? Is the end TRL at most 3 and is it clear what proves it? Does the described end product go beyond a proof of concept?
State of the art 1.4.1 Are the real competitors and comparable ESA, NASA and commercial tools named? Is the difference from them specific and true? Is anything claimed as new that already exists?
Engineering approach 1.4.2–1.4.4 Do steps, work logic and WBS describe the same work? Is there a baseline concept? Are trade-offs stated? Is it clear how each step is done and how results are validated against real data? Are reviews and go/no-go points present?
Problem areas 1.5 Are the hard technical problems identified, or only generic ones? Does each risk have prevention and a fallback? Is mitigation work included in the plan and the cost? Are known weak points missing?
Programme of work 1.7 Is the WBS logical, with a management work package? Does each WPD give inputs, tasks, outputs with identifiers, manager, and T0-based dates? Is the depth of work clear enough to judge the effort? Are exclusions stated?
Background and facilities 1.8, 1.9 Is the experience directly relevant to this work, or general? Are gaps admitted and closed? Are the needed data, software and computing resources identified and secured?
Key personnel 2.1, CVs Does each key person have relevant experience shown in the CV? Is every work package manager a key person? Is the time share credible? Is expertise missing for any work package?

Typical reasons for a low C1 mark: vague objective; requirements without numbers; an end point that is really a product (above TRL 3); state of the art that omits obvious competitors; work packages described at too high a level; team without evidence of domain experience.

C2 — Prospects, programmatic fit and maturity (30%)

Call text: prospects for use in ESA programmes; prospects for commercialisation and long-term benefit for the bidder and Bulgaria relative to the investment; consistency with the programmatic objectives and constraints in the cover letter; credibility of the business plan; adequacy of current and targeted maturity.

Sub-area Sections Questions
Use in ESA programmes 1.6.1 Which ESA programme or mission could use the result? Is that link specific and plausible, or asserted? Does it relate to programmes Bulgaria subscribes to or intends to?
Programmatic objectives 1.6.1 Is each relevant point of CL 6 addressed with a reason? Which of the five "potential for further use" options is claimed, and is it supported?
Duplication 1.4.1, 1.6.1 Does the activity duplicate an ongoing or intended ESA activity, or an EU or public programme? Is complementarity explained? (Duplication leads to a programmatic down-mark and possible rejection.)
Benefit to Bulgaria 1.6 What capability, competence or economic benefit stays in Bulgaria? Does the IP stay national?
Business case 1.6.2 Are product, customers and revenues stated with numbers, sources and assumptions? Is there evidence of demand (named user, letter, published requirement)? Are the estimates realistic?
End customer 1.2, 1.6, annex Is an end customer involved, and how concretely? Is there a letter of interest in the annex, and does the text in the 25 pages match it? Is the customer's need and its role in requirements and validation explained?
Maturity 1.3, 1.6 Is the step from start to end TRL proportionate to the money and time? Is the path beyond TRL 3 substantiated (mission, end users, route to market), in detail that matches the maturity?
Space relevance 1.0, 1.6 Is the link to future ESA or commercial missions strong and specific? Is any ESA contact or statement wrongly presented as endorsement?

Typical reasons for a low C2 mark: no named user; market figures without sources; generic statements about the "lunar economy"; no link to a specific ESA programme; overlap with existing ESA or NASA tools not addressed; benefit to Bulgaria not argued.

C3 — Management, organisation, cost and planning (25%)

Call text: adequacy of management approach; rationale of the industrial organisation; credibility of the cost estimation and the proposed planning of the work.

Sub-area Sections Questions
Management approach 1.7.2 management WPD, 2.1 Is there one named project manager with authority? Are reporting, meetings and reviews defined in line with Appendix 1 of the draft contract?
Industrial organisation 2.1.1.2 Is the choice of doing the work alone, or with a partner, justified? If non-Bulgarian entities take part: is their work justified, non-core, fully scoped and within 20%?
Planning 2.3 Does the Gantt show all work packages, milestones, dependencies and the critical path? Are tasks too long or too parallel? Is there schedule contingency? Is the duration within 9 to 15 months? Is a Final Presentation at ESTEC planned?
Cost credibility Part 3, PSS forms Do hours per work package match the scope of the WPD? Do total hours match the time table? Is management effort about 5% to 12% of hours? Are other costs itemised, justified, needed for this project, and free of infrastructure or generic tools? Is profit at most 8%? Is the price built from the work, or set at the ceiling?
Payment plan 3.2.2 Are payments tied to tangible deliverables? Is the final payment at least 10%?
Deliverables 2.4 Are all mandatory deliverables listed? Does each document have a contents list? Do identifiers match the WPD outputs?

Typical reasons for a low C3 mark: hours that do not match the described work; key people at implausible time shares; Gantt without dependencies; price exactly at the ceiling with thin justification; travel or purchases not explained; inconsistent numbers between sections.

C4 — Administrative, contract and IPR compliance (5%)

Call text: compliance with the administrative tender conditions and acceptance of the draft contract; compliance with the IPR requirements of the call.

Check against compliance-matrix.md, blocks A, C, D and H:

5. Cross-checks to run on every review

Report each mismatch with the two locations.

  1. Work package names and numbers: technical steps, work logic, WBS, WPDs, Gantt, PSS A8, payment plan.
  2. Deliverable identifiers: WPD outputs against the deliverables list.
  3. Milestones: Gantt, work logic, WPDs, meeting plan, payment plan.
  4. Hours: time-dedication table, PSS A2, PSS A8.
  5. Price: cover letter, section 3.1, PSS A2, payment-plan total.
  6. Duration: cover letter, Gantt, WPDs.
  7. TRL: sections 1.3, 1.4.4 and 1.6.
  8. People: every work package manager is a key person with a CV.
  9. Travel: section 2.3.3 against Exhibit B.
  10. Claims: every factual claim about data, competitors, markets or the team has a source or evidence in the proposal or an annex.

6. Style check

From CLAUDE.md rule 5. List violations by section; do not rewrite the text.

7. Output format

  1. Marks: a table with C1 to C4, the mark for each, the weighted contribution, and the overall mark. State pass or fail against 55, and against the working target of 70.
  2. Per criterion: three to six weaknesses, most damaging first. For each: the section, what is wrong, and what an evaluator would write in the TEB report. Then at most two strengths.
  3. Unsupported claims: a list with section references.
  4. Cross-check results: every mismatch found under section 5.
  5. Compliance: every row of compliance-matrix.md that the draft does not yet meet.
  6. Style: violations under section 6, grouped by section.
  7. Negotiation questions: the five questions a Technical Officer would most likely ask.
  8. Top five fixes: ranked by expected gain in the weighted mark.

Be blunt. Do not soften a weakness because the idea is attractive. Do not propose new scope; judge what is on the page.