How to organise research papers for CPD

You do not need to reorganise every paper you have saved. Start with a question you are working on now and the reading that could help you explore it. Aim to keep three things easy to find:

• The paper and enough source detail to identify it.
• A short note explaining why it matters to your work.
• Any question or next step you want to return to.

Throughout this guide, we follow a fictional team leader who gives short teaching sessions at work. Colleagues usually say the sessions were useful, but the comments rarely explain what helped or what was unclear. The team leader saves a paper about feedback questions to explore this. The paper and learning note are invented to demonstrate the workflow.

Use folders in your existing file storage or a reading list in the system you already use. A small collection can work well with a simple arrangement:

• To read: papers you want to consider, with a brief reminder of why you saved them.
• A few topic or project folders: useful sources grouped under names you would look for, such as Teaching and feedback or Supervision.
• A note beside the source: your question, learning and a reference to the file. This could be a document, a reading-list entry or a linked CPD record.

For the team leader, the paper starts in To read with the note: “Could this help me ask for more useful feedback after teaching?” Once read, it belongs in Teaching and feedback if it is worth keeping. Saving it for later does not require a CPD record straight away. You can also decide a paper is not relevant and take it off your reading list.

Name saved files consistently, for example Author – year – short topic. Keep the full title, authors, publication year and a DOI or source link in your note. If a paper relates to several topics, choose one main home and refer to that file from the other notes instead of keeping several copies that may drift apart.

Store copies you have permission to retain. Where a copy is not available to keep, record the citation and source link so you can find it again through the publisher or your library.

A highlighted sentence shows what caught your attention. A few words of your own explain why. Alongside the source details, capture the parts of these prompts that are useful:

• My question: what was I trying to understand?
• What the paper says: the relevant finding or argument, with a page, section or table reference so I can check it again.
• Limitations and fit: what about the methods, participants or setting affects how I interpret it?
• My learning: what changed, was reinforced or became less certain in my understanding?
• What follows, if anything: a question to explore, something to try or a reason to revisit the source.

Keep quotations clearly marked and separate from your interpretation. For a more structured examination of a study, choose a CASP critical appraisal checklist that fits its study type.

A short note may be enough. You do not need a long reflection or a change to make after every paper. If reading leads to a deeper discussion, the Rolfe journal-club worked example shows one way to explore it further.

The team leader has now read the fictional paper and wants to keep it for their next teaching session. Here is how the file and note could fit together.

A source they can find again

They place the PDF in Teaching and feedback and give the accompanying note a title they will recognise: Getting more specific feedback after teaching. At the top, they record the paper's full citation, its filename and the section comparing general satisfaction questions with questions about a particular explanation. For a real paper, these details would come from the source itself.

A short note in their own words

“I wanted to understand why feedback after my teaching is usually positive but rarely specific. The comparison between question types made me think about what I am actually asking colleagues to comment on. I have been treating ‘that was useful’ as feedback on my explanation, although it tells me little about which parts were clear.

“The paper concerns a training course, while I give short workplace updates. I need to consider that difference before applying its ideas. My learning is to separate an overall impression of the session from feedback that could help me improve a particular explanation.

“At my next session, I will ask for one point that was clear and one that needs more explanation. I will then consider whether the responses give me something useful to work with. I do not yet know whether this will help.”

A clear reason to return

They finish the note with Revisit when preparing the next teaching session. The question, the source and the proposed experiment are now together. When they return, they can recover their reasoning without rereading the whole paper or searching through several folders.

If the team leader uses HandyCPD, the Evidence Library can hold the paper, with their learning captured in a CPD record linked to that file:

1. Store the paper. Upload the permitted PDF to the Library and place it in a Teaching and feedback folder.
2. Describe the reading. In Plant a Seed, add when they read it, the time spent learning and their own note about the feedback question.
3. Connect the source. Choose From Library and select the saved paper. Include its citation and the relevant section in the activity notes.
4. Review and file. Check the suggested details and summary against their notes. The proposed feedback question should remain a plan, with no results claimed yet.

When preparing the next session, they can return to the record for their question and reasoning, with the supporting paper attached. The file supplies the source; their note explains what the reading contributed.

Check the attachment's reading status before relying on a draft. Some files cannot supply usable text, and long papers may be only partly read. Include the detail that matters in your own notes; our guide to what HandyCPD can read explains the limits.

Keep the original paper available and check important statements against it. In the teaching example, a summary might help locate the discussion of feedback questions, but the team leader still needs to examine the study's limits and explain their own learning. Our NotebookLM research workflow shows how to explore sources and manually bring your learning notes into HandyCPD.

Before their next teaching session, the team leader can use the note to prepare the feedback question. Afterwards, they can record what the responses actually helped them understand, including anything still unclear. A follow-up note or activity can refer back to the original reading without rewriting it or duplicating the PDF.

Use your next CPD review, supervision discussion or relevant task as a chance to revisit open questions. Check your To read list too: keep what still interests you and remove items that no longer serve a purpose. You do not have to finish every paper you save.

The method is useful if you can find both the source and your reason for keeping it. For the wider workflow, see how to organise CPD records digitally.