Skip to main content

Data Glossary

A plain-English guide to the core data concepts used in Trebellar

Written by Jeff Gagnon
Updated over 3 months ago

This glossary explains the key data terms used throughout the Trebellar platform. These definitions are intended for business users and describe how Trebellar understands your organization, people, and spaces.

As Trebellar AI continues to learn about your organization’s data and use cases, you can use your own lexicon when prompting our agents. For example, our database uses “People Group” to define what most people call department, team, or business unit. While you can use your own unique lexicon, you can always reference this glossary to provide greater specificity when prompting Trebellar AI.

Core Location & Space Concepts

Structure

A Structure represents a physical building or office location that Trebellar tracks.

Examples:

  • “NY Office”

  • “San Francisco HQ”

  • “Dallas Headquarters”

Structures are the foundation of the Trebellar platform. All attendance, utilization, and portfolio analytics roll up to one or more structures.

Common attributes

  • Address

  • Lat/Long

  • Headcount assigned to the building

  • Number of seats

  • Total square footage

  • Timezone

Floor

A Floor represents a level within a building.

Floors help organize spaces and enable more detailed analysis within a structure. If no floors are provided, information will be aggregated at the building level.

Examples:

  • “Floor 1”

  • “Event Floor”

  • “Lobby”

Space

A Space represents an individual area within a floor.

Spaces are typically shared or functional areas rather than assigned desks.

Examples:

  • Meeting rooms

  • Break rooms

  • Lobbies

  • Collaboration areas

Spaces can be marked as bookable or non-bookable and may have an assigned capacity. Additionally, you can associate any number of metadata fields to a Space. For example, a meeting room might have attributes pertaining to AV kit (e.g., Zoom vs. Cisco conferencing), whiteboard (“yes/no”), natural light (“yes/no/partial”), and other dimensions. Your Trebellar Account Manager can assist you when configuring and updating your Trebellar instance.

Workstation

A Workstation represents an individual desk or seat where a person sits.

Workstations are often associated with:

  • A floor

  • A space (for example, an open work area)

  • A People Group (department or team)

Workstation data enables more granular planning and utilization analysis but is optional depending on your use case.

Neighborhood

A Neighborhood represents a defined grouping of workstations within a space, typically used to organize seating by team, function, or work style.

Neighborhoods are commonly used to:

  • Group desks for a specific People Group (e.g., Engineering, Sales)

  • Support team-based or hybrid seating models

  • Enable flexible or unassigned seating within a designated area

A Neighborhood is typically associated with:

  • A floor

  • A space (such as an open office area)

  • One or more People Groups

Neighborhoods provide an intermediate level of structure between individual workstations and broader spaces, supporting planning, allocation, and utilization analysis without requiring seat-level assignment.

People & Organization Concepts

People Group

A People Group is Trebellar’s generic term for a group of people within your organization.

In practice, this usually maps to:

  • A department

  • A business unit

  • A function

  • A team

Examples:

  • Engineering

  • Marketing

  • Sales

  • Finance

You may see the term People Group in the platform even if your organization typically uses “department” or “team.”

Person (Employee / User)

A Person represents an individual worker in your organization.

Each person is identified using a unique, anonymized ID (not a name or email) and may be associated with:

  • A People Group

  • Full time (FTE) or contingent worker status

  • An assigned location (typically a building)

  • Seniority/Level

  • Optional metadata such as postal code (used only for commute analysis)

Trebellar does not require personally identifiable information (PII), though having a unique identifier for employees greatly enhances the analytical power of the Trebellar platform. (These IDs may be hashed or otherwise encrypted for added security. Please see this article for more details.)

Attendance & Badge Data

Badge Event

A Badge Event represents a person entering a building (or space) on a given day.

Badge data is the primary signal Trebellar uses to understand attendance patterns.

Badge data can be:

  • Unaggregated (one row per badge swipe), or

  • Aggregated (daily counts by building and People Group)

Multiple badge events by the same person on the same day are automatically de-duplicated.

Attendance

Attendance reflects how many people are physically present at a location over time.

Attendance is typically measured:

  • By building

  • By day or week

  • By People Group

Attendance is distinct from utilization, which considers space capacity.

Utilization & Capacity Concepts

Capacity

Capacity represents how many people a space, floor, or building is designed to support.

Examples:

  • A building with 500 seats

  • A meeting room with capacity 8

  • A cafeteria with 300 seats

Capacity is used as the denominator in basic utilization calculations.

Utilization

Utilization measures how much of a space or building’s capacity is actually being used.

In simple terms:

Utilization = People present ÷ Available capacity

Utilization helps identify underused or overcrowded spaces and supports scenario planning and cost optimization.

Identifiers & Data Mapping

External ID

An External ID is an alternate identifier used to match Trebellar data with data from other systems (e.g., badge systems, HR systems, booking tools).

External IDs allow you to:

  • Keep internal naming conventions

  • Map inconsistent labels across systems

  • Update display names without breaking data connections

Lease Data

Lease Data provides financial context for locations.

It may include:

  • Lease start/end dates; other key dates

  • Rent payments

  • Non-rent operating expenses

  • Currency

Lease data enables cost-based analysis and more informed AI recommendations.

OPEX Data

Data on operating expenses (OPEX) enables Trebellar users to analyze spending trends, identify cost over runs or opportunities to reduce costs, and connect spend to other data sources, such as sentiment or attendance.

OPEX data includes:

  • Category

  • Sub-Category

  • Currency

  • Additional metadata values, such as Structure or Vendor

Room Booking Data

Room Booking Data represents scheduled meetings or reservations for bookable spaces.

This data is commonly used to:

  • Analyze meeting room usage

  • Identify room squatting
    Compare booked vs. actual usage (when paired with sensors)

Sensor Data

Sensor Data includes real-time or historical measurements from physical sensors.

Examples:

  • Occupancy or presence

  • Air quality

  • Environmental conditions

Sensor data enhances utilization accuracy and enables deeper operational insights.

Employee Sentiment

Sentiment Data captures general employee feedback and/or feedback about workplaces.

This is often provided as:

  • Net Promoter Score (NPS) or Customer Satisfaction Score (CSAT)

  • Survey responses tied to locations

Sentiment data helps connect how people feel about spaces with how those spaces are actually used.

How This All Fits Together

At a high level:

  • People belong to People Groups

  • People attend Structures

  • Structures contain Floors, Spaces, and Workstations

  • Badge, booking, and sensor data describe how those spaces are used

  • Lease and sentiment data add financial and experiential context

Together, this unified data model allows Trebellar to deliver accurate analytics, trusted AI insights, and actionable recommendations.

Did this answer your question?