A person can inquire about one gym, speak with another location and eventually join somewhere else. If one “location” field tries to represent all three events, the report can hide the difference between demand, ownership and membership.
TLDR: Define inquiry location, responsible location and membership location separately. Count people, inquiries and memberships using explicit rules. Preserve cross-location and missing-data exceptions, and verify any integration mapping before treating CRM data as membership truth.
Decide what each location field means
We recommend documenting the location relevant to each business question. Inquiry location can describe the facility requested by the prospect. Responsible location identifies who must respond. Membership location reflects the accepted membership record from the appropriate operating system.
These are proposed data definitions, not built-in HubSpot fields guaranteed to exist in your portal. Check existing properties before creating new ones.
As checked on August 28, 2026, HubSpot supports creating and editing properties, subject to permissions, subscription limits and field-type considerations. The data model still needs to reflect your operating process. HubSpot property documentation
Your lead tracking process should preserve the inquiry and the person responsible for the next step.
Keep the unit of analysis explicit
We recommend separating unique people from inquiries. One person may submit more than one request or ask about more than one location. That does not automatically represent multiple new members.
Decide whether a report counts first inquiries, all eligible inquiries, unique people or confirmed memberships. Use a stable identifier from the relevant system and document how duplicate or repeated events are handled.
Do not merge people merely because they share a phone number or household. The identity rule should be reviewed separately from the location reporting rule.
Inspect a synthetic two-location dataset
This dataset is fictional. It does not describe a Selworthy client, integration result or gym benchmark.
| Person | Inquiry location | Responsible location | Confirmed membership location |
|---|---|---|---|
| P-001 | North | North | North |
| P-002 | North | South | South |
| P-003 | South | South | Not confirmed |
| P-004 | Unknown | Central review | Not confirmed |
Under this example's unique-person rule, there are four people: two North inquiries, one South inquiry and one unresolved location. There are two confirmed memberships, one at each location. The other two rows are not confirmed members; “not confirmed” is not evidence that they will never join.
P-002 illustrates why demand and membership location should remain separate. Crediting both locations with the same confirmed member would require a deliberately defined shared-credit model, not an accidental duplicate count.
Verify the integration boundary
We recommend identifying which system owns membership status and which fields or events reach HubSpot. Inspect the actual mapping, update timing, failure handling and identifier behavior. Do not assume every membership event is available merely because the systems are connected.
The Mindbody and HubSpot integration discussion provides adjacent context. It is not evidence of your account's current mapping or a guarantee that a particular integration supports every field in this model.
Keep billing, health and other sensitive information outside an ordinary marketing-reporting worksheet unless the specific use has been reviewed and approved. This article proposes lead and membership-status reporting, not medical or payment-data handling.
Inspect HubSpot report joins and location exclusions
HubSpot's custom report builder documentation explains that the primary data source and associations affect which records appear. It also warns that records can be counted more than once when associated records meet filters repeatedly. HubSpot report data-source guidance
We recommend testing the report against a small, approved reference dataset before using totals in management decisions. Confirm how missing locations, transfers and multiple inquiries appear.
- Unassigned inquiry. Keep an owner and a visible reason for central review.
- Cross-location transfer. Retain the original request and the new responsibility.
- Repeated inquiry. Apply the documented counting rule consistently.
- Unconfirmed membership. Preserve the uncertainty instead of treating it as a confirmed sale or loss.
Report the follow-up decisions gym owners need to make
A demand report can inform follow-up and local marketing. An ownership report can reveal unhandled requests. A membership report needs verified membership evidence. Keep their definitions alongside the chart.
For broader service context, see the gym marketing and HubSpot overview. To design the underlying records and handoffs, explore HubSpot Sales Hub support or request a scoped review.
Build the location reporting specification before the dashboard
For a multi-location gym, “location” can mean the site selected on a form, the club assigned to follow up, the place a prospect visits or the location where a membership is eventually recorded. We recommend keeping those meanings separate. Overwriting the original inquiry location with the latest assignment can make historical reporting difficult to explain.
Define the reporting period and the unit being counted. A person can submit two inquiries, attend an event and later change their preferred club. Those are several activities, not necessarily several new people or new members. Keep event registrations and membership outcomes separate from lead totals until the source data supports the relationship.
Give gym owners two useful views
The first view answers where demand began. It uses the agreed original inquiry location and preserves unknown locations. The second answers who needs to act now. It uses the current follow-up owner and the receiving club. A transfer can legitimately move a person between operational queues without changing where the inquiry originated.
Marketing teams can compare campaigns using the first view, while location managers use the second to manage follow-up. Do not combine the two into a location league table without explaining the definitions. A busy transfer queue is not proof of better marketing performance.
Calculate conversion rates with an explicit denominator
In a fictional example, ten distinct eligible inquiries lead to three verified consultation visits during the agreed follow-up window. The visit rate for that defined cohort is three divided by ten. It is not a membership conversion rate, and it should not include unrelated visits simply because they happened during the same month.
If membership data is unavailable, show that outcome as unavailable. Do not substitute CRM contact creation, a booked appointment or a verbal expression of interest for a confirmed membership. Monthly revenue and annual revenue require their own financial source and date definitions.
Review missing customer data without inventing a location
Keep an exception queue for missing club preferences, conflicting assignments and membership records that cannot be matched confidently. Assign someone to review it. Do not force those records into the largest club to make a dashboard complete.
The result should let fitness professionals explain a number back to its underlying records. A useful report supports a decision about demand or follow-up; it does not need to claim that HubSpot replaces member management software.
