Sign in with your Iconic email.
Everything the team logged this week, drawn straight from their own entries.
One champion per division learns to solve real Iconic problems with Claude — building on the same in-house stack (Claude Code · GitHub · Railway) that already put the BBFA Tracker into production. The program owner coaches every spoke.
Approved and being built — and only those. Anything with a champion assigned to it lives here as a live build card: who owns it, their task, target start and completion dates, and the current build stage. It arrives automatically when it is approved on the Opportunities tab, whether it came from the TELUS assessment or from someone's submitted idea, and it leaves that queue at the same moment.
Tickets raised to IT for the AI program — access, tools, hardware, fixes. Raise one with the button below.
Three questions, kept apart because they have different audiences and different answers: is the program worth it, is each build on budget, and where is capacity going. Every figure below is a filter over one ledger of money events — click any number to see the rows behind it.
Plan capacity month by month. This auto-captures the hours already logged across every project: Hours Saved by Position becomes a Worker (capacity freed, +, to add to their day-job) and Workers & Labour build hours become an AI Champion (−, removed from their day-job scope). You can also add rows manually below. The net, by person and position, shows month by month where capacity is opening up or getting tight. 1 FTE ≈ 173 hrs/month.
Every QMS document logged across all projects, consolidated here with its approval tick-off: ① Champion uploaded procedure → ② Process manager revised → ③ Approved & in place. Documents are attached on each project's "Updates to QMS" card.
Learning resources and champion training for the AI program.
Today IPS data lives in many separate systems. To power an AI system, we first need reliable ways to pull that data into one central place. Iconic hasn't picked the central home yet — so the work runs in two phases.
For every system below, capture the method(s) to get the data out (MCP, API or other), commit a plan, then mark it complete when the extraction works. The node lights yellow when a plan is set and green when it's working.
Everything waiting on a decision lives under this tab, whichever way it arrived: ideas people submit themselves (below) and the TELUS assessment findings (the other pill above). Both are assessed by Greg, Adam, Roy and the relevant discipline manager and routed to a delivery path. Once something is approved and has champions on it, it moves to the Projects tab and leaves this queue.
The ten-business-day clock applies only to submitted ideas — someone put their name to it and is waiting on an answer. The TELUS findings carry no clock; they sit until they are worked through. Once champions are on something it leaves this page entirely and lives on Projects.
Submitted or in assessment. The clock is running — ten business days from submission to a recorded decision. Overdue cards turn red.
A decision is on the record, with the delivery path it was routed to.
Every row that adds up to it
Fully burdened cost by position — the only source of an hourly rate in this app
Who can sign in to the tracker
Opportunity Definition — the business case for a new idea
Raised to Adam — IT Technical Administrator
Every save is kept, so any mistake can be rolled back.
They appear on the org chart with their own onboarding status, and become assignable to projects.
Step 2 of 2 — who gets time back, and how much