You tick “Required” on the fields you need at closed won. Contract value, close reason, the notes customer success keeps asking for. The setting saves, the reps grumble, and for a few weeks the pipeline looks honest.
Then you pull a closed-won report and the columns you required are blank on deals that closed last week.
The checkbox did what HubSpot says it does. The question is which deals it ever saw.
Why are required deal properties empty in HubSpot?
Required stage properties apply to a person saving a record. HubSpot says that if a property is required, “users cannot create or update the record until they set a value for it,” and it describes conditional stage logic as showing properties “when users manually create a record in or move a record to a specific stage” (HubSpot, Set up and manage object pipelines, updated October 22, 2026). A deal reaching a stage another way isn’t described as covered.
That’s how empty fields reach closed won without a rep clicking past a prompt.
You’re in good company with the blanks. In Validity’s State of CRM Data Management in 2025, a survey of 602 CRM users and stakeholders published July 2, 2025, 76% said less than half of their organization’s CRM data is accurate and complete (Validity, The State of CRM Data Management in 2025). Required fields are the usual response to that. They cover the path HubSpot documents, and that path is narrower than it looks from the settings page.
Blank fields on late-stage deals don’t stay in one report, either. They feed a forecast you can’t trust and a handoff that starts with questions.
What HubSpot’s documentation covers, path by path
HubSpot documents required stage properties for the manual path: a user creating a deal in a stage or moving it there. For pipeline rules, a separate control, HubSpot names the bypasses outright: Super Admins and users with Edit property settings permissions, records created or edited by workflows, and records created or edited by API. Map which of your deals arrive by each path before you decide what to change.
The pipelines page doesn’t mention imports, workflows, the API or integrations when it describes stage properties. The page on the create panel is about manual creation too: you choose which fields appear when users manually create deals, and making properties required there takes a Starter, Professional or Enterprise subscription (HubSpot, Set up fields seen when manually creating records, updated September 9, 2026).
Two neighboring controls are documented more completely. Pipeline rules are enforced “when manually creating or updating records on desktop, in the HubSpot mobile app, and via integrations or HubSpot public APIs when a user ID is being passed,” and all pipeline rules except deal approval can be bypassed by the list above (HubSpot, Set up rules for object pipelines, updated September 9, 2026). Validation rules apply “when editing or importing data,” and HubSpot lists workflows as not enforced (HubSpot, Set validation rules for a property, updated September 10, 2026). Validation rules govern the format of a value, and HubSpot’s page doesn’t say they can require one to be present.
Put side by side, it looks like this.
| Path a deal takes | What HubSpot’s documentation says | What to assume |
|---|---|---|
| Rep moves the deal to a stage in HubSpot | Stage properties show when users manually move a record to a stage. A required one blocks the update until it has a value. | Enforced. This is the documented path. |
| Rep creates the deal directly in a later stage | Stage properties show when users manually create a record in a specific stage. The pages don’t say whether earlier stages’ requirements apply, or whether the skip-stage rule stops a deal being created in a later stage. | The chosen stage’s requirements apply. Earlier stages: not documented, test it in your portal. |
| Workflow sets the stage | The pipelines page doesn’t mention workflows. HubSpot says workflows bypass pipeline rules, and validation rules aren’t enforced in workflows. | Not documented for required stage properties, test it in your portal. Build the workflow to set the values itself. |
| Integration or API writes the deal | The pipelines page doesn’t mention integrations or the API. Pipeline rules apply through APIs when a user ID is passed, and records created or edited by API can bypass them. | Not documented, test it in your portal. |
| Import | The pipelines page doesn’t mention imports. Validation rules apply on import. | Not documented, test it in your portal. |
If reps create deals late in the pipeline because they wait until a deal feels real, that’s a separate decision worth making on purpose. When to create a deal in HubSpot covers it.
Does a workflow that changes the deal stage check required properties?
HubSpot’s documentation doesn’t say that a workflow moving a deal into a stage checks that stage’s required properties. For the two neighboring controls it does document, it says workflows go around them: records “created or edited by workflows” can bypass pipeline rules, and validation rules aren’t enforced in workflows. If a workflow moves deals into a stage, that workflow, or a branch after it, has to set or check the required values.
Open each workflow that sets deal stage and look at what else it writes. If the stage is the only thing it changes, it’s moving deals forward with whatever happened to be filled in.
To see what your portal does, run a test deal through the workflow with the required field empty, then open the record. One test deal tells you more than a quarter of blank reports.
Can pipeline rules stop reps from jumping stages?
On Professional or Enterprise, within limits. Pipeline rules can stop users skipping stages, though HubSpot says users “will still be able to skip stages if a record is moving to a Closed/Closed Lost stage,” and they can stop a record moving backwards once it reaches stages you select (HubSpot, Set up rules for object pipelines). That keeps manual moves passing through the stages whose requirements you set.
Two limits. The bypass list applies here too: Super Admins, users with Edit property settings permissions, workflows and API edits can go around these rules. And the closed exception means a deal can still go from an early stage straight to closed won, so the fields you required at the stages in between are worth checking on those deals.
HubSpot’s page also doesn’t say whether the skip rule stops someone creating a deal directly in a later stage. Test that before you rely on it.
Three backstops that catch what the setting misses
Put the requirement where the stage change happens, then look for what slips past it. Set or check the required values inside any workflow that moves a deal’s stage. Keep a saved view or report of late-stage deals with the required property empty, scoped by the date they entered the stage, and review it weekly. Then open property history on the gaps to see which path they came through.
Set the values where the stage moves. A workflow that changes the stage owns the fields that stage requires. Have it set them, or branch on whether they’re filled and route the deal to its owner when they aren’t.
Review the blanks weekly. HubSpot records the date and time a deal entered and exited each stage in Date entered and Date exited stage properties, and these stage calculated properties need a Professional or Enterprise subscription (HubSpot, HubSpot’s default deal properties, updated September 29, 2026). Filter for deals that entered closed won since your last review with a required property empty, and work that list before it reaches a board deck.
Read the history on the gaps. Property history shows the historical values of a property, “the date and time a change occurred” and “the source of a change,” and when a custom agent made the change, its name appears in the source along with who created it (HubSpot, View a record’s property history, updated October 16, 2026). Open the deal stage history on a few blank deals. The source tells you what moved them, and that tells you which row of the table to work on.
Which fields deserve a requirement at all?
Fewer than the settings page tempts you into. A requirement is a prompt a rep answers before saving, and each one you add makes the others easier to rush. Keep requirements for fields someone downstream depends on, like the handoff from sales to customer success, and let the rest go.
If your deal record has grown a field for each request anyone has made, CRM field bloat is the place to start trimming.
Trust the checkbox, or find out where the blanks come from
You can keep trusting the checkbox. It works on the path HubSpot documents, and the reports will keep showing you the deals that took another one. Or you can spend an afternoon in property history and find out which path your blanks arrive by. The setting stays the same. What changes is that you know which workflow, integration or import to put a backstop on.
The free CRM Diagnostic runs 40+ automated checks across data quality, pipeline hygiene, freshness, reachability and ICP fit, including closed-won deals missing the fields your process requires. If you’d rather see that list before you start, book the free CRM Diagnostic.