> 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/overview/trial-subscription-guides/data-requirements/minimum-data-requirements.md).

# Minimum data requirements

## Overview

## Minimum data requirements

{% stepper %}
{% step %}

### Floorplan Images

We require an image of your floorplans, which can be a CAD file, an image, or a PDF. These will be automatically uploaded to gospace using our dedicated floorplan upload feature.

<img src="/files/mhQPYOW2QxBduKe0p6No" alt="" data-size="original">

{% endstep %}

{% step %}

### Historic Attendance Data (CSV via SFTP or upload)

This information will help us gain a deeper understanding of user patterns and behaviours, to train the AI forecasting model, and allocate daily forecasted sharing ratios for each team. For this we need 6+ months of daily data by person or team (ideally 12 months), anonymised userIDs are supported as long as they are the same as in the directory file.

For this we need the following fields:

* UserID (Same as exists in your directory)
* Location
* Date/Timestamp of entry and/or exit of location

#### For clarity, please ensure the data is formatted as follows:

| Date            | Card Name    | User ID         | Location |
| --------------- | ------------ | --------------- | -------- |
| 10/2/2025 16:14 | Rees Foulkes | uid-c2dr5-6f8l0 | Boston   |
|                 |              |                 |          |

{% file src="/files/2T8MAKq9RHunCn1iAGt1" %}
{% endstep %}

{% step %}

### Directory Data (CSV via SFTP)

#### **User Fields:**

**Mandatory fields for your integration:**

* **User ID**: Select the column from your CSV file that contains a unique identifier for each user, such as an employee ID or username, this must be the same user value as in your occupancy data so it is mapped correctly.
* **Email**: Select the column that contains the email address for each user.
* **First Name**: Select the column that contains the first name of each user.
* **Last Name**: Select the column that contains the last name of each user.

#### **Team Fields:**

**Mandatory fields:**

* **Team ID**: Select the column from your CSV file that contains a unique identifier for each team.
* **Team Name**: Select the column that contains the name of each team.

#### Example file:

| First\_Name | Last\_Name | Email                      | UserID          | Team\_Name | TeamID |
| ----------- | ---------- | -------------------------- | --------------- | ---------- | ------ |
| Rees        | Foulkes    | <rees.foulkes@gospace.com> | uid-c2dr5-6f8l0 | Product    | P10T   |
| Rex         | Foulks     | <rees.foulks@gospace.com>  | uid-c56n-6hjl0  | Product    | P10T   |
| Ron         | Jones      | <ron.jones@gospace.com>    | uid-d4h5-9pn61  | Sales      | S11T   |

{% file src="/files/UpOTpuOY8mxhBxudmo01" %}
{% endstep %}

{% step %}

### Continuous Occupancy Dumps

Either daily, or weekly, we require your occupancy data (in the same CSV format) to be uploaded to either your SFTP or ours, this informs the AI of the current occupancy trends so the system is aware of people coming to the office.
{% endstep %}
{% endstepper %}

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gospace.com/overview/trial-subscription-guides/data-requirements/minimum-data-requirements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.