Team Operations: Partner Performance Scorecard by Project Outcome

Prompt: Partner Performance Scorecard by Project Outcome

Description: Compares team members on the health and outcomes of the projects they own, using project status and candidacy progression as proxies for performance.
Frequency: Monthly or Quarterly
Connectors: Clockwork Recruiting

Prompt: (copy/paste the prompt below into your chat in your LLM)

For the trailing 90 days, build a Partner Performance Scorecard. Fetch projects with ? include=lead,owner,client_company,closing_reason,placement and display as <Company> \ <Project> throughout.

Method note: Placement detection is canonical. A filled project is closed, has closingReason.name == "Placement", and has a candidacy with status.category == "in-placed" (include=placement returns the placed person directly).

Step 1 — Pull projects from the trailing 90 days and group by owning team member (owner.id, falling back to lead.id). get_user_projects(user_id=..., status=active,closed) gives each person's book directly.

Step 2 — For each owner, compute: Active projects; Projects closed in window; Filled and fill rate (filled / closed); Approximate average time-to-fill (startedAt → closedAt for filled); Average pipeline depth (candidacies with rank >= 100 per active project); Average days-to-first-client-stage (now derivable precisely from get_candidacy_status_history — the first transition into in-contenders or higher); Stalled project count (active projects with no note in 14+ days).

Output: a ranked table with all metrics, then a 3-paragraph narrative on the standout performer, the partner whose pipeline depth most exceeds throughput (potential bottleneck), and the partner whose throughput most exceeds pipeline depth (running thin).

Adapt It: Run quarterly or annually for review Add average time-in-stage across the funnel to find where each partner's candidates stall Weight by search difficulty or fee size Focus on a single partner for a deep-dive