121 CRM working template · Pipeline-stage worksheet

Pipeline-stage worksheet: structure the work before configuring it.

Make each commercial stage observable and reviewable. This template provides a compact working structure, prompts for the information that matters and shows how Juniper Fitness might complete it. It is guidance, not proof of legal, commercial or operational sufficiency.

Subscribe to 121 CRM Seller, billing and cancellationRead the implementation checklist

Customer Thread

Pipeline-stage worksheet at a glance

Illustrative example

Stage purpose
State the fact or decision in plain English.
Entry evidence
Add enough evidence for another person to understand the record.
Exit evidence
Add enough evidence for another person to understand the record.
Owner and ageing response
Name who checks it and what happens next.
Human decision

Fictional completed example for Juniper Fitness, a two-site fitness studio.

Fictional completed extract

See the pipeline-stage worksheet in use

The interface illustrates a working decision record, with ownership and review visible.

121 CRM · Control responsibilities

Control questionOwnerNext check

Who can export customer data?CustomerConfirm

Who changes workflow permissions?Agreed scopeRecord

What happens at account closure?SharedDefine

Which suppliers process data?SharedCheck

Illustrative exampleIllustrative governance pattern. It does not assert that a specific technical control or certification is in place.

Inside the working system

See what each part contributes.

The CRM is easier to plan when contacts, conversations, work, access and automation are treated as separate capabilities with clear responsibilities.

Capability 01

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 use it: Makes the sales process visible so follow-up is based on stage rather than memory.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 02

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 use it: Separates progress through a process from the final commercial outcome.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 03

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 use it: Shows which customer conversations are active commercial work rather than general contacts.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 04

Tasks

Creates assigned, dated and optionally recurring actions against contacts or opportunities.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Turns the next step into owned work instead of leaving it inside notes or inboxes.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

How to use it

Complete the pipeline-stage worksheet in a short working session

Bring the people who understand the source work and the people who will own the result. Complete the first version with evidence to hand, then test it rather than polishing it in isolation.

Set a narrow scope

Name the process, team, data population and decision covered by this pipeline-stage worksheet. Create another record when the owner, purpose or risk is materially different.

Use observable wording

Write facts, rules and expected results that another person can inspect. Replace words such as “quick”, “complete” or “automatic” with a time, population, event or named responsibility.

Human review point

Record uncertainty

Mark missing evidence and unresolved decisions openly. Do not turn an unknown entitlement, data condition or approval into a positive answer simply to complete the sheet.

Fields to complete

The four parts of this pipeline-stage worksheet

The prompts are deliberately small. Add a field only when it changes configuration, testing, ownership or a later decision.

1. Stage purpose

Describe stage purpose for the exact scope being reviewed. Include the source of the information, the person responsible for keeping it current and the evidence that would show the entry is wrong or incomplete.

2. Entry evidence

Describe entry evidence for the exact scope being reviewed. Include the source of the information, the person responsible for keeping it current and the evidence that would show the entry is wrong or incomplete.

3. Exit evidence

Describe exit evidence for the exact scope being reviewed. Include the source of the information, the person responsible for keeping it current and the evidence that would show the entry is wrong or incomplete.

4. Owner and ageing response

Describe owner and ageing response for the exact scope being reviewed. Include the source of the information, the person responsible for keeping it current and the evidence that would show the entry is wrong or incomplete.

From record to action

Check the handover before approval

A second view shows how the recorded decision should connect to testing, exceptions and accountable human review.

121 CRM · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314

11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

Fictional example

A completed extract for Juniper Fitness

Juniper Fitness uses the template for one bounded CRM change. The example is intentionally modest: it shows the quality of a useful entry without suggesting a universal answer.

Stage purpose

The team wants one agreed record and owner for website enquiries received during working hours. Success means each valid enquiry has a source, owner and dated next action.

Entry evidence

Amina owns the working definition; Sam covers absence. The office team can edit the record, while managers can review exceptions and results.

Exit evidence

The team tests five ordinary examples plus a duplicate, an opt-out, missing information and an unassigned record. Every mismatch is logged for correction.

Owner and ageing response

A person reviews the result after two weeks. Activation or wider use proceeds only if the sample reconciles and staff can handle exceptions without a private workaround.

Review before use

Treat the template as a decision record, not a certificate

A completed worksheet helps people inspect their reasoning. It does not itself establish compliance, product availability or a successful implementation.

Check the evidence

Ask whether every important statement has an identifiable source and whether that source covers the current scope. Recheck vendor capability and account configuration separately.

Test the handover

Give the record to someone who did not write it. If they cannot explain the owner, rule, exception and next action, revise the wording before relying on it.

Set a review trigger

Review after a failed test, material process change, supplier change, new channel, altered responsibility or evidence that staff are bypassing the agreed method.

Questions about this page

Useful answers, without the sales fog.

1. Can we use this pipeline-stage worksheet without changing it?

Use the structure as a starting point, but adapt the scope, fields, evidence and approvals to the real process. Delete prompts that do not affect a decision and add only those you can maintain.

2. Is the pipeline-stage worksheet a legal or compliance template?

No. It is an operational planning aid. Obtain appropriate professional advice where the work involves legal, regulatory, contractual, clinical or other specialist obligations.

3. Does completing the pipeline-stage worksheet confirm a 121 CRM entitlement?

No. Product features and account availability must be checked against the live configuration and agreed commercial scope before implementation.

4. Who should approve the completed pipeline-stage worksheet?

The person accountable for the affected process should review it with the people responsible for data, configuration, customer communication and exception handling.

Read all CRM questions

Continue the journey

Guides Implementation checklist Lead-qualification worksheet

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing