Locations in Aclaimant

The Locations module is the foundational structure of your Aclaimant environment. It serves as a digital map of your organization, defining how data is categorized, how reports are generated, and how user access is controlled.

Properly configuring your locations ensures that incident data is attributed correctly and that your organizational hierarchy is reflected accurately for long-term analytics.

Organizing Your Locations

Aclaimant uses a Parent-Child relationship model to organize your business structure. This nested format allows you to mirror your physical and operational reality, whether you have a single office or a global presence.

Nested Structure

You can organize your company into multiple tiers, such as:

• Corporate (Top Level)

  • Region

    • Office 

      • Job Site 

This structure allows you to group locations in ways that make sense for your workflows, such as by geography (East vs. West) or by business unit (Manufacturing vs. Logistics).

Key Features

• Nested Structure: Organize your company into levels (e.g., Corporate → Region → Office). You can even group the same offices in different ways, such as by geography or by management structure.

• Automatic Permissions: If you give a manager access to a "Parent" location (like the Western Region), they automatically see all locations under it.

• Customized Views: A local supervisor only sees reports for their specific shop, while a VP can see the big picture for the whole company.

• Search and Navigation: Quickly navigate between sites using the hierarchy tree or breadcrumbs within the platform. This ensures that when a user is filing a report, they are always selecting from a pre-defined, accurate list of active sites.

  

Location-Based Permissions

User access in Aclaimant is tied directly to the Location module. By assigning a user to a specific point in your hierarchy, you control exactly what data they can see.

• Inherited Access: If a manager is granted access to a Parent location (e.g., the "Southern Region"), they automatically receive visibility into all locations nested beneath it.

• Restricted Views: A site-level supervisor assigned only to a specific "Job Site" will only see reports and data for that site. They will not have visibility into other branches or higher-level corporate data.

• Security & Privacy: This system ensures that sensitive claim or incident information is only accessible to authorized personnel based on their operational scope.

Managing Your Company Information

Aclaimant also makes it easy to keep track of your important company details—like associated safety reports, incidents, and assets—all in one place. Instead of keeping this information in separate spreadsheets, store them within Aclaimant. This ensures that your information is always accurate and easy to find when you're filling out a report.

Managing Location Status: Active vs. Inactive Status

As your business evolves, your location list will change. Aclaimant allows you to manage these changes without losing critical data.

When a job site is completed or an office is closed, mark the location as Inactive.

• Clean Interfaces: Inactive locations are hidden from daily dropdown menus and search results, preventing users from accidentally filing new reports against a closed site.

• Data Preservation: Marking a location as inactive does not delete its history. All past incidents, audits, and financial data remain stored in the system.

• Historical Audits: You can still run reports on inactive locations to analyze historical trends or fulfill compliance requirements.

Reporting

A significant benefit of a mapped location hierarchy is reporting. Because every incident is tied to a specific location, the data is surfaced through the hierarchy.

• Granular Insight: View safety performance for a single shop.

  • For example, compare the incident rates of the "Midwest" vs. the "Northeast" with one click.

• Executive Overview: View high-level data at the Corporate level that aggregate data from every underlying location in real-time.

Best Practices for Locations

• Standardize Naming: Use consistent naming conventions (e.g., Site Codes or City Names) to make searching easier for field users.

• Map Before You Build: Determine your reporting needs before setting up your hierarchy. If you need to report by "Division," ensure Divisions are represented as a tier in your map.

• Keep it Clean & Current: Regularly audit your location list to mark completed projects as "Inactive" to keep the user interface streamlined for your team.