What This Update Actually Is
HubSpot date properties have supported validation rules for a while. You could restrict a field to "Any future date" or "Past dates only." But there was a gap: today was excluded from both.
This update adds a single checkbox in the Rules section of the property creator and editor. When you check it, today's date becomes a valid selection for whichever rule you've applied. You can turn it on or off per property, independently of any other setting.
That's the whole feature. Small surface area, meaningful impact for any team that works with scheduling, deadlines, or time-sensitive data entry.
Why HubSpot Shipped This
Here's the real-world frustration this solves. Imagine you have a date property called "Contract Start Date." You want to make sure reps don't accidentally enter a date from last quarter. So you add a "Any future date" validation. Makes sense.
But then a deal closes today. The rep tries to enter today's date, and HubSpot blocks it. The validation rule does its job, just a bit too aggressively. The rep either skips the field, enters a wrong date, or calls you to ask why the CRM won't let them do their job.
The same problem shows up on the past-date side. A team logging a completed milestone wants to mark it as done today. The "Past dates only" rule excludes today, so they're stuck.
HubSpot shipped this because data quality and data entry speed are both important. Humans shouldn't have to choose between the two. This update lets you enforce the spirit of a validation rule without the unintended friction of blocking a legitimate same-day action.
How to Use It Step by Step
- Go to Settings in your HubSpot portal.
- Navigate to Properties under the relevant object type (Contacts, Companies, Deals, Tickets, or a custom object).
- Open an existing date property or create a new one with the field type set to "Date."
- Scroll to the Rules section in the property editor.
- Select either "Any future date" or "Past dates only" as your validation rule.
- Check the new "Allow today" checkbox that now appears beneath the rule selection.
- Save the property. The change applies immediately to any record where that property appears.
That's it. No workflow changes, no re-publishing, no portal-wide toggle. You control it at the property level, which means you can be precise about where today's date is valid and where it isn't.
What It Touches in Your HubSpot Strategy
This update is narrow in scope but wide in practical reach. Here's where you'll feel it across your portal.
CRM Records and Data Integrity
Any object that uses date properties benefits here. Deals with close dates, contacts with last-touched dates, tickets with resolution dates. When validation rules block same-day entries, reps either leave fields blank or enter incorrect dates. Both outcomes damage your reporting downstream.
Key Takeaway
Blank or incorrect date fields are one of the most common causes of broken pipeline reports and inaccurate lifecycle stage timing. This update removes one of the main reasons humans skip required date fields.
Forms and Data Entry Workflows
If you use HubSpot forms (internal or external) to collect date information, this validation improvement carries over. Service intake forms, onboarding forms, and sales handoff forms often ask for start dates. Letting humans select today removes an unnecessary support question.
Automation and Workflow Triggers
Workflows that trigger based on date property values become more reliable when the underlying property accepts a complete range of valid dates. If a workflow fires when a "Start Date" is set and that property blocked today, you had a silent gap. Now you don't.
This connects directly to how HubSpot handles property-level controls more broadly. If you've been following how HubSpot is giving admins more granular control over their portals, you might also want to read about the customizable title card on CRM records, which lets you pin the most important properties to the top of any record view.
Reporting and Dashboard Accuracy
Date properties often anchor your most important reports: time-to-close, SLA compliance, cohort analysis. When those properties have validation gaps that cause skipped or wrong entries, your reports lie to you. Fixing the validation rule upstream means cleaner data flows into every dashboard that depends on it.
Key Takeaway
Audit your existing date properties with active validation rules. Any that use "Any future date" or "Past dates only" are candidates for the new "Allow today" checkbox. Start with deal close dates, contract start dates, and task due dates.
If you're working to tighten up your reporting setup overall, the recent updates to HubSpot's reporting dashboard header simplification are worth a look alongside this one.
Who Should Care Most
This update matters most to the humans who build and maintain property infrastructure in HubSpot. Here's who should act first.
- HubSpot Admins and RevOps leads who set up date validations and now get a cleaner, more flexible rule set without sacrificing data integrity.
- Sales managers who've seen reps skip or fudge date fields because the validation blocked today's date. This fix removes that friction point at the source.
- Service and operations teams using ticket or custom object date fields for SLA tracking, where same-day logging is routine.
- Marketing ops professionals who use date properties in forms, smart lists, or enrollment triggers and need today's date to be a valid input.
- Business owners at growth-stage companies where the team wears multiple hats and can't afford CRM friction slowing down daily operations.
Because this is available on all hubs and tiers, there's no paywall to worry about. Every HubSpot portal gets this.
George's Take
I've audited a lot of portals, and date property problems are almost never the first thing a team notices. They show up later, in a report that doesn't add up, or in a pipeline review where a deal close date is blank because the validation was too strict. This update is the kind of thing that quietly improves data quality without requiring a big project. My advice: go through your date properties this week, identify every one with a future or past validation rule, and ask whether today should be valid. For most of them, the answer is yes. Check the box, save it, and move on. Small fix, real impact.
“The best CRM improvements aren't always the flashy ones. Sometimes it's a single checkbox that stops humans from entering bad data just because the rule was a little too rigid.”
If you want a second set of eyes on your property setup, validation rules, or overall data architecture, that's exactly what we dig into during a Sidekick strategy session. Let's make sure your portal is set up to help your team flourish, not slow them down. Book a strategy call at sidekickstrategies.com and we'll start there.
Frequently Asked Questions
What does the 'Allow today' checkbox do in HubSpot date property validations?
The 'Allow today' checkbox lets you include today's date as a valid selection when you've set a date property to 'Any future date' or 'Past dates only.' Without it, today's date is excluded from both rules. With it checked, users can select today alongside future or past dates, depending on your rule.
Which HubSpot hubs and tiers get the 'Allow today' date validation feature?
This feature is available across all HubSpot hubs and all tiers, including Free, Starter, Professional, and Enterprise. There's no paywall or plan restriction. Any HubSpot portal can use it on any date property, for any object type.
Where do I find the 'Allow today' option in HubSpot?
Go to Settings, then Properties, and open any date property. In the Rules section, select either 'Any future date' or 'Past dates only.' The 'Allow today' checkbox will appear beneath the rule. Toggle it on, save the property, and the change applies immediately to all records using that property.
Can I enable 'Allow today' on some date properties but not others?
Yes. The setting is controlled at the individual property level. You can enable it on a deal close date property, for example, and leave it off on a contract end date property. Each property maintains its own setting independently.
Why would a HubSpot date validation rule block today's date?
Before this update, 'Any future date' required a date strictly after today, and 'Past dates only' required a date strictly before today. Today fell in neither category and was blocked. This was a common source of data entry friction, especially for teams logging same-day events like contract starts or completed milestones.
Does the 'Allow today' date validation change affect HubSpot workflows or automation?
Indirectly, yes. Workflows that trigger based on date property values become more reliable when the property accepts today's date. If your workflow fires when a date field is set and that field was previously blocked from accepting today, you had a silent gap in your automation. Enabling 'Allow today' closes that gap.
