# How to Set Up Project-Based Research Note Folders: A Step-by-Step Guide ## Quick Answer - Create a project-based research note folder system using a consistent hierarchy of Project, Subproject, and Note Type to keep active work separated from archived material. - Name every folder with a date prefix and descriptive project code so files sort chronologically and remain identifiable across multiple concurrent projects. - A folder structure alone does not guarantee data integrity, so pair it with a written naming convention and a review schedule tied to your institution's data management expectations. ## Why Project-Based Research Note Folders Fail Without a Structure Researchers often start with a simple desktop folder or a cloud drive and add files as they go. Within weeks, the same project has notes scattered across multiple locations, duplicate versions of the same file, and no clear way to distinguish raw observations from analyzed results. The problem is not a lack of effort. It is the absence of a folder architecture that matches how research work actually progresses. A project-based research note folder system solves this by creating a fixed container for every piece of information tied to a specific research effort. Instead of asking where a file belongs, you ask which project it belongs to and what stage of work it represents. This shifts the cognitive load from remembering locations to following a repeatable rule. The National Library of Medicine hosts research methods resources that emphasize the importance of systematic approaches to managing the research process, including documentation practices that support reproducibility and transparency. A folder structure is a practical expression of that principle. It creates the physical and digital conditions for orderly record keeping before you need to retrieve a specific observation months later. For researchers who manage multiple projects simultaneously, the stakes are higher. Mixing notes between projects can lead to misattributed data, lost context, and errors in reporting. The Committee on Publication Ethics lists data handling and integrity among its core practices for responsible research conduct. A clear folder system is one concrete way to support that expectation at the individual researcher level. ## At a Glance: Core Folder Hierarchy | Folder Level | Purpose | Example Name | Retention Rule | | --- | --- | --- | --- | | Project Root | Contains everything for one research effort | 2025-06_antibiotic-resistance-survey | Keep active until project closes | | Subproject | Separates distinct workstreams within a project | 01_literature-review | Archive when subproject completes | | Note Type | Distinguishes raw notes from processed outputs | 03_analysis-notes | Review quarterly for accuracy | | Archive | Stores completed or inactive project material | _archive_2024 | Retain per institutional policy | The hierarchy works because each level answers a specific question. The project root answers which effort the material belongs to. The subproject answers which phase of work the material supports. The note type answers what kind of record the file represents. The archive answers whether the material is still active. ## Core Principles of Project-Based Note Organization ### Separation of Active and Inactive Material Active projects need fast access to current notes. Inactive projects need safe storage without cluttering the working space. A folder system that does not distinguish between these two states forces you to wade through old material every time you open your research directory. Create a clear boundary between active project folders and an archive folder. Move completed projects to the archive instead of leaving them in the main working area. This keeps your active view focused and reduces the chance of editing an outdated file. ### Consistent Naming Conventions A naming convention is the rule that makes your folder system predictable. Without one, you rely on memory and habit, which vary by day and by person. With one, you can locate any file by applying the same logic every time. Use a date prefix in ISO format (YYYY-MM) followed by a short project code and a descriptive name. For example, `2025-06_antibiotic-resistance_sampling-log`. The date prefix ensures chronological sorting. The project code ensures unique identification. The descriptive name ensures human readability. ### Fixed Note Type Categories Research notes are not uniform. Raw observations differ from meeting notes, which differ from analysis logs. A folder system that treats all notes the same way makes it difficult to find a specific type of record when you need it. Define a fixed set of note type categories and apply them consistently across all projects. Common categories include literature notes, experimental logs, analysis notes, meeting notes, and administrative records. The exact categories depend on your field, but the principle is the same: each category has a defined purpose and a defined location. ## Practical Workflow for Setting Up Your Folder System ### Step 1: Define Your Project Boundaries Before creating folders, decide what counts as a project. A project is a research effort with a defined question, a defined scope, and a defined endpoint. A literature review for one paper is a project. A multi-year laboratory study is a project. A single experiment within that study is a subproject. Write down the projects you currently have active. Assign each one a short code that you will use in folder names. Keep the code to three to five characters to avoid unwieldy file paths. ### Step 2: Create the Project Root Folder Create one root folder for each active project. Use the naming convention you defined in the previous step. Place all project folders in a single parent directory that you use exclusively for research work. The project root folder is the container for everything related to that project. It should not contain files from other projects. If a file relates to two projects, decide which project owns it and place a reference in the other project folder pointing to the original location. ### Step 3: Add Subproject Folders Within each project root, create subproject folders for distinct workstreams. Use a numeric prefix to control the display order. For example, `01_literature-review`, `02_data-collection`, `03_analysis`, `04_writing`. Subproject folders help you separate work that happens at different times and with different purposes. A literature review folder contains notes from reading. A data collection folder contains raw observations. An analysis folder contains processed results. This separation prevents raw data from being confused with interpreted findings. ### Step 4: Create Note Type Subfolders Within each subproject folder, create note type subfolders. These are the finest level of organization and the most important for retrieval. Use consistent names across all projects so you always know where a given type of note lives. A typical structure within a subproject folder might include `raw-notes`, `processed-notes`, `meeting-notes`, and `admin`. The raw notes folder holds observations as they were recorded. The processed notes folder holds cleaned or analyzed versions. The meeting notes folder holds records of discussions and decisions. The admin folder holds correspondence, consent forms, and other administrative material. ### Step 5: Establish an Archive Folder Create a single archive folder at the top level of your research directory. When a project ends, move the entire project root folder into the archive. Do not delete it unless your institution's policy requires destruction after a specified retention period. The National Institutes of Health data management and sharing policy describes expectations for preserving and sharing research data. While the policy applies to NIH-funded research, the underlying principle of retaining data for verification and reuse applies broadly. An archive folder is the practical mechanism for honoring that principle at the individual level. ## Records and Measurements: What to Track in Your Note Folders ### File Naming Records Every file you create should follow a naming convention that includes the date, the project code, and a descriptive element. Track your adherence to this convention by reviewing your folder contents periodically. If you find files that do not follow the convention, rename them immediately instead of waiting for a cleanup session. ### Version Control Notes Research notes evolve. A raw observation becomes a cleaned data point, which becomes an analyzed result. Each stage should be a separate file with a version indicator in the name. Use `v01`, `v02`, and so on, or use the date in the file name to distinguish versions. The Committee on Publication Ethics core practices emphasize the importance of data integrity and accurate record keeping. Version control is a practical way to demonstrate that your records reflect the actual sequence of your work. It also protects you if a question arises about when a particular observation was made or when a decision was recorded. ### Review Logs Schedule a regular review of your folder structure. A monthly review is appropriate for active projects. During the review, check that files are in the correct folders, that naming conventions are followed, and that no files are missing from expected locations. Keep a simple log of your reviews. Record the date, the projects reviewed, and any corrections made. This log serves as evidence that you are actively managing your research records, which can be relevant if questions arise about data provenance. ## Common Failure Patterns in Research Note Organization ### The Desktop Dump Files accumulate on the desktop or in a downloads folder because creating a proper folder structure feels like overhead. The result is a collection of files with no organizational logic and no way to find a specific note without searching. The fix is to make folder creation part of the project setup process. When you start a new project, create the full folder structure before you collect any data. This front-loads the organizational work and eliminates the need to sort files later. ### The Single Folder Trap Some researchers create one folder per project and place all files directly inside it. This works for very small projects but breaks down as the project grows. Files with similar names become indistinguishable, and the folder becomes as chaotic as the desktop. The fix is to use subproject and note type folders even for small projects. The overhead is minimal, and the structure scales as the project grows. ### The Over-Nested Structure The opposite failure is creating too many levels of folders. A structure with eight levels of nesting makes files difficult to reach and encourages users to bypass the system entirely. The fix is to limit your hierarchy to three or four levels: project root, subproject, note type, and file. If you need more granularity, use file naming conventions instead of additional folder levels. ### The Inconsistent Naming Problem Different projects use different naming conventions, or the same project uses multiple conventions over time. This makes it impossible to predict where a file belongs or what a file contains. The fix is to write down your naming convention and keep it visible. Include it in your project setup notes and refer to it whenever you create a new file. ## Options and Tradeoffs in Folder System Design ### Local Storage Versus Cloud Storage Local storage keeps your files on your own device, which gives you full control and offline access. Cloud storage provides synchronization across devices and automatic backup, but it introduces questions about data security and institutional policy. The National Institutes of Health grants and funding pages describe expectations for data management that may apply to funded research. If your research is funded, check whether your funding agreement specifies storage requirements. For unfunded research, choose the option that best balances accessibility and security for your situation. ### Paper Notes Versus Digital Notes Some researchers prefer paper notebooks for raw observations and digital folders for processed material. This hybrid approach can work, but it requires a clear rule for how paper notes are transferred to the digital system. If you use paper notes, scan or photograph them and place the digital copies in the appropriate note type folder. Record the date of the original note and the date of the digital transfer. This creates a complete record that exists in both formats. ### Single User Versus Collaborative Use A folder system designed for one person may not work for a team. Collaborative research requires shared naming conventions, shared folder structures, and clear rules about who can modify files. The Committee on Publication Ethics core practices address authorship and contribution, which depend on accurate records of who did what. A collaborative folder system should include a convention for indicating who created or modified each file, either in the file name or in a metadata field. ## Welfare and Safety Context for Research Note Management ### Data Security Considerations Research notes often contain sensitive information, including personal data from human subjects, proprietary information from sponsors, or unpublished findings that could be misused. Your folder system should include security measures appropriate to the sensitivity of your data. The National Library of Medicine research methods resources address ethical considerations in research, including the protection of participant data. If your research involves human subjects, your folder system must comply with your institution's data security requirements and any applicable regulations. ### Institutional Policy Compliance Your institution may have specific policies about data retention, storage location, and access control. These policies may be more restrictive than the general principles described here. Check with your institution's research office or data management office before implementing a folder system that involves sensitive data. The National Institutes of Health data management and sharing policy describes expectations for NIH-funded research, including the development of a data management plan. Even if your research is not NIH-funded, the policy provides a useful framework for thinking about what your data management obligations might be. ## Professional Escalation Criteria ### When to Consult Your Institution's Data Management Office Contact your institution's data management office if you are unsure whether your folder system complies with institutional policy, if you handle data that requires special security measures, or if you are preparing a data management plan for a funding application. The National Institutes of Health grants and funding pages describe the application process and the expectations for data management plans. If you are preparing a grant application, consult the relevant guidance early in the process so your folder system aligns with the requirements. ### When to Consult Your Research Integrity Office Contact your research integrity office if you suspect that data has been lost, misattributed, or altered, or if you have questions about authorship or contribution records. The Committee on Publication Ethics core practices describe expectations for handling allegations of misconduct and for maintaining accurate research records. A folder system is not a substitute for professional judgment. If you discover a problem with your records, address it promptly and seek guidance from the appropriate office instead of attempting to fix it silently. ## Decision Framework for Choosing Folder Granularity ### Matching Folder Depth to Project Complexity The three-level hierarchy described earlier works well for most projects, but not every research effort needs the same depth. A short literature review with ten sources does not require the same folder architecture as a multi-site clinical study with thousands of records. Applying the same structure to every project creates unnecessary overhead for small efforts and insufficient organization for large ones. Use a project complexity assessment before creating folders. Score each project on three dimensions: duration, data volume, and number of contributors. A project that runs longer than six months, generates more than fifty files, or involves more than two people needs the full three-level structure. A project that is shorter, smaller, and solo can use a simplified two-level structure with project root and note type folders only. The National Library of Medicine research methods resources describe how documentation practices should match the scale and nature of the research effort. A folder system is a documentation practice. It should scale with the work it supports, not impose a fixed structure regardless of need. ### The Two-Level Structure for Small Projects For a small project, create a project root folder and place note type subfolders directly inside it. Skip the subproject level entirely. A typical small project structure looks like this: `2025-06_reading-group_notes` containing `raw-notes`, `processed-notes`, and `admin`. This structure works when the project has one workstream and a short timeline. The reduced nesting makes file access faster and reduces the number of decisions required when saving a new file. The tradeoff is that you cannot separate distinct phases of work within the project. If the project grows beyond its original scope, you can add subproject folders later and move files into them. ### The Four-Level Structure for Complex Projects For large projects, use the full hierarchy with project root, subproject, note type, and file. This structure supports multiple concurrent workstreams and makes it possible to locate any record without opening unrelated folders. A complex project structure might look like this: ``` 2025-06_antibiotic-resistance-survey/ 01_literature-review/ raw-notes/ processed-notes/ 02-data-collection/ raw-notes/ processed-notes/ meeting-notes/ 03-analysis/ raw-notes/ processed-notes/ 04-writing/ drafts/ admin/ ``` The four-level structure adds one decision point when saving a file, but it prevents the mixing of material from different workstreams. For projects with multiple contributors, this separation is essential because each person works in a different subproject and does not need to navigate the entire project folder. ### When to Upgrade or Downgrade Folder Depth A folder system should change when the project changes. Review the complexity of each active project during your monthly folder review. If a project has outgrown its two-level structure, upgrade it by creating subproject folders and moving existing files into the appropriate locations. If a project has shrunk or simplified, downgrade the structure to reduce overhead. This is less common than upgrading, but it happens when a project loses a workstream or when a large project is reduced to a single remaining task. The Committee on Publication Ethics core practices emphasize the importance of maintaining accurate records throughout the research process. A folder structure that changes with the project is a practical way to keep records aligned with the actual state of the work. ## Record System for Folder Structure Decisions ### The Structure Decision Log Keep a simple log of folder structure decisions for each project. Record the date, the project code, the structure level chosen, and the reason for the choice. This log serves two purposes. It documents why a project uses a particular structure, and it provides a reference point when you need to decide whether to upgrade or downgrade. The log does not need to be elaborate. A spreadsheet with columns for date, project code, structure level, and rationale is sufficient. Store the log in your research directory at the top level so it is accessible from any project folder. ### Structure Change Records When you change a project folder structure, record the change in the decision log. Note the date, the previous structure, the new structure, and the reason for the change. This record is important because it explains why files moved and when the move happened. The National Institutes of Health data management and sharing policy describes expectations for documenting data management decisions. While the policy applies to NIH-funded research, the principle of documenting structural decisions applies to any research record system. ## Troubleshooting Folder Structure Problems ### The Structure Mismatch Problem A common failure is using a two-level structure for a project that has grown into a complex effort. The symptom is files accumulating in the project root because the note type folders cannot accommodate the variety of material. The fix is to upgrade the structure by creating subproject folders and moving files into them. ### The Structure Overkill Problem The opposite failure is using a four-level structure for a small project. The symptom is that files are difficult to reach and the researcher starts bypassing the structure by placing files at the project root. The fix is to downgrade to a two-level structure and consolidate files. ### The Structure Drift Problem Structure drift occurs when a project starts with one structure and gradually changes without a deliberate decision. The symptom is a mix of folder levels within the same project, with some files in subproject folders and others directly in the project root. The fix is to review the project structure during your monthly review and align all files to the intended structure. ## Records and Measurements for Structure Decisions ### Folder Count Records Track the number of folders in each active project. A sudden increase in folder count without a corresponding increase in project activity may indicate that the structure is becoming over-nested. A sudden decrease may indicate that files are being consolidated or that the structure is being bypassed. ### File Placement Accuracy During your monthly review, check whether files are placed in the correct folder for their type. Calculate the percentage of files that follow the structure. If the percentage falls below 90 percent, the structure is likely too complex for the project or the naming convention is unclear. ### Structure Change Frequency Track how often you change the structure of each project. Frequent changes indicate that the initial structure was poorly matched to the project. Infrequent changes indicate that the structure is stable and appropriate. ## Professional Escalation Criteria for Structure Decisions ### When to Consult Your Institution's Data Management Office Contact your institution's data management office if you are unsure whether your folder structure meets institutional requirements for data organization, if you are preparing a data management plan that requires a specific folder architecture, or if you are handling data that requires a particular level of organization for compliance. The National Institutes of Health grants and funding pages describe expectations for data management plans in grant applications. If your funding application requires a data management plan, consult the relevant guidance early so your folder structure aligns with the plan you submit. ### When to Consult Your Research Integrity Office Contact your research integrity office if you discover that a folder structure change has caused files to be lost, misattributed, or mixed between projects. The Committee on Publication Ethics core practices describe expectations for handling data integrity issues. A folder structure change that results in data loss is a data integrity issue and should be addressed promptly with professional guidance. ## Frequently Asked Questions ### What is the difference between a project folder and a subproject folder? A project folder contains everything related to one research effort with a defined question and endpoint. A subproject folder separates distinct workstreams within that project, such as literature review, data collection, and analysis. The project folder is the top-level container, and subproject folders organize the work within it. ### How many levels of folders should I create? Limit your hierarchy to three or four levels: project root, subproject, note type, and file. Additional levels make files harder to reach and encourage people to bypass the system. If you need more granularity, use file naming conventions instead of adding folder levels. ### Should I use dates in my folder names? Yes. Use a date prefix in ISO format (YYYY-MM) at the start of project folder names. This ensures chronological sorting and makes it easy to identify when a project started. For files within folders, include the full date in the file name to distinguish versions. ### How do I handle files that relate to multiple projects? Decide which project owns the file and place it in that project's folder. In the other project folder, create a reference note that points to the original location. This prevents duplicate copies that can diverge and cause confusion. ### What should I do with notes from a completed project? Move the entire project folder to your archive folder. Do not delete it unless your institution's policy requires destruction after a specified period. The National Institutes of Health data management and sharing policy describes expectations for preserving research data that are relevant even beyond NIH-funded research. ### How often should I review my folder structure? Review active project folders monthly. Check that files are in the correct folders, that naming conventions are followed, and that no files are missing. Keep a log of your reviews, including the date, projects reviewed, and corrections made. ### Can I use this folder system for collaborative research? Yes, but you need to establish shared conventions before starting. Agree on naming conventions, folder structures, and rules for file modification. Include a convention for indicating who created or modified each file, either in the file name or in metadata. ### What should I do if I find a file that does not follow my naming convention? Rename it immediately using the correct convention. Do not wait for a cleanup session. The longer a misnamed file remains in your system, the more likely it is to be overlooked or confused with another file. ## Using the Evidence | Source | Best use in this topic | Important limitation | |---|---|---| | [Research Methods Resources](https://www.ncbi.nlm.nih.gov/books) | official guidance | Check the linked page for current local requirements | | [EQUATOR Network](https://www.equator-network.org/) | official guidance | Check the linked page for current local requirements | | [Core Practices](https://publicationethics.org/core-practices) | official guidance | Check the linked page for current local requirements | ## Related Articles - [Bioinformatics Portfolio: Projects That Demonstrate Real Research Judgment](/blog/guides/bioinformatics-portfolio-projects-that-demonstrate-real-research-judgment) - [Git for Research Projects: Version Control for Code, Data, and Analysis Notes](/blog/guides/git-for-research-projects-version-control-for-code-data-and-analysis-notes) - [Reference Managers for Researchers: Choosing a Workflow That Survives Collaboration](/blog/careers/reference-managers-for-researchers-choosing-a-workflow-that-survives-collaborati) - [Protein Synthesis Step By Step](/blog/guides/protein-synthesis-step-by-step) - [Open Science Practices: A Guide for Researchers](/blog/guides/open-science-practices-a-guide-for-researchers) ## References and Further Reading - [Research Methods Resources](https://www.ncbi.nlm.nih.gov/books). National Library of Medicine. - [EQUATOR Network](https://www.equator-network.org/). EQUATOR Network. - [Core Practices](https://publicationethics.org/core-practices). Committee on Publication Ethics. - [NIH Grants and Funding](https://grants.nih.gov/). National Institutes of Health. - [ORCID for Researchers](https://info.orcid.org/researchers). ORCID. - [Data Management and Sharing Policy](https://sharing.nih.gov/data-management-and-sharing-policy). National Institutes of Health. - [NCBI Literature Resources](https://www.ncbi.nlm.nih.gov/). National Center for Biotechnology Information. - [PubMed](https://pubmed.ncbi.nlm.nih.gov/). National Library of Medicine. > This article is educational and does not replace institutional policy, professional advice, or applicable safety and regulatory requirements.