Questionnaire
Organization & hierarchy
How is your organisation built — legal entities, divisions, departments, cost centres — and which of those does Gfacility need to know to carry the rest of the configuration?
Updated May 18, 2026
Questionnaire · 4.1
Why this first
Almost everything in Gfacility hangs off an organisational context: users, rooms, tickets, chargeback, reporting. Model it too coarse and you get stuck on permission separation. Model it too fine and you end up with a matrix nobody maintains. You pick the right granularity now — not when the configurator starts asking questions.
What do you deliver?
Org chart with scope marks
In/out-of-scope per node, with sponsor-owner and migration source.
Cost centre mapping
Which cost centre hangs off which organisational unit, for chargeback.
Naming convention
Fixed spelling (language, capitals, abbreviations) for entities and departments.
External organisations
Suppliers, partners, customer organisations — owner, contract owner, status.
Key questions
- 1Which legal entities go into Gfacility? One or more, and where do the separation lines run (separate invoicing, separate permissions, separate reporting)?
- 2Which divisions or business units inside those entities must be visible — and why? Which decision changes if this unit is not separate?
- 3Department depth — two, three or more levels? What is the deepest level at which you still report or charge back?
- 4Cost centres — do you actually use them? One-to-one with department or overlapping? Which source system holds the truth?
- 5External organisations — do suppliers, contractors and customers also live in Gfacility? Which data comes along, which is managed in Gfacility?
- 6Reorganisations — do you expect name changes, mergers or spin-offs in the next 12-18 months? How do you handle that without tickets and bookings detaching?
- 7Naming convention — formal name, short name, abbreviation? English or local names? Pick once, apply everywhere.
- 8Ownership — who keeps the org chart in Gfacility current when HR processes a change? PM, IT-admin, HR-system sync?
Template — Org chart table
| Level | Name (formal) | Short name | Parent | Type | Cost centre | In scope? | Owner |
|---|---|---|---|---|---|---|---|
| 1 | e.g. Acme Holding NV | Acme | — | Legal entity | 100 | Yes | CFO |
| 2 | Acme Belgium NV | Acme BE | Acme Holding | Legal entity | 110 | Yes | MD BE |
| 3 | IT | IT | Acme BE | Department | 2200 | Yes | CIO |
| … | … | … | … | … | … | … | … |
Common choices
→ Keep it shallow
Three levels (entity → division → department) covers 80% of organisations. Deeper granularity is rarely maintained.
→ Split only if decision-relevant
Separate unit = separate permissions, reporting or chargeback. If not — don't split.
→ Use HR as source
Let HR own the org chart; Gfacility syncs. Prevents two truths.
→ External organisations in a separate tree
Suppliers in a separate branch, not mixed with internal departments.