F6 resources
How to preserve context from idea to published
An operating baseline that keeps files, owners, reviews, and decisions connected throughout production.
F6 Team · PublishedStart with a clear unit of work
A Project groups the production. Each Media Item keeps its own workflow, files, review, and publication target. Separating those layers prevents a campaign from becoming an impossible list to interpret.
Tie every decision to the exact version
An approval is only useful when it answers three questions:
- Which version was reviewed.
- Who made the decision.
- What changed after that decision.
Keep originals where they already live
If the team works in Google Drive, it does not need to duplicate originals to regain operational control. The operating system can retain stable identifiers, proxies, and reviews without confusing them with the source file.
Close the loop
Published should not be a loose note. Record the destination, date, and evidence so the next project starts with real context.