Professional Fellowship Evidence Checklist for Researchers

Prepare a professional fellowship evidence register with a worked contribution example, referee brief and checklist for verified research achievements.

Build your professional fellowship application around three to five contributions that match the programme’s criteria. For each contribution, record what you did, why it mattered, what can be verified and who can verify it. Use the current application guidance to decide which examples belong in the main case and which should remain in your working files. A clear evidence trail helps a panel assess your role in work shared with collaborators.

Professional fellowships recognise contributions according to each organisation’s purpose. Some assess research leadership or service. Some assess teaching and support for learning. Some scientific societies elect fellows through nomination. A funded research fellowship follows the funder’s own award terms. The evidence a panel asks to see depends on the route, so find the correct programme and grade before you start writing.

Researcher sorting documents and references for a professional fellowship application
Illustrative image generated for Emergent Africa.

Start with the exact fellowship criteria

Confirm whether your target route accepts a direct application or starts with a nomination. Find the programme’s current eligibility, application or nomination process, assessment descriptors and referee instructions. Save the version and the date you accessed it. Identify the criterion that describes the grade you want and write down what the panel needs to decide. If the standard requires sustained influence, one project may be the start of a case but the panel needs to see what continued. If it asks for leadership, show the decisions you owned and their consequences.

Two public routes illustrate the difference. Advance HE Fellowship recognises practice in higher education and uses its Professional Standards Framework. The Royal Society’s fellowship election guidance describes its own nomination and assessment process, including nomination by two Fellows. Use those documents to see how schemes specify what counts. Apply the exact criteria of the fellowship you are pursuing.

Criterion in the chosen schemeQuestion it asks about your workEvidence to look for
Research contributionWhich idea, method, resource or finding did you help develop?Versioned outputs, contributor statements, protocol records and project documents
Leadership or coordinationWhich decisions or responsibilities were yours?Terms of reference, milestones, approved decisions and corroborating accounts
Influence on practiceWho changed what they do as a result of the work?Adoption records, implementation reports, public guidance or independent feedback
Teaching or mentoringWhat changed in the learning or support you provided?Approved materials, activity records and appropriately shared evaluation results
Professional or public serviceWhat continuing contribution benefited a community or field?Meeting records, working-group outputs or an organisational account

If the criteria are broad, turn each one into a question an assessor could answer after reading your documents. “Show sustained professional contribution” becomes “Which work continued over a defined period, who used it and what can they confirm?” Keeping that question visible helps you choose what to leave out.

Build an evidence register before you draft

Make one row for every claim you might include. Record the criterion, project or activity, dates, your responsibility, outcome, document, and the name or role of a verifier who knows the work. Add a column for sharing permission. A date or measurement can mean little without its source, so include the page, table or paragraph that supports it. For a public link, check that it opens the relevant record rather than a general department homepage.

Use evidence close to the work when you can. An approved work plan can show what you were asked to do. A version history can show what you changed. A dated implementation record can show whether a team adopted a method. A paper’s contributor statement may show a role in the output. Each document proves a different point. A CV can help a reader navigate the evidence. Pair its strongest claims with records a panel can inspect or ask someone to verify.

Give the evidence a status that guides your next action. A public repository release or published policy is ready to cite if it says what you claim. A project summary from your own files may need confirmation from the team. A document with identifiable research participants or confidential partners needs permission and an approved way to share any extract. Mark missing evidence as pending, then revise or drop the claim if the gap cannot be closed by the deadline.

Claim in a fictional fellowship applicationEvidence with the closest fitWhat it can support
I designed a validation guide for a shared research datasetDated guide and contribution recordsThe guide’s content and my part in its development
Three project teams adopted the guide over the following yearDeployment notes and the teams’ approved reporting recordsWhich teams used it and when
I supported implementation through monthly workshopsSession schedule, approved materials and a coordinator referenceThe frequency and scope of the support
Users resolved more issues during the first reviewDefined metric and comparable before-and-after recordsA limited comparison for those teams and periods

This structure helps you catch a common problem. Evidence that a guide exists is good evidence of a deliverable. It takes a different record to support a claim about adoption. For the last row, a comparison may still leave open whether staffing, workload or other process changes also played a part. Give the assessor that context.

Select a small set of contributions that work together

Rank examples by the criteria they support and the evidence behind them. Start with a contribution that captures the grade’s central requirement. Pick another that adds evidence the first one cannot supply. An application about leadership across projects might start with a documented change you led and then show how you helped a second group use it. An application about sustained service might trace several connected roles over time instead of describing unrelated activities in equal detail.

Look for progression. If you started by running checks on one project and later trained a group to run the procedure, state when each responsibility began. Explain the change in scope. Give your title only when it helps the reader place the work. A panel can learn more from a short description of the decisions you made than from five titles attached to the same project.

Then look for overlap. A report, a presentation and a repository may all represent the same contribution. Group them under that contribution unless they show different outcomes. If your strongest example is a team output, say who led the project and what you personally owned. The research assistant contribution statement guide gives examples of how to explain those boundaries for work done under supervision.

Write claims an assessor can check

For each chosen contribution, write five things in order. Explain the problem, identify your responsibility, say what you did, state what happened and give the evidence. The order makes it easier to find the sentence that needs support. If you want to mention a percentage, name the original count, denominator, observation period and comparison. If you only have evidence of an output, describe the output and its purpose. A narrower claim can show substantial work.

Worked example for a research data contribution

Three project teams used different conventions for recording missing data, which made cross-site reports hard to compare. I was responsible for drafting a shared validation guide and testing it against the rules agreed by the data managers. I documented exceptions and trained the designated contacts in each team. The teams recorded adoption in their monthly implementation notes over the next year. My contribution is supported by the guide’s version history and the data coordinator’s account. The project records confirm adoption. They provide limited evidence about longer-term changes in reporting error rates.

This example states where the person’s responsibility begins and ends. It also shows what to do when an attractive outcome goes beyond the available record. You can add a later result when it is documented. Keep the evidence reference close to the specific claim, and avoid language that turns a group decision into an individual achievement.

If you are describing an award, membership or fellowship as evidence, give its correct title, organisation and year, along with a verification route where available. A nomination, a shortlist, an invitation and an award are different statuses. Use the one that the record shows. If a position or membership is still awaiting a formal decision, leave it out of any line that lists credentials already held.

Ask referees for corroboration they can provide

Read the rules for referee independence, institutional affiliation, length, timing and direct submission. A referee who can speak to the work is usually more useful than someone who only knows your title. Ask each prospective referee whether they can comment on the period and activities you plan to describe. Give them the application deadline and the official instructions. If a scheme asks for two different perspectives, decide which parts of the case each person can observe directly.

Prepare a short brief with the scheme name, relevant criterion, two or three claims, and the sources behind them. Ask the referee to correct dates or scope where their records differ. Offer links or approved extracts they can inspect. Let them write the assessment in their own words and send it through the route the organisation specifies. Our institutional research support letter guide explains how to distinguish a personal account from a commitment made on behalf of an organisation.

Dear [Name],

I am preparing an application for [fellowship and grade]. Would you be able to comment on my work on [project] between [dates], particularly my responsibility for [specific task or decision]? I have enclosed the relevant assessment criteria and a short list of records you may find useful.

The programme requests [submission route] by [date and time zone]. Please let me know if any detail in the summary differs from your records.

Thank you,

[Name]

Use a dated timeline to show sustained contribution

A timeline helps when you have to show what continued after the initial project. For the fictional validation guide, the first entry might be the date of the draft and the second the date that the first team used it. Later entries could record training sessions, a follow-up revision and an independent implementation decision. Select points that add evidence. Several dates for the same draft have less value than a record showing who used it and when.

The timeline can also make a gap visible. If records show activity in January and September, find out what happened between those dates before you describe continuous delivery. An appropriately qualified sentence such as “I led the January setup and returned to train a new team in September” gives the panel two verifiable contributions. It leaves space to explain a genuine break or change in role if the scheme asks.

Use comparable measures where the data allow

Suppose two project teams recorded 16 incomplete handovers among 80 before they adopted a guide, and 9 among 90 afterward. Those figures equal 20% and 10% under the same definition. The comparison can support a statement about the observed periods if the records are comparable. It cannot, on its own, show that the guide caused the change. State what else changed, including the teams, procedure or review period, if you know. Keep the underlying count in your evidence index.

When the scope does not support an outcome measure, look for something observable and relevant. A dated adoption decision, a repeated use of the procedure or a colleague independently applying your training can show practical influence. Ask what can be verified before choosing the language. Use the evidence to decide how far the case goes, especially when several contributors worked toward the same result.

Build a small shortlist of evidence before asking for permission

List the strongest available source and one fallback for each major claim. For an adoption claim, the strongest item might be a public implementation report. If that report is restricted, a programme manager’s approved confirmation may convey the dates and scope a panel needs. For an individual contribution, the strongest source might be the published contributor statement, with a short referee account to clarify a shared responsibility.

Where possible, give your verifier the exact question the record leaves open. “Can you confirm who approved the revised process and which tasks I was responsible for?” is easier to answer than “Can you say I was a leader?” The response may change which example you choose or how you describe it.

Protect confidential evidence and check the final submission

Use the organisation’s approved route for restricted documents. If an assessor can verify the claim from a public report or an authorised reference, there is usually no need to send the underlying identifiable records. A redacted extract should retain enough context for the panel to understand what it supports. Check the final file for names in comments, tracked changes, document properties or embedded images. Keep the unredacted version in its approved location.

Make a single evidence index in the order your claims appear. Record the display name, date, source, accessibility and whether a referee can corroborate it. Open every public link from a browser without your institutional login. If it requires access, supply the permitted alternative or explain the route available to the panel. Give the current date and versions to each referee so they respond to the same case.

Before submitting, ask a colleague to read a few claims and identify where the evidence is. Give them the criteria and see whether they can match each example to the right one. Check the person and project names, contribution dates, the membership or election grade, referee deadlines and any fees stated by the organisation. If you cannot establish an essential criterion, it may be useful to ask the scheme what alternative evidence it accepts before committing to that route.

Frequently asked questions

How many examples should a professional fellowship application include?

Follow the programme instructions. Three to five well-supported contributions can be a useful starting point for your working file. The application itself may ask for a different number or format. Choose examples that cover the assessment criteria and show the scope of your responsibility.

Can I use unpublished work?

Check the fellowship rules and your institution’s sharing requirements. A public summary, approved extract or referee confirmation may be possible. Explain the stage of the work and give only the details you have permission to share.

Can a team publication establish my contribution?

It can support it when there is a contributor statement or other evidence showing your role. Add the method, decision, deliverable or validation work you were responsible for so the assessor can distinguish it from the wider team output.

What can I use if I have little published evidence?

Look for approved protocols, versions of guides you created, participation records, public artefacts or a reference from the person who observed the work. Different routes give different weight to those records. Compare your evidence to the particular scheme before you apply.

If you are considering the society’s professional route, review Emergent Africa’s fellowship grades and application information. Ask the Secretariat to confirm current requirements, terms and fees. For recognition of a specific project or output, see the award nomination criteria.

Emergent Africa prepared this guide and checked the cited institutional sources. You can send a correction or a source update.

Published by Emergent Africa. Read Joseph Sunday’s author biography.