# What data is needed for which output

<table data-full-width="true"><thead><tr><th width="266.64453125">Level</th><th width="380.4921875">Data Required</th><th width="657.7421875">AI – Predicting &#x26; Managing Demand</th><th width="800">AI – Scheduling &#x26; Allocating Supply</th></tr></thead><tbody><tr><td><strong>1</strong> – Basic</td><td>- Org team headcounts<br>• via directory integration or CSV<br>• manual input (CSV)</td><td>- Maintain accurate, up-to-date headcounts<br>• No forecasting or intelligent sharing at this level</td><td>- Auto-update space allocations, assignments or neighbourhoods to match current headcounts<br>• Instant block &#x26; stack planning</td></tr><tr><td><strong>2</strong> – Weekly Patterns</td><td>- Weekly attendance counts (anonymized)<br>• individual IDs matched to teams<br>• count of days attended per week</td><td>- Identify team-level in-office patterns<br>• e.g. 50% attend 1 day/week, 30% attend 2 days, 20% attend 3 days<br>- Classify “office personas”<br>• e.g. Type A: 5 days every other week (avg 2.5); Type B: avg 2.5 days/week<br>- <strong>Limit:</strong> no day-specific ratios → sub-optimal allocations</td><td>- Load-balance demand across weekdays<br>• Recommend which days employees should come in<br>- Match complementary schedules<br>• e.g. pair 1-day/5-day patterns with 4-day/2-day to maximize co-attendance</td></tr><tr><td><strong>3 (Recommended minimum)</strong></td><td>- Daily attendance (anonymized)<br>• did / did not attend each day<br>• IDs matched to teams</td><td>- Calculate <strong>daily sharing ratios</strong> per team<br>• e.g. Team Alpha: 2.7 people/desk (Mon), 2.1 (Tue), 1.3 (Wed), 1.9 (Thu), 3.2 (Fri)<br>- Predict <strong>peak weekly demand</strong><br>• e.g. Team Alpha peak 1.3 ratio → 8 desks for 10 people<br>- Compute <strong>team co-attendance scores</strong> (same-day % of team onsite)</td><td>- Auto-allocate the right number of desks per team, per day<br>- Optimize neighbourhood assignments<br>- Recommend day-swaps to boost same-day attendance</td></tr><tr><td><strong>4</strong> – Real-Time Insights</td><td>- Real-time attendance &#x26; location (per user)<br>• IDs matched to teams</td><td>- <strong>Live building capacity</strong> monitoring<br>• Enables on-the-fly re-provisioning<br>- <strong>Individual co-attendance recs</strong><br>• Detect low co-attendance patterns &#x26; suggest schedule tweaks<br>- <strong>Preferred space types</strong><br>• Track Wi-Fi/MAC to learn seating preferences</td><td>- Direct people to nearby desks or neighbourhoods based on real-time demand<br>- Push in-office day recs to individuals for better collaborator alignment<br>- Update future allocations by learned preferences</td></tr><tr><td><strong>5</strong> – Collaboration Driven</td><td>- Collaboration data (MS Graph, Google, Slack)</td><td>- Identify <strong>informal teams</strong> based on interaction frequency<br>• Reveal cross-org project groups<br>- Surface <strong>preferred collaborators</strong><br>• Correlate meeting locations with Wi-Fi/MAC footprint</td><td>- Auto-suggest new custom teams based on communication patterns<br>- When users span multiple teams, learn their true “home” teams via shared-wifi behavior</td></tr></tbody></table>


---

# Agent Instructions: 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/what-data-is-needed-for-which-output.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.
