§19 — Missing Documents, Images & Renderings Register

Status: [DRAFT — register, will be maintained]

Principle: Name what is missing, who has it, and what we have asked for. Nothing accusatory — just a clear ledger.

19.1 Why this section exists

A platform of this scale generates thousands of documents — design drawings, renderings, photography, technical specs, bond documents, lease detail, vendor agreements, MOUs, board minutes. Not all of them are with us.

Some of that is fine: many documents live correctly with the parties that own them (NBCU's, Gray legal, bond counsel, design firms). Some of it is not fine: documents that should be in the campus operating record are not, or have not been transmitted on closeout, or are sitting with the developer / architect / designer in a way that is friction-inducing rather than policy-driven.

This section names what's missing — calmly. It is not an accusation document. It is a request register.

19.2 The register (initial — to be maintained)

Item	Type	Custodian (where it likely sits)	Status	Action
Phase 1 record drawings (full set, as-built)	Drawings	HGOR / Gipson / GC	`[REQUESTED]`	Formal closeout request
Phase 1 design renderings (master set, current versions)	Imagery	Architects / designers	`[PARTIAL]`	Identify what we have vs. what exists
Phase 1 progress photography (build-out, monthly)	Imagery	GC / developer / Gray comms	`[PARTIAL]`	Consolidate into single archive
Backlot specifications (each facade set)	Specs	NBCU + builder	`[INTERNAL]`	Held appropriately by NBCU; campus-side reference summary needed
Stage 5 / immersive partner concept renderings	Imagery	Partner candidates	`[NOT YET — partner-specific]`	Per-partner during MOU
Pringle (amphitheater) design package	Drawings + renderings	Designer	`[REQUESTED]`	Formal request
IMAX entertainment complex design package	Drawings + renderings	IMAX + designer	`[REQUESTED]`	Per IMAX partnership
Hotel design package	Drawings + renderings	Hotel JV designer	`[NOT YET — JV-pending]`	Per JV milestone
Hotel Bel-Air visual references / mood-boards	Imagery	Designer	`[REQUESTED]`	Formal request
Dale Chihuly exhibit hall concept	Concept docs	Designer + artist team	`[REQUESTED]`	Formal request
Master plan (current canonical version)	Plan docs	Developer / planner	`CONFIRM`	Confirm version of record
Phase II detailed master plan	Plan docs	Planner	`[PARTIAL]`	Consolidate
LED tower technical specs	Specs	Vendor	`[REQUESTED]`	Operating reference
Public park / 5-acre programming master	Concept	Designer + ops	`DRAFT`	Build campus-side
MARTA station / mobility coordination memos	Plan docs	CDCID / MARTA / GovRel	`[REQUESTED]`	Through GovRel seat
CID, TAD, SSD bond documents (originals + amendments)	Legal	Bond counsel / Gray legal	`[INTERNAL]`	Confirm campus access copy
NBCU lease (full copy + amendments)	Legal	Gray legal	`[INTERNAL]`	Held privileged appropriately
Lease abstracts (operating reference, not full lease)	Legal summary	Gray legal	`[REQUESTED]`	Operating-level need
Production tenant MSA / sub-lease summaries	Legal	NBCU / Gray legal	`[REQUESTED]`	Per partnership protocol
Insurance policies (master + venue-by-venue)	Legal	Risk / broker	`[REQUESTED]`	Safety/Risk Officer task
Vendor master list w/ contracts	Operating	Operations	`[BUILD]`	New build
Brand asset register (logos, marks, fonts, photo library)	Brand	Marketing / outside firm	`[REQUESTED]`	Marketing seat task
Press archive (all coverage, by year)	Brand	Comms team / agency	`[BUILD]`	Marketing seat task
Board minutes (campus governance entity)	Governance	Counsel	`[INTERNAL]`	Confirm campus copy
Annual safety / inspection reports	Safety	Operations + outside	`[BUILD]`	Safety/Risk Officer task

19.3 Why the register stays in the master doc

Two reasons:

1. Visibility. The CEO sees, at a glance, what we have asked for and have not received. That visibility — held neutrally — is the only durable forcing function.

2. Fairness. Each item names where it likely sits, not who is at fault. Many gaps are normal (privileged with the right party). Some are friction. The register lets both kinds resolve calmly.

19.4 The closeout standard (going forward)

To prevent this from recurring on Phase II:

1. Every contract has a closeout package definition — record drawings, specs, warranties, brand assets, photography, vendor list — owed to the campus operating record at substantial completion.

2. Closeout packages are a payment milestone, not a goodwill request.

3. The §22 register has an entry per closeout package, opened at contract execution, closed only when received.

This is industry-standard practice. We are not inventing anything — we are making sure it happens.

19.5 Open items

TBD Confirm canonical master plan version with developer + planner.
TBD Set first formal closeout request packet (single document, polite, dated, listing each item).
CONFIRM Custodian seat for the campus document of record (recommend Operating Lead).

The tone of every request: "We are building the operating record for the platform; please send the items below." No accusation, ever. The register is the safeguard.