Documents and version control
Event project folder structure
The event files are scattered across inboxes, personal drives and chat threads, and a new team member cannot find the current programme.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Set up one shared project folder with a numbered top level, one owner per folder, and a naming rule that puts the date and version in the file name. Keep the live version of each document in one place only.
The aim is that anyone on the team can find the current approved version in under a minute, and that a handover to a new person needs no explanation beyond the folder itself.
Why structure matters before the event, not after
Most file problems come from documents being copied rather than linked. Once there are three programmes, nobody knows which is approved.
A structure decided in week one costs an hour. The same structure imposed in week twenty costs days of sorting and leaves old copies behind.
A top-level layout that suits most professional events
| Folder | What goes in it | Typical owner |
|---|---|---|
| 00 Admin and decisions | Brief, decision log, meeting notes, contact list | Project lead or secretariat |
| 01 Programme and speakers | Programme versions, speaker details, session materials by session ID. Check versions with the materials version checker. | Programme lead |
| 02 Venue and suppliers | Quotes, contracts, requirements, floor plans | Operations lead |
| 03 Registration and communications | Registration setup, invitations, web copy, templates | Communications lead |
| 04 Finance | Budget, approvals, invoices. Track with the budget variance calculator. | Finance lead |
| 05 On-site | Run sheets, role lists, printed pack masters | Operations lead |
| 06 Reporting and handover | Evidence, final report, handover pack | Project lead |
| 99 Archive | Superseded versions only | Project lead |
Naming and versions
- Use one pattern, for example: date, short title, version, status. Example: 2027-03-12 programme v04 DRAFT.
- Mark approved files APPROVED and move older versions to the archive folder, never delete them.
- Name the owner of each folder in a short readme file inside it.
- Keep links, not copies, when another folder needs the same document.
Access and confidentiality
Give each person access to the folders they need. Finance and contracts folders are usually narrower than programme folders. Work this through in a file access matrix and review it at each phase change.
Personal data such as attendee lists should sit in one controlled place, with access agreed with whoever is responsible for privacy, not scattered across folders.
Setting it up in order
- Agree the top-level folders with the committee chair and secretariat.
- Create the folders and a readme in each with the owner's name.
- Move live documents in and leave a note in the old locations pointing to the new one.
- Agree the naming rule and put one example file in each folder.
- Review after four weeks and adjust.
Worked example · Fictional example
A secretariat tidies a conference's files
Fictional organisation and figures, illustrative only.
A fictional association had its conference files across five inboxes and two shared drives. The secretariat created eight top-level folders, named an owner for each and agreed a date-version naming rule.
In the first month, three draft programmes were consolidated into one approved version with the older two moved to the archive. When a part-time volunteer joined, she found the speaker list and run sheet without asking anyone.
Use this yourself
Event project folder set-up checklist
Copy this and tick each item as you set up.
- Top-level folders agreed and numbered (see the layout table)
- Owner named for every folder, written in a readme file
- Naming rule chosen: date, short title, version, status
- One example file placed in each folder
- Live documents moved in, with pointers left at old locations
- Archive folder created, and the rule for moving older versions agreed
- Access set per folder and recorded
- Personal data location and access agreed with the privacy owner
- Review date set for four weeks after set-up
Open the tool: Conference materials and translation-version checker
Handle it in-house, or bring in help?
Your team can usually handle this when
- One or two people maintain the files and the project is small.
- The committee already uses a shared drive and agrees on one location.
- The structure is for internal use only.
Outside planning help earns its fee when
- Several organisations, volunteers or agencies edit the same documents.
- Files are already scattered and conflicting versions exist.
- A handover to a new person or team is coming and nothing is written down.
Want the structure set up and kept in order?
A conference project lead can agree the folder layout, naming rule and owners with your team, then keep the live versions, decisions and handover documents in order through the project. Send a description of where files sit today, even if it is messy.
Questions organisers ask
Which platform should we use?
Use the shared drive your organisation already supports and your members or suppliers can access. The structure matters more than the product.
Should suppliers have access to the folders?
Give suppliers access only to the folders or files they need, and review it as phases change. Do not give blanket access.
How do we handle files that two teams need?
Keep one master in the owning folder and link to it from the other. Do not copy it.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.