Unlike most of its competitors, Aguardion utilizes a modern, ‘hierarchical’ database and logic structure.
A few examples:
‘Clients’ and ‘events’ are distinct entities within the system: events are subservient to the client record.
Equipment packages/invoice items etc are defined at the customer level and but further configured at the individual agency level
This modern, ‘object-based’ approach has a lot of advantages over the older design styles many other case management systems use. It lends itself to powerful, more nuanced reporting, is easier to customize upon and is generally more flexible.
With all these advantages comes a few caveats that the user should be aware of.
Users should think in terms of ‘events’ not ‘individuals’. When tracking down an individual case, it's easiest to utilize the event dashboards: utilizing the client dashboard as a starting point will be slower as you will be forced to follow the hierarchy (‘client’ then ‘event’) vs going straight to the event.
Secondly, when troubleshooting things like incorrect daily rates or fee items. Because of the hierarchical structure, configuration options are often split between the instance-wide and agency level.