Marketing Kitchen

Shared production view: what we are making, what ingredients exist, what is missing, who has the next move, and what is ready to publish.

Kitchen operating rule

Menu → Ingredients → Production → The Pass → Schedule → Results. Done is better than perfect, but public technical claims still pass Mark. A blocker must include a proposed next move.
Weekly menu
0%
Average production progress
Cadence
3/wk
Main posts; adapted across channels
Ingredient gaps
0
Requests still needed
Waiting at Pass
0
Items needing Mark review
Content equity
0:00
Toward 7:00 useful published hours
Library readiness
0%
Infrastructure checklist

This Week's Menu

Three principal outputs. Each piece has one audience, one job, one stage and one clear next move.

Production Line

Where the work is physically sitting.

Next Moves by Station

One highest-value move per role; not a wall of tasks.

Ingredients Needed

Missing footage or information stopping a menu item.

Field Radar

Upcoming ICC work that creates capture opportunities.

Team Now

Kitchen Systems

Production line

Every content item moves through the same visible stages. No hidden piles of almost-finished work.

Add Pantry Asset

Index the ingredient before deciding every campaign it may support.

Pantry rule

RAW FILE → TIMECODED SEGMENT → TAGS → QUALITY → SEARCHABLE INGREDIENT → CAMPAIGN MATCH → EDIT Do not create dozens of duplicate files just to identify useful moments. Reference the source and timecode whenever possible.

Indexed Ingredients

Searchable working inventory.

Request Ingredient

Danaya, Mark or AI identifies what is missing. Zach receives a precise shopping list.

Good ingredient request

Waterloo Before-condition wide shot Horizontal + vertical safety take 10–20 seconds Visible deterioration Needed for: September waterproofing / manager education Due: before crew begins work

Ingredient Board

Add Field Opportunity

Marketing does not need full labour management here; it needs visibility into where ICC work creates media opportunities.

Field operating rule

Where are we working? What is happening there? What should be captured? Who can capture it? What is the minimum acceptable coverage if Zach cannot attend? What needs to be in the pantry afterward?

Field / Capture Radar

The Pass

Mark is not approving every creative keystroke. The Pass exists for technical truth, commercial risk and final publish readiness.

Approval standard

CHECK: • Technical claims accurate? • Product/system terminology correct? • Client/site confidentiality respected? • Safety representation acceptable? • Commercial call-to-action sensible? DO NOT HOLD FOR: • Minor subjective creative preference • A different transition Mark personally prefers • Endless polishing with no business impact

Publishing Calendar

Target three principal posts per week. Platform adaptations can multiply distribution without multiplying the core production burden.

My Task Progress

0%

Communication standard

CAN — I can do it. DOING — I am doing it; here is the output/ETA. BLOCKED — I tried X/Y; here is the blocker and my proposed move. CANNOT — I cannot do it; here is the reason and alternative.

My Current Tasks

My Production Handoffs

Log Completed Work

Make business movement visible without turning the kitchen into surveillance.

Management test

Paid time → identifiable ICC work → visible result/evidence → next action. Effort is valid context. Output and movement are the operating record.

Work History

Published pieces
0
Tracked in calendar/menu
Qualified inquiries
0
Commercial signal
Canada audience
Average where recorded
Relevant audience
Decision-maker relevance where recorded

Add Result

Scoreboard principle

Relevant Canadian decision-maker reach > raw global views. Track: • audience geography • property/facility/engineering relevance • company/profile visits • qualified inquiries • opportunities influenced • useful content accumulated Virality is useful only when it helps the right audience.

Results History

Infrastructure supports output; it does not pause output.

Temporary selected-file handoff can operate while the permanent NAS, Media Agent and searchable AI library are being completed.

Kitchen Systems

Target architecture

FIELD CAPTURE ↓ RAW ICC STORAGE / NAS ↓ MEDIA AGENT + INDEX ↓ PANTRY (metadata + proxies + timecodes) ↓ MENU / CAMPAIGN SEARCH ↓ PRODUCTION ↓ THE PASS ↓ PUBLISH + RESULTS Temporary mode: Selected files → Google Drive / direct handoff → production.

Backend roadmap

Current browser version: localStorage operating model. Next shared layer: • Cloudflare D1 — menu, tasks, requests, assets, field radar, work logs, approvals, results • Cloudflare R2 — proxies, thumbnails, manifests, approved exports • NAS / ICC Media Agent — file manifest, metadata, thumbnails, proxies, timecoded segments • Cloudflare Access — real user identity / role mapping • AI layer — semantic footage search, campaign matching, missing-ingredient detection No employee compensation or private management commentary belongs in this operating interface.