Researcher and academic portfolio guide: research, teaching and keeping it current

Academic careers already come with a long document: the CV. It records every paper, grant, talk and committee, and it's essential. But a CV is built for completeness, not for understanding. A search committee, a potential collaborator, a journalist or a prospective student usually wants to know something simpler first: what do you study, why does it matter, and what have you found? A portfolio site answers those questions in a few minutes, then points to the full record. This guide covers how it differs from a CV, how to write a research statement people will actually read, and how to present publications, teaching, funding, talks, data and code.

How a portfolio differs from a CV

Think of the CV as the archive and the portfolio as the guided tour. The CV lists everything in a standard order. The portfolio selects, explains and links.

• The CV is complete; the portfolio is selective. You might list forty publications on a CV and highlight five on your site.
• The CV is formal; the portfolio can explain. You can say in plain words why a project matters and what you found.
• The CV is static; the portfolio is linked. Papers, preprints, datasets, code, slides and recordings can all be one click away.
• The CV has one audience; the portfolio has several. Committees, collaborators, students, funders and the public all land on the same page.

Keep your CV available as a downloadable file and link it clearly. For the general difference between the two kinds of document, see resume vs. portfolio.

Who reads an academic portfolio

Before writing, consider your readers:

• Hiring committees want your research direction, track record, teaching and fit with their department.
• Collaborators want to know your methods, data and what you're working on now.
• Prospective students and postdocs want to know what joining your group would be like.
• Journalists and the public want a plain-language explanation.

Your homepage should serve all of them with a short introduction. For example: "I'm an ecologist studying how urban heat affects pollinators. My group combines field surveys with long-term sensor data, and I teach courses in field methods and statistics."

Writing a research statement for the web

A formal research statement for a job application can run to several pages. The version on your site should be much shorter, around 300 to 600 words, and readable by someone outside your field.

A simple structure

1. The big question your work addresses, in one or two sentences.
2. Why it matters, to your field and beyond.
3. Your approach: methods, data, collaborations.
4. What you've found so far, in plain language.
5. Where you're going next.

Before and after

Before:

"My research interrogates the multi-scalar dynamics of socio-ecological systems through an interdisciplinary lens, leveraging novel methodologies to advance understanding of complex adaptive phenomena."

After:

"I study why some small fisheries recover after a collapse and others don't. I combine catch records going back several decades with interviews with fishing communities, looking for the local rules and habits that help a fishery bounce back. So far, the strongest pattern is that communities with informal agreements about where and when to fish recover faster than those relying only on official quotas. Next, I'm testing whether that pattern holds in other regions."

The second version is concrete, readable and still serious. A specialist can find the detail in your papers; your site's job is to make them want to.

Write the first paragraph for an intelligent reader outside your field. If a colleague in another department couldn't explain your work after reading it, simplify.

Publications

Don't reproduce your entire publication list on the homepage. Instead:

• Highlight a handful of key papers, perhaps three to eight, each with a one or two sentence plain-language summary of what it found.
• Give full citations in your field's usual style, with links to the published version and an open-access version where you can share one.
• Mark your role where your field's author order doesn't make it obvious.
• Link to a complete list, through your CV or a researcher profile, so you don't have to maintain two full lists.
• Include preprints and work under review, clearly labeled as such.

Respect publishers' rules on sharing versions of your papers. Many allow an accepted manuscript to be posted after a certain period; check the agreement you signed.

Teaching

Teaching often gets one line on an academic site, but committees at many institutions care about it a great deal. A short teaching section can include:

• Courses you've taught, with level, size and your role.
• A brief teaching philosophy, a paragraph tied to what you actually do in class. The approach in the teacher portfolio guide adapts well to university teaching.
• Sample materials, such as a syllabus, an assignment you designed or an open resource you made.
• Supervision and mentoring: students supervised, at what level, and where they went next, with their permission.
• Evidence of effectiveness, such as a peer observation summary or a course change you made in response to feedback. Share only what you have permission to share, and never publish individual student comments without consent.

Grants and funding

Funding is part of your track record, but you don't need to publish amounts. Describe grants in general terms:

• The funder and type of award.
• The project title or topic.
• Your role, such as lead investigator or co-investigator.
• The period.

For example: "Lead investigator on a three-year national research council project on coastal flood forecasting." That's enough for most readers. Full details belong in the CV and formal applications.

Talks, outreach and media

Talks show that you can communicate, and recordings let people see it. List selected invited talks, keynotes and conference presentations, and link slides or recordings where you can. Outreach, such as public lectures, school visits, podcasts or articles for general audiences, deserves a mention too; many funders and institutions value it. Keep this list selected rather than exhaustive.

Datasets, code and other outputs

Research outputs aren't only papers. Increasingly, datasets, software, protocols and models are recognized contributions in their own right. If you've produced them:

• List them with links to the repository where they're archived, ideally with a persistent identifier.
• Explain briefly what each is for and who might use it.
• Note how to cite them.
• Keep restricted data restricted. Never post data containing personal or sensitive information, or anything covered by ethics approvals, data agreements or confidentiality terms. Link to the controlled-access route instead.

If you write a lot of code, the software developer portfolio guide has advice on presenting repositories, and the data analyst portfolio guide covers presenting analyses clearly.

For early-career researchers

PhD students and postdocs often feel they have too little to show. You likely have more than you think: a thesis summary, conference posters, a methods tutorial, teaching assistant roles, a dataset, a reading group you ran. Write a clear research statement about your current project and where you want to take it. Committees hiring early-career researchers are often looking for direction and potential as much as a long list.

Keeping it current

An academic site with a "recent news" section last updated three years ago does more harm than having no news section at all. A few habits help:

• Avoid sections that need constant updates unless you'll keep them up.
• Review the site each term or when something significant happens: a new paper, grant, role or student.
• Update your research statement when your focus shifts.
• Keep your CV file current, since many readers will download it.
• Check your links; publisher and repository addresses change.

Our guide to keeping your portfolio up to date has a simple routine you can follow.

Putting it together

A strong academic portfolio is a guided tour of your work. Open with a plain-language introduction, write a short research statement anyone curious could follow, and highlight a few key publications with a sentence on why each matters. Add teaching, funding described generally, talks and the data and code that make your work reusable, then link the full CV for anyone who wants the complete record. Keep it current, and it will do quiet work for you long after you've published it.