How to Share Event Files With Crew Without Resending Every Update

The problem is not sending the first file

The difficult part is keeping the current version easy to find after the schedule, venue access, parking, or call time changes. Attachments and message threads create copies that stop being current.

A better workflow gives the event one resource record and controls who can see it.

Give each resource enough context

• A clear title that makes sense outside the original message.
• A category such as schedule, call sheet, venue, safety, or client presentation.
• A short note explaining how the resource should be used.
• The current link or uploaded file.
• Explicit internal, crew, and client visibility.

Use audience controls instead of duplicate folders

A crew call sheet may be crew-visible but not client-visible. A client presentation may be visible to the client but unnecessary for most crew. An internal risk note should remain private.

Independent audience controls let one project workspace hold all three without pretending every participant should see everything.

Tell crew where the current source lives

When an update is important, send a concise notification that points back to the event resource instead of attaching another copy. The message explains what changed; the portal remains the current source.

Flightcase keeps crew-visible files, links, messages, and show context close to the assignment so fewer handoffs need to be rebuilt.

Review visibility as the event changes

Sharing is not a one-time setting. Review audience access when a resource becomes final, when sensitive information is added, when crew changes, and when the event closes.