🗣 Speakers
44 fldspeople featured in segments≈ owners & stakeholders
- ★Name
- ·Title
- ⇄Lower Third Asset
A series of interconnected bases for managing the production of a sales enablement livestream.
Every folder, filename, review link and notification in this system keys off one computed string. Parent records contribute their part; the formula assembles it; and it's properly referenced everywhere it needs to be.
informed by data rolled up from linked records
26_EVNT — event code, set once per productionPREC — deliverable typeR054 — recordingEV22279 — segment number, auto-assignedsame shape: assembled once, upstream, by formula
q3_launch_w2 — from the campaign recordrcs — from the channel recordoffer_a — from the link recordCampaign defines → channel inherits → link assembles. The string is a formula — so it is always accurate and up to date depending on the relevant variables.
Clean relationships are the foundation — Airtable layers working surfaces, automation and integrations on top of the same records.
Each team works in an interface shaped to its job — producers in a run-of-show, designers in a render queue, reviewers in an approval view — all reading and writing the same records. No exports, no copies.
Status changes trigger the next step: a record meets conditions and a notification is sent; approvals happen, and the next task is created, with the right teammate assigned based on established logic. All within the base itself.
In this system, assets move from file storage to the video-review platform automatically, and every resulting link is written to Airtable — automations talk to Box and Slack while Airtable remains the source of truth.
| ƒAsset Name | ·Status | ·Latest Draft Link | ·Latest File Name |
|---|---|---|---|
| Example Segment | EV22279 | Ready for Review | https://app.box.com/s/9f3k2m1q8w7e5r4t6y0u | 26_EVNT_PREC_R001_EV22279_Example_v1.mp4 |
Bases draw the isolation boundary — one per siloed team or workstream — and shared data syncs across them: one-way for reference directories, two-way where a team writes back. Every record keeps exactly one source of truth. Interfaces layer granular access on top: permission types and collaborator-tagged records decide who sees what, down to the row.
Timezone conversions, status roll-ups, character-count validation — all formula → lookup → rollup across linked records. The pattern of 30 Excel tabs, with sheets feeding sheets, becomes linked fields forming relationships between tables in a proper but accessible database.
The schema is managed like software: a base like this ships as a managed app — built in a development base, published to the org library, updated centrally — so connected bases inherit changes instead of drifting. Standard building blocks (a UTM builder table, link fields) publish as locked components and stay identical everywhere they're used.