File Sharing for Event Planning: A Complete Guide

Event planning runs on files: venue contracts, CAD floor plans, vendor COIs, catering counts, AV specs, speaker bios, and the photographer's deliverable bucket the day after. A working file-sharing setup for events uses a central hub (Google Drive, Dropbox, or Notion) for the planning team, vendor-specific share links for each supplier, a transfer tool for one-off large sends (like 12 GB of photo deliverables), and a locked-down post-event archive once the dust settles. This guide covers the file types, workflows, and security specifics that event planners actually deal with.

The File Types Event Planners Juggle

A mid-size corporate conference generates a predictable set:

Contracts: venue, catering, AV, entertainment, speakers. .pdf and .docx, often with e-sign traces from DocuSign or Adobe Sign.
Floor plans: .dwg (AutoCAD), .vwx (Vectorworks), .pdf exports. Sizes from 5 MB to 200 MB with nested references.
Production schedules: .xlsx or Google Sheets with minute-by-minute timing.
Vendor certificates: COI (Certificate of Insurance), W-9, safety certifications. .pdf, usually under 2 MB each but dozens per event.
Catering documents: menu, dietary restrictions list, final counts. Tight revision cycles 48 hours before.
AV specs: input lists, stage plots, lighting cues. Variable formats, often vendor-specific.
Creative assets: stage graphics, slides, video reels, sponsor logos. .ai, .psd, .mp4, .png.
Post-event media: photographer deliverables (20-80 GB), videographer edits, attendee-captured content.

No single tool handles all of these well. The hub-plus-spokes pattern wins.

The Central Hub for the Planning Team

Everyone on the internal planning team needs one place to find everything. Options:

Google Drive shared drive: free-flowing, good search, 5 TB per file cap.
Dropbox shared folder: strong sync for desktop users, good for designers working on stage creative.
Notion with linked Drive folders: best for teams that want docs and file attachments side by side.
SharePoint site: for corporate events where IT mandates Microsoft 365.

Folder structure that works:

/{Event Name} {Year}
  /01-Contracts
  /02-Venue
  /03-Vendors
  /04-Speakers
  /05-Production
  /06-Creative
  /07-Onsite
  /08-Post-Event

Numbered prefixes keep the order consistent. Every event clones this template.

Vendor-Specific Access Without Handing Over the Keys

Vendors need their pieces, not the whole event. Give each vendor their own slice:

Venue: shared folder with contract, floor plans, insurance certs, load-in schedule. Not the whole event.
Catering: separate folder with menu, counts, dietary list, timing. Never the budget.
AV: rider, stage plot, input list, schedule. Not the speaker bios.
Photographer / videographer: shot list, schedule, VIP list. After event: an upload link for deliverables.

For vendors without an account in your system, share-by-link with specific permissions (view-only for contracts they need to reference, edit for timing docs they need to update) works. Set expiry dates that match the event lifecycle.

Floor Plan Handling

Floor plans are specific. A few traps to avoid:

CAD files have external references. Send the .dwg with all xrefs packaged (AutoCAD's eTransmit, Vectorworks' "Create Folder With Project"). Otherwise the recipient opens a file with missing elements.
Large plans need PDF exports for non-CAD users. The venue's operations manager doesn't own AutoCAD. Export a paginated .pdf at 1:100 or 1:200 with a cover sheet listing all layers.
Version discipline matters. Plans change weekly. Name files {Event}_FloorPlan_R{revision}_{date}.dwg. Old revisions archive to /07-Onsite/_Archive.

For 50+ MB plans that need to go to multiple vendors, a transfer link beats a Drive share for the initial broadcast — vendors download once rather than navigating folder permissions.

Post-Event Photo and Video Delivery

The biggest single file transfer in most events is the photographer's deliverable dump the day after. 20,000 photos at 25 MB each in RAW plus edited JPEGs adds up to 50-100 GB.

Three-phase handoff:

Immediate: photographer sends 20-50 selects via a transfer tool within 24 hours for social and press use. 2-4 GB typical.
Full edit: 500-1,500 selected images, color-corrected and exported JPEG, within 7-14 days. 10-30 GB.
Full archive: everything, including RAWs, within 30 days. 50-200 GB. Often goes to long-term storage rather than the active event hub.

HexaTransfer handles the immediate send (10 GB cap covers most same-day batches) with client-side AES-256-GCM encryption — appropriate for keynote speaker photos that embargo until the press release drops. For the full archive, a service that supports chunked resumable uploads (MASV, Smash Pro) matters because an 80 GB transfer on a flaky connection will fail without resume.

Vendor COI and Compliance Docs

Every vendor hands over a Certificate of Insurance. Many events require OSHA safety cert, ABC liquor license (for beverage caterers), or city-specific permits. These pile up fast.

Track in a spreadsheet or Airtable:

Vendor name, contact, scope of service.
COI on file (date, expiry, carrier, policy number, limits).
Additional insured listed (venue, primary event company).
Other cert requirements met.
Link to the PDF in the shared drive.

Audit the week before the event. Expired COI on event day means either scrambling to get an updated one or pulling the vendor — both bad.

Contract Handling and E-Signature

Contracts live in two places: the e-signature platform (DocuSign, Adobe Sign, HelloSign) that created the audit trail, and the event hub where the signed PDF gets filed.

After signature, download the fully-executed PDF and drop it in /01-Contracts. Keep the e-sign platform link as well — if there's ever a dispute, the platform's audit log has details (IP, email, viewing timestamp) the PDF doesn't carry.

For contracts over $10,000 or with unusual terms, also save the redlined Word version that shows the negotiation history. Future events with the same vendor go faster if you can find the previous terms.

Onsite Day-of Access

During the event, the planning team is running. Access patterns change:

Mobile-first: people need files on phones and tablets, not laptops.
Key docs ready offline: download the run-of-show, floor plan, and vendor contact list to every planner's device before load-in. Wi-Fi at the venue cannot be trusted.
Real-time updates: Google Sheets or Notion updates sync across devices. Slack or WhatsApp broadcasts for critical changes.
Limited sharing: onsite is not the time to be setting up new share permissions. Do that in the week before.

Post-Event Archive

After the event ends, file hygiene matters. Within 30 days:

Export the final run-of-show with actual timing noted next to planned timing.
Archive financials: final invoices, reconciliation, budget vs actual.
Archive deliverables: final photos, videos, attendee survey results.
Close vendor-specific share links that are no longer needed.
Export any files stored only in the transfer tool to long-term storage — transfer links expire.
Copy the event folder to /Archives/{Year}/ and mark read-only.

Future events reference the archive for templates, pricing negotiation, and lessons-learned reviews.

Security for High-Profile Events

Celebrity speakers, security-sensitive corporate announcements, or government events need tighter controls:

NDA-bound contractors get individual accounts, not shared folders.
Speaker bios and green room logistics travel by password-protected transfer with 48-hour expiry.
Venue blueprints with security-sensitive areas (backstage access, executive holding rooms) are not dropped in general vendor folders.
Post-event media deliveries that embargo need locked buckets until release date.

The Pragmatic Stack

For most mid-size events, a $20-50/month tooling budget covers it: a Google Workspace or Dropbox team plan for the hub, a transfer tool (free tier usually) for one-off sends, and e-signature with a starter DocuSign plan. Add Airtable or Notion if vendor tracking gets complex.

The event doesn't succeed because the file sharing is elegant. But it can fail because the file sharing is broken. Set it up once per event, follow the template, and let the work move through the seams.

Try it at hexatransfer.com — free, no account, 10 GB max.