# Make Fields Required Based on Other Property Updates (e.g., Close Date Push → Push Reason)

**URL:** <https://community.hubspot.com/t/make-fields-required-based-on-other-property-updates-e-g-close-date-push-push-reason/136986>\
**Category:** HubSpot Ideas\
**Tags:** properties\
**Created:** [July 28, 2025, 1:41pm UTC](https://community.hubspot.com/t/make-fields-required-based-on-other-property-updates-e-g-close-date-push-push-reason/136986 "2025-07-28T13:41:05Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![DFox2](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@DFox2](https://community.hubspot.com/u/DFox2)\
**Post date:** [July 28, 2025, 1:41pm UTC](https://community.hubspot.com/t/make-fields-required-based-on-other-property-updates-e-g-close-date-push-push-reason/136986/1 "2025-07-28T13:41:05Z")

</div>

**Conditional logic must extend beyond enumerated fields: it should be standard functionality for any property type whenever a value is known or updated.**

Right now, conditional logic only supports enumeration fields when a specific dropdown value is selected. That’s helpful, but far too limited for the complexity of modern revenue operations.

**Example Use Case:**

Leadership needs visibility into _why_ a deal is being delayed -- whether the Close Date is pushed out of this quarter, into the next, beyond 90 days, or moved more than 30 days multiple times. While I’ve built workflows that trigger email and Teams notifications to the deal owner and leadership when the Push Reason is missing, those alerts arrive _after_ the fact. By then, the behavior is already off-track.

Expecting reps to read a follow-up email or Teams ping every time they update a property is unrealistic and inefficient. That’s not a scalable compliance mechanism. It’s a workaround.

**The only viable safeguard is inline enforcement.**

Requiring dependent fields in real time, based on any property change, is table stakes for driving consistent CRM hygiene and pipeline accuracy. This isn’t a nice-to-have; it’s foundational for operational discipline.

And this is just one example—there are dozens more where behavioral enforcement depends on smarter, real-time field validation.

---

_[View the full topic](https://community.hubspot.com/t/make-fields-required-based-on-other-property-updates-e-g-close-date-push-push-reason/136986)._