events & activations · a reusable model

An event is
a whole universe.

A launch dinner connects people, money, agreements, creative work, logistics, files, and outcomes. Make those relationships reusable, and the next project starts with a complete operating structure.

Proposed standard, informed by the NAD+ Peptide Cream launch-dinner source set. It remains a model to validate with the teams.

one project, connected areas

Everything has a role.
Everything has a relationship.

Select an area to explore its records, documents, work, and completion evidence. The same source can support several actions while keeping one original file.

Open the full-screen visual map ↗

Shared library

Formats · templates · supplier references · reviewed learnings

Event instance

Its own scope, people, budget, sources, decisions, and work

Shared memory

Contextual results and reviewed improvements for the next event

the connecting record

The event project

Purpose · lead · date · decisions · phases · key sources

example relationship

Supplier → engagement → agreement → invoice → payment evidence → event closeout

Areas describe the event’s information model. They are not eight new databases or eight sequential phases.

Strategy selected.

the reusable library

Choose the format.
Adapt the operating detail.

Every format uses the eight areas. Its audience and delivery needs change the documents, roles, and work that belong inside them.

launch dinner

A curated seated audience

Product storytelling, hospitality, guest relationships, and content capture.

a standard starting package

01
Event brief
Objective, scope, lead, date, budget boundary, and success criteria.
02
Budget and charge grid
Planned, committed, actual, payment, and evidence fields.
03
Guest and supplier trackers
People and services connected to this event.
04
Creative and production pack
Approved assets, staffing, deliveries, and run of show.
05
Closeout and learning record
Reconciled results and contextual improvements.

The format evolves.
The historical event stays intact.

Review each proposed improvement before changing a template. Apply the new version to future instances and retain the source versions that describe past events.

one original, useful connections

Where the files live.
Where the work connects.

A resource has a type, a responsible owner, a current version, a state, and its original link. Register it once and connect it wherever the team needs it.

Drive

Original documents, signed agreements, creative masters, exports, photography, and video.

the source files

Sheets

Budgets, guest lists, supplier tracking, shipments, seating, and production schedules.

the operating data

goop in Notion

Projects, tasks, decisions, meetings, review actions, contextual resources, and executive updates.

the coordination

Put the link
where it becomes useful.

Project home: Brief, master, current budget, final production plan, recap, and complete resource catalogue.
Phase or area: Its working documents and required inputs.
Task: The sources needed to perform the action and verify its delivery.
Supplier reference: Reusable service information, with event-specific engagements and evidence linked separately.

proposed resource record

A production schedule

Type: Run of show
Project / area: This event / Production
Owner: Responsible production role
Version / state: Current version / Draft, In review, Approved, or Archived
Original link: The source schedule in Sheets
Used by: Staff briefing, supplier arrivals, event delivery, and load-out

These resource states describe a proposed document convention, independent from task Status. Start the catalogue as a project section; add a shared tracker when cross-project use calls for it.

A consistent Drive structure

The same areas make files predictable to find. The event pack contains approved exports for delivery; archive versions retain their history.

00 · Brief and strategy
01 · Budget and legal
02 · Creative and assets
03 · Guests and communications
04 · Venue and vendors
05 · Production and staffing
06 · Photography and video
07 · Results and learning
99 · Archive

from one event to the next

A repeatable lifecycle.
Evidence at each handoff.

Set the workback plan from the actual event date and scope. Select a stage to see its outcome and the condition for moving forward.

Reviewed learningTemplate improvementNext event instance

the reference case

NAD+ Peptide Cream.
One instance of the universe.

The launch-dinner folder brings together strategy, budgets, guests, creative decks, supplier documents, staff briefings, production schedules, media, and a recap. The reusable model comes from the relationships between those families.

Open the source folder ↗Open the Notion test project ↗

Structure the information

Recognize the entities and document families before creating the task plan.

Connect the delivery

Give actions an owner, completion evidence, dependencies, and the relevant sources.

Improve the next instance

Keep learnings with their evidence and context. Review what should become a reusable default.

Source links require the reader’s own access. This page presents a proposed operating model; source files and the test project retain their original locations.