<\/p>\nImagine one well-oiled research ecosystem that you open each morning: a single folder, clear naming rules, a research diary, a central literature list, and a living document where your IA data, your EE argument, and your TOK reflections all meet and feed each other. For many IB students the three big beasts \u2014 Internal Assessments (IA), the Extended Essay (EE), and Theory of Knowledge (TOK) \u2014 feel like separate projects with competing deadlines. But they don\u2019t have to be. With a single, intentional research system you’ll build coherence across tasks, reduce duplication, and produce stronger evidence of thinking and reflection.<\/p>\n
<\/p>\n
At heart, the IB asks you to demonstrate inquiry, analysis, and reflection. Those are the same cognitive moves whether you\u2019re measuring reaction rates in a chemistry IA, writing an EE in history, or exploring knowledge claims in TOK. By designing one research workflow you get three big benefits: you save time, you create richer evidence of learning, and you improve the quality of reflection \u2014 especially when TOK thinking is woven into empirical work.<\/p>\n
Here\u2019s a quick list of advantages that students report when they adopt a single system:<\/p>\n
The structure below is deliberately simple so it\u2019s usable on paper or inside your favorite cloud drive. You can scale it to any subject and any research method.<\/p>\n
Adopt a naming rule like: Subject_Component_Version_Date (for example: Chem_IA_v02_2023-11-15 or Hist_EE_draft3_2023-12-01). Use ISO-style dates (YYYY-MM-DD) so files sort chronologically. Each draft should include a one-line changelog at the top so you and your supervisor can see what improved and why.<\/p>\n
To unify practices, think in phases rather than by assessment: question & focus, research & sources, methods & evidence, analysis & argument, reflection & implications, and presentation. The table below shows what each phase looks like in the three components.<\/p>\n
| Research phase<\/th>\n | Internal Assessment (IA)<\/th>\n | Extended Essay (EE)<\/th>\n | Theory of Knowledge (TOK)<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|---|
| Question & focus<\/td>\n | Clear, focused investigable question tied to syllabus.<\/td>\n | Open, original research question that supports sustained argument.<\/td>\n | Knowledge question or claim with scope for analysis.<\/td>\n<\/tr>\n |
| Research & sources<\/td>\n | Short literature\/aperiodic sources and precise method citations.<\/td>\n | Extensive bibliography, primary & secondary sources.<\/td>\n | Examples, thought experiments, and interdisciplinary sources.<\/td>\n<\/tr>\n |
| Methods & evidence<\/td>\n | Experimental or observational design, clear data.<\/td>\n | Methodological justification, triangulation where appropriate.<\/td>\n | Analysis of knowledge methods, reliability, and bias.<\/td>\n<\/tr>\n |
| Analysis & argument<\/td>\n | Data interpretation linked to syllabus criteria.<\/td>\n | Structured argument, analysis, and critical evaluation.<\/td>\n | Evaluation of knowledge claims, counterclaims, and implications.<\/td>\n<\/tr>\n |
| Reflection & supervision<\/td>\n | Reflective commentary and supervisor feedback record.<\/td>\n | Reflection on process, limitations, and further questions.<\/td>\n | Meta-level reflection on how knowledge is constructed.<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\nHow to design the single workflow \u2014 a practical blueprint<\/h2>\nStart small: build the skeleton and test it on one IA task before committing to your EE. Here\u2019s a step-by-step blueprint you can adopt immediately.<\/p>\n 1. Create the master folder and subfolders<\/h3>\n2. Start a research diary from day one<\/h3>\nYour diary is the spine of the system. Make an entry every time you switch tasks: what you did, what you found, what the next step is, and a short TOK-style reflection about the implications for knowledge. These reflections turn everyday notes into powerful assessment evidence.<\/p>\n 3. Use a universal bibliography<\/h3>\nKeep one master bibliography. Tag each source for IA, EE and TOK references. Make short annotations about why each source matters and include exact quotes with page numbers where possible. This saves time and improves citation accuracy across all components.<\/p>\n 4. Keep raw data raw and analysis separate<\/h3>\nNever overwrite original data. Keep a folder for raw files and a separate analysis folder where you import copies to work on. Record transformations and calculations so you can justify your analysis choices in both IA and EE write-ups.<\/p>\n 5. Make the supervisor log routine<\/h3>\nTreat supervisor meetings as formal evidence. Keep a one-page note for each meeting: date, participants, agenda, key advice, and an action list. Link these notes to the diary entries that follow so assessors can see how feedback shaped your work.<\/p>\n Connect TOK meaningfully \u2014 not as an afterthought<\/h2>\nTOK is an opportunity to interrogate the knowledge assumptions behind your IA and EE. When you adopt one system, TOK sections can be integrated as short reflective nodes that live beside each major analysis. For instance, after a data analysis entry in your diary, add a TOK reflection: what assumptions about measurement, objectivity, or generalization were involved? How might different methodologies yield different knowledge claims?<\/p>\n Integrating TOK like this does three things: it makes reflection habitual, it supplies concrete TOK examples for your presentation or essay, and it strengthens the evaluative language in your EE and IA write-ups.<\/p>\n Templates that actually get used<\/h2>\nStudents avoid templates that are clunky. Keep your templates short and task-focused. Here are three to start with:<\/p>\n
|
<\/p>\n