What This Update Actually Is
Conditional property logic lets you show or require a property on a record only when another property meets a specific condition. Until now, that controlling property had to be a text, number, dropdown, or checkbox field.
As of May 27, 2026, you can set a date or datetime property as the controlling property. The conditions available are: is known, is before a specific date, and is after a specific date. Any dependent properties you attach will then show up or become required on the record when that condition is met.
This works on any standard CRM object: contacts, companies, deals, tickets, and custom objects. The logic lives under Settings, not inside workflows, so it applies everywhere that object record is edited, including inside deals, sidebars, and mobile.
Why HubSpot Shipped This
The external problem is a familiar one. Sales and ops workflows are deeply time-sensitive, but your property forms haven't been. A renewal field showing up on day one of a deal creates noise. A kickoff notes field appearing before anyone knows a start date creates confusion. The right field at the wrong time is almost as bad as no field at all.
The internal frustration is harder to name but ops managers feel it every week. You build a clean property setup, train the team, and then watch reps skip fields because they don't feel relevant yet. You end up with follow-up reminders, Slack pings, and half-filled records. That's not a people problem. It's a form design problem that HubSpot couldn't solve until now.
Date-driven conditional logic closes that gap. The record itself becomes context-aware, surfacing what's needed when it's actually needed.
How to Use It Step by Step
- Go to Settings in your HubSpot account, then click Properties in the left sidebar.
- Select the object type you want to configure (for example, Deals or Contacts), then click the Conditional logic tab.
- Click Create logic, then choose a date or datetime property as your controlling property. Good candidates include Contract End Date, Start Date, or any custom date field you're already tracking.
- Set your condition. Choose from: is known, is before, or is after a specific date. If you pick is before or is after, enter the specific date you want to use as the threshold.
- Add the dependent properties you want to appear or become required when the condition is met.
- Click Save logic. The rule applies immediately across all record views for that object.
One important caveat: the is before and is after conditions use a fixed date you set manually, not a rolling date like today minus 30 days. If you need dynamic, rolling date logic, you'll still want a workflow to handle that. Plan your conditions with that constraint in mind before you build.
What It Touches in Your HubSpot Strategy
This update is narrowly scoped but widely felt. Here's where the ripple lands across your portal.
Deal records in Sales Hub: Surface renewal or upsell-related fields only after a contract end date is set. Keeps deal records clean during early pipeline stages and focused during late-stage conversations.
Ticket records in Service Hub: Require a reason-for-delay field automatically when a due date has passed. No extra process, no manager follow-up. The record asks for the context the moment it's relevant.
Contact and company records: Onboarding and customer success teams can prompt kickoff notes or implementation details to appear once a start date is confirmed. The humans on your team see the right prompt at the right moment without any manual nudging.
Key Takeaway
This update doesn't replace workflows. It handles the form layer: what fields appear and when. Use it to reduce clutter at early stages and enforce completeness at late stages. Use workflows for everything that needs to run automatically in the background.
Properties strategy: If you've been hiding fields using workarounds like separate pipeline stages or view-based forms, you may be able to simplify. One object with smarter conditional logic often beats multiple pipelines built to fake field visibility.
Data quality: Required fields that only appear at the right moment get filled. Required fields that appear too early get skipped or stuffed with placeholder text. This update directly improves the data quality picture for any portal using date milestones in their process.
Key Takeaway
Audit your current conditional logic rules after enabling this. Any rule that uses a dropdown or checkbox to approximate a time-based condition (like a Stage field used as a proxy for when a date was set) is now a candidate for cleanup.
This update pairs naturally with the recent CRM index page and board view improvements. Cleaner records load faster and display more meaningfully when the right fields are visible at the right time.
Who Should Care Most
RevOps and HubSpot admins: This is your update. You've been the one designing workarounds for time-based field visibility. Start with your highest-volume object and your most frequently missed required fields. Map the date milestones that should control them.
Sales managers: If your reps consistently skip renewal fields or delay logging deal context, check whether those fields are visible before they're relevant. Date-driven logic may solve the behavior problem you've been blaming on discipline.
Customer success and onboarding leads: Any process tied to a kickoff date, go-live date, or renewal date is a strong candidate. Require the notes and context fields at the moment the milestone becomes real, not before.
Operations teams running project or service delivery objects: The delay-reason use case from HubSpot's own examples is directly applicable here. When a due date passes, require the context automatically. Your reports will thank you.
This update is available on Professional and Enterprise tiers across Commerce Hub, Content Hub, Marketing Hub, Data Hub, Sales Hub, Service Hub, and Smart CRM.
George's Take
We've audited hundreds of HubSpot portals over the years, and one of the most common patterns we find is a property setup that was built for day one of the portal but never evolved to match how the team actually works. Humans don't fill out fields because they're required. They fill them out because they make sense in the moment. Date-driven conditional logic is one of the most practical tools HubSpot has shipped for solving that exact mismatch, and I'd put it near the top of any admin's implementation list this month.
“The best CRM setup isn't the one with the most fields. It's the one where every field that appears actually belongs there right now. Dates finally get a seat at that table.”
If you're pairing this with AI-assisted CRM updates, the Notetaker with Smart Deal Progression is worth revisiting. Having the right fields appear at the right time matters a lot more when an AI is trying to suggest what to fill in.
And if you're thinking about how your CRM data structure connects to the broader buyer experience, our piece on building a B2B customer journey that actually guides buyers walks through how HubSpot-powered systems can match the way buyers actually move.
Want help auditing your current conditional logic setup and building a property architecture that actually matches your team's workflow? Book a strategy call with the Sidekick team and let's make your portal work the way your process does.
Frequently Asked Questions
What is conditional property logic in HubSpot?
Conditional property logic in HubSpot lets you show or require a property on a CRM record only when another property meets a specific condition. For example, you can make a 'Renewal Terms' field appear only after a contract end date is set. It's configured under Settings, then Properties, on the Conditional logic tab.
Can I use a date property to trigger conditional logic in HubSpot?
Yes, as of May 27, 2026, you can use date and datetime properties as the controlling property in conditional logic rules. You can trigger dependent properties to show or become required when a date is known, is before a specific date, or is after a specific date.
Which HubSpot plans include date-driven conditional property logic?
This feature is available on Professional and Enterprise tiers across Commerce Hub, Content Hub, Marketing Hub, Data Hub, Sales Hub, Service Hub, and Smart CRM. It's not available on Free or Starter plans.
What's the difference between conditional property logic and workflows in HubSpot?
Conditional property logic controls what fields appear or are required when a rep views or edits a record. Workflows automate actions in the background, like sending emails or updating fields automatically. For time-sensitive field visibility, use conditional logic. For automated actions triggered by dates, use workflows.
Can I use a rolling date like 'today minus 30 days' in HubSpot conditional property logic?
Not currently. The is before and is after conditions in conditional property logic require a fixed, manually entered date. For dynamic rolling date conditions, you'll need to use HubSpot workflows instead. Plan your rules with this limitation in mind when designing your property setup.
What are the best use cases for date-based conditional property logic?
The strongest use cases include surfacing renewal fields only after a contract end date is set, requiring kickoff notes once a start date is confirmed, and making a delay-reason field required when a due date has passed. Any workflow where the right data is tied to a time milestone is a good candidate.
