IB DP Mini-Guides: How to Build a “Core Components” Folder Structure That Works

IB DP Mini-Guide: Build a Core Components Folder Structure That Works

Imagine opening your laptop during a supervisor meeting and finding every draft, comment and piece of evidence lined up and ready — not scattered across downloads, email, or ten versions of “final_final.” A reliable folder structure is less about rigidity and more about reducing friction: it frees you to focus on argument, analysis and reflection instead of hunting for files. This guide walks you through a friendly, practical approach to organizing the DP core — IA work, your Extended Essay, and Theory of Knowledge materials — with clear examples, naming rules and checklists you can adapt to your school’s workflow.

Why folder structure matters (and what good organization actually does)

Good folder organization does three concrete things for you: it protects time, protects marks, and protects your sanity. Time is saved because you aren’t digging through old drafts when a deadline looms; marks are protected because supervisors and moderators can trace your work and feedback quickly; and sanity is preserved because the cognitive load of small admin tasks is removed so you can think more clearly.

For core DP components — IA, EE, TOK — the stakes are higher than for a typical homework folder. Supervisors expect drafts and evidence in reasonable order, examiners may request specific artifacts, and you will need to show evolution: planning notes, supervisor comments, formative feedback, and final drafts. A predictable structure helps you produce that story of development without panic.

Principles to follow

• Consistency: Use the same top-level layout for each component so nothing gets missed.
• Traceability: Keep a clear record of versions with dates and short notes on what changed.
• Clarity: Use human-readable names so you and your supervisor don’t have to decode file names.
• Redundancy: Back up in at least two places (cloud + local) and keep a simple change log.
• Privacy and access: Share only what your supervisor needs and keep personal drafts private until appropriate.

Top-level layout: a simple, scalable root

Start with one root folder called Core-Components (or Core_Components). Inside it, create one folder for each major area: EE, TOK, IA, and optionally CAS evidence if you prefer to keep everything in one place. Within each of those, use the same subfolder logic: 01_Admin, 02_Drafts, 03_Feedback, 04_Final, 05_Evidence. The numeric prefix keeps items in the order you expect.

Example top-level tree (readable and predictable)

• Core-Components/
  • EE/
    • 01_Admin
    • 02_Drafts
    • 03_Feedback
    • 04_Final
    • 05_ResearchNotes
  • TOK/
    • 01_Admin
    • 02_Presentations
    • 03_Essays
    • 04_Feedback
    • 05_Resources
  • IA/
    • 01_Admin
    • 02_Drafts
    • 03_DataAndEvidence
    • 04_Feedback
    • 05_Final
  • CAS_Evidence/ (optional)
    • 01_Logs
    • 02_Reflections
    • 03_Forms

This structure is intentionally simple: numbers keep the order clear, short names keep path lengths manageable, and separate folders for feedback and drafts make it quick to locate supervisor comments when you’re revising.

Naming conventions and version control that actually make sense

Pick one clear filename pattern and use it everywhere. A good pattern answers four questions at a glance: What is the document? Who made it? When was it last updated? Which version is it? Here’s a compact, adaptable pattern you can use and modify for different subjects:

• Pattern: [SUBJ]_[TYPE]_[STUDENTINITIALS]_[YYYYMMDD]_[v01].ext
• Example (EE draft): EE_Draft_JD_YYYYMMDD_v01.docx
• Example (IA data): BIO_IAData_JD_YYYYMMDD_v02.xlsx

Notes:

• Use subject codes or short names (EE, TOK, BIO, ENG) so the files sort logically.
• Use an ISO-style date placeholder (YYYYMMDD) so chronological sorting works; you can update it to the actual date when you save.
• Keep the version counter simple: v01, v02. Increment when you make substantive changes; minor edits can remain the same version if you keep a change log file.

Why separate ‘Drafts’ from ‘Feedback’?

Files in a Drafts folder are your working copies. Files in Feedback should be copies that include supervisor comments, grading rubrics, or written notes. Keeping feedback copies in a dedicated folder prevents accidental overwriting of a working draft and preserves the timeline of comments — which can be vital if you need to show the development of your ideas to a moderator or during supervision.

Practical workflows for IA, EE and TOK — tailored advice

Each core component has its own rhythm. The folder structure above adapts to all three, but here are specific habits that make a real difference.

Internal Assessments (IA): evidence-first organization

• Keep raw data and evidence in IA/03_DataAndEvidence with clear metadata. A single row describing each file (what it is, date, short note on how it was collected) saves time when you’re writing up methodology and analysis.
• When supervisors annotate digital files, save a PDF copy of the annotated version in IA/04_Feedback so you keep a clean copy of the comments and your working draft separate.
• For lab-based or media-heavy IAs, include a README.txt in IA/03_DataAndEvidence explaining any abbreviations or instrument settings so a moderator can follow your process.
• If you use a code notebook (e.g., Python analysis), keep the source notebook, an exported PDF or HTML of the output, and a short changelog describing which version produced which figure.

If you sometimes need focused, personalized feedback on method or analysis, Sparkl can help with 1-on-1 guidance and tailored study plans that clarify next steps in revision.

Extended Essay (EE): a development story, not a single file

• Treat the EE folder like a research archive. Keep proposals and supervisor meeting notes in EE/01_Admin so you can trace approvals and topic evolution.
• Store incremental drafts in EE/02_Drafts and move the “final” submitted PDF to EE/04_Final. Keep a short ResearchLog.txt that notes major changes between versions and why you made them.
• Put annotated bibliographies, interview transcripts, and raw archival scans into EE/05_ResearchNotes with clear file names (e.g., Interview_Lastname_Firstname_YYYYMMDD.pdf).
• If your EE includes images, permissions or ethical consent, place signed forms in EE/01_Admin so evidence of permission is accessible during moderation.

When you’re juggling supervisor meetings and draft feedback it helps to have a single coach who understands the EE rhythm. Sparkl‘s tailored tutors and AI-driven insights can make planning sessions more efficient and flag weak evidence chains early, though you should always follow your supervisor’s advice first.

Theory of Knowledge (TOK): reflections, presentations and evidence

• Split TOK into Essay and Presentation streams: TOK/03_Essays and TOK/02_Presentations. Presentations often have recorded materials, slides and peer feedback that need an evidence folder.
• Keep a TOK_Concepts.pdf or notes file that ties presentation themes and essay arguments to key TOK concepts and real-life examples; this makes revision for the essay far easier.
• Keep meeting notes with your TOK teacher in TOK/01_Admin because your approach to the essay question and feedback timeline is important to track.

Practical tips for collaboration with supervisors and maintainers

Make it easy for supervisors to give feedback by doing three small things every time you share a draft:

• Provide the filename pattern so they know which version it is (e.g., EE_Draft_JD_YYYYMMDD_v03).
• Attach a 1–2 line summary of what you specifically want feedback on at the top of the document or in the shared message.
• Save a copy of their annotated version in your Feedback folder so nothing is lost when comments are accepted and overwritten.

Consider a shared supervision log (a simple shared document) where you paste dates, brief meeting notes and agreed next steps. This lives in each component’s 01_Admin folder and provides a quick reference if either of you needs to review the supervision history.

Digital tools, export formats and backups

A folder structure is only as safe as its backups and export strategy. Pick a primary cloud (school-managed or personal) and a secondary backup (external drive or another cloud). Export final files as PDFs for submission-ready versions and keep editable files separately.

• Primary working copies: native editable formats (.docx, .xlsx, .ipynb).
• Submitted or archival copies: PDF (flattened), with file name that includes the word ‘Final’ or ‘Submitted’.
• Media: keep both source files (e.g., raw audio) and compressed delivery files (e.g., MP3 or MP4) with clear naming.

For version control beyond simple v01/v02 naming, a change log in each component root — a short text file with date, time, change summary, and file referenced — can be a lifesaver. It’s low-tech and robust.

Security and privacy

Be mindful when collaborating in shared folders. Only give edit access to people who need it; otherwise use view-only links. For sensitive interview data or personal information, keep a separate restricted folder and anonymize files used in drafts or presentations if required by your school’s ethics guidelines.

Sample checkpoint table: what to track and when

Quick practical checklists

Daily / weekly tidy-up

• Move any completed drafts into the Drafts folder and apply the correct filename pattern.
• Save annotated feedback PDFs into the Feedback folder immediately after a meeting.
• Update the component’s supervision log with date and 2–3 agreed next steps.

Before any submission

• Export a flattened PDF and place it in the Final folder with a clear filename including ‘Final’ or ‘Submitted’.
• Check that all raw data and required evidence is in the Evidence or ResearchNotes folder and that any permissions are present in Admin.
• Create a single zipped archive of the final folder as an extra backup if the submission rules allow it.

Examples and small adaptations for different students

If you’re a student who works better visually, add color-coded tags or emojis in file names (where allowed) or use folder color features from your cloud provider. If you collaborate frequently (e.g., group IA data collection), create a shared ‘Team-Data’ folder and keep a readme that explains who added what and when.

For students who like strict tracking, add a tiny spreadsheet in each component called VersionLog.xlsx with four columns: filename, date, short change note, owner. It takes five minutes to maintain and can save hours later.

Common mistakes to avoid

• Never rely on email alone to keep final copies; move attachments into the appropriate folder as soon as you receive them.
• Avoid ambiguous file names like ‘Final.docx’ or ‘EssayVersion3.docx’ — be explicit about subject and date.
• Don’t overwrite feedback files: save a copy and then incorporate comments into a new draft with an incremented version number.

Bringing it all together: a tiny roadmap you can implement today

Spend one hour this week to create Core-Components and set up the top-level folders described here. In that hour do three things: create the folder tree; create one example file in each ‘Admin’ folder that explains the naming convention; and create a VersionLog.txt or .xlsx in each component with one row filled in. That small investment will remove a lot of future friction.

Students sometimes ask whether they should use external coaching when organizing their work. If you want regular one-to-one help that blends structure with academic feedback, platforms like Sparkl can offer personalized tutoring, tailored study plans, and tools to track progress alongside your existing supervisor guidance. Keep in mind that any external support should complement — not replace — your supervisor’s direction and your school’s policies.

Final thoughts

A clear, consistent folder strategy is a small habit that compounds into major gains: more transparent supervision, easier final submissions, and less last-minute stress during assessment windows. Whether you’re polishing an IA, polishing an EE draft, or rehearsing TOK presentations, a predictable structure tells the story of your learning in a way that teachers and examiners can easily follow.

Organize once, follow the system, and let your ideas get the attention they deserve.