ICC Marketing Command Center v25

ICC operating rule

Do not report effort alone. Record the problem, action taken, evidence/output, result, blocker if any, and next move. Mission Control should show what changed without Mark having to chase for an explanation.

Open work

0

Tasks not yet complete.

Crew on site

0

Reported status, not GPS tracking.

Work logged today

0

Completed-work records entered today.

Danaya-ready

0

Assets currently available for creative work.

Mark

Set commercial priorities, approve technical truth, remove real blockers, review results.

Zach

Capture, Matterport, crew coordination, storage/source mapping, footage indexing and visible work output.

Danaya

Campaign ideas, hooks, scripts, creative packaging, platform direction and missing-footage requests.

Operations / Crew

Report where the crew is scheduled, current site/status, what changed, and operational blockers.

Latest completed work

Reported crew status

How ICC communicates

Problem → Action → Evidence → Result → Next move Bad: “I have been trying things but I keep getting blocked.” Good: “YouTube upload blocked. I tested A and B. Existing 8th Ave assets are mapped here. I moved the review workflow to NAS folder X. Next I am indexing Calgary while the upload restriction clears. I need one decision from Mark: Y.”

My Work

Operating standard

Command Board

Task, owner, status, deadline and blocker. Work belongs here when it requires a next action.

Crew / Job Update

Use this to report where people are scheduled and their current operational status. This is manual reporting until the shared backend is connected.

Crew control rule

Every active field day should answer: • Who is working? • Which job/site? • What are they doing? • Current reported status? • Who is coordinating? • What changed? • What is blocked? • What happens next?

Important“Where are the crew?” currently means the latest reported site/status entered here. It is not automatic GPS location tracking.

Current Crew / Job Board

Latest reported operational picture.

Completed Work Log

Log work as it happens. Crew coordination, meetings, troubleshooting, uploads, Matterport, capture, editing and organization all count when they produce a work result.

Zach / team problem-solving standard

1. State the issue in one line. 2. Say what you already tried. 3. Show what was produced anyway. 4. Give the evidence/location. 5. Propose the next move. 6. Escalate only the decision you cannot make yourself. A blocker explains a condition. It does not replace output.

Management testPaid time → identifiable ICC work → visible result/evidence → next action.

Work History

Campaign Planner

Campaign direction comes from Mark + Danaya + the Command Center. Zach should not have to invent the campaign while reviewing every clip.

Campaign operating model

Weekly / monthly planning: Mark + Danaya + AI choose campaigns → define audience + objective → identify required footage → search existing indexed library → request missing shots from Zach → create → approve → publish → measure → improve.

A scraper shot can serve Waterproof Wednesday, engineer education, ASMR, worker craftsmanship or a parking-garage campaign. Index the shot first; assign campaigns later.

Campaign Board

NAS Library Map

Raw footage stays on ICC storage. Mission Control tracks what exists and where it lives. Automatic server scanning remains a backend step.

Required ICC structure

00_ADMIN_SYSTEM/ 01_RAW_ARCHIVE/ 02_PROXIES_FOR_REVIEW/ 03_DANAYA_WORKING/ 04_EXPORTS_FOR_REVIEW/ 05_APPROVED_OUTPUTS/ 06_SOCIAL_PUBLISHING/ 07_WEBSITE_CASE_STUDIES/ 08_MANIFESTS_TAGS/ 99_UNSORTED_INTAKE/

Storage confirmation checklist

Server principle

Raw stays home. Metadata travels. Proxies travel. Selected raw travels only when required. Mission Control is the operating/indexing layer, not the physical raw-media disk.

Asset Intake

Create a searchable record for footage, a proxy, an export or a source location.

Index first, campaign second, edit last

Source file → timecoded segment → process/area/people/visual/stage tags → quality/money-shot rating → searchable library → campaign selection → creative edit.

Do not physically chop every useful moment into a new file. The future logger should reference in/out timecodes back to the original source.

Asset Library

Danaya Feed

Clean creative inputs: selected assets, project facts, campaign objective and missing-footage requests.

AI creative brief

Publishing Calendar

No artificial Friday target. Set the milestone from the campaign and available material.

Approval Desk

Mark approves public technical claims and final publish readiness.

Tracking + Setup Checklist

Static/local functionality is live; shared data and automation remain v25 backend work.

Manual Analytics Entry

Analytics records

System Activity Log

Local browser audit trail until the shared backend database is connected.

Backend Roadmap

This v25 page now models operations, crew reporting and work accountability. The next layer makes it shared and automatic.

Next technical layer: - Cloudflare Pages Functions / Worker API - Cloudflare D1 for shared users, crew/jobs, work logs, tasks, campaigns, assets, approvals and events - Cloudflare R2 for proxies, thumbnails, manifests and exports - NAS / ICC Media Agent for file manifests, metadata, thumbnails, proxies and timecoded indexing - Cloudflare Access identity mapped to real user roles - Shared live crew/job board across devices - Optional future location check-in / GPS only if ICC deliberately chooses that policy - AI video analysis + temporal segment indexing - Campaign-to-footage search and missing-shot requests Current limitation: Crew locations/statuses and work logs entered in this v25 build are stored in the current browser via localStorage. They are not yet shared multi-user records.