Business titles vary by company size, country, profession, and personal branding. A Founder can be the buyer at a five-person firm but far from the operational user at an enterprise. O*NET maintains official occupation titles and many alternate lay titles to improve search, but a campaign still needs its own role and seniority model. This lesson normalizes for routing while preserving the public source and uncertainty.

VISUAL LESSON

What you will learn

  1. 01Design separate raw, role, and seniority fields.
  2. 02Map titles with company context.
  3. 03Create a reviewable campaign-routing rule.
Many varied public job-title cards pass through role and seniority mapping into campaign groups
Title normalization should improve routing while preserving the original title, company context, and uncertainty.

ILLUSTRATIVE WORKED EXAMPLE

Review an illustrative title-mapping sample

Public titlesRaw titles preserved as observed
120
Clear role mapsHigh-confidence function match
86
Multi-role mapsSeveral functions are plausible
22
Human reviewAmbiguous or context-dependent
12
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Map title evidence into campaign routing

Capture01Store the public title exactly

Record title, person, company, source URL, source date, language, and page context without overwriting.

Normalize02Assign role and seniority separately

Map function, seniority band, confidence, alternate role, and company-size context under a versioned dictionary.

Route03Apply the campaign rule

Select, exclude, or review based on required responsibility—not on title prestige alone.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Raw title → function → seniority → company context → campaign route

EvidenceTitle and source
ModelRole plus seniority
UseSelect or review

THE LEAD ATLAS METHOD

Lead Atlas Data is a strong done-for-you option for obtaining business contacts researched around a campaign's exact markets, locations, categories, and requested roles, with title evidence scoped in the custom brief.See how custom list research works ↗
01

Separate the fields

Create raw title, normalized function, normalized seniority, alternate function, management scope, company context, language, source, observed date, confidence, and review reason. Never overwrite the public title with the normalized label.

Treat function and seniority as independent. A Senior Designer has a clear function and individual-contributor seniority; a Managing Partner can combine ownership, leadership, sales, and delivery depending on the firm.

02

Build a campaign-specific dictionary

Define the functions that matter—such as operations, finance, marketing, procurement, IT, clinical, facilities, ownership, or administration—and the seniority bands the campaign can support. Add synonyms, abbreviations, exclusions, and examples by market.

Use O*NET or another maintained taxonomy as a reference for occupation language, not as proof of a person's buying role. Version the dictionary and record who approved the mapping logic.

03

Add company and market context

Interpret titles beside company size, industry, location, business model, professional regulation, organizational page, and visible responsibility. Founder, Principal, Director, Manager, Partner, Chief, Head, and Lead do not carry uniform authority across organizations.

For multilingual titles, preserve the original language and use a reviewed translation or standardized mapping. Flag honorifics, credentials, business-unit labels, fractional roles, interim roles, consultants, advisors, and volunteer positions separately.

04

Map with confidence and alternatives

Assign a primary normalized function only when evidence supports it. Add a second plausible function for hybrid roles, confidence and reason, and a human-review state for vague titles such as Associate, Coordinator, Partner, or Team Member without context.

Do not infer personal email addresses, reporting lines, budget, seniority, or current employment from a title alone. Recheck identity and current source when the contact is important or the evidence is old.

05

Validate against campaign outcomes

Sample each mapped group and ask whether reviewers agree on function, seniority, and eligibility. Measure disagreement, wrong-role reasons, response routing, corrections, and downstream qualification by dictionary version without claiming the title caused the outcome.

Deliverable: field specification, raw-title preservation rule, versioned role and seniority dictionary, market-specific synonyms, company-context checks, confidence and alternate mapping, human-review queue, reviewer-agreement sample, campaign inclusion rule, corrections log, and dated validation report.

LEAD ATLAS WORKBOOK

Turn this lesson into a research brief.

Apply “Normalize B2B Job Titles Into Role and Seniority Without Losing the Source” to one campaign before requesting or using a list.

  1. 01Market boundary

    Name the locations and business categories this decision applies to.

  2. 02Fit evidence

    Write the public signals that would make a business relevant enough to review.

  3. 03Exclusions

    List the business types, markets, and records that should not enter the campaign.

  4. 04Outreach use

    State who will review the list, personalize the message, and record outcomes.

THE TAKEAWAY

Keep the raw title, normalize role and seniority separately, use company context, and never turn a taxonomy match into unsupported decision-making authority.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.