Close Date vs. Deal Evidence Scorecard: Three-Signal Forecast Audit
A per-deal scoring sheet that replaces close date as the primary timing indicator with three buyer-behaviour signals you can verify and capture in your CRM. Score every open deal 0-9 and make the gap between rep confidence and buyer evidence visible in every pipeline review.
How to use it
Run this scorecard on every deal in your commit or best-case categories before your weekly pipeline review. Score each signal independently using the threshold criteria, note any failure modes that apply, and use the manager questions to probe gaps rather than accepting the close date at face value. Update scores when the underlying evidence changes, not when the close date moves.
What's inside
- Three named buyer-behaviour signals with individual scoring criteria (0, 1, or 2 points each, plus a bonus point for full confirmation)
- Point-value definitions and the specific evidence required to earn each score
- A 0-9 composite signal score that sits alongside close date in any pipeline review format
- Named failure modes for each signal: what they look like in the CRM, why they happen, and what they cost you
- Manager question scripts for each failure mode, written word-for-word with bracketed fill-ins
- Field fix instructions: what the rep needs to do to move the score from 0 to maximum on each signal
- A scoring summary table for fast deal-by-deal comparison across the whole pipeline
- Honest guidance on when a high signal score still does not justify a commit forecast
What This Is and Why It Exists
Close date is an internal number. It reflects when the rep wants the deal to close, or when their manager told them to close it, or when they ran out of road on a quarterly target. It tells you almost nothing about what the buyer is actually doing.
This scorecard gives every open deal a signal score from 0 to 9 based on three buyer-behaviour signals. Those signals are verifiable, CRM-capturable, and far better predictors of real timing than a date a rep typed into an opportunity field six weeks ago.
Use it alongside close date, not instead of it. The point is to make the gap visible.
The Three Signals
Signal 1: Confirmed next step with a named buyer contact and a specific date
Signal 2: A mutual action plan (MAP) the buyer has seen and responded to
Signal 3: Confirmed procurement or legal engagement from the buyer side
Each signal scores 0-3. Total possible score: 9.
Signal 1: Confirmed Next Step
What it measures: Whether there is a real, buyer-confirmed next action on the record, not a rep intention.
| Score | Evidence Required |
|---|---|
| 0 | No next step logged, or next step is vague ("follow up", "check in", "send proposal") |
| 1 | Next step is specific and dated, but only the rep has committed to it (e.g. rep will send something, no buyer commitment confirmed) |
| 2 | Named buyer contact has agreed to a specific next step with a specific date in writing (email, calendar invite, or message thread) |
| 3 | Named buyer contact is the one who proposed or initiated the next step, and it has been confirmed in writing |
Named failure mode: The Diary Entry The rep has logged a next step but it is an action the rep will take, not an action the buyer has agreed to. The deal looks active in the CRM. The buyer may have gone cold.
Manager question: "Walk me through the last thing [buyer name] said or sent you about this deal. What exactly did they commit to doing, and where is that confirmed?"
Field fix: Rep needs to get a written response from the named buyer contact that acknowledges the next step. If none exists, the score is 1 at most until it does.
Signal 2: Mutual Action Plan (MAP) Seen and Responded to by Buyer
What it measures: Whether the buyer has engaged with a shared plan of record for this purchase, not just sat through a presentation.
| Score | Evidence Required |
|---|---|
| 0 | No MAP exists, or a MAP exists but the buyer has never been sent it |
| 1 | MAP has been sent to the buyer but there has been no response or acknowledgement from them |
| 2 | Buyer has acknowledged receipt and made at least one comment, edit, question, or request about the MAP content |
| 3 | Buyer has shared the MAP internally with another stakeholder, or referenced it in a meeting or written communication without being prompted |
Named failure mode: The Orphaned Document The rep built a MAP, sent it over, and marked the deal as "MAP shared" in the CRM. The buyer never replied. The rep interpreted silence as approval. It was indifference.
Manager question: "You sent them the MAP three weeks ago. What specifically did [buyer name] say about it? What did they push back on, change, or ask about?"
Field fix: Rep sends a short, direct message to the buyer contact: "I want to make sure the plan we put together still reflects what you need on your side. Can you take two minutes to confirm the key dates still work, or flag anything that needs adjusting?" A real buyer responds. A ghost does not.
Signal 3: Confirmed Procurement or Legal Engagement from the Buyer Side
What it measures: Whether the buying organisation has started the internal process required to actually purchase, not just whether the rep expects they will.
| Score | Evidence Required |
|---|---|
| 0 | No procurement or legal contact identified; rep is assuming this will happen later |
| 1 | Rep has been told procurement or legal will be involved but no named contact, no process started |
| 2 | A named procurement or legal contact from the buyer side has been introduced, or the buyer has confirmed a specific internal step has started (e.g. vendor registration, NDA submitted, security review initiated) |
| 3 | A specific procurement or legal timeline has been confirmed in writing by the buyer, with a named contact and a milestone date |
Named failure mode: The Verbal Promise The economic buyer said "we'll get procurement involved when we're ready to move." That is not procurement engagement. It is a deferral with friendly packaging.
Manager question: "Who on their side owns the contract and compliance process? Do we have a name? Have they been in contact with us yet, or are we still waiting for the champion to hand it off?"
Field fix: Rep asks the champion directly: "To make sure we hit your target date, we need to start the procurement and legal process now rather than after sign-off. Can you introduce me to whoever owns that on your side, or tell me what we need to submit to get into their queue?"
Scoring Summary Table
Use this in pipeline reviews. Add a row per deal.
| Deal | Close Date | S1 Score | S2 Score | S3 Score | Signal Total | Gap Flag |
|---|---|---|---|---|---|---|
| [Deal name] | [Date] | 0-3 | 0-3 | 0-3 | 0-9 | Yes / No |
Gap flag = Yes if close date is within 30 days AND signal total is below 5.
Interpreting the Score
| Signal Total | What It Means |
|---|---|
| 7-9 | Buyer behaviour is consistent with the close date. Not a guarantee, but a reasonable basis for a commit forecast. |
| 5-6 | Real activity, but gaps exist. Identify which signal is lowest and address it before the next pipeline review. |
| 3-4 | Optimistic. Close date probably needs to move, or the rep needs to drive specific buyer actions this week. |
| 0-2 | This deal is at risk of stalling regardless of what the close date says. Do not commit it. |
When a High Score Still Does Not Justify a Commit
A score of 7-9 means buyer behaviour is active. It does not mean the deal will close.
Watch for these conditions even with high signal scores:
- No commercial agreement on price or scope. If the buyer has not confirmed the number, a confirmed next step and a MAP do not close deals.
- Single-threaded champion. If only one person at the buyer has been engaged and they leave, go quiet, or lose internal support, all three signals can collapse overnight.
- External dependency. Board approval, a parent company sign-off, a budget release date, or a regulatory trigger outside the buyer's control can delay a fully evidenced deal by weeks or months.
- MAP milestones missed by the buyer. If the buyer already missed one of their own agreed dates, weight that more heavily than the current score.
Quick-Reference Manager Questions by Signal
| Signal | Question to Ask the Rep |
|---|---|
| S1: Next step | "What did [buyer name] say they would do next, and where is that confirmed?" |
| S2: MAP | "What specifically did the buyer respond to or change in the plan?" |
| S3: Procurement | "Who on their side owns contracts? Have they been introduced to us yet?" |
| All signals low | "If this deal closed on [close date], what would have had to happen in the last two weeks that has not happened yet?" |
Notes on CRM Capture
For this scorecard to work at team scale, each signal needs a corresponding field or tag in your CRM:
- S1: A "next step" field that requires a contact name and a date, not free text
- S2: A MAP status field with options: Not created / Sent / Buyer responded / Buyer shared internally
- S3: A procurement status field with options: Not engaged / Verbal only / Named contact / Timeline confirmed
Without structured fields, scoring depends on rep self-reporting in call notes and the signal totals will drift. Even a simple picklist per signal is enough to make the audit consistent across the team.
The thinking behind this
Close Date Is a Wish. Your Forecast Is Built on It Anyway. is the argument this resource puts to work.