# R&D adviser selection: milestone discussion note

Use the same note with each shortlisted candidate. Complete it with your technical lead and grant adviser, using material the evidence owners permit you to share. This is an editorial discussion aid, not a contract or a grant-body form. It does not score candidates or decide eligibility.

## Bring to the discussion

- Current call URL, document version/date and the grant adviser's open technical questions.
- Existing prototype/evaluation outline and the technical lead's explanation of the gap.
- Current work-package dependencies, vendor remit and preparation resources.

## Agree one bounded contribution

| Discussion point | Your entry |
| --- | --- |
| Decision and milestone | What decision should the work enable? Name the inspectable output and distinguish a planning milestone from an executed experiment. |
| Personal contribution | What will this candidate personally review, design or coordinate? Who retains cross-package coordination? |
| Inputs and access | Which existing materials can be reused? Who authorizes access and resolves each missing prerequisite before execution? |
| Deliverable | What will be handed over, in what usable form? If execution is needed, agree it separately from evaluation design/review. |
| Review and authority | Name the technical reviewer, grant adviser and sponsor. Say who judges the reasoning, checks application alignment and authorizes resource or scope changes. |
| Handover | Who maintains the revised plan? Who receives unresolved questions? What remains with the existing team, vendor and other advisers? |

## Ask the candidate to change the note

1. Which entry would you challenge, and on what evidence?
2. What could you deliver yourself, and which contribution belongs with someone else?
3. What would change the next milestone if an input were unavailable or the comparison inconclusive?
4. Is a grant writer or a narrow specialist sufficient? If you recommend a senior remit, which additional dependencies need coordination?

## Filled illustration: evaluation-design assignment

**Invented and unperformed; the same fictional surface-defect brief used in the article.** No experiment or performance result is supplied.

- **Decision/milestone:** approve a revised evaluation design before committing to method-dependent integration.
- **Candidate's contribution:** review a clean-image-only comparison against a simple threshold method; propose conditions addressing the intended input range, including glare, and explain what evidence would be retained.
- **Coordination:** the company's technical lead retains coordination of data access, vendor scope and later milestones. Expand the external remit only if this coordination is the actual missing contribution.
- **Input dependency:** the evidence owner must resolve permitted access to glare examples before execution. The design should describe the consequence if those inputs remain unavailable.
- **Deliverable:** annotated evaluation design and dependency note; no implied execution or validated performance.
- **Review/authority:** assign real people as technical reviewer, grant adviser and authorizing sponsor before commissioning the work.
- **Handover:** technical lead maintains the plan; vendor retains interface delivery. Finance, legal review and submission retain their separately assigned owners.

Record receipt, the technical review conclusion and the sponsor's next decision separately. A clear negative or inconclusive conclusion can still support a useful milestone decision.
