A pipeline reviewed every day against rules the team wrote, with each flag sent to the person who can act on it.
Problem
Deals go quiet without anyone deciding they should. Follow-ups are missed because the reminder lived in one person's notes, and the pipeline review meeting spends its time finding out what changed instead of deciding what to do.
The cost is lost opportunities that nobody chose to lose, and a forecast built on records that are out of date.
Typical applications: sales pipeline monitoring.
Shape
The steps below are platform-neutral. A platform page shows which vendor capability carries each one.
- Write down what stale means for each stage, in days and in missing next steps.
- Review every open record against those rules on a schedule.
- Flag the records that break a rule to their owner, with the reason.
- Prepare a short brief before a scheduled meeting, drawn from the record's history.
- Suggest a next action for the owner to accept, change or dismiss.
- Escalate records that stay flagged past an agreed period.
Control set
The control set is part of the design, not a follow-up. Each control is agreed with the process owner before the build starts.
| Control | How it is met |
|---|---|
| Review | Suggestions are suggestions. Nothing is sent to a customer or prospect, and no stage is changed, without the owner's action. |
| Data | The workflow reads pipeline records and their activity history. Meeting content is included only where the team has agreed to record meetings. |
| Monitoring | Flags raised, flags acted on, flags dismissed and time to action are tracked. A high dismissal rate is a signal that a rule is wrong. |
| Off switch | The daily review can be paused for a team or a stage without affecting the records. |
| Correction | A wrong flag is dismissed with a reason. Reasons are reviewed and the stale rules adjusted. |
Measures
Reference design. This pattern has not yet produced measured results in a C9D Consulting engagement. The targets below are examples of the shape, not results and not promises. Real targets come from the baseline measured in the diagnostic.
| Baseline | Metric | Example target |
|---|---|---|
| Open records with no next step | Records without a dated next action | None older than the stage's limit |
| Time a flagged record waits for action | Median time from flag to action | Within two working days |
| Time the review meeting spends on status | Meeting time spent establishing status | Most of the meeting spent on decisions |
Handoff
At the end, the client team owns:
- The written stale rules per stage and the playbook for changing them
- An escalation path with named people
- A runbook for pausing the review and handling dismissed flags
- Champions on the team that owns the pipeline
Where it applies
| Platform | Application |
|---|---|
| monday.com | AI Enablement on monday.com |
A platform that is not listed has no published application yet. The pattern itself does not depend on any one vendor.
Engagement
This pattern is not sold on its own. It is delivered through the engagement shapes in the Engagement Specification.
- E-01 Decision Advisory. Settles whether this pattern is the right first move, on which process and on which platform. It starts with a diagnostic and ends with the playbook handoff.
- D-01 Delivery Engagement. Where the client wants the workflow built, the build ends with working software and its playbook.
Read the Engagement Specification, or request a conversation.