How to Set Up Deal Stage Dependencies and Required Fields in HubSpot

Deal stage dependencies are how you stop reps moving a deal forward until the data behind it actually exists. In HubSpot the mechanism is the required property, also called conditional stage requirements. You tell a stage which fields must be filled before a deal can land there, and HubSpot blocks the move until they are. It is one of the cheapest pipeline-hygiene wins available, and most mid-market teams have it switched off without realising.

This guide covers the current HubSpot UI, why gating stages matters more than it looks, and where to draw the line before the controls start slowing your team down rather than protecting them.

What deal stage dependencies actually do

A deal stage dependency forces a property to be completed before a deal can enter a given stage. Try to drag a deal into "Proposal sent" without a close date or amount, and HubSpot pops a window asking for the missing fields. The deal does not move until they are supplied.

That single behaviour fixes a surprising amount. Forecasts stop being fiction because every late-stage deal carries an amount and a close date. Reporting works because the fields your dashboards depend on are no longer blank. And handovers between sales and delivery stop falling apart, because the information delivery needs was captured at the stage where it mattered, not chased down three weeks later.

Setting up required fields by stage (current UI)

HubSpot has moved these controls around over the years. Here is where they live now.

1. Click the Settings gear icon in the top navigation bar.
2. In the left sidebar, go to Objects > Deals.
3. Open the Pipelines tab and select the pipeline you want to configure from the dropdown.
4. Find the stage you want to gate and click Edit properties (or the pencil or edit option on that stage).
5. Add the properties you want to appear when a deal reaches this stage, then toggle each one to Required.
6. Click Save.

From then on, any deal entering that stage triggers a prompt for the required fields, whether it is dragged on the board, edited on the record, or moved by automation. Repeat per stage so the requirements tighten as deals progress: light at the top of the funnel, stricter as commitment and value increase.

Which fields to require at each stage

The goal is to require the minimum that keeps your data trustworthy. Over-gate and reps start entering junk to get past the popup, which is worse than no gate at all. A sensible mid-market pattern looks like this.

• Early qualification: deal amount (even a rough figure) and a primary contact, so nothing sits in the pipeline as an unowned mystery.
• Proposal or negotiation: close date, decision-maker, and the products or line items, so forecasting and quoting have something real to work with.
• Closed won: the fields your delivery or onboarding team needs to start work without a follow-up call. This is where required fields quietly become a clean sales-to-service handover.

Keep the list short at every stage. Three well-chosen required fields that reps respect beat ten they learn to defeat.

Where native required fields stop, and what to do next

HubSpot's built-in requirements are deliberately simple: a field is required, or it is not. They do not handle conditional logic such as "require a discount-approval field only when the discount exceeds a set threshold", or rules that depend on a value in another object, or cross-pipeline standards you want enforced everywhere at once.

For those, teams layer on more capable controls:

• Workflow-based validation that flags or reverts deals breaking a rule the native settings cannot express.
• Conditional property logic that shows or requires fields based on other values, so the form adapts to the deal.
• Data-quality automation that standardises and cleans inputs the moment they are entered, instead of leaving you to fix them in reporting.

This is where stage gating stops being a settings task and becomes a CRM architecture decision. If you are designing a pipeline from scratch or untangling years of inconsistent data, our HubSpot CRM implementation service builds the stage logic, required fields, and validation rules around how your business actually sells. For teams whose data is already in a mess, our data engineering team standardises and cleans it so the new gates work on a sound foundation.

Keeping the rules consistent across your stack

Required fields only protect data that originates in HubSpot. If deals, contacts, or product data flow in from another system, the gate is only as good as the data arriving at it. A required amount field means nothing if your quoting or billing tool pushes deals in with the value blank.

That is why pipeline hygiene and integration go together. If HubSpot exchanges deal or revenue data with other platforms, see how we keep records consistent across systems on our integrations hub, and the deeper playbook in our guide to connecting anything with HubSpot. Clean inputs at the source plus required fields at the stage gate is what gives you a pipeline you can actually forecast from.

Get your pipeline gating built properly

Required fields are quick to switch on and easy to get wrong. If you want a pipeline with stage logic, validation, and data quality designed around how your team sells rather than bolted on afterwards, we will build it for you.

Talk to us about CRM implementation