Research Documentation Systems Guide
A complete framework for managing research documents, files, and versions across the full lifecycle of an academic or professional research project.
1. Why Documentation Architecture Matters
Disorganised research documentation is one of the most underestimated threats to research quality. When files cannot be found, when versions are confused, when raw data is overwritten, and when citation sources are lost — the research itself is compromised. Documentation architecture is not administrative overhead; it is research infrastructure.
2. Folder Structure System
Use the following master folder architecture for all research projects. Apply it from day one — retrofitting structure onto an existing chaotic project is far harder than starting with discipline.
/PROJECT-NAME/
One folder per research project. Name using the format: YEAR_ProjectName (e.g., 2026_PhDMethodology).
/01_Literature/
All source papers, articles, and books. Subfolders by theme or methodology area. PDFs named: AuthorYear_ShortTitle.pdf.
/02_Data/
Raw data (never modified), processed data, and analysis outputs. Subfolders: /raw/, /processed/, /outputs/. Raw data is read-only.
/03_Writing/
All manuscript drafts. Version-controlled using naming conventions. Never delete old versions.
/04_Notes/
Research notes, reading notes, meeting notes. Use plain text or Markdown. Dated and titled precisely.
/05_Admin/
Ethics approval, correspondence, institutional forms, invoices. Non-academic but essential documentation.
3. File Naming Conventions
Consistent file naming eliminates the single greatest source of research document chaos: ambiguous, date-free, version-free filenames like "final_draft.docx" or "notes_new.pdf".
The Standard Convention
YYYY-MM-DD_ProjectCode_DocumentType_Version.ext
Examples:
2026-06-14_PHD01_MethodologyChapter_v03.docx2026-05-20_PHD01_LitReview_FINAL.docx2026-04-10_PHD01_InterviewTranscript_P04.txt
Rules: No spaces in filenames (use underscores or hyphens). Always include the date. Always include the version number. "FINAL" is a version designation, not a substitute for version numbering.
4. Version Control for Academic Documents
Version control is not optional for serious research. Use one of the following approaches based on your technical comfort level:
Option A: Manual Version Numbering (minimum standard)
Increment the version number each time you save a substantive revision: v01, v02, v03. At major milestones (chapter complete, supervisor feedback incorporated), increment to the next major version: v1.0, v2.0.
Option B: Git Version Control (recommended for text-heavy research)
Use Git (with GitHub or a private repository) to track all changes to your writing files. Every commit message should describe what changed and why. Provides full revision history, enables branching for experimental rewrites, and prevents irreversible data loss.
Option C: Cloud Auto-Versioning
Google Drive and OneDrive both maintain version histories automatically. Effective as a backup but does not replace intentional version naming in your filenames.
5. Naming Conventions for Literature
All source documents should follow: AuthorLastname_Year_ShortTitle.pdf
Example: Creswell_2018_ResearchDesign.pdf
For institutional reports: Organisation_Year_ReportTitle.pdf
6. Backup Protocols
Research data loss is permanent. Apply the 3-2-1 backup rule:
- 3 copies of all research data and documents
- On 2 different storage media (e.g., local drive + external drive)
- With 1 copy offsite or in cloud storage
Backup frequency: daily for active writing projects, weekly for archival material. Test your backups periodically — a backup you cannot restore is not a backup.