Notion Database Streamlining for Video Production Creative Brief
Budget: $30 – $250 USD
I am restructuring six “Creative Brief Plans,” one for each short video I will be filming. Alongside these, there is a separate Notion database called Visual Content Specs, which serves as a centralized visual reference library. It contains mood boards, image references, and detailed visual options, and is designed to be easy to expand. The purpose of the two databases is distinct but complementary:
- Creative Brief Plans focus on written direction and storytelling.
- Visual Content Specs focuses on visual details and imagery.
Together, they provide a clear, consistent guide showcasing options, direction and uniformity for the visually desired story, helping me decide what to include in each video.
DELIVERABLES:
The data across both databases is heavy in both text and images, and it needs to support text-driven and image-driven views equally. I need help auditing and restructuring the system so it is intuitive, efficient, and easy to use without confusion.
- Specifically, I need the structure to support:
- A simplified, centralized overview that makes the big picture of both databases immediately clear. Clear call-outs to the most efficient “starting point” (whether that is a dedicated overview page, a space-level page, or the main database view)
- Correct and consistent property formats so each piece of information is understandable at a glance. This is especially critical for image-based content
- Purpose-built database views for both Pages and Properties with particular attention to image viewing, comparison, and reference
- Clear, intuitive navigation from *All Pages*, including a clean and logical “Cultures | Archive” structure
- No redundant or duplicated information across pages, properties, or views
- Both databases must remain easy to add new research and images to without breaking the structure.
- It is essential that all key information can be understood directly from the database level, without needing to open individual pages—using toggles, collapsible sections, and multiple database view modes (or other appropriate tools).
- Finally, Visual Content Specs must be easily and frequently referenced from within each Creative Brief Plan, reinforcing a clear link between written direction and visual execution.
PLEASE NOTE
I’ll be asking to sign a NDA - non disclosure agreement, requesting full privacy of this project once we begin working together
CURRENT CREATIVE BRIEF PLAN DATABASE STRUCTURE DETAILS:
Each “Creative Brief Plan” has a corresponding Notion database that houses key text and images, structured as follows:
- Header Row — 7 different Properties (the properties are: 1 Subliminal Messages; 2 Visual Inspo; 3 Sounds & Music Audio (+source); 4 Text Audio (+source); 5 Editorial won’t say; 6 Summary of 2 Lines (+details); 7 Tangents I won’t go into (Not to be confused with..))
- Header Column — 6-10 different ”Topic” Pages (First page used as the “Umbrella Summary” page)
- Under each “Topic“ Page, [as Sub-items] there are 3 “call out” pages (referencing other existing pages with a “@”), including: 2 “City“ Pages and “Cultures | Archive” page. ”City” Pages live in the database titled ”Cultures | Archive”. “City” Page names are ”Yucatan” and ”Aegean”. This list of “City” Pages will expand to more City names.
I am currently in the process of populating the 6 “Creative Brief Plan” databases by adding the necessary info under each listed property above (the Header Row). The “Topic” Pages populate a description, while below as a toggled sub-item, the “City” Pages populate city-specific data which includes text, links and images.*
The structure is as follows (listing the Header Columns titles):
- The Parent Page — “Topic” Pages: A description under each of the 7 properties, explaining what it is
- Child Page 1, as a toggled sub-item — “Cultures Archive”: Examples of data for the descriptions above under each of the 7 properties
- Child Page 2, as a toggled sub-item — “Yucatan” Page 1, titled“Yucatan”: City-specific data under each of the 7 properties
- Child Page 3, as a toggled sub-item — “Aegean” Page 2, titled “Aegean”: City-specific data under each of the 7 properties
*The problem here is many duplicate pages are created, both an original page and creating a whole new page on this database.
- Creative Brief Plans focus on written direction and storytelling.
- Visual Content Specs focuses on visual details and imagery.
Together, they provide a clear, consistent guide showcasing options, direction and uniformity for the visually desired story, helping me decide what to include in each video.
DELIVERABLES:
The data across both databases is heavy in both text and images, and it needs to support text-driven and image-driven views equally. I need help auditing and restructuring the system so it is intuitive, efficient, and easy to use without confusion.
- Specifically, I need the structure to support:
- A simplified, centralized overview that makes the big picture of both databases immediately clear. Clear call-outs to the most efficient “starting point” (whether that is a dedicated overview page, a space-level page, or the main database view)
- Correct and consistent property formats so each piece of information is understandable at a glance. This is especially critical for image-based content
- Purpose-built database views for both Pages and Properties with particular attention to image viewing, comparison, and reference
- Clear, intuitive navigation from *All Pages*, including a clean and logical “Cultures | Archive” structure
- No redundant or duplicated information across pages, properties, or views
- Both databases must remain easy to add new research and images to without breaking the structure.
- It is essential that all key information can be understood directly from the database level, without needing to open individual pages—using toggles, collapsible sections, and multiple database view modes (or other appropriate tools).
- Finally, Visual Content Specs must be easily and frequently referenced from within each Creative Brief Plan, reinforcing a clear link between written direction and visual execution.
PLEASE NOTE
I’ll be asking to sign a NDA - non disclosure agreement, requesting full privacy of this project once we begin working together
CURRENT CREATIVE BRIEF PLAN DATABASE STRUCTURE DETAILS:
Each “Creative Brief Plan” has a corresponding Notion database that houses key text and images, structured as follows:
- Header Row — 7 different Properties (the properties are: 1 Subliminal Messages; 2 Visual Inspo; 3 Sounds & Music Audio (+source); 4 Text Audio (+source); 5 Editorial won’t say; 6 Summary of 2 Lines (+details); 7 Tangents I won’t go into (Not to be confused with..))
- Header Column — 6-10 different ”Topic” Pages (First page used as the “Umbrella Summary” page)
- Under each “Topic“ Page, [as Sub-items] there are 3 “call out” pages (referencing other existing pages with a “@”), including: 2 “City“ Pages and “Cultures | Archive” page. ”City” Pages live in the database titled ”Cultures | Archive”. “City” Page names are ”Yucatan” and ”Aegean”. This list of “City” Pages will expand to more City names.
I am currently in the process of populating the 6 “Creative Brief Plan” databases by adding the necessary info under each listed property above (the Header Row). The “Topic” Pages populate a description, while below as a toggled sub-item, the “City” Pages populate city-specific data which includes text, links and images.*
The structure is as follows (listing the Header Columns titles):
- The Parent Page — “Topic” Pages: A description under each of the 7 properties, explaining what it is
- Child Page 1, as a toggled sub-item — “Cultures Archive”: Examples of data for the descriptions above under each of the 7 properties
- Child Page 2, as a toggled sub-item — “Yucatan” Page 1, titled“Yucatan”: City-specific data under each of the 7 properties
- Child Page 3, as a toggled sub-item — “Aegean” Page 2, titled “Aegean”: City-specific data under each of the 7 properties
*The problem here is many duplicate pages are created, both an original page and creating a whole new page on this database.