Meeting Documentation Folder Structure for Labs (Naming + Permissions Template)

A clear meeting documentation folder structure helps a lab find decisions fast, protect sensitive work, and hand off operations without chaos. Use one shared “Meetings” hub with consistent subfolders for agendas, minutes, transcripts, and action logs, plus a separate “Projects” area that links back to meeting decisions. This template includes naming conventions and permission tiers (lab-wide vs PI-only) so everyone knows what goes where.

Primary keyword: meeting documentation folder structure

Key takeaways

• Keep meeting records in one “Meetings” hub with four standard subfolders: Agendas, Minutes, Transcripts, Action Log.
• Use a single naming pattern with date-first (YYYY-MM-DD) so files sort correctly and stay searchable.
• Separate “Lab-wide” and “PI-only” areas at the top level to avoid accidental sharing.
• Make handover easy with a “Start Here” folder, an index, and a monthly “closeout” routine.

The lab-wide structure (copy/paste template)

This structure works in Google Drive, SharePoint/OneDrive, Dropbox, or a lab server. Keep top-level folders stable, and let projects and meetings evolve inside them.

• 00_START-HERE
  • README_Lab-Docs-Map.html (or .docx)
  • Lab-Directory_Contacts-Roles.docx
  • Permissions-Map.xlsx
  • Templates
    • Agenda_Template.docx
    • Minutes_Template.docx
    • Action-Log_Template.xlsx
    • Decision-Record_Template.docx
• 10_MEETINGS (Lab-wide)
  • 01_Agendas
  • 02_Minutes
  • 03_Transcripts (if used)
  • 04_Action-Log (master)
  • 05_Decision-Records
  • 90_Archive (read-only)
• 20_PROJECTS (Lab-wide)
  • Project-Name_A (with its own substructure)
  • Project-Name_B
  • 99_Project-Archive
• 30_ADMIN (Lab-wide)
  • Onboarding
  • Lab-Policies
  • Vendors-Tools
  • Equipment-Inventory (if appropriate)
• 90_PI-ONLY (Restricted)
  • 01_Personnel
  • 02_Budgets-Grants
  • 03_Sensitive-Collaborations
  • 04_Incident-Notes (if needed)
• 95_COMPLIANCE (Restricted, need-to-know)
  • IRB-IACUC (as applicable)
  • Data-Use-Agreements
  • Security-Access-Logs (if needed)

If your lab already has a strong project folder system, keep it. Just add the “10_MEETINGS” hub and make it the single source of truth for meeting outcomes.

Folder-by-folder: what belongs where (and what does not)

10_MEETINGS: the “single source of truth” for decisions

Put every recurring meeting series in the same location so people do not hunt across project folders. Use subfolders by record type (agenda, minutes, transcript) rather than by meeting name, because naming can drift.

• 01_Agendas: finalized agendas used in the meeting (not brainstorming notes).
• 02_Minutes: the approved record of what was decided, assigned, or deferred.
• 03_Transcripts: verbatim or near-verbatim text from recorded meetings, when you need detail.
• 04_Action-Log: one master spreadsheet that tracks all open actions across meetings.
• 05_Decision-Records: short “decision memos” when a decision affects scope, budget, authorship, timelines, or policy.
• 90_Archive: past years or closed series, set to read-only.

Avoid storing working drafts of project documents in “Meetings.” Instead, link to them from minutes and keep the files in “Projects.”

20_PROJECTS: where the work lives

Store protocols, analysis plans, manuscripts, posters, and datasets in the project folder. In minutes, include a link to the exact file (not just the folder) so the decision trail stays clear.

• Use a “00_Project-Admin” subfolder for project-specific meeting notes if the project runs its own working meetings.
• Keep an “09_Decisions” subfolder for decision records that only apply to that project.

90_PI-ONLY and 95_COMPLIANCE: what should never be lab-wide by default

Separate restricted materials at the top level so permissions stay simple and mistakes stay rare. If someone needs access, grant it intentionally and document it in the permissions map.

If your lab handles human subjects or regulated data, follow your institution’s rules for where records may live and who may access them. For general guidance on protecting controlled unclassified information, see NIST’s cybersecurity framework resources.

Naming conventions (simple rules that keep everything searchable)

A good naming convention helps the lab sort files automatically, search across years, and avoid duplicates. Keep it strict for meeting records, but flexible for research drafts.

Core pattern (recommended)

• Date first: YYYY-MM-DD (so alphabetical sorting matches time order).
• Meeting series code: LABMTG, GROUPMTG, 1ON1, PROJECTX, JOURNAL, etc.
• Record type: AGENDA, MINUTES, TRANSCRIPT, ACTIONLOG, DECISION.
• Optional: topic tags and version.

File name formula: YYYY-MM-DD__SeriesCode__RecordType__ShortTopic__v01

Examples you can copy

• 2026-03-04__LABMTG__AGENDA__Quarterly-planning__v01.docx
• 2026-03-04__LABMTG__MINUTES__Quarterly-planning__APPROVED.pdf
• 2026-03-04__LABMTG__TRANSCRIPT__Quarterly-planning__raw.docx
• 2026-03-04__LABMTG__DECISION__Authorship-policy-update__v01.docx
• Action-Log__LAB-WIDE__MASTER.xlsx

Versioning rules (keep it light)

• Use v01, v02 for drafts that will circulate.
• Mark the final minutes as APPROVED and export to PDF to prevent accidental edits.
• Do not create “final_final2” files; replace them with version numbers.

Permission tiers (lab-wide vs PI-only) with a practical map

Permissions work best when they match the folder design. Aim for a small set of tiers, then assign them at the top folder level and inherit downward.

Recommended tiers

• Lab-wide (Read/Write): most lab members, for day-to-day collaboration.
• Lab-wide (Read-only): rotating students, visitors, or collaborators who should see outcomes but not edit.
• Managers (Read/Write): lab manager, project managers, and a backup admin for templates, indexes, and archives.
• PI-only (Restricted): PI and designated admin only.
• Need-to-know (Restricted): compliance and sensitive folders, with named access lists.

Permission recommendations by folder

• 00_START-HERE: Lab-wide read; Managers write.
• 10_MEETINGS: Lab-wide write for agendas/minutes; transcripts may be read-only after posting.
• 20_PROJECTS: project-team write; lab-wide read if you want transparency; restrict if not.
• 30_ADMIN: Managers write; lab-wide read for policies and onboarding.
• 90_PI-ONLY: PI-only, no inherited access.
• 95_COMPLIANCE: need-to-know access with explicit membership list.

When you create a new project, set access at the project folder once. Avoid file-by-file sharing, because it breaks auditability and makes handover harder.

Practical workflow: agenda → minutes → transcript → actions (with templates)

This workflow keeps meetings lightweight while still producing strong records. You can run it with shared docs and a single action log spreadsheet.

1) Before the meeting: create the agenda

• Create the agenda file in 10_MEETINGS/01_Agendas using the naming rule.
• Include: date/time, attendees, goals, discussion items, and “decisions needed.”
• Add links to pre-reads stored in 20_PROJECTS (link to the file, not just the folder).

2) During/after: write minutes that capture outcomes

• Save minutes in 10_MEETINGS/02_Minutes.
• Focus on: decisions, action items, owners, and due dates.
• Use consistent headings: Decisions, Actions, Risks/Blocks, Notes.

3) If you record: store transcripts with care

Transcripts help when you need precise wording, training notes, or detailed technical review, but they can include sensitive information. Put them in 10_MEETINGS/03_Transcripts and consider limiting access or posting a cleaned version.

• Use two levels when needed: raw (restricted) and clean (lab-wide).
• Link the transcript from the minutes, and note any redactions.

If you use automated tools for a first draft, plan a quick review step to fix names, jargon, and action items. For teams that need speed, an AI-first workflow can start with automated transcription and then move to human review when accuracy matters.

4) Maintain one action log (the real operational backbone)

Keep a single master action log in 10_MEETINGS/04_Action-Log. Do not create a new action list inside each set of minutes, because actions will disappear.

• Columns to include: Action, Owner, Due date, Status, Meeting date, Link to minutes, Project tag.
• Status values: Not started, In progress, Blocked, Done, Dropped.
• Weekly hygiene: sort by due date, review blocked items, close out completed items.

5) Create decision records when it really matters

Minutes often feel too long for future readers who only need the “why.” Use a one-page decision record for high-impact items, and file it in 10_MEETINGS/05_Decision-Records.

• Include: decision, date, context, options considered, rationale, who approved, and what changes next.
• Link the decision record from the minutes and from the affected project folder.

Handover-friendly setup for new lab managers

A good structure is only half the job. Handover succeeds when the next person can understand what is “current,” what is “historical,” and how to run the weekly routine.

Build a “Start Here” that answers the first 10 questions

• Where are meeting docs stored?
• Which meetings are official, and who owns them?
• How do we name files?
• Where is the master action log?
• What is PI-only, and how do we request access?
• What is the monthly archive process?

Create an index that points to the right place

Put a simple index (spreadsheet or doc) in 00_START-HERE with:

• Meeting series name and series code
• Cadence (weekly/monthly)
• Owner (person responsible for agenda/minutes)
• Primary folder links (agendas, minutes, transcripts)

Use a monthly “closeout” routine

• Confirm that each meeting has an agenda and minutes file.
• Check that all new actions made it into the master action log.
• Convert approved minutes to PDF and move any superseded drafts to a “Drafts” subfolder or delete them.
• Move older items (for example, last year) into 10_MEETINGS/90_Archive and set it to read-only.

Pitfalls to avoid (and quick fixes)

• Pitfall: Each project keeps its own meeting notes with no standard.
  Fix: Keep the lab’s official meeting records in “10_MEETINGS,” and link out to projects.
• Pitfall: Actions live only inside minutes.
  Fix: One master action log, with links back to minutes.
• Pitfall: Too many permission exceptions.
  Fix: Separate restricted folders at the top level, then inherit permissions.
• Pitfall: File names like “Lab meeting notes.”
  Fix: Date-first naming plus series code and record type.
• Pitfall: People fear documentation because it feels heavy.
  Fix: Keep minutes short, reserve transcripts for when you need detail, and use decision records for high-impact items.

Common questions

Do we really need transcripts if we already have minutes?

Not always. Minutes capture outcomes, while transcripts capture exact wording and technical detail, so transcripts make sense when accuracy, attribution, or complex discussion matters.

Should we organize by meeting type or by date?

Use date-first file names so sorting stays consistent, and keep folders by record type so the structure stays stable even if meeting names change. If you run many series, add a short series code in every file name.

Where should 1:1 meeting notes go?

If they include performance, compensation, or sensitive personnel issues, keep them in 90_PI-ONLY (or a restricted managers folder). If they are project check-ins without sensitive content, you can store them in the project folder or the meetings hub with restricted access.

How do we handle sensitive topics that come up in a lab-wide meeting?

Keep minutes focused on decisions and actions, and avoid personal details. If needed, store a restricted addendum in a PI-only folder and reference it carefully from the minutes.

What file type should minutes be?

Draft in a shared document format for easy collaboration, then export approved minutes to PDF for a stable record. Keep the editable version if you need it, but label the approved PDF clearly.

How long should we keep meeting records?

Retention depends on your institution and the kind of work you do. Ask your research administration or compliance office, and document your retention rule in the “Start Here” folder; for general records management guidance, see U.S. National Archives records management resources.

What is the fastest way to make meeting recordings searchable?

Create transcripts and store them with consistent names, then link them from minutes and your action log. If you need a quick first draft, you can start with automated transcription and then proofread for names and action items.

If your lab wants meeting records that are easy to search and share, a solid folder structure is a strong start. When you also need accurate transcripts, minutes support, or captions for recorded sessions, GoTranscript can help with professional transcription services that fit into the structure above.