Tasks Ready for Assignment — Corporate

Filter applied (corporate equivalent of the TrackVia view Tasks Ready For Assignment - My Division, view 2607 / filter 3955, with the division scoping removed):

• Assigned Task Date is not blank
• AND Team (Task Team) is blank
• AND Completed Date/Time is blank

• 12,642 task records pulled; 8,329 have an assignment date; 226 of those have no team; 152 remain after excluding 74 already-completed tasks that were never credited to a team (a data-hygiene population, not a backlog).
• Team and Team Name agree on every record (0 disagreements), so "no team assigned" is unambiguous.
• 0 matching tasks carry a status other than Unassigned.
• Unlike the division view, the assignment date here is not capped at 7 days out — the full overdue tail is shown, which is the point of a corporate view.
• The source view is scoped to active jobs (no Cascade Final date), so finaled jobs are out of scope. A task on a finaled job that is still unassigned will appear in the division view but not here.
• Task-type ordering. The pivot lists task types in construction sequence. 9 of the 21 carry their real order code, read off the TrackVia view; 12 are positioned by their observed median offset from the job's 4-Way date (checked against the known codes at rho 0.97); 0 had too little history to place and sit at the end. Granting this report's API user the Tasks table order field would make all of them exact.

Crew availability (the trade-axis tables) comes from MCP Task Team Info (view 2835), 300 crews, filtered to the hand-raise checkbox ¿Listo para otro trabajo?:

• A crew counts as available to every division in its coverage list — that field is a generated list of division names, so a crew whose home division is one place but who covers another appears under both. Home division is shown in the drill-down, and visiting crews are marked.
• This is not TrackVia's Hand Raise Queue. That queue is view 2608 on the Coverage Areas table, one row per crew-trade-division, ranked by Spot in Scheduling Queue within each division-trade. That table has no API view at all, so neither the hand-raise time nor the queue position is shown here, and a crew is counted once per division rather than once per queue row — so this count can differ from the queue's row count.
• Task type to trade is inferred, not read. The authoritative field (Tasks :: Trade) exists but appears in no view, so the mapping here comes from ~11,000 real crew-to-task assignments, keeping only the unambiguous ones. 12 of 152 tasks — the catch-alls any trade performs, plus Scratch Coat, which resolves to Rock at only 50% — are deliberately parked in Any trade rather than given a column that would look precise and be wrong. 140 are mapped.
• Crew counts exclude nothing else: a suspended or zero-headcount crew with the box checked still appears. Crew size, rating, last completed task and hand-raise red flags are in the drill-down so you can judge.