A research assistant contribution statement should name the project, explain the task you owned, describe what you did and point to a result someone can verify. State what your supervisor and collaborators were responsible for when that context matters. Use the level of detail appropriate to a CV, application or manuscript. A good statement lets the reader tell what you can do again on another project.
Many assistants contribute to a result without designing the whole study, leading the team or appearing as authors. They might maintain a dataset, validate an analytical output, run an agreed procedure or prepare figures that inform decisions. These contributions become clearer when the reader can see the actions and supporting evidence. Start with one output and work backwards to the decisions, materials and checks you were responsible for.

- Name the project
Give enough context for a reader to understand the assignment.
- Show your action
Specify your task, method and scope using a precise verb.
- Name the output
Describe what you delivered and how the team used it.
- Point to the record
Give an approved source or verifier and describe any limits.
Choose the right kind of statement
First ask who will read it and what they need to decide. A hiring panel looks for evidence that you can perform part of the advertised role. A referee may need dates and records that show what you did. A journal needs contributions described according to its policies and agreed with the team. One set of project notes can serve all three audiences if you adapt the length and level of detail.
| Where the statement goes | What the reader needs | What to keep in reserve |
|---|---|---|
| CV or résumé | A concise action and a concrete output or scope | Versions, logs and a fuller example for interviews |
| Supporting statement | A short story that shows a criterion in action | Supporting documents and relevant context |
| Portfolio | An approved example with your role and its limitations | Restricted material and permission records |
| Manuscript | Agreed contribution roles under the journal policy | Team confirmation and draft contributor records |
| Fellowship or award application | A contribution supported by evidence and appropriate attribution | An evidence index and named verifier |
For a job application, read the essential criteria before picking the project. A role requiring careful data handling may benefit from a brief account of how you found and logged discrepancies. A role seeking clear communication may benefit from a different example, such as a guide you wrote for other staff. Use the research assistant supporting statement guide if the application asks you to address several criteria.
Reconstruct the evidence before you write
Start with your project records. Look for an approved task brief, a dated version, code changes, a reference manager export, a data dictionary, a lab or field log, a meeting record or a published acknowledgement. Choose the records that show your action rather than those that only prove the project existed. A report with the team’s name may establish the output. A version history or supervisor account may establish which part of the report you produced.
Build a compact contribution record. Capture the project’s purpose in one sentence, the period you worked on it, what you were assigned, what you did, what changed and what the record can verify. Include the person or team who reviewed the work. If your role changed, separate the stages. You may have started by applying a protocol and then proposed a revision after seeing a repeated problem. Each stage gives the reader a different account of your skills.
| Record you can access | Claim it can help support | Limitation to check |
|---|---|---|
| Dated code commits or analysis notebooks | What you implemented, changed or tested | The project may use shared accounts or pair work |
| Approved protocol or change request | A procedure you drafted or a change you proposed | The person who approved the method may be someone else |
| Audit or query log | The kind and number of checks you ran | A flagged record may not be a confirmed error |
| Published output or repository | The resource that became available | The source may not identify your part without attribution |
| Supervisor or project lead reference | Your assigned responsibility and observed work | Ask only about activities the referee can speak to |
Where you can count work accurately, use the unit that best describes it. Records reviewed, sources screened, comparison sites, or analysis versions all mean different things. State whether you processed all items or a sample. If a team count appears in the headline, give your own share only when you can distinguish it. A documented scope does more work than an estimate presented as a fact.
Use a four-part sentence
The sentence can follow this order. Give the work context, choose an accurate action verb, name the output and point to the evidence or result. Add a team boundary if the same sentence could imply responsibility you did not hold.
For [project], I [action and scope] using [method or tool] and produced [output]. [Role or team] used or reviewed it for [purpose]. The contribution is recorded in [record], and [person or role] can confirm my responsibility.
Words such as cleaned, checked, extracted, reconciled, documented, implemented, visualised, tested and synthesised can make the action concrete. Use designed when you created the relevant method or design. Use led when the record supports your ownership of a defined part of the work. “Led weekly data-quality checks for the survey team” can be accurate when “led the study” would overstate the role. Name what you led.
Example for a data-quality role
This is a fictional example based on a small survey project. The assistant’s supervisor approved the criteria and made the final decision about which records to include.
I checked 180 survey records against agreed completeness rules, flagged 24 for supervisor review and documented the resolution of 18 flagged records in the shared query log. The project lead approved the final dataset.
That wording separates records reviewed, flagged and resolved. It avoids presenting 24 flags as confirmed errors or claiming an improvement rate without a comparable baseline. If the count came from a shared log, the applicant should confirm which entries they handled and how duplicates were excluded. For a CV version, the first sentence may be enough. In an interview, the person can explain how the check worked and what they escalated.
Example for a literature review
I screened titles and abstracts for the agreed date range and coded a first set of studies using the review team’s eligibility form. I recorded uncertain decisions for a second reviewer and updated the screening guide after the team approved two clarifications. The screening log and dated guide record my work.
The phrase “first set” should become a verified number if the applicant can support one. If screening required two independent reviewers, identify your responsibility and say how disagreements were handled. Avoid implying that you independently decided eligibility for the entire review when the team used a joint process.
Example for a research coordination role
I maintained the weekly handover record for a multi-site project and produced a checklist that helped coordinators report incomplete submissions in a consistent format. The coordinator approved the checklist, and its use is recorded in meeting notes for the following six weeks.
A coordination statement can explain a practical result without inventing an impact metric. If there is measured evidence of faster processing, add the comparison period, the definition of a completed submission and other relevant changes. Otherwise, say who used the checklist and what it was used for.
Match contribution roles when a publisher uses CRediT
The CRediT contributor role taxonomy gives teams a common vocabulary for describing work. Its roles include investigation, data curation, validation, software, visualisation and writing. Read the definitions before choosing terms. A person may contribute to more than one role. A team can also have several people contributing to the same role. Record the particular work behind the label and agree the wording with collaborators.
| If you did this work | CRediT term to discuss with the team | Point to verify |
|---|---|---|
| Maintained and annotated reusable research data | Data curation | Which data, documentation or version did you maintain? |
| Tested whether the results could be reproduced | Validation | Which result or procedure did you check and how? |
| Conducted work to collect evidence | Investigation | Which activities and data were part of your assignment? |
| Created or tested software used for the research | Software | Which code or component did you implement or test? |
| Prepared figures or visual presentation of the results | Visualisation | Which items and versions can the team identify? |
CRediT is a way to describe contributions. For an authorship decision, follow the journal and field’s requirements. The ICMJE recommendations illustrate that distinction in medical publishing. They address substantial contribution, intellectual input to the manuscript, final approval and accountability together. Discuss how the rules apply with the project lead before publication, and use the journal’s contributor statement. If a journal requests acknowledgement, check its instructions and ask permission before naming someone.
A contribution statement for a job application can still describe genuine work when the output is unpublished or your name does not appear on it. Say what stage the work reached. If a manuscript has been submitted, use the word submitted only if it has been. An article under review, an accepted manuscript and a published article are different statuses. Give the status that can be verified.
Adapt one contribution for three different audiences
Imagine that you worked with a supervisor to compare two data entry versions for a transport study. Your role was to write a validation script and report discrepancies. The team decided how to treat the records and used the report in its revision. Here are three ways to use the same underlying facts.
| Audience | Fictional wording |
|---|---|
| CV | Built a validation script to compare two versions of a transport study dataset, documented discrepancies and handed over the checks to the project lead. |
| Application statement | When two versions of the dataset produced different counts, I wrote a script to flag disagreements and created a query log the supervisor used to decide which records to retain. I documented the check so it could be repeated. |
| Contributor statement | [Initials] contributed to Software and Validation by implementing the version check and reviewing the discrepancy output. [Other contributor initials] approved the treatment of flagged records. |
The application version gives the reader a decision and a method. The CV version gives a quick account of the output. The publisher version assigns work to the contributors who did it. For academic or funding contexts that ask for a wider account of capability, UKRI’s Résumé for Research and Innovation guidance shows how to organise examples within a team narrative. The funding call determines how the format should be used.
Prepare an interview version that explains your decisions
Use the statement as a prompt for one example you can explain in about a minute. Tell the interviewer why the task mattered, how you went about it, what you did when a case was unclear and who approved the final result. An interviewer can then ask about the skill rather than guess from a label. Be ready to explain the limitations of the work and which parts could carry over into the advertised role.
In the survey example, one follow-up might be why 24 records were flagged but only 18 resolutions were documented at the point described. If the remaining six were waiting on clarification, say so. If you did not see what happened after the handover, explain the boundary. Keep evidence of the process and your role within the approved sharing arrangements. It is often possible to discuss the decision in general terms without bringing a copy of the underlying data.
Build a reference note a supervisor can recognise
Before you request a reference, send the supervisor a short factual note with the project, dates, task and two points relevant to the vacancy. Ask them to correct your summary if their records differ. If the position uses a formal application portal, give them the official instructions and deadline. A compact note can also help when the person supervised several assistants and needs to place your work within a specific project phase.
Show what you learned from a result that did not go as planned
Work that uncovered a weakness can demonstrate the same judgement as work that produced a successful result. Suppose a supervisor asked you to test whether two coding rules gave comparable classifications. You found that a small set of borderline records consistently produced different results. Describe how you documented those cases, who reviewed them and how the finding was used. The useful result is the evidence of disagreement and the decision it informed.
An example like this can be particularly relevant to roles requiring reproducible work. It lets you discuss how you handled exceptions and recorded the reasoning for someone else. Use the language of the vacancy where it fits and retain the actual project terms in your supporting evidence.
Check permissions and prepare for follow-up
Use public or approved evidence. A hiring manager does not need a raw data file to understand that you checked a dataset. A redacted example, public repository or referee’s confirmation can support the claim. Ask the appropriate person before you share code, interview excerpts, internal correspondence or material a participant might recognise. Keep original documents in their approved locations.
Do a final fact check against your CV and the project records. Verify the title, dates and contributor names. Read each verb from the supervisor’s point of view. If someone might reasonably understand it to mean a wider role, name the task you owned. If you claim an outcome, ask what evidence would allow an interviewer to reproduce or confirm the comparison. Prepare a sentence explaining what you would do differently on a similar project.
If your only research project is your degree dissertation, the final-year project CV guide can help you turn the record into a strong evidence entry. If you are collecting evidence across several projects for recognition, the professional fellowship evidence checklist explains how to match contributions to criteria.
Frequently asked questions
How long should a research assistant contribution statement be?
One to three sentences can work for a CV or short supporting statement. A job application may ask for a longer answer about a specific criterion. For a manuscript, follow the journal’s format and the team’s agreed wording.
Can I describe a contribution if I was not an author?
Yes. Give an accurate account of the work you did and how it is documented. Follow permission and attribution rules and use your genuine role. Acknowledgement, authorship and employment are distinct forms of recognition.
What if I cannot verify how many records I handled?
Use the closest confirmed scope. Describe the type of records, task, period or output. A reviewer can assess a claim that you applied a specified procedure to one project phase even if the exact record count is unavailable.
Should I write in the first person?
A supporting statement commonly uses “I” to show personal responsibility. A CV may start each entry with a verb. A journal may use initials or a named roles format. Follow the audience’s instructions and keep the same facts across formats.
Browse more Research Assistant Careers guides or check Emergent Africa’s membership eligibility if you are looking for a professional community while developing your research career.
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.