To close your opportunity as won, select Close as Won, according to Microsoft.
Ensure your closed deals have accurate reasons and timestamps
Accurate closure data is the foundation for reliable coaching feedback and pipeline reporting. When a sales manager audits a closed deal, the first verification step is confirming that the outcome was recorded using the system’s designated controls. Microsoft documents the specific action for winning a deal: to close your opportunity as won, select Close as Won, according to Microsoft. This instruction defines the standard interaction for marking a positive outcome in that environment.
Similarly, the process for recording a negative outcome follows a parallel structure. To close your opportunity as lost, select Close as Lost, according to Microsoft. The seven fields you will audit are lost reason, mandatory logic, won time, list view column, admin permission, close date logic, and pipeline stage.
Check those seven closure fields in Freshworks, HubSpot, and Pipedrive before the coaching review.
Key takeaways for how to verify deal closure settings and data accuracy
Verify that the "Reason for loss" field is marked mandatory when the controlling field is set to "Lost," as described in Freshworks. Confirm that moving a record to a closed stage updates the Close date value to today's date, according to HubSpot. Check that changing a deal stage probability from an open percentage to Lost or Won leaves the previously set Close date value intact, according to HubSpot. Ensure that only users with deals admin permissions enabled can edit the deal won time, as noted by Pipedrive. Verify that any new pipeline configuration includes a minimum of 3 stages, inclusive of Won and Lost, according to Freshworks.
Why lost deal reasons matter for coaching
When you audit closed deal data, the "Reason for loss" field is the first place to look. Freshworks explains that when you choose the outcome of a deal between won or lost, selecting the option "lost" presents a set of options that allows you to pick reasons for why the deal was unsuccessful, according to Freshworks. Choosing the option lost presents a set of options that allows you to pick reasons for why the deal was unsuccessful. Without this dependency, a rep can mark a deal as lost without providing the context needed to diagnose the failure.
For example, a controlling field has two choices, "Won" and "Lost," and when the choice "Lost" is connected to the dependent fields "Reason for loss," marking the field "Lost" mandatory would make the field "Reason for loss" mandatory, according to Freshworks. This logic ensures that the system does not accept a closed-lost record until the reason is documented. For a sales manager, this means the data entering your pipeline reports is already filtered for completeness. You do not have to chase down reps for missing information during your one-on-one meetings because the CRM enforces the input at the point of closure.
Understanding how the mandatory check works is essential for verifying data accuracy. Freshworks states that if the dependent field is marked mandatory, the mandatory check will be made only when the dependent field is shown on the form based on the controlling field value, according to Freshworks. This conditional behavior prevents unnecessary friction for won deals while ensuring strict compliance for lost deals. This consistency allows you to aggregate loss reasons across the team to identify common patterns, such as pricing objections or competitor displacement.
To apply this in your next coaching review, check that your CRM’s field dependency settings match your team’s needs. If the "Reason for loss" field is not appearing when a deal is marked as lost, the dependency is not configured correctly. If it is appearing but not mandatory, the rep can still close the deal without providing a reason. Verifying these settings ensures that the data you use to guide your team is both present and complete. This foundational check is the first step in ensuring that your coaching feedback is based on accurate, actionable information.
A filled reference table for CRM closure settings
The following table lists the specific rules for the seven deal fields you must audit before your next coaching review. Each row corresponds to one of the seven items in the title, sourced directly from the vendor documentation.
| Publisher | Field/Setting | Rule or Behavior | Source URL |
|---|---|---|---|
| Freshworks | Lost reason field | Choosing the option 'lost' presents you with a set of options that allows you to pick reasons for why the deal was unsuccessful. | Freshworks |
| Freshworks | Mandatory logic | Marking the field “Lost” mandatory would make the field “Reason for loss” mandatory. | Freshworks |
| Pipedrive | Won time edit | If you prematurely mark a deal as won, you may want to change the won time for that deal later on. | Pipedrive |
| Pipedrive | List view column | To change a deal’s won time in the list view, start by editing your columns to include won time. | Pipedrive |
| Pipedrive | Admin permission | This action is only available to users with deals admin permissions enabled. | Pipedrive |
| HubSpot | Close date logic | When you move a record to a closed stage, the Close date value will be updated to today's date. | HubSpot |
| Freshworks | Pipeline stage | At least a minimum of 3 stages are mandatory(inclusive of Won & Lost). | Freshworks |
Verify that your CRM configuration matches the behavior described in the row for your specific tool before you begin auditing closed deals.
How to enforce mandatory lost reason fields
To make a specific field required only when a deal is marked as lost, you must configure field dependency logic. According to Freshworks, this logic connects a controlling field to dependent fields based on specific choices. The controlling field in this scenario has two choices: “Won” and “Lost.” When the choice “Lost” is selected, it is connected to the dependent field “Reason for loss.”
The mechanism works by marking the controlling choice as mandatory. According to Freshworks, marking the field “Lost” mandatory would make the field “Reason for loss” mandatory. This creates a conditional requirement where the dependent field cannot be left blank if the controlling field is set to the specified value.
This configuration is distinct from making a field mandatory by default. The requirement is triggered specifically by the selection of the “Lost” option in the controlling field. If the controlling field is set to “Won,” the dependency does not trigger the mandatory status for the “Reason for loss” field.
When setting this up, ensure the controlling field is properly defined with the exact choices “Won” and “Lost.” The dependent field must be explicitly linked to the “Lost” choice. According to Freshworks, marking the field "Lost" mandatory would make the field "Reason for loss" mandatory.
Do not assume this behavior applies to all fields or all CRM systems without verifying the specific dependency configuration. The example provided by Freshworks illustrates a specific setup where the “Reason for loss” field becomes mandatory only when the controlling field is “Lost.”
To implement this, navigate to the field dependency settings in your CRM. Identify the controlling field that tracks deal outcomes. Add the dependent field “Reason for loss” to the dependency list. Select the “Lost” option in the controlling field and mark the dependent field as mandatory for that specific selection.
This setup ensures that sales reps must provide a reason for loss when closing a deal as lost. It prevents blank entries in the “Reason for loss” field for lost deals, which is critical for accurate coaching feedback and pipeline analysis. The mandatory logic is tied directly to the “Lost” status, not the general deal record.
Correcting won times in detail and list views
If you prematurely mark a deal as won, you may want to change the won time for that deal later on, according to Pipedrive. This specific scenario highlights why managers should audit timestamps before using them in coaching feedback.
To edit a deal’s won time in the detail view, click the pencil icon next to won time under details, according to Pipedrive. This direct access point allows for quick corrections when a rep realizes a deal was closed earlier than the actual win date.
To change a deal’s won time in the list view, start by editing your columns to include won time, according to Pipedrive. Adding this column makes the data visible for comparison across a pipeline.
After you add the won time column, edit the date by clicking the pencil icon next to the won time value, according to Pipedrive. This step ensures the list view reflects the corrected dates for the specific deals you are auditing.
Note: This action is only available to users with deals admin permissions enabled, according to Pipedrive. Managers must verify their own permission levels before attempting these edits. If you do not have these permissions, request access from your IT administrator or CRM owner.
Check your team’s permission settings to confirm who can perform these timestamp corrections. This prevents unauthorized changes to historical deal data.
When reviewing your coaching logs, cross-reference these corrected won times with your call notes. Use the Timestamped call notes: 5 fields before you post guide to ensure your documentation matches the CRM data. This alignment supports accurate performance reviews.
Verify that your list view includes the won time column before your next pipeline review. This preparation saves time during the audit process.
Ensure your team understands the difference between detail view and list view editing capabilities. This knowledge helps reps self-correct minor timestamp errors when they have the appropriate permissions.
Review your recent closed deals for any premature won markings. Correct these dates to maintain data integrity for your pipeline reports.
Consult your CRM administrator if you encounter permission errors when attempting to edit won times. This step resolves access issues quickly.
Keep a log of all timestamp corrections you make during your audit. This record provides transparency for future coaching sessions.
Use the Sales coaching logs: 6 audit items to check framework to document your findings. This systematic approach ensures no details are overlooked.
Blank worksheet for auditing closed deal data
Use this table to log your audit findings for the seven deal fields. The final row references the minimum stage count rule, which states that at least a minimum of 3 stages are mandatory, inclusive of Won & Lost, according to Freshworks. Fill in the remaining rows with your specific observations.
| Field | Current State | Required State | Action Taken |
|---|---|---|---|
| Lost reason field | _ _ | _ _ | _ _ |
| Mandatory logic | _ _ | _ _ | _ _ |
| Won time edit | _ _ | _ _ | _ _ |
| List view column | _ _ | _ _ | _ _ |
| Admin permission | _ _ | _ _ | _ _ |
| Close date logic | _ _ | _ _ | _ _ |
| Pipeline stage | _ _ | Minimum of 3 stages (inclusive of Won & Lost), according to Freshworks | _ _ |
Review each row to confirm the current state matches the required state. If a discrepancy exists, note the specific action you took to resolve it. This worksheet helps track which fields have been verified and which require further attention before your next coaching review.
FAQ: How to verify deal closure settings and data accuracy
How do I make the lost reason field mandatory in Freshworks?
In Freshworks, marking the field "Lost" mandatory would make the field "Reason for loss" mandatory. For example, if a controlling field has two choices, “Won” and “Lost,” and the choice “Lost” is connected to the dependent fields “Reason for loss,” marking the field “Lost” mandatory would make the field “Reason for loss” mandatory, according to Freshworks.
Does changing a deal to lost update the close date in HubSpot?
When you move a record to a closed stage, the Close date value will be updated to today's date, according to HubSpot.
Who is allowed to change the won time in Pipedrive?
This action is only available to users with deals admin permissions enabled, according to Pipedrive.
What is the minimum stage count for a new pipeline in Freshworks?
At least a minimum of 3 stages are mandatory (inclusive of Won & Lost), according to Freshworks.