Writing a Clear Research Contribution Statement
Describe your own research contribution with precise scope and evidence, separating individual tasks and outputs from the wider team result.
A research contribution statement is a short, evidence-bound account of the part of a piece of work that a named person can defend: the question they addressed, what they personally did, how they did it, what output can be attributed to that work, and what may be said about it publicly. It is narrower than a project summary and more specific than a CV line. Its function is to let a reader check a claim without either inflating a team's achievement or disclosing material the author has no permission to share.
What the statement is for
Three documents are often confused. A CV entry records a position, a period and an output. An abstract describes the work as a whole. A contribution statement connects one person to one part of the work, using verbs the person can evidence and outputs that exist. It follows the work rather than the career, which is why the same researcher may need a different statement for each project.
That distinction matters most when the work was collaborative. A team report can carry a single institutional author while the underlying tasks were divided among several people. The statement's job is to describe that division honestly, not to redistribute credit in either direction. A reader who wants to assess the author's judgement needs to know which decisions were theirs.
The three questions the statement must settle
What did you do? Answer with verbs attached to tasks: designed, drafted, coded, interviewed, modelled, reviewed, coordinated. Each verb should survive a request for evidence — a work plan, a draft, a methods annex, a set of minutes.
What did others do? Name the division of labour without turning the statement into a team biography. It is enough to say that sampling and the quantitative analysis were led by colleagues, or that the evaluation was directed by another researcher. Readers do not need names; they need the boundary.
What can be mentioned publicly? This is a permissions question, not a stylistic one. Client identity, funder identity, unpublished findings, embargoed reports and personal data may each be subject to a different constraint. The statement should say what the author may disclose rather than leaving the reader to assume that everything described is public.
A five-part working format
The format below is a suggested working structure, not a validated instrument or an institutional requirement. It is designed so that each sentence can be checked against a record.
| Element | Question it answers | What to put | Risk if omitted |
|---|---|---|---|
| Question | What problem did the work address? | One or two sentences naming the issue, population or decision context | The statement substitutes the importance of the field for the actual question |
| Personal role | What did you do? | Verbs tied to tasks you performed, with the team context stated | Participation is written up as leadership |
| Method | How was the work done? | Design, data, sampling, analysis or process at a level a peer could assess | Methods used by colleagues appear to be shared |
| Attributable output | What exists because of this work? | Report section, dataset, model, tool, recommendation, with authorship or citation status | An organisation's publication is counted as personal output |
| Permission limits | What may be said publicly? | Named or unnamed client, embargo, anonymisation, disclosure rules | Internal circulation is mistaken for publication clearance |
The order is deliberate. The question comes first because a role without a task is difficult to assess; permissions come last because they govern how the earlier lines may be phrased. When the limits are restrictive, the earlier elements are rewritten rather than deleted.
Keeping your role distinct from the team's
The most common distortion is verb inflation. "Led" covers everything from chairing a workstream to attending meetings; "designed the methodology" can mean drafting an interview guide under someone else's direction. Neither is dishonest in every context, but both become misleading when the reader cannot tell which sense is meant.
A practical test is to ask what a co-author would say if shown the sentence. If the answer is "that overstates it", the verb needs narrowing. Useful distinctions include:
- Led: held the directing role and can name the decisions taken.
- Contributed to: performed defined tasks within a design set by others.
- Drafted: produced a text, section or instrument, subject to review.
- Co-authored: shared authorship, with the specific sections identifiable.
- Supported: provided input without responsibility for the output.
The same test applies in reverse. Some authors understate their role because a lead took the credit publicly. A contribution statement can record a substantive task without commenting on how the team presented itself elsewhere. Precision is not a complaint.
Deciding what can be mentioned publicly
Permission operates at several levels, and a statement may satisfy one while breaching another. The organisation that commissioned the work may be named in a CV but not in a public article. A report may be citable but not quotable. A dataset may be shareable in aggregate but not at case level. These are separate questions and need separate answers.
The UKRIO Code of Practice for Research covers research roles and dissemination responsibilities, including authorship and contributorship. This is research good-practice guidance, rather than permission to disclose client work. A contribution statement should identify the researcher's work and which output may be described publicly; the agreement and relevant permissions remain separate checks.
Where the constraint is unclear, write the statement at a level that does not depend on the answer, then seek written clarification before adding names or figures. Internal circulation is not clearance; nor is the absence of an express prohibition.
Worked example (fictional): revising an inflated team claim
The following example is invented to illustrate the method. It does not describe a real researcher, client or project.
An author drafted this line for a public profile:
Led a multi-site evaluation of a youth employment programme, designed the methodology, and produced recommendations adopted by participating regions.
Read against the five elements, the line fails in three places. "Led" conflates team membership with direction. "Designed the methodology" takes credit for a design finalised by the project lead. "Recommendations adopted" attributes a collective decision to one author and cannot be verified from any document the author holds.
A revised statement, written in the five-part format, might read:
- Question: whether the intake process of a youth employment programme affected completion rates across four sites.
- Personal role: drafted the interview guide and coding frame, conducted part of the fieldwork, and wrote the methods section of the final report.
- Method: semi-structured interviews with delivery staff, analysed thematically; sampling and the quantitative analysis were designed and led by colleagues.
- Attributable output: co-author of the methods chapter in the report delivered to the commissioning organisation; the coding frame is retained in the project archive.
- Permission limits: the commissioning organisation is not named; the report is not publicly released; findings may be described in general terms only after written clearance.
| Original claim | Revised wording | Reason for the change |
|---|---|---|
| "Led a multi-site evaluation" | Team member; specific tasks named | Direction sat with the project lead |
| "Designed the methodology" | Drafted the interview guide and coding frame | Design was set by others; the instruments were the author's work |
| "Recommendations adopted by participating regions" | Report delivered to the commissioning organisation; no adoption claim | Adoption is unverified and not the author's decision to report |
The revision is longer, but each line can be defended from a document. It also tells a reader more: drafting instruments and writing a methods section are assessable skills, whereas "led" without a scope is not.
Checking the statement before it circulates
Three checks catch most problems. First, underline every verb and confirm that each one matches a record. Second, read the statement as if a co-author were reviewing it, and remove any phrase that would require their silence to survive. Third, separate the private working version, which may name clients and internal documents, from the public version, which should contain only cleared material. Date both and keep the versions distinct, because permissions change and an old draft can outlive the clearance it relied on.