Before committing a software deal to this quarter, check stage prerequisites, agreement routing, legal timing, approval controls, and deal evidence to verify the proposed close is supported. As of 26 August 2026, an opportunity needs at least one Opportunity Product before it can move from 2-Scoping to 3-Technical Evaluation according to GitLab.
Commit deal checklist: the evidence to inspect first
The five evidence checks form the baseline for any quarterly commitment. Each check requires specific documentation or system state before the deal moves from pipeline to commit.
1. Stage prerequisites Verify that the deal meets the mandatory field requirements for its current stage. The Product Editor widget sits at the top of the Related list in the right-hand pane, and a banner states the Stage 3 requirement according to GitLab. Inspect your local pipeline rules to identify similar blocking fields. If a required field is empty, the stage transition is not supported by the system state.
2. Agreement routing Confirm that the contract has been routed to the correct reviewers based on value thresholds. Greater than $25,000 ARR (USD) Opportunity to review edits on GitLab Agreement version(s) according to GitLab. Greater than $100,000 ARR (USD) Opportunity to review Customer agreement version(s) according to GitLab. Check whether your deal’s annual recurring revenue triggers these specific review levels. If the routing path is incomplete, verify whether legal review has begun.
3. Legal timing Assess the expected duration of legal negotiations against the quarter end. Deals in which we use the customer agreement take on average 60 days longer to close than if completing using our standard subscription agreement with changes as requested by customer counsel according to GitLab. Use this observed average to evaluate whether the remaining days in the quarter are sufficient. Distinguish this historical average from a guaranteed timeline for the specific deal.
4. Approval controls Ensure that the deal has passed through the required approval workflow. Verify that the necessary permissions are held by the users who will approve the deal. Where your local rules require an approval step, confirm it is recorded before the deal is treated as committed.
5. Deal evidence Capture participant involvement and stale deal warnings as part of the record. Use the recorded involvement as evidence without treating it as proof of purchasing authority.
Take one deal proposed for commit and fill in the five evidence areas, bringing each unresolved item to the next forecast call.
Key takeaways for what should i check before committing a software deal to this quarter?
Before treating a proposed close as supported, verify five distinct evidence areas. These checks separate company-specific examples from universal policy, allowing you to build a local checklist without adopting external thresholds as your own standard.
1. Stage prerequisites Confirm that required fields are populated before a deal advances. This specific rule applies to GitLab’s pipeline configuration. Do not assume this prerequisite exists in your own system without checking your local stage rules. Verify that your CRM enforces similar field requirements at critical transition points.
2. Agreement routing Identify which contract examples trigger review processes. GitLab documents a threshold where opportunities greater than $25,000 ARR (USD) require a review of edits on GitLab Agreement examples, according to GitLab. This is a documented example of how agreement value can dictate review intensity. Your organization may use different financial thresholds or contract types. Inspect your own agreement routing logic to ensure high-value deals receive appropriate legal scrutiny.
3. Legal timing Understand the impact of contract type on close duration. Deals using the customer agreement take on average 60 days longer to close than those using the standard subscription agreement with changes requested by customer counsel, according to GitLab. This is an observed average, not a prediction for any single deal. When a deal involves a customer agreement, account for this potential delay in your forecast. Do not use this average to guarantee a specific close date for an individual opportunity.
Before the call, inspect stage prerequisites and agreements
Verify that the deal meets the specific field requirements for its current stage before advancing it. In GitLab’s Sales Order Processing handbook, an opportunity requires at least one Opportunity Product before it can move from 2-Scoping to 3-Technical Evaluation, a rule documented as of 26 August 2026 GitLab. This prerequisite acts as a hard gate; if the product entry is missing, the stage change is blocked. You can confirm this requirement visually because the Product Editor widget sits at the top of the Related list in the right-hand pane, and a banner states the Stage 3 requirement GitLab. Inspect your own CRM’s stage rules to identify similar mandatory fields that must be populated before a deal can progress to the next phase.
Next, check which agreement examples apply to the deal’s value. The choice of agreement often determines the level of legal review required. For example, an opportunity with greater than $25,000 ARR (USD) triggers a review of edits on GitLab Agreement version(s) GitLab. If the deal value exceeds $100,000 ARR (USD), the review scope expands to include Customer agreement version(s) GitLab. These thresholds are specific to GitLab’s internal policy and should not be treated as universal standards for every software company.
Use these examples to audit your own agreement routing. Determine what ARR thresholds trigger legal or finance review in your organization. Identify which specific fields or products must be present to move a deal from scoping to evaluation. Confirm that the correct quote document is selected for the deal type. If your CRM does not enforce these rules automatically, verify that the sales rep has manually completed the required steps. A deal that lacks the necessary product entry or uses the wrong agreement version is not ready for commit, regardless of the customer’s verbal intent.
Review the deal record for the presence of the required product line items. Check the stage banner or validation message to see if any prerequisites are unmet. Compare the deal’s ARR against your internal thresholds for agreement review. Ensure the correct quote document is attached to the opportunity. If any of these elements are missing, flag the deal as unsupported for the current quarter’s commit. The goal is to confirm that the administrative and contractual foundations are in place before the close date is proposed. This prevents late-stage delays caused by missing data or incorrect routing.
Take one deal proposed for commit and verify its stage prerequisites and agreement routing against your local policy before the forecast call.
During the call, examine legal timing and approval controls
Legal negotiation timelines and CRM approval controls determine whether a proposed close date is operationally feasible. Assess these two areas during the forecast call to verify that the deal has cleared necessary procedural hurdles.
Legal negotiation timelines
When a deal moves from standard terms to a customer agreement, the closing timeline often extends. According to GitLab, deals using a customer agreement take on average 60 days longer to close than those completing with a standard subscription agreement modified by customer counsel. This observed average serves as a benchmark for evaluating whether the current close date remains realistic if legal negotiations are ongoing.
Beyond the timeline, the process requires active engagement from the buyer’s leadership. According to GitLab, the primary decision maker must indicate willingness to facilitate the internal process so that issues reach closure within 30 days of negotiations. Verify that this commitment exists in writing or has been explicitly stated during the most recent call. Without this facilitation commitment, the 30-day closure window is not guaranteed, and the deal may stall in legal review.
CRM approval controls
While legal teams handle contract language, your CRM system enforces procedural compliance through approval workflows. Ensure that your pipeline configuration supports the necessary governance steps before committing the deal.
If you want to configure required properties before a record can be moved to a pipeline stage, learn how to configure conditional stage logic, according to HubSpot. This setup ensures that deals cannot advance to a later stage without the required properties populated.
For deals specifically, you can set up an approval process for deals in the pipeline (deals only), according to HubSpot. This feature allows you to route deals for review within the pipeline.
However, access to these controls is restricted by subscription tier and user permissions. A Sales Hub Enterprise subscription is required to configure the deal approval process, according to HubSpot. Additionally, Super Admin permissions are required to configure object pipeline rules, according to HubSpot. If your team lacks these permissions or the necessary subscription tier, you cannot configure these HubSpot deal approval or pipeline rule settings. In such cases, manual verification of approvals becomes the primary control mechanism.
Verification steps for the call
- Confirm legal status: Determine if the deal uses a standard agreement or a customer agreement. If it is a customer agreement, assess whether the 60-day average delay applies to your current timeline.
- Verify decision maker commitment: Check for documented evidence that the primary decision maker has agreed to facilitate issue closure within 30 days of negotiations.
- Check CRM permissions: Confirm that the user configuring HubSpot object pipeline rules holds Super Admin permissions.
- Validate subscription tier: Ensure the organization has a Sales Hub Enterprise subscription to access deal approval process configuration.
- Review stage logic: Verify that conditional stage logic is configured to require specific properties before moving the deal to the commit stage.
If any of these controls are missing, review local policy to see whether equivalent controls exist before relying on the close date. Address these gaps before including the deal in the quarterly commit.
After the call, capture participant evidence and stale warnings
Record who was involved and monitor how old the deal has become before the next forecast meeting. The evidence you capture here supports the deal evidence check by documenting involvement and flagging aging risks.
Record participant involvement In Pipedrive, you can add a participant by opening a deal, going to the participants section in the deal detail view sidebar, then clicking “+” according to Pipedrive. This action creates a record of who was engaged in the deal. To verify the full scope of involvement, you can click “View All” to see the full list of participants linked to that deal according to Pipedrive. Use this list as evidence of recorded involvement. Do not treat a linked participant as proof of purchasing authority; the record shows involvement, not decision-making power. If a key stakeholder is missing from this list, add them now so the next reviewer sees the complete picture.
Monitor deal staling Freshsales keeps track of the age of a deal and turns the deal red whenever a deal crosses the staling age according to Freshsales. This visual warning indicates the deal has exceeded the configured age threshold. As a deal ages and get closer to its stale age, the likelihood of conversion of the deal drops according to Freshsales. Inspect this warning without inventing a universal age threshold or probability. The red status is a signal to review the deal’s progress, not a guarantee of loss. If the deal is red, document why it has aged and what action you are taking to move it forward or close it.
Verify rule enforcement context If your pipeline uses automated rules, understand when they apply. Pipeline rules are enforced when manually creating or updating records on desktop, in the HubSpot mobile app, or through integrations or HubSpot public APIs when a user ID is being passed according to HubSpot. In HubSpot, this means that if you update a deal manually or through an integration that passes a user ID, the pipeline rules will check the data. If a rule blocks a stage change, check the rule configuration to see if the update method triggered it. This context helps you distinguish between manual errors and automated enforcement.
Action step Review the participant list and the deal’s age status. If the deal is red or missing key participants, update the record before the next forecast call. Bring these specific observations to the meeting so the team can assess the deal’s readiness based on documented evidence.
Publisher reference table for the five evidence checks
| Publisher | Evidence Check | Documented Detail |
|---|---|---|
| GitLab | Stage prerequisites | An opportunity needs at least one Opportunity Product before it can move from 2-Scoping to 3-Technical Evaluation, according to GitLab. |
| GitLab | Agreement routing | Opportunities greater than $25,000 ARR (USD) require review of edits on GitLab Agreement version(s), according to GitLab. |
| GitLab | Legal timing | Deals using the customer agreement take on average 60 days longer to close than GitLab's standard subscription agreement with changes requested by customer counsel, according to GitLab. |
| HubSpot | Approval controls | A Sales Hub Enterprise subscription is required to configure the deal approval process, according to HubSpot. |
| Freshsales | Deal evidence | The product keeps track of the age of a deal and turns the deal red whenever a deal crosses the staling age, according to Freshsales. |
Related guides
FAQ: evidence behind a software deal commitment
What belongs in a commit deal checklist?
A commit deal checklist should list five specific evidence areas: stage prerequisites, agreement routing, legal timing, approval controls, and deal evidence. These items separate the structural requirements of the sales process from the specific documentation proving a deal is ready for a quarterly commitment. Reviewing these five areas helps distinguish between a deal that meets internal stage rules and one that has the external evidence to support a close date.
Does HubSpot deal approval setup require my account to have Sales Hub Enterprise?
Yes, a Sales Hub Enterprise subscription is required to configure the deal approval process, according to HubSpot. This requirement applies specifically to the configuration of the deal approval process within that platform. If your account does not hold this specific subscription tier, you cannot set up the deal approval rules described in the documentation.
How much longer does GitLab say customer agreements take to close?
GitLab reports an average of 60 days longer for customer agreements than for its standard subscription agreement with changes requested by customer counsel. It serves as a data point for legal timing rather than a universal prediction for every software company’s negotiation timeline.
How can I see every participant linked to a Pipedrive deal?
You can click “View All” to see the full list of participants linked to that deal, according to Pipedrive. This action reveals the complete record of individuals associated with the opportunity in the system. Reviewing this full list provides evidence of recorded involvement, though it does not automatically confirm which participant holds purchasing authority.
When does Freshsales turn a deal red?
The product keeps track of the age of a deal and turns the deal red whenever a deal crosses the staling age, according to Freshsales. This visual indicator signals that the deal has exceeded a specific age threshold defined by the system. Inspecting this warning helps identify stale opportunities without assuming a universal probability of conversion or a fixed age limit across all vendors.