Best Practices in Setting Up Hierarchical Reporting

Updated 

The best practices are listed below:

  1. Map Out Levels: Start by defining the levels of hierarchy (for example, Organization > Region > Store > Team). Make sure these levels correspond to your organizational framework. Make sure there is a distinct column that aids in recognizing each individual record or entity within the organizational hierarchy structure.

  2. Consistent Naming Conventions: Utilize consistent naming conventions for hierarchy levels and units to prevent misunderstandings during configuration and evaluation.

  1. Initial Data Upload: Make sure that the data utilized for establishing the hierarchy is precise. Utilize verified Excel or CSV files for a seamless upload.

  2. Regular Updates: Regularly refresh the hierarchy to account for changes within the organization (such as the introduction of new departments or alterations in reporting structures). Utilize the dynamic update function to upload only the rows that have been changed.

  3. Quality Checks: Conduct routine audits to ensure that the hierarchy and related data are accurate.

  1. Custom Metrics: Establish metrics that represent the key performance indicators (KPIs) pertinent to every level of the hierarchy. For example:

    1. Regional Managers: Store-level sales and satisfaction scores.

    2. Customer Experience Officers: Consolidated performance trends and strategic KPIs.

  2. Benchmarking: Utilize hierarchical reporting to evaluate comparable units (such as stores within the same area) for the purpose of performance benchmarking.

  1. Interactive Dashboards: Make use of visual tools like charts and graphs to simplify data interpretation at all levels.

  2. Filtering: Enable filtering options to allow users to concentrate on specific segments (for example, by region, store, or department).

  1. Naming for hierarchy fields: Create and designate hierarchy fields in a way that allows them to be easily identifiable for both the user setting up the hierarchy and any analyst developing a dashboard that includes filters based on the specific data represented by those fields.

  2. Create User fields: The user is required to establish user fields solely for those fields that analysts intend to use for generating dynamic reports involving all stakeholders.

  3. Populate the user fields value: Make sure to input values into the user fields exactly as they appear in the hierarchy to ensure consistent filtering.

  • Maintain Column Consistency:

    • Ensure that the names of the columns in the revised data file exactly match those set during the original configuration of the hierarchy mappings.

    • The “Unique ID” column is the only required field; all other columns are optional.

  • Unique ID is Key:

    • Always ensure that the “Unique ID” column is included in the update file, as it serves as a reference for aligning records.

    • Eliminate duplicate Unique IDs in the file to avoid any conflicts.

  • Include Only Necessary Records:

    Only include the records that require updates or new entries. It is unnecessary to re-add the complete hierarchy data.

  • Format for New Fields:

    • When incorporating new fields (such as "Country President" or "Region Governor"), make sure to add these fields as additional columns in the updated data file, ensuring they are correctly mapped during the upload process.

    • Make sure that the new column detection is genuinely a new field rather than a mistake in the column name.

  • Template Utilisation:

    • Utilize the supplied template as a foundation to guarantee the proper structure and format of the update file.

  • Ensure that the appropriate fields are linked to the hierarchy; otherwise, the hierarchical data will not be associated with the survey.

  • When utilizing APIs to populate custom field data, ensure that the appropriate value and the correct field are being filled in.

  • Make sure that the data being added aligns with the Unique ID of the hierarchy.