Pomio CRM keeps deals, stages, notes and activities on linked records. A pipeline only works when each stage means something specific, and that meaning comes from the exit criteria a deal must meet before it moves on. A skip quietly bypasses those criteria. That is sometimes the right call, but it should be a visible decision by someone who answers for the forecast, not a drag-and-drop that nobody notices.
Why skipped stages are a problem
Every stage exists because something has to be true before the next step makes sense. A proposal sent before discovery is often a price list sent to someone who has not yet explained the problem. When salespeople can move a deal two or three stages forward at will, the pipeline shows deals in Proposal that have never had a real conversation about needs, budget or timing. The win rates per stage drift, conversion reports lose meaning, and the forecast counts deals as further along than they are.
What counts as a skip
Keep the definition simple so nobody has to argue about it. A forward move of one stage with the exit criteria met is a normal stage change. A forward move that passes over one or more stages is a skip, for example Qualified to Proposal without Demo or Discovery. A move backward is a correction, not a skip. Closing a deal as lost from any stage is also not a skip; it only needs a lost reason. Write these rules down as part of the shared stage definitions, so sales and management read them the same way.
Note, approval or block: three levels
Not every stage change deserves the same control. A one-stage move with criteria met needs a short note, the same habit as a note on every stage change. A skip needs a named approver and a reason. Missing hard data, such as an amount or a close date, is better handled by required fields that block the stage change than by an approval. Approval is for judgement, not for data entry, so keep it to the moments where someone has to decide whether bypassing a stage is justified.
Legitimate reasons to skip
Skips are not always a sign of sloppy work. An existing customer may order an extension that needs no discovery, a tender may arrive with the requirements already written out, or a referral may come in ready to sign. In those cases the approver records the reason, such as “existing customer, scope known from current contract”, and the deal moves on. The point is not to slow down good deals but to make the exception visible, so a pattern of skips by one person or on one product can be discussed in the weekly pipeline review.
Who approves, and how fast
Name one approver per team, usually the sales lead or the founder in a small company, with a stand-in for holidays. The approval should take minutes, not days: a short reason on the deal and a yes or no. If approvals take too long, people will start making small one-stage moves in quick succession to avoid them, which defeats the purpose. Check the days in current stage as well; a deal that spent zero days in three stages is usually a skip in disguise.
How Pomio CRM helps
In Pomio CRM each deal keeps its stage history together with the notes and activities from the sales process. When a deal skips a stage, the reason and the name of the approver are recorded on the deal, so anyone who opens it later sees why it moved and who agreed. In the weekly review, deals that skipped stages can be checked next to their activities, which shows quickly whether the skipped work really was unnecessary or simply did not happen.
A practical checklist
Define exit criteria for every stage; treat a one-stage forward move with criteria met as a normal change with a note; treat any forward move past a stage as a skip; require a named approver and a short reason for every skip; allow backward moves with a note; use required fields for hard data, not approvals; name an approver and a stand-in per team; review skipped deals in the weekly pipeline review.
Further reading
Does a skip approval slow down the sales team?
Only if approvals take long. A short reason and a quick yes or no from a named approver takes minutes and keeps the pipeline honest.
Should the approver be the salesperson's manager?
Usually the sales lead or the founder. What matters is that it is one named person who also answers for the forecast.
What if a stage has no exit criteria?
Then skipping it is hard to judge. Define the exit criteria first; until then, a stage without criteria is a label rather than a step.
Should skips be counted in reports?
Yes. Track the number of skips per salesperson and per stage. A stage that is skipped often may not be needed, or may be badly defined.