AICRO Dashboards

Live · Week of — · — clients · Loading…
Client
Owner
Type
Status
Brief

The Bench

Each operator's stack of campaign creation tasks for the next three weeks, sorted oldest first.
How the capacity bar & bench math work

Capacity bar

Load = count of tasks currently at 80 - Needs Approval with Last Modified in current Mon–Sun.

Target = 10 campaigns/week per GTME (the floor every operator should hit).

Zones: green <80% · amber 80–100% · red >100%.

Trade-off: once a task is approved (moves to 100 - Done) it drops out of this filter. The bar can therefore decrement as the manager works through approvals. This is intentional — the bar reflects "currently sitting on the manager's desk this week," not approval cadence.

Caveat: Last Modified bumps on any field edit, not just status transitions. Edge case: if someone tweaks a field on a still-pending task, the modified-time updates. Real-world impact is low.

Bench buckets (open work shown as cards)

Open task = Status is 01 - TO DO or 50 - In Progress. 09 - On Hold is excluded.

Overdue — Due Date < today  ·  2W — Due Date within next 14 days  ·  W3 — Due Date 15–21 days out.

Due dates are visual priority signal only. They are not used in the capacity math (intentional — prevents sandbagging).

Status filter: the chip row toggles the bench between Open (default — TO DO + In Progress, due-date windowed) and Needs Approval (last 30 days of Last Modified). The Needs-Approval bench is a wider 30-day queue; the capacity bar above is strictly this week. They answer different questions.

Two-Week Calendar (capacity scheduling)

Each operator's open queue is sorted by tier rank then due date and laid out 2 tasks per weekday across the next 14 days (Mon-Fri only). Saturdays and Sundays are non-production. The position of a task in the calendar is its scheduled slot, not its due date — due date governs queue order only.

Capacity ceiling: 2/day × 5 weekdays × 2 weeks = 20 slots per operator. Tasks beyond 20 silently overflow the calendar but still appear on the bench.

Window & refresh

Tasks shown: Due Date in [today − 3w, today + 3w]. Server caches Airtable reads for 5 min. Refresh all forces a live re-pull.

Source

Airtable Task Hub (tbl1Lkez5PkvHuz3A), all open task types. Use the Type chip row to scope.

Two-Week Calendar

Each operator's queue spread 2 tasks/weekday in priority order. Due dates govern queue order, not the day they appear in.

Client Planning

One row per client. Surfaces planned vs unassigned at a glance — sort by Unassigned to see who has campaigns sitting without an owner.
How counts are computed

Total = open tasks (status 01 - TO DO or 50 - In Progress) for this client in the dashboard window, after the active Type and Brief filters.

Assigned = tasks with a GTME owner. Unassigned = tasks with no owner.

Sched W1 / W2 = scheduled into Week 1 / Week 2 of the calendar by the same capacity-based scheduler used in the Weekly Plan tab. Unassigned tasks do not schedule onto the grid (they live in Needs Assignment).

No Brief = tasks with no External Campaign Brief link.

Tier is read directly from the Airtable Clients table (Priority Tier field), 6h cache. B is the default fallback when null.

Campaign QA tab — owned by the QA dashboard session.

Their handler at /api/campaigns will populate this panel with the four-level disclosure (Client → Campaign → Settings + Sequence → Step) from their existing mock at scripts/campaign-qa-dashboard/mock.html.

Shared client filter above scopes both tabs.