Clean an unreliable pipeline without replacing bad data with guesses
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A pipeline can look cleaner after a bulk update and become less trustworthy. Moving every old opportunity to lost removes ambiguity from the screen, but it also turns silence into a claim about the buyer. Merging similar opportunities can erase the distinction between two purchases. Filling empty fields from a seller’s memory can make an unsupported stage look verified.
The safer approach is to freeze a bounded set of records, review the integrity problems with the greatest consequences first, and separate evidence-backed corrections from questions that remain open. Preserve the original values, record why each change was justified, and finish with an explicit list of unresolved cases—not a requirement that every field be filled.
The sales pipeline cleanup checklist below is built around a completed worksheet. It covers one cleanup pass, not contact deduplication, deletion rules, recurring pipeline meetings, or forecast reconciliation.
1. Define the cleanup boundary before opening records
Choose a set that can be reviewed as a single batch: for example, opportunities from a particular import or records owned by one team. Record the selection rule and cutoff time. Otherwise, new edits and newly created opportunities can keep expanding the job.
Before changing anything, preserve an authorised snapshot or equivalent record of the original values and relevant notes. Include opportunity identifiers, stage, owner, pause status, linked evidence references, and any fields the cleanup may affect. Keep that material within approved access boundaries.
Write down the permitted changes. A useful boundary is: correct demonstrated field errors, repair evidence references, identify duplicate opportunities, and clarify documented pauses. Do not use the exercise to redesign stages or rewrite the team’s commercial history.
Completion means every selected record has a disposition. It does not mean every record is verified. A record awaiting evidence can be fully reviewed and still remain unresolved.
2. Prioritise integrity problems, not just old opportunities
Age is useful for finding candidates, but weak as a decision rule. A recent unsupported closed-won status may create more immediate confusion than an old opportunity with a clearly documented pause.
Order the queue by the consequence of trusting the record as it stands:
- Conflicting terminal statuses: won or lost records whose supporting evidence disagrees with the status or cannot be located.
- Possible duplicate opportunities: records that may represent the same purchase and could prompt parallel work.
- Unsupported stage claims: stages whose required milestone is not evidenced.
- Ambiguous pauses: records that confuse buyer-requested delay, seller inactivity, and an unanswered message.
- Missing evidence references: records where the claim may be sound but the supporting material is inaccessible or unlinked.
Move a case higher if someone is about to act on it. Document that exception rather than silently changing the queue. If evidence conflicts, resolve the meaning of the evidence before editing the field.
This order deliberately favours integrity risk over easy wins. Fixing many empty fields can produce an impressive completion count while leaving the most misleading records untouched.
3. Decide what would justify each correction
Use the team’s existing stage criteria as the test. If those criteria are missing or contradictory, record a definition gap. A cleanup reviewer should not invent a new meaning for a stage and then apply it retrospectively.
- Stage correction: identify the milestone required by the current stage and evidence supporting the proposed replacement.
- Duplicate disposition: establish that the opportunities describe the same purchase, not merely the same account or contact.
- Pause clarification: distinguish a buyer’s stated timing from a seller’s assumption. Retain the reason and any documented review date.
- Evidence repair: confirm that the linked material belongs to the opportunity and supports the specific claim.
- Ownership repair: obtain an authorised assignment rather than inferring ownership from the last person who edited the record.
Evidence must be specific enough for a second reviewer to understand the decision. “Checked with sales” is weak. A dated note identifying who confirmed which purchase and what they confirmed is more useful. A seller’s recollection can guide the search, but it should remain labelled as recollection unless corroborated.
Missing proof of a proposal does not prove discovery is the correct stage. Missing proof of a win does not prove a loss. Where no replacement value is supported, retain the original value with a visible unresolved qualification, or use an established review status if one exists. Do not introduce a new stage merely to hide the problem.
4. Filled worksheet: a fictional cleanup batch
Fictional worked example: Every organisation, identifier, date, quantity, and outcome in this worksheet is hypothetical. This is a recommended operating design, not a description of software functionality or customer results.
Batch: Imported opportunities owned by the fictional North team, selected at 09:00 on 12 May 2026. Scope: six records, grouped into five review cases. Authorised changes: stage correction, pause clarification, evidence-link repair, and duplicate-opportunity designation. Deletion, amounts, contact records, and forecast categories are excluded.
Local stage criteria used in this example: Discovery requires a documented requirements discussion; Proposal requires evidence that a proposal was sent; Won requires documented buyer acceptance. These are hypothetical team definitions, not universal sales rules.
Queue position 1 — O-401, Cedar renewal: conflicting won status
- Original record: Won; note says “accepted verbally”; attached proposal is unsigned.
- Evidence checked: Proposal and activity notes. The owner confirms that the acceptance note was entered from memory and cannot identify a supporting message.
- Correction evidence: Insufficient to establish either acceptance or a replacement stage.
- Disposition: Unresolved. Keep the original stage, explicitly mark its acceptance evidence as unverified, and include it in the handoff exception list.
- Open question: Did the buyer accept this renewal? Owner Mira must locate or obtain confirmation by 15 May. That is a review deadline, not an assumed buyer decision date.
Queue position 2 — O-402 and O-403, Harbor equipment purchase: suspected duplicate
- Original records: Both open, under different sellers, with similar names.
- Evidence checked: Both reference the same buyer purchase request, PR-H17. The owners confirm that they cover the same purchase, not separate phases.
- Correction evidence: Matching purchase reference and documented owner confirmation. O-402 contains the fuller activity history.
- Disposition: O-402 designated as the retained working opportunity. O-403 designated as a duplicate of O-402 and excluded from the agreed working list after reviewer approval. Both histories remain available, with reciprocal references.
- Open question: None for duplicate identity. The buyer’s commercial decision remains open on O-402.
Queue position 3 — O-404, Juniper pilot: unsupported proposal stage
- Original record: Proposal after import; no proposal evidence linked.
- Evidence checked: Import mapping shows that the source value “requirements discussion” was mapped to Proposal. A dated buyer discussion note and owner confirmation establish that discovery is the current milestone and no proposal has been sent.
- Correction evidence: Demonstrated mapping error plus positive evidence supporting Discovery.
- Disposition: Correct stage from Proposal to Discovery. Preserve the original imported value and mapping explanation in the cleanup log.
- Open question: None for this correction. Proposal timing remains uncommitted.
Queue position 4 — O-405, Alder expansion: ambiguous pause
- Original record: Open; seller note says “on hold”; no reason or review date.
- Evidence checked: Buyer message requests that discussion resume after a planning session scheduled for 2 June.
- Correction evidence: Buyer-stated timing supports a pause, but not a promise to purchase.
- Disposition: Retain the existing stage. Record “buyer-requested pause pending planning session” and an internal review date of 3 June.
- Open question: Whether the buyer will resume. Do not substitute the internal review date for a buyer commitment.
Queue position 5 — O-406, Birch service package: missing evidence reference
- Original record: Proposal; attachment link unavailable.
- Evidence checked: The authorised reviewer locates the sent proposal and transmission record in the approved shared location. Opportunity identity and proposal version match.
- Correction evidence: The located records support the existing Proposal stage.
- Disposition: Repair the evidence reference; retain the stage. Confirm that the designated reviewer can access the replacement location.
- Open question: Buyer response remains unknown. Evidence of sending is not evidence of acceptance.
5. Apply changes in small groups and preserve the before-state
Separate review from execution. First propose the disposition; then have an authorised person apply it. For consequential or ambiguous changes, use a second reviewer. This is particularly useful when the reviewer is also the opportunity owner.
Group edits by their supporting rule, not by convenience. Repairing verified evidence references is different from changing stages. Two opportunities that look similar should not inherit the same disposition merely because they appeared together in a filtered list.
Check whether each record changed after the snapshot. If a seller added a new buyer message or altered the stage during review, pause that case and reassess it against the current record. Do not overwrite newer evidence with an older worksheet decision.
If an incorrect edit is discovered, restore the affected prior value from the preserved before-state, retain the cleanup entry, and add a reversal with its reason. Review other edits made under the same faulty rule. Quietly erasing the mistake makes later investigation harder.
6. Complete the disposition log, including non-changes
The log should explain what happened without requiring someone to reconstruct the reviewer’s reasoning from scattered messages. A non-change is a valid disposition when evidence is insufficient.
Completed hypothetical disposition log, 12 May 2026:
- L-01 / O-401: Reviewer Leon recorded “unresolved acceptance evidence”; original Won stage retained with explicit qualification. No replacement stage authorised. Mira owns evidence follow-up due 15 May.
- L-02 / O-402 and O-403: Leon approved duplicate identity using PR-H17 and both owners’ confirmations. Working opportunity set to O-402; O-403 retained and marked as duplicate. Reciprocal references checked. No deletion performed.
- L-03 / O-404: Mira changed Proposal to Discovery after Leon reviewed the import mapping and discovery note. Before-value preserved. Post-change stage checked against the worksheet.
- L-04 / O-405: Owner Sam added buyer-requested pause reason and internal review date. Stage unchanged. Leon checked that the date was not represented as a buyer commitment.
- L-05 / O-406: Sam repaired the proposal evidence reference. Stage unchanged. Leon confirmed that the linked version and purchase identity matched.
Batch outcome: All six records received a disposition across five cases. Four cases were resolved for the identified integrity issue; one remained unresolved. Only one stage changed. The duplicate designation preserved both histories, and no records were deleted.
Those counts describe this hypothetical cleanup, not improved sales performance. “Resolved” means the identified integrity question was answered; it does not mean the opportunity will close.
7. Close the batch with an uncertainty handoff
Publish the exception list alongside the completed log. For each unresolved case, include the unsupported claim, evidence already checked, responsible person, next action, and review deadline. Explain how readers should interpret the record in the meantime.
There is a trade-off in retaining O-401’s original stage: it preserves the before-state but leaves a potentially misleading label visible. If a supported review flag or separate exception list is available, use it prominently. Do not treat an annotation hidden in a long note as sufficient warning to people acting on the stage.
If the evidence deadline passes without an answer, record that fact. Escalate the disposition decision to the authorised owner of the pipeline rules. Do not let an expired internal deadline automatically become a loss, a win, or evidence of buyer intent.
For your next bounded cleanup, select a hypothetical-sized batch of ten records and require three observable outputs: every record has a logged disposition, every changed value has a supporting evidence reference, and every unresolved case has an owner and next review date. Check those outputs before increasing the batch size. The useful result is not a pipeline without blanks; it is a pipeline whose claims, corrections, and remaining uncertainties can be distinguished.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications