When qualified pipeline misses plan, a meeting can quickly become a dispute about channels, lead quality, follow-up, or pricing. A control sheet makes the shared funnel observable. It does not decide which team is at fault in advance; it records the evidence each owner must provide before the next decision.
1. Define the miss and the review window
Write the planned metric, actual metric, period, segment, offer, and source systems. State whether “qualified pipeline” means accepted leads, created opportunities, forecast value, or another local definition. Never compare a forecast number with a booked outcome without labelling the difference.
Name the decision: repair qualification, change a channel, improve response, adjust the offer, protect sales capacity, or hold spend. The Salesforce lead implementation guide is a useful reference for making lifecycle stages, ownership, and handoffs explicit; adapt the objects and thresholds to the local process.
2. Sign one stage dictionary
For each stage, record entry evidence, exit evidence, accountable owner, service level, ageing rule, and disqualification reasons. Separate observed behaviour from a manager’s interpretation. A lead can have a real form submission and still fail the local acceptance rule.
Add distinct states for unknown, duplicate, existing customer, not a fit, no response, and not yet reviewed. Do not force every record into accepted or rejected merely to make the conversion rate look complete.
3. Verify demand evidence
For a sample of records, capture source, campaign or content, landing page, stated problem, account context, consent state, and first meaningful action. If an event is used as evidence, check its definition and parameters against the GA4 event guidance. An event proves that a tracked interaction happened; it does not prove buying intent.
Compare source evidence with the intended audience and offer. Keep broad traffic, product interest, partner referrals, and existing-customer requests separate. If a source cannot be identified, label attribution as unknown rather than assigning it to the last visible channel.
For search-driven demand, use the Search Console Performance report to inspect queries, pages, devices, countries, impressions, clicks, and CTR. Treat those observations as discovery evidence, not as a qualification or revenue definition.
4. Audit lead acceptance
Take a fixed sample of new records and ask the sales owner to accept, reject, or request more information using the same rule. Record acceptance date, reason, next action, and time to first meaningful response. Measure rejected reasons by source and segment, but do not infer that a rejection means the channel is bad without checking the offer and follow-up context.
Escalate any rule that two teams interpret differently. A qualification definition that changes in a meeting is not a stable control.
5. Test the handoff
Trace one accepted lead from the source record to the CRM owner, notification, response, meeting, opportunity, and disposition. Record who received it, when, through which system, and what happened if the owner was unavailable. Test duplicates, out-of-office routing, missing fields, and a record that needs a different segment owner.
Keep marketing’s delivery timestamp separate from sales’ acceptance timestamp. A handoff can be technically successful and still fail because the owner cannot act on the information.
6. Review response quality, not only speed
Sample first responses for relevance, clarity, promised next step, and evidence that the stated problem was understood. A quick generic reply may satisfy a response-time chart while reducing trust. Record whether the lead reached a meeting, requested a different path, went silent, or was disqualified.
If the process uses a form or email, verify consent, routing, and the actual response destination. The owner should be able to reproduce the path without relying on a screenshot or an unlogged manual forward.
7. Reconcile opportunity progression
For accepted records, track opportunity creation, stage movement, disqualification, closed outcome, and reason. Keep sales-cycle lag visible. A pipeline miss in the current month may be a timing issue rather than a demand failure, while a high pipeline number with repeated slippage may be a quality issue.
Write the source-to-opportunity boundary: first touch, last touch, assisted, or unknown. Do not treat an attributed opportunity as revenue until the accounting or CRM outcome is reconciled.
8. Add the owner and exception matrix
| Control | Primary owner | Evidence | Escalation | | — | — | — | — | | stage definition | revenue owner | signed dictionary | executive decision | | source capture | marketing operations | event and campaign record | analytics owner | | acceptance | sales manager | decision and reason | revenue owner | | response | sales owner | timestamp and quality sample | team lead | | progression | opportunity owner | stage and disposition | forecast owner | | reconciliation | finance or revenue operations | outcome and date | executive owner |
Add an exception path for missing data, duplicate accounts, unassigned leads, and suspected consent problems. An exception is a controlled state, not a reason to silently edit history.
9. Check capacity and incentives
Ask whether the miss is caused by insufficient sales capacity, unclear acceptance, poor routing, offer mismatch, delivery limits, or a combination. Compare accepted lead volume with response capacity, meeting availability, specialist coverage, and sales-cycle length.
Review incentives that can distort the record. If marketing is rewarded for volume and sales for rejection, the shared funnel will contain predictable friction. Use a joint outcome review rather than adding a new stage to hide the disagreement.
10. Run the decision gate
| Finding | First action | Hold condition | | — | — | — | | stages disagree | sign one dictionary | no channel change yet | | source is missing | repair event and campaign capture | do not claim channel performance | | accepted leads wait | test routing and capacity | pause volume increase | | response is fast but irrelevant | review quality sample and offer | stop automation expansion | | opportunities slip stages | inspect fit and sales cycle | hold forecast claim | | outcomes cannot reconcile | repair CRM/accounting bridge | no ROI conclusion |
11. Close the loop
At the review date, record what changed, which owner accepted the action, what evidence will be collected next, and what would stop the action. Keep the previous definition and baseline so that a later improvement is not created by rewriting the denominator.
The checklist is complete when marketing, sales, and the owner can explain the same record from source to outcome, including what remains unknown. Until then, choose the smallest reversible repair and keep the material local and non-indexable pending overlap, technical, and editorial approval.
How did this article land?
Choose one reaction. You can change it anytime.
