Skip to main content

How to track venue availability in HubSpot | TabCalendar

Last updated: March 23, 2026 (America/Los_Angeles)

This guide reflects current shipped behavior.

Tracking venue availability in HubSpot works until the team grows, the booking volume increases, and the spreadsheet someone maintains stops being authoritative. This page covers the native manual path and the operational-utility approach with TabCalendar.

TabCalendar is a CleverCat operational utility for HubSpot: a hosted fullscreen calendar for availability planning across Company and Deal records, with explicit status states and a year-view that’s actually useful.

Fast answer

Native HubSpot baseline (manual)

  • Store availability dates as properties on Company or Deal records.
  • Track sold / held / unavailable status as custom property values, updated manually.
  • Use notes or tasks to communicate availability decisions across the team.
  • Reconcile availability manually when booking conflicts or questions arise.

When native is enough

Manual property tracking works for low-volume venues with a single booking coordinator and infrequent availability changes.

Where native breaks

  • Year-view context is hard to read from a list of property values — you can’t see the shape of a year at a glance.
  • Status language drifts when multiple people manage the same venue’s calendar.
  • Double-bookings happen when the spreadsheet or property list wasn’t updated between requests.
  • Deal-date context (when deals close, when events run) isn’t visible alongside availability without cross-referencing multiple records.

Operational utility path

Use TabCalendar when multiple people check or update availability for the same venues, sold/held/unavailable status needs to be visible alongside HubSpot deal dates, and year-view planning is a regular part of the workflow.

Why this is harder than it sounds

  • Venue availability is cross-date and cross-record: it’s not one field on one record, it’s a state that spans time and links to deals.
  • sold vs held vs unavailable are operationally distinct states that need consistent meaning across the team — not just different values in a dropdown.
  • Manual date reconciliation is fragile: the moment two people are checking availability simultaneously, the spreadsheet is already stale.
  • Deal dates in HubSpot and venue availability are logically connected, but HubSpot doesn’t surface them together natively.

What you’ll get (TabCalendar)

  • Hosted fullscreen calendar at /calendar/fullscreen, launched from HubSpot Company or Deal context.
  • Year / Month / Week / Day view modes over the same availability model.
  • Canonical status set: sold, held, unavailable — defined and consistent across the team.
  • Day-level actions: manual holds, plus deal and note creation from a specific date (permission-dependent).
  • Optional read-only ICS subscription feeds (tokenized URLs; treat them as secrets, not public links).
  • Visibility into deal dates alongside availability status.

Prerequisites

  • TabCalendar installed and configured for your HubSpot portal.
  • Access to the Company and Deal records you’ll use as context.
  • Team agreement on sold / held / unavailable status semantics for your venue model.
  • If creating records from the calendar: permission to create Deals and Notes in HubSpot.

Boundaries and limitations

Does

  • Provide a year-view availability planning surface inside HubSpot.
  • Keep status semantics explicit and consistent across the team.
  • Surface deal-date context alongside availability.

Does not

  • Automatically resolve booking conflicts or prevent double-booking through system locks.
  • Replace HubSpot as the system of record for deals and contacts.
  • Act as a full booking system (it’s a planning and visibility surface).
  • Protect ICS feed URLs beyond the token itself.

Validation slice checklist (before rollout)

  • Pick 1–2 Company records with known deals and a representative date range.
  • Open the calendar from Company context and confirm the correct year loads.
  • Verify sold / held / unavailable status behavior on a few known deals.
  • Create one manual hold, refresh, and confirm it persists.
  • Create a test Deal and test Note from a date (if those actions are part of your workflow).
  • If using ICS: generate a feed, subscribe in a calendar client, and verify scope and filters match expectations.

Support-intake checklist

When contacting CleverCat support, include:

  • HubSpot portal ID.
  • Company ID and Deal ID if deal-scoped.
  • Steps to reproduce, with expected vs actual behavior.
  • Screenshot of the calendar state and any error message shown.
  • If ICS is involved: share the feed URL privately (it’s a secret, not a public link).
  • Approximate timestamp and your timezone.

Fallback: validate behavior in a narrow test slice, then use Known limitations and Support.

Next steps

FAQ

What status states does TabCalendar use for venue availability?

sold, held, and unavailable. These are the canonical status states — consistent across all users in the portal.

Does TabCalendar show a full year view?

Yes. TabCalendar supports Year / Month / Week / Day view modes.

Can multiple people use the same calendar?

Yes. TabCalendar is accessible to anyone with access to the associated HubSpot Company or Deal records and the TabCalendar permission context.

Does TabCalendar prevent double-bookings automatically?

No. TabCalendar makes availability visible so your team can avoid double-bookings, but it doesn’t enforce system-level booking locks or conflict resolution. Your team’s workflow determines how status changes are coordinated.

Can I subscribe to the availability calendar in Google Calendar or Outlook?

Yes, when ICS feeds are enabled. TabCalendar generates tokenized, read-only ICS subscription feeds. Treat the feed URLs as secrets.

HubSpot does a lot. Why add TabCalendar for venue availability?

HubSpot does a lot. For everything else — year-view availability planning with sold, held, and unavailable states visible alongside deal dates — there’s CleverCat.