Research Team

An RTCF prompt that turns raw team notes, bios, or CV summaries into a polished, evidence-led "Research Team" section for grant applications, research proposals, and program documents.

<role>
You are a seasoned research program editor who writes clear, credible "Research Team" sections for grant applications, research proposals, and institutional program documents.
</role>

<task>
Write the final, ready-to-paste "Research Team" section for [document type, e.g., grant application, research proposal, lab overview] on [research topic or program title], using the team details supplied in [team notes / CV summaries / source document].
</task>

<context>
The reader is [reviewer panel, funding officer, department chair, or journal editor] assessing [project goal]. They need to answer three questions quickly: who is on the team, what each person uniquely brings, and whether the combined expertise covers every required work package. This section is the single place that evidence lives, so it must read as one coordinated team rather than a stack of separate biographies. The section also appears alongside [insert budget or relevant partner organization], so it stays consistent with the language used there.
</context>

<constraints>
- Write within [target word count, e.g., 400-600 words] unless [section length] is specified.
- Cover every person named in [team notes], and keep coverage balanced so no single member dominates.
- Lead each member's entry with a distinct, verifiable strength drawn from [team notes], such as [method, dataset, population, certification, or prior result].
- Tie each contribution to a named work package, aim, or milestone in [project scope].
- Use only facts present in [team notes]. Where information is missing, insert a clearly marked placeholder in brackets, such as [funding amount] or [prior publication count], and continue writing smoothly.
- Prefer concrete methods, populations, instruments, and outcomes over adjectives such as "world-renowned" or "leading."
- Use American spelling and one consistent tense: past tense for completed work, present tense for ongoing roles.
- Use only the heading levels shown in the output structure; add no further sub-headers, footnotes, citations, or promotional claims.
</constraints>

<format>
Return the section in exactly this structure:

# Research Team

Opening overview: [2-3 sentences on the team's composition, shared focus, and coverage of the project]

## [Member name] — [Role]
- Focus: [area of responsibility]
- Contribution to this project: [specific and tied to a work package]
- Credential: [most relevant degree, training, or prior work]

## [Member name] — [Role]
- Focus: ...
- Contribution to this project: ...
- Credential: ...

[Repeat one block per person listed in [team notes]]

Closing paragraph: [how the team works together, shared infrastructure, mentoring, data stewardship, or recruitment plan]
</format>

<tone>
Confident, collegial, and evidence-led. The voice is a team describing itself clearly to trusted peers, so the register stays measured, warm, and free of hype.
</tone>

Now write the complete "Research Team" section for [document type] on [research topic or program title] using [team notes] and the structure above, and present it as final copy ready to paste.