HCP Tech Ranking Card

💎

Implications (per memory rule 1)

🎯 Bucket touched	Pure ST + Migrated (ST-era jobs only)
⚠️ Problem	Raw ST sold_by_id under-reports Kalen by 100% (he can't log in — Ashton creates his estimates). Without remap, commission decisions burn the wrong tech.
💰 $ at stake	Mis-credited revenue = wrong commission. Kalen invisible. Reconciles against Ramp line-items before any commission paid.
✅ Action unlocked	Apply Ashton-creates-Kalen remap rule. Filter cancels. Cross-check against Ramp before quarterly commission decisions.

📊 Full bucket diagram + 4 data-integrity findings: BSP HCP Intelligence Report · HCP Reports Hub

Active Techs (ST)

—

Top Performer (sold_by)

—

Kalen visibility

NO ST LOGIN

Attribution Method

sold_by_id

Per-Tech P&L

Tech	Jobs Sold	Revenue Sold	Avg Ticket	Close %	Notes
Kalen	—	—	—	—	Ashton creates Kalen's estimates — sold_by attribution must be remapped via Ashton-creates-Kalen rule
Ashton	—	—	—	—	Sales role + dispatcher
Wires to titan.jobs filtered job_status='completed' grouped by sold_by_id with Ashton-creates-Kalen remap applied. Endpoint pending.

Critical Caveats (per CLAUDE.md memory)

sold_by_id ≠ technician_id. sold_by = who sold the job. technician_id = who got dispatched. Use sold_by for sales credit.
Kalen has no ST login. All his estimates are created under Ashton's account. Without remap, Kalen looks like he sold $0.
Cancels excluded. Filter job_status NOT ILIKE '%cancel%' from every metric.
Ramp cross-check. Sales-credit decisions should reconcile against Ramp commission line-items before any commission is paid.

What this report closes

Closes the loop on Revenue By Tech. Revenue-by-tech shows the raw number; the Tech Ranking Card adds avg ticket, close rate, and the Kalen-remap so commission decisions are based on REAL contribution, not raw ST sold_by.