# Pipeline | 121 CRM > A plain-English definition of Pipeline, with a practical CRM example, related terms, common misunderstandings and implementation questions. Pipeline means an ordered view of opportunities grouped by meaningful stages in a commercial process. The meaning is useful only when the business agrees how the term appears in its own records, decisions and customer journey. ## Pipeline in a customer record Fictional example using Northstar Joinery, a six-person joinery business. ## Capabilities explained ### Pipelines Defines an ordered sales process through which opportunities can be reviewed and moved. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Makes the sales process visible so follow-up is based on stage rather than memory. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Opportunities Represents a potential sale or deal linked to a contact, value, owner and pipeline position. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Shows which customer conversations are active commercial work rather than general contacts. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Stages and statuses Uses configured stages plus open, won, lost and abandoned statuses to describe the state of a deal. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Separates progress through a process from the final commercial outcome. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Dashboards Combines supported widgets and filters into an operational view for ongoing monitoring. **How it works:** Aggregates eligible source data into configured dashboards, reports or exports. **Why a business would use it:** Helps a team review the few measures needed for the next decision. **Limitations:** A report reflects available source data and configuration; it does not prove causation or data completeness. **Human responsibility:** A person must interpret results, investigate gaps and decide what action is justified. ## What pipeline means In this glossary, pipeline is an ordered view of opportunities grouped by meaningful stages in a commercial process. Different suppliers may label fields differently, so the team should document its working definition rather than relying on a menu label alone. ### The essential idea Pipeline helps people describe a particular part of customer work consistently. Its value comes from a shared definition and an action or decision that follows from it. ### What it is not Pipeline is not a forecast, because stage information does not guarantee timing, value or outcome. Keeping those ideas separate prevents reports, workflows and handovers from combining records that mean different things. ### Why the definition matters If two people use pipeline differently, counts and automation can appear precise while describing inconsistent situations. Agree the rule before measuring or triggering action. ## Pipeline at Northstar Joinery Northstar Joinery uses the term in one bounded workflow. The example shows the definition in use without asserting a fixed 121 configuration. ### The situation Northstar Joinery receives an enquiry through its website. A record is created with the source, contact details provided and a named owner for the next review. ### The classification The owner applies the written pipeline definition to the facts available. If information is missing or the case is unusual, it is held for a person rather than classified by guesswork. ### The consequence The recorded term changes what appears in the team view, which checks apply and what next action is expected. The team can later inspect the original facts and decision. ## Questions to settle before using pipeline A glossary definition is a starting point. Configuration still needs an owner, boundaries and realistic testing. ### Which record owns it? Decide whether pipeline belongs on a contact, company, opportunity, activity or another record. Avoid copying the same value into several places without a clear source of truth. ### Who may change it? Set the role allowed to create or change the value and the evidence they should use. Restrict consequential or sensitive changes to appropriate people. ### What happens next? Document any view, task, workflow or report that depends on pipeline. Test ordinary, missing, duplicate and exceptional cases before relying on the rule. ## Keep pipeline distinct from neighbouring terms Clear language reduces configuration mistakes and makes management reporting easier to challenge constructively. ### Use examples Keep two or three fictional examples that meet the definition and one that does not. Examples often reveal ambiguity faster than a longer abstract definition. ### Align the reports Check that dashboard labels and filters use the same definition. A report should state its population, period, exclusions and data-quality limits. ### Review after change Revisit the definition when the customer journey, services, data model or responsibilities change. Update dependent workflows and reports together. ## Frequently asked questions ### Is pipeline defined the same way in every CRM? No. The underlying idea may be common, but suppliers and businesses can use different labels and rules. Record the working definition used by your team. ### Can pipeline trigger automation? It may be used in configured rules where supported, but the definition, data quality, entitlement, timing, exceptions and human responsibilities must be checked before reliance. ### How should we introduce pipeline to staff? Explain the definition with examples, show where it is recorded, state who can change it and make clear what action or report depends on it. ### Does the pipeline definition confirm the configuration in a 121 account? No. It explains public concepts using evidenced product building blocks. Live fields, permissions, workflows and plan availability require separate verification. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/guides/what-is-a-crm](https://121.direct/crm/guides/what-is-a-crm) - [/crm/features/customer-management](https://121.direct/crm/features/customer-management) - [/crm/glossary/lifecycle-stage](https://121.direct/crm/glossary/lifecycle-stage) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.