For modelling different types of organisational hierarchies, falcony uses the following functionalities:
The best way to use places
For each observation or audit a place must be chosen, so it pays back to:
Make them clear and distinct from each other for end-users
Not have too few of them, so that conclusions from statistics are more meaningful.
NOTE: even though in Falcony they are called places, they don't necessarily have to relate to physical sites (like stores, restaurants or buildings) but can be projects, cost centres or anything else.
Good rule of thumb is to use the lowest level of units in the organisational hierarchy. That is because they typically impact user rights but are still distinct enough for end-users. So for different industries it typically means:
Stores for Retail
Factory lines for Manufacturing
Projects for project businesses
Properties or buildings for Facilities Management
Cost centres for Logistics
Routes for Transportation
Construction projects for Construction
Restaurants and hotels for Hospitality
When you are in need of more detailed location or unit of information, it's easier to use observation questions (e.g. free-text, location or choice).
NOTE: for businesses, where places change a lot (like project businesses), Falcony allows for archiving places. This is helpful to keep the list of place neat but not lose relevant data.