Reward & Recognition - Signposting and Best Practice for Reporting and Data

Introduction 

The purpose of this article is to signpost reporting and data resources (R Reports, Platform Insights, MI Reports) based on common questions and to provide best practice that enables RGER employees and our clients to have structured discussions around utilising reporting and data resources. 

This article provides signposting and best practice for Reward and Recognition reporting and data resources.

Recognition

Reward

InstantAwards

AwardNominator

AwardFilePlus

Scheduled Recognition

Disclaimer: The R Reports are not designed for showing the total numbers for each department but if required these results can be obtained by exporting the R reports to a spreadsheet. These reports are not restricted to a department and can sum up across other datapoints too.

Other useful information:

Best Practice for Clients

1. Best practice and advice when it comes to using R reports for each module

R Reports are generated directly from the database and are in real time.

2. Best practice for finding and using various data sources (MI v Insights v R Reports)

Generating each report will depend on client requirements. R Reports are the most detailed reports available.

3. What are some of the most popular reports that clients use? And what is RGER’s guidance on this topic?

• R57
• R86
• R94
• R621
• R627
• R628
• R605+609

4. Why can’t R Reports or Platform Insights be displayed like MI Reports?

Each report is generated from a different dataset.  

5. What are the most efficient methods for exporting data from R Reports and Platform Insights?

The most efficient method is to export the reports into a spreadsheet.

Access and Permissions Q&A

1. What Permissions roles are needed to assign and approve access to reporting roles?

a. The only role (should be both internal and external) needed for the Reports is Reports Viewer.

2. What Permissions roles are needed to access, run and export reports? Could this be broken down by product/system feature?

a. No extra permissions are required to run and export reports.

3. Best practice - what should clients consider when deciding who has access to reports?

a. Firstly what should be taken into consideration is what kind of reports exactly they have - we have reports that are strictly internal but for those that can be shared with clients, they need to be enabled scheme by scheme. There are reports that give general data and nothing sensitive but there are some that provide details that may be considered sensitive so this should be decided by the client internally with the help of their CRM/CSM.

4. Best practice - limiting access to specific reports (e.g. different contacts for R&R management v SmartSpending management)

a. The schemes are the client platforms - some clients have just one, some may have multiple (like one global, one for UK, one for US etc). during the implementation phase once the client platform/scheme is live, if the client reports that they need something the CSMs/CRMs can check if we have this report that they need and if so - enable it for them

b. The report needs to be enabled/disabled for the entire client
c. For the enabled reports only the people with the Report viewer role from the client's end can see this. But we can't segment them, meaning whoever has the role can see all enabled reports.

Best Practice for Clients providing Data to support Reporting

1. Advice around managing bespoke data/columns added to membership data uploads, or product specific data uploads, so that they pull through to our systems? For example - needing to populate data as ‘list’ rather than ‘text’.

a. Custom data is normally added as a list rather than text when working with client membership data. This is because data added as a list will only appear in the reports. This data is available as a dropdown in the reports. Data added as ‘Text’ is not available in the reports. For more information on membership data please check Integration - Membership Data Validation article.

2. Overview on how ‘Registration Questions’ can impact membership data?

a. We use the registration questions to populate custom data which is not automatically getting into the reports. This instructs the system it should take the field from the file upload and then a config into the report is made so that the data can start getting reported automatically. Therefore if the data is not provided correctly via the membership upload then the reg question is not doing its job effectively e.g. adding the data into the reports.

3. Glossary and terminology 

a. Eligibility List: It is important to manage membership eligibility to ensure only legitimate employees have access. To achieve this we need a list of people who are allowed access to the client's program. This is called an Eligibility List.

b. Preloaded Members: The Preload option enables you to upload key information about your eligible employees to our system in advance, so all eligible employees can receive an email prompting them to activate their account on the site.

Relevant Articles:

• Managing membership eligibility
• Membership Data Validation
• Registration Criteria Options Client Welcome Pack