> For the complete documentation index, see [llms.txt](https://docs.gospace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gospace.com/how-gospace-works/your-data-and-what-it-unlocks.md).

# Your data and what it unlocks

Start with what you have. See what gospace does with your data today, and what each additional source adds.

***

You don't need perfect data to get value from gospace. With just your **floorplans** and your **people and teams**, gospace can plan and allocate your workplace from day one.

Every other data source you connect makes gospace smarter. It takes a job you would otherwise do by hand, such as setting targets or deciding which teams sit together, and lets gospace do it from your real data. None of these sources is required to get started, and you can add them at any time.

**Start with what you have.** If you only have floorplans and a list of people and teams, you can already use gospace. Add more data when it suits you, and gospace upgrades automatically. Nothing you set up earlier needs to be redone.

### Features at a glance

Every available feature works from day one with your floorplans and your people and teams. Each column to the right shows what that data adds.

<table data-first-column-sticky><thead><tr><th width="189.3359375">Feature</th><th>Day one</th><th>+ Attendance</th><th>+ Zone usage</th><th width="154.38671875">+ Identified Wi-Fi</th><th>+ Microsoft 365</th></tr></thead><tbody><tr><td><strong>Occupancy planning</strong></td><td>Plans on your targets</td><td>Recommends targets</td><td>—</td><td>—</td><td>—</td></tr><tr><td><strong>Consolidation</strong></td><td>Plan it yourself</td><td>Estimates busy and quiet zones</td><td>Uses measured occupancy</td><td>Measures zone usage</td><td>—</td></tr><tr><td><strong>Desk allocation</strong></td><td>Allocates on your rules</td><td>Auto-books regulars</td><td>—</td><td>Auto-releases desks, suggests communities</td><td>Suggests communities</td></tr><tr><td><strong>Meeting rooms</strong></td><td>Recommends rooms</td><td>—</td><td>—</td><td>Releases no-show rooms</td><td>Reads calendar requests</td></tr><tr><td><strong>AI-generated teams</strong> <em>(coming soon)</em></td><td>—</td><td>—</td><td>—</td><td>—</td><td>Proposes new teams</td></tr></tbody></table>

"Day one" means floorplans plus people and teams. The sections below explain each source in detail, or go straight to Find your starting point.

### What you get from day one

With your floorplans and your people and teams, gospace can:

* **Allocate space to your teams automatically.** You set the targets, for example how many desks each team needs. AIDRA, gospace's AI engine, works out the best layout and respects the rules you give it: which teams should sit near each other, which spaces have particular features, and which desks are fixed or flexible.
* **Plan scenarios and consolidation.** Test "what if?" layouts, and plan which floors or zones to consolidate.
* **Recommend meeting rooms.** gospace knows the size of every room from your floorplans and where each team is allocated. When people request a room through the gospace app, it suggests the most suitable one nearby.

### How each data source makes gospace smarter

| Without extra data, you...                | Add this data...                   | ...and gospace does it for you                                                                                                                 |
| ----------------------------------------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Set each team's space targets by hand     | **Attendance history**             | Forecasts each team's demand and recommends targets from how they actually use the office. Books desks ahead for people who come in regularly. |
| Plan consolidation from your own analysis | **Zone usage**                     | Shows how much each floor and zone is really used, highlights low-occupancy areas, and bases consolidation on measured use.                    |
| Decide which teams should sit together    | **Presence or collaboration data** | Recommends communities of teams that work together. You review and accept each recommendation.                                                 |
| Release unused desks yourself             | **Live presence**                  | Releases desks automatically when the person who booked them isn't in the office. No check-in needed.                                          |
| Enter meeting requests in the gospace app | **Calendar**                       | Picks up meeting requests from your calendar automatically, including Microsoft Places bookings.                                               |

### What your data tells gospace

gospace thinks about data in terms of what it reveals, not where it comes from. Some sources reveal several things at once, and some things can come from more than one source.

| What gospace learns                                       | Where it can come from                                                              |
| --------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| **Your space:** buildings, floors, zones, desks and rooms | Floorplans (DXF, IMDF, PDF, JPEG), or Microsoft Places                              |
| **Your people and teams**                                 | A directory integration or a file upload over SFTP                                  |
| **Attendance history:** who came in, on which days        | Badge or access-control data, **or** identified Wi-Fi data that covers past periods |
| **Zone usage:** how much each area is used                | Space sensors, **or** Wi-Fi data (identified or anonymised)                         |
| **Live presence:** who is in the office right now         | Identified Wi-Fi data, for example from Cisco Meraki                                |
| **Meeting requests**                                      | The gospace app, Microsoft Places **or** your calendar                              |
| **Collaboration:** who works with whom                    | Microsoft 365 (Microsoft Graph and calendar)                                        |

### Find your starting point

Already have one of these? Here's what it gives you on top of floorplans and people.

#### Badge or access-control system

Gives gospace your **attendance history**. This unlocks demand forecasting per team, recommended targets, and automatic desk booking for regular attenders.

#### Wi-Fi, identifying people

The most complete single source. gospace pulls Meraki data every 5 minutes, which gives it:

* **Live presence**, so unused desks can be released automatically
* **Zone usage**, for utilisation insight and consolidation
* **Community recommendations**, based on which teams spend time together
* **Attendance history**, if your data covers past periods. In that case you don't need badge data as well.

#### Wi-Fi, anonymised

Gives gospace **zone usage**: how much each area of your building is used. This unlocks utilisation insight and consolidation based on measured use. Because the data doesn't identify people, it doesn't unlock person-level features such as live presence or communities.

#### Space sensors

Gives gospace **zone usage**, unlocking utilisation insight, low-occupancy areas, and consolidation based on measured use.

#### Microsoft 365 calendar and collaboration data

Gives gospace **collaboration** data and **meeting requests**. This unlocks community recommendations and automatic capture of meeting room requests. Our team sets this up with you.

### How much history do you need?

To forecast demand, gospace needs some attendance history. It can work with **3 months**; we recommend **at least 6 months**. If you don't have historic data, gospace starts collecting from the day you connect, and forecasting switches on once enough history has built up. In the meantime you keep working with the targets you set yourself.

### Identified or anonymised Wi-Fi?

You choose what your Wi-Fi data includes.

* **Anonymised data** is enough for zone usage and consolidation.
* **Data that identifies people** also unlocks live presence, automatic desk release, community recommendations and, with enough history, attendance forecasting.

### Coming soon

* **Automatic booking from live presence:** booking desks based on who is actually in the office, in addition to forecasts.
* **AI-generated teams:** proposing new team groupings based on how people collaborate.

### Next steps

* Connect your data: see [Connecting an integration](https://docs.gospace.com/integrations/connecting-an-integration).
* Map your people and attendance data: see [Mapping your data](https://docs.gospace.com/integrations/mapping-your-data).
* Not sure where to start? [Get in touch](https://www.gospace.com/contact) and we'll help you work out what your data can do.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gospace.com/how-gospace-works/your-data-and-what-it-unlocks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
