Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Picklist

A CRM field type that accepts one value from a defined list of permitted values, so that records can be reported on instead of typed in many spellings.
AnalyticsconceptUpdated

Definition

A picklist is a field type that accepts one value from a defined list of permitted values. The CRM fundamentals guide lists it among the property types that matter, beside short and long text, multi-select, number, date, true or false and lookup, and gives it the shortest definition: one value from a list.

Two neighbours are easy to mix up with it. A multi-select field accepts several values from a list, which suits a contact's interests but not a field that reports must count once per record. A lookup field points at another record rather than holding a value of its own.

Why it beats free text, and its limits

The fundamentals guide calls choosing a picklist wherever a free-text field would do the single most useful habit in CRM design, because free text cannot be reported on. A field called industry with values typed by hand produces dozens of spellings of the same thing; a picklist produces a report. Routing, scoring and segmentation rules depend on exact values, so they inherit the same benefit.

Its limits are about where data comes from. The guide to standardising CRM field values points out that picklists solve the problem only at the forms and screens the business controls. Ad platform lead forms, event lists, integrations and records created by hand all bring values from outside, so a picklist still needs a workflow that maps incoming raw values onto it. Some fields should not be picklists at all: job titles are too varied to fit a list, so the title stays as typed and a separate role picklist holds the version that rules use.

In practice

  • Audits. The tutorial on auditing and documenting CRM fields records each field's type and permitted values. A picklist with options nobody chooses needs pruning, and a free-text field with a short list of recurring answers is a picklist waiting to be built.
  • Conversions and imports. Converting a field means mapping every old value to an agreed one and changing every form, import template and integration that writes it, or the free text comes straight back.
  • Migrations. The guide to moving to a new CRM maps every picklist value by value, because a value spelled one way in the old system and another in the new will split every report.
  • Reason codes. The guide to lead stages and pipeline has sales reject a lead with a reason chosen from a short picklist agreed by both teams, which is what makes the reasons countable.
Illustrative example — not a real result

A freight firm turns an unusable field into a report

Ombrevast Freight, an invented road freight company, wanted a report of won deals by customer industry. Its industry field was free text, and across 8,600 company records it held 412 distinct values, including 23 spellings of food and drink manufacturing. Marketing and sales agreed a list of 15 industries, mapped every old value to one of them, sent the 57 values that fitted nowhere to a review list, and converted the field to a picklist. The website form and the two lead sources that wrote the field were changed the same week, and a workflow now maps raw values from event lists. The first report split won deals across the 15 industries and showed that 2 of them accounted for nearly half the revenue.

A CRM is the system whose fields picklists belong to. A Lifecycle Stage is one of the most important picklists in it, recording where a contact stands. A Naming Convention does for campaign names and tracking parameters what a picklist does for a field: limits the spellings so reports can group them. Cardinality is the number of distinct values a field holds, which is exactly what a free-text field lets grow and a picklist keeps small.

Common confusions

  • A picklist is just a nicer form control. Its value is the fixed list of permitted values, which is what reports and rules rely on; a form that keeps sending free text into the field undoes it.
  • More options make it more accurate. Inventing an option for every odd value fragments the report again. Map to the agreed set and review the list on a schedule.
  • Creating the picklist fixes the data. Every writer of the field must change too, and the old values must be mapped, or the problem returns.
  • Every field should be a picklist. Some answers, such as job titles, are better kept as typed with a picklist beside them for the version the rules use.

More terms to look up

Where this term is used

Related