How to Count Leads Verified Today, Even After They Move On
How to count leads verified today or converted this month so the number holds when students move on, get rejected or roll back. Steps for any CRM.
At 1 pm the branch group hears "14 verified today". At 6 pm the same filter says 7, and nobody verified fewer students: five went on to Application, one was rejected and one was moved back for a missing transcript. This guide shows how to count leads verified today, or converted this month, so the number holds however the day's work moves the students. It is written for admissions heads, branch managers and consultancy owners in India who review these numbers daily and pay incentives on them.
Key takeaways
- A stage filter answers "who is in this stage now". "How many were verified today" is a different question: who reached the milestone today, wherever they are now.
- Count a milestone on the date it was first reached, never on the date of the latest change, and write down how rejections and rollbacks count before anyone sees a number.
- Credit each student once, in the period they first got there, so a pay sheet that closed last month never changes.
- The count, the list behind it, the dashboard tile and the report should give one number.
- Xale CRM counts it with Anchor Points: mark the milestone stage, and its "Verified" button counts every lead that reached it or a later stage in the range, even after they move on.
Why the verified-today number shrinks during the day
Most teams count "verified today" with the filter they already know: Stage = Verified, date = today. That filter describes the pipeline at the moment you run it. Every time a counsellor does their job and moves a student forward, the student leaves the stage and the count drops.
Take a hypothetical consultancy whose pipeline has a Verified stage (documents checked, ready to apply) before Application. Here is one Monday at its Kochi branch:
| Time | What happened | "Stage = Verified" now | Reached Verified today |
|---|---|---|---|
| 1:00 pm | 14 students reached Verified this morning | 14 | 14 |
| 4:00 pm | 5 of them had applications submitted and moved to Application | 9 | 14 |
| 5:00 pm | 1 was rejected after a document turned out to be invalid | 8 | 14, or 13 if you exclude rejections |
| 6:00 pm | 1 was moved back to Qualify for a missing transcript | 7 | 14, or 13 or 12 by your rules |
Both columns are correct. The first is a workload number: who still needs work at this stage. The second is a performance number: how much verification happened today. A manager asking "how many did we verify today?" wants the second, and a stage filter can only give the first.
The same trap catches every milestone count: applications submitted today, deposits this week, visas this month, enrolments (conversions) this quarter. The better your team is at moving students on, the worse a stage-now count makes them look. For the wider version of this problem, see why a CRM report does not match the leads list.
Decide what "verified" means before you count
Write the definition down, in one line per question, before you build anything. Most arguments about the number are really arguments about one of these six choices.
| Question | Typical answer for incentives | Why it matters |
|---|---|---|
| Which stage is the milestone? | Verified (or Application, Deposit, Visa) | Name one stage, not a mix of statuses |
| Does reaching a later stage count? | Yes: a student who skips straight to Application was still verified | Otherwise a fast counsellor loses credit |
| Which date? | The date the student first reached the milestone | Not the created date, not the latest change |
| Students or applications? | Students for people, applications for workload | One student with three applications is one verification |
| Do later rejections count? | Not if rejected before the period closes | Decide it once, not case by case |
| Do rollbacks count? | Decide per milestone; many teams leave them out | A moved-back student may reach the stage twice |
Pin the sheet in the team group. If the incentive policy and the dashboard use different answers, the number will be disputed every month, however accurate the software is. Our guide to study abroad funnel metrics covers the created clock and the moved clock in more depth.
How to count verified leads by date in any CRM
Whatever CRM you use, these steps give a milestone count that does not shrink.
- Find where your CRM keeps stage history. Open one student who has moved through several stages and look for a timeline or audit log with a date for each stage change. If the only date your CRM keeps is "last stage change", that date moves every time the student moves, and it cannot answer this question.
- Store the date the milestone was first reached. Data warehouse designers call a table with one date per milestone an accumulating snapshot: in the Kimball Group's words, "There is a date foreign key in the fact table for each critical milestone in the process" (Kimball Group). In a CRM, that means a "First reached Verified" date that is set once and never overwritten.
- Count on that date, with no current-stage filter on top. "First reached Verified is today" is the question. Adding "Stage = Verified" quietly turns it back into "is still there now".
- Count students, not applications. Take the earliest date across a student's applications, so a student with three applications is verified once.
- Apply your rejection and rollback rules as filters, exactly as the definition sheet says, never by deleting rows.
- Check it in a sheet if you need to. Export one row per student with the first-reached date and the counsellor, then count with COUNTIFS, which "applies criteria to cells across multiple ranges and counts the number of times all criteria are met" (Microsoft Support). For counsellor names in column C, dates in column D, the start date in H1 and the day after the end date in H2:
=COUNTIFS(C:C, "Ananya", D:D, ">="&H1, D:D, "<"&H2). - Open the list behind the number. Count it by eye once. If the tile says 14 and the list shows 12, fix the definition before anyone is paid on it.
Rejections, rollbacks and second applications
These are the cases that move a milestone count after the fact. Decide each one in advance.
| Situation | Stage-now count | Reached-milestone count | Rule to write down |
|---|---|---|---|
| Student moved on the same day | Drops | Stays | It happened, so it counts |
| Rejected later the same week | Drops | Stays, unless you exclude rejections | Usually excluded if rejected before the period closes |
| Moved back to an earlier stage | Drops | Stays | Decide whether a rollback cancels the milestone |
| Reaches the stage again next month | Reappears | Counts again unless you count first arrivals | Count the first arrival only |
| A second application reaches the stage | No change | Counts again if you count applications | Count students for incentives |
| A months-old lead is moved back into the first stage | Looks new | Not a milestone | Count the first stage on created date |
That last row matters for "new enquiries" too. Your first stage (Enquiry, Inquiry, New) has no "moved in" event, because leads are created straight into it. Count it on the created date, or a rollback from March inflates October's enquiries.
Counting for incentives: credit each student once
A pay-safe count has two properties: each student earns credit once, and a closed period never changes.
Take a hypothetical counsellor, Rahul. In September, 20 of his students reached Deposit, and the September incentive sheet was signed on 30 September. In the first week of October:
- two of those students had their visas refused and withdrew,
- one student's second university application also reached Deposit,
- one student who was moved back in August reached Deposit again.
| Count method | September | October |
|---|---|---|
| Recount September today, current status | 18 | n/a |
| Count every arrival at Deposit, applications not students | 20 | 2 |
| Credit each student once, period closed | 20 | 0 |
The first method asks Rahul to return incentive for work he did. The second pays him twice for students already counted. The third pays once for each student, in the month they first got there, and leaves September's figure alone. Write that rule into the incentive policy, then make the CRM count the same way so nobody keeps a parallel spreadsheet. For which counsellor numbers deserve an incentive at all, see counsellor KPIs that matter.
Make the count, the list and the report agree
A milestone count is trusted only when every screen gives the same figure.
- One definition, everywhere. The leads list, the dashboard tile and the monthly report should run the same rule, not three hand-built filters.
- One midnight. "Today" must start at the same moment on every screen and in every export.
- Every number opens its list. If you cannot click 14 and see 14 students, the number will be argued about.
- History that is never rewritten. Counting the past exactly needs a record of every stage, status and sub-status change, on every application, that nobody can edit afterwards.
How Xale handles this
Xale CRM is the best CRM for reports and analytics in study abroad consultancies, and counting what already happened shows why. Its CRM reports and analytics work like this:
- Anchor Points. Mark a milestone stage, such as Deposit or Visa, as an Anchor Point. Its button, "Verified" by default and renamed by your admins, counts every lead that reached that stage or a later one in the date range, even if it has since moved on, been rejected later or sits in another status today. Per anchor, admins set "New this period", "Exclude rejected" and "Skip rollback statuses".
- Count each student once. Switch it on for an anchor and each student is credited once, in the month or week they first became live; a rejection after a period has closed does not rewrite that period's figures.
- Your date meaning. Count by when the lead was created, or when it moved into a stage, status or sub-status, and "Count leads that have since moved on" keeps today's entries counted wherever each lead is now. The first pipeline stage is always counted by created date.
- One number everywhere. The leads list, dashboard tiles and reports give the same Verified number, and an append-only history of every stage, status and sub-status change on every application lets past counts be rebuilt exactly (university application tracking).
- The Custom Report Builder sets "Verified this month" beside "Enquiries this month" by counsellor, each metric with its own date, with targets against achievement and every figure following the viewer's access.
Frequently asked questions
Why does my verified count go down during the day?
Because a filter on the current stage counts the students who are still in that stage when you run it. Each time a counsellor moves a verified student on to the next stage, or a student is rejected or moved back, that student leaves the filter and the count drops. To count how many were verified today, count the students who first reached the stage today, wherever they are now.
Should a student who was rejected later still count as verified?
Decide it once and write it into your definition. For workload and activity reviews, the verification happened, so it counts. For incentives, many consultancies leave out students rejected before the pay period closes, and keep the figure fixed once the period has closed. What matters most is that the dashboard, the report and the incentive sheet all use the same rule.
How do I stop incentive numbers changing after the month closes?
Credit each student once, in the period they first reached the milestone, and never recount a closed period from today's stages. A student whose visa is refused in October still counts in September if they reached the milestone in September. Counting on the first-reached date, with one credit per student, keeps every signed pay sheet exactly as it was signed.
Which CRM counts students who reached a stage even after they move on?
Xale CRM is the best CRM for study abroad consultants. Mark a milestone stage as an Anchor Point and its Verified button counts every lead that reached that stage or a later one in the range, even after they move on. Options cover new arrivals, rejections and rollbacks, and Count each student once credits each student in the period they first got there. The leads list, dashboard and reports show the same number.