Write Entry and Exit Rules for Every Pipeline Stage

Ask three people on the same team what "Contacted" means and you may get three answers. One person moves an enquiry there after a single unanswered call. Another waits until there has been a real conversation. A third uses it for anything that is not brand new. The pipeline view looks tidy, but it no longer tells the owner what is actually happening.

The fix is not more stages or a new tool. It is a short written rule for each stage: what has to be true for an enquiry to enter it, and what has to be true before it can leave. Once those rules exist, the same view means the same thing to everyone who reads it.

Why stage names stop meaning the same thing

Stage names are usually chosen in a meeting, written on a whiteboard and never defined. Over a few months, small habits pull each name in a different direction:

• Stages describe effort, not progress. "Called" records that someone dialled, not that the customer moved any closer to a decision.
• People move cards to look busy. Without a rule, moving an enquiry forward feels like progress even when nothing changed for the customer.
• Old enquiries sit in the middle. Nobody agreed when an enquiry should be closed, so the "Proposal sent" column fills with quotes from months ago.
• New staff guess. Each new joiner learns the stages from whoever sits next to them, and the meaning drifts again.

Our earlier piece on pairing pipeline stages with follow-up sequences looked at what the team does at each stage. This one goes a step before that, to what each stage means.

What an entry rule and an exit rule look like

An entry rule is one sentence that says what must already be true when an enquiry arrives in a stage. An exit rule says what must be true before it can move on. Good rules share three traits:

• They describe something you can check. "Customer confirmed budget range on a call" can be checked. "Customer seems keen" cannot.
• They are about the customer, not the staff member. "Customer has the written quote" is better than "We sent a quote".
• They fit on one line. If a rule needs a paragraph, the stage is probably doing two jobs and should be split.

A useful test: hand the rule to someone who joined last week, show them three enquiries, and ask which stage each belongs in. If their answer matches yours, the rule is clear enough.

A worked example for a small business pipeline

Every business will word these differently, but a services or property enquiry pipeline might read like this:

1. New enquiry. Enters when a form, call or walk-in is recorded with a name and a way to reach the person. Leaves when someone has spoken or exchanged messages with them.
2. In conversation. Enters after the first two-way contact. Leaves when the customer's need, rough budget and timing are written in the notes.
3. Need confirmed. Enters when those three details are recorded. Leaves when the customer has a written quote, proposal or shortlist in hand.
4. Proposal with customer. Enters when the customer has the document. Leaves when the customer says yes, says no, or asks for a changed proposal.
5. Won. Enters when the customer confirms in writing or pays a booking amount, whichever your business treats as the commitment.
6. Closed, not now. Enters when the customer says no, stops replying after the contact attempts your team agreed, or the need no longer fits what you offer. Always record the reason in one line.

Notice that "Closed, not now" has a rule too. A pipeline without a clear way out is the main reason middle stages fill up with enquiries nobody is working.

Give each stage an owner and a review rhythm

Rules work when someone is responsible for them. For each stage, write down two more things next to the rule:

• Who owns enquiries in this stage. It might be a named person, or a role such as "the sales lead for that site".
• How long an enquiry can sit there before it is reviewed. This is not a promise to the customer; it is a prompt for the team to look again.

Then hold a short weekly review. Go stage by stage, open anything that has sat past its review point, and either move it on, close it with a reason, or write the next step in the notes. Fifteen minutes a week keeps the view honest.

Keep the rules where the team works

A rule sheet stored in someone's laptop folder will be forgotten. Put the one-page sheet wherever the team already looks: pinned in the shared drive, printed by the desk, and walked through with every new joiner on their first day. When a rule changes, change the sheet and tell the team the same day.

The rules also depend on what arrives at the start. If you have not yet agreed how enquiries are labelled, our guide on tagging every enquiry with its source covers that, and sending form enquiries by webhook explains how website forms can hand enquiries over without email forwarding. Notes written at intake, as set out in capturing enquiry context at intake, make the "In conversation" exit rule much easier to check.

Where Flo fits

In Flo, you can set your own pipeline stages, and each new website-form lead opens a pipeline opportunity you can move through them.

The entry and exit rules, who owns each stage and how often the team reviews it are your team's decisions. Moving an enquiry from one stage to the next is a person's call against the written rule, and the weekly review is where that call gets checked.

Start with one stage this week

You do not need to rewrite the whole pipeline at once. Pick the stage that holds the most old enquiries, usually the one just after a proposal goes out. Write its entry rule and exit rule in one line each, name its owner, and set a review point. At the next weekly review, apply the rule to every enquiry in that column and close or move what no longer fits. Then do the next stage. If you'd like a walkthrough of Flo, book a short conversation.