---
title: "When a picklist rename silently broke a dozen pipeline reports"
type: case-study
evidence_type: proof
category: "Attribution & Lead Lifecycle"
publisher: "LeanScale"
date_modified: 2026-08-08
word_count: 389
topics: ["demand-generation", "revenue-operations"]
canonical_url: https://knowledge.leanscale.team/customers/fixing-bdr-attribution-and-territory-routing/
source: "LeanScale Knowledge Hub — https://knowledge.leanscale.team"
license: "Free to quote and cite with attribution to LeanScale."
---

# When a picklist rename silently broke a dozen pipeline reports

**Evidence type:** proof (what happened)

A B2B software company could not reconcile what its BDR team generated with what its dashboards showed. LeanScale rebuilt inbound and outbound attribution, re-keyed territory routing, and found the reports that had been quietly filtering on a dead picklist value.

## The challenge

Inbound and outbound BDR attribution did not reconcile with the revenue-generation numbers leadership reviewed. Meeting types were mapping inconsistently from two different inbound scheduling tools, and territory routing was assigning leads on rules that no longer matched how the team was carved up. A stage picklist value had also been renamed at some point, and nobody knew how many saved reports had been silently filtering on a value that no longer existed.

## The approach

BDR attribution and reconciliation reporting
Built inbound and outbound BDR attribution reporting and a revenue-generation reconciliation dashboard, so sourced-meeting counts could be tied back to pipeline instead of argued about in a meeting.

A full report audit after the picklist rename
Audited roughly 200 saved reports named for the sales-accepted-lead stage, isolated the ones whose status filters had been silently broken by the picklist rename, repointed each to the current value and re-verified the output — treating a rename as a reporting migration rather than a field edit.

Territory routing rebuilt on the real coverage model
Rebuilt territory routing on new round-robin objects keyed to territory region and account size, replacing rules that no longer reflected how the team was actually covering the market.

Consistent meeting source across two booking tools
Fixed meeting-type mapping across two inbound scheduling tools so booked meetings landed with a consistent type and source, and remediated the downstream reporting fallout from the earlier stage rename.

Ownership backfilled across the whole book
Ran a temporary flow to backfill the account-manager field on roughly 3,000 existing-business, cross-sell and renewal opportunities, so ownership reporting worked across the installed base and not just new business.

Post-sale handoff automation
Wired provisioning-complete signals into onboarding round-robin assignment with Slack alerts, plus a sales-to-post-sale handoff template and 60-day trial check-in reminders, so the lifecycle did not go dark at closed-won.

## Outcomes

12 silently-broken reports found and fixed
An audit of roughly 200 saved reports named for the sales-accepted-lead stage found 12 whose status filters had been silently broken by a picklist rename; all 12 were repointed to the current value and re-verified.

~3,000 opportunities backfilled with an owner
A temporary flow backfilled the account-manager field across existing-business, cross-sell and renewal opportunities so ownership reporting covered the full book.

Routing re-keyed to the actual coverage model
Territory routing was rebuilt on new round-robin objects keyed to territory region and account size.

## Quotes

> With other clients that you've worked with or other Salesforce instances you've worked with, is it typical to like create new fields and not display them by default or do you typically display them by default?
>
> — Customer, Systems and data lead


## Canonical

https://knowledge.leanscale.team/customers/fixing-bdr-attribution-and-territory-routing/