When to open it
At the start of any KiNETiQai work session
Open Master Tracker whenever you're about to work on KiNETiQai client or build work. It's your reference — not your cockpit (that's KaiBoss OS). Sequence: Open KaiBoss OS first to set your zone and priority → then open Master Tracker to check client NIAs and build phase status for that session.
Tab 01 · Clients
After every client interaction — update the card
After a call or email: Find the client card → click "Notes" → add what happened, what was decided, what the new NIA is. Change the progress status if something moved. Adding a new lead: Click "+ Add Client" → fill in name, priority, vertical, contact info, and NIA. Rule: Every client card should always have a current NIA. If it doesn't, something is stale.
Tab 02 · KaiBoss Build
Check off items as you complete them — add notes when blocked
Completing a task: Click the checkbox row to mark done. If blocked: Click "Notes" → set status to "Blocked" → describe what's blocking. Adding a new build task: Click "+ Add Task" in the relevant phase → fill in the label and optional context. Rule: If you finish a build phase, bring the completion to Chief → Chief logs it in Notion session handoff.
Tab 05 · GovCon
Don't touch until SAM.gov UEI is active — then work top to bottom
The checklist is gated. Item 1 (SAM.gov UEI active) must be checked before anything else starts. Once it's checked, work down the list sequentially. Each item feeds the next. Bring VS Code build output back to Chief after each item.
⚡ Chief Summary button
Generate before every session close or major handoff
When to use it: End of a KiNETiQai work session, before bringing findings to Chief, before a client call, or any time you need a status snapshot. What it produces: A formatted summary of all client statuses, build phase completion %, notes on blocked items, and open NIAs — ready to paste directly into a Chief session. How to use it: Click "⚡ Chief Summary" tab → review the generated text → copy → paste into Chief chat with "Chief — here's my tracker summary, what's the NIA?"
Adding items
Any tab with a "+ Add" button supports custom rows
Clients tab: add new leads or clients. Build tab: add tasks to any phase. GovCon tab: add scanner tasks. Rule for adding: Only add items that have a clear owner (you) and a clear NIA. Don't add vague backlog items — keep this tracker actionable, not a dumping ground.
Relationship to your other tools
Each tool has one lane — don't merge them
KaiBoss OS (kaiboss-os.vercel.app) — daily cockpit, zone/priority/open loops. Open this first every session. EYCC Sync Center v3 — Division 1 only. Wednesday syncs and QB pulls. Completely separate lane. TMS Call Brief v3 — in-call tool for Palmier TMS sessions only. Open before every TMS call, close when call ends, bring findings here. GHL Launch Sprint — active parallel tool. Run both until Sprint tracks are complete, then retire the Sprint. See Tab 06 · Tool Map for the full breakdown.
Saving your work
This tracker uses localStorage — it saves automatically in your browser
Checkboxes, notes, status changes, and new items all save to localStorage in the browser you're using. This means: If you open the file in a different browser or on a different device, your data won't be there. Solution: Always use the same browser on the same device. When you generate a Chief Summary and paste it to Chief, that becomes your cross-device backup in Notion. Do not rely on this file as your only record — Notion is the system of record.
When to bring Chief in
After every build phase completion or client status change
This tracker is your working reference. Chief is your sync and decision layer. Rule: When you complete a build phase → bring Chief Summary to Chief → Chief updates Notion session handoff. When a client status changes significantly (deal progresses, proposal sent, first payment received) → bring to Chief → Chief logs the decision and updates the handoff.