Imported data attributes let you bring a single, user-specific value into a review — a feedback score, a moderation note, a quality-and-risk rating — and place it exactly where it is needed. By the end of this guide you will know what imported data is, when to choose it over the other review input types, how to set it up, and what your people will see in their review.
What imported data is and when to use it
Imported data attributes are custom, single-value data points you attach to individual users and reference flexibly inside a review. Because each attribute holds one value, you can place it anywhere — inside a question, a prompt, or a summary — rather than in a fixed block.
Reach for imported data when you want to surface a specific figure or note next to the right question, and each person should see only their own value. If you need to show a set of related numbers together in a structured grid (for example fees, hours and utilisation across periods), a financial table is usually the better fit.
Example use cases
Show a partner's moderation outcome or quality-and-risk rating beside the relevant reflection question.
Bring last cycle's feedback score into a self-review prompt so people can reflect on the change.
Display a single KPI — for example a client-satisfaction score — inside the question that asks about it.
Surface a suggested banding or 'next box' note to inform a remuneration conversation.
Choosing between imported data and other input types
Reviews support several specialised input types. Use this to pick the right one before you build.
Input type | Best for | How it appears |
Imported data | Single, user-specific values placed flexibly | A standard field anywhere in the form |
Financial data table | Several related metrics shown together | A fixed table in the financial section |
Configuring imported data
Setup runs in three stages. Each links to a detailed step-by-step guide.
1. Create the import fields
Import fields live in Settings → Attributes → Import Field Group, organised into groups (for example 'Partner data' or 'Moderation meeting'). Add a group, then add each field and set its type. You must create the fields before you can import any values.
Full steps: Create an import attribute or group to hold external data
2. Load the values
Once your fields exist, add data against users:
For many users at once, use the bulk importer under Utilities → Data Utilities → Review and RemCom data import: download the sample template, populate it (keyed by Employee ID), then work through Upload File → Map Columns → Edit & Validate → Import.
For one person, add or edit their values directly in the Data Manager.
Full steps: Bulk add imported data against multiple users and Upload or edit imported data against a single user
3. Add the field to your review
In the review builder, add an imported-data field and set its identifier to match the attribute you created. The identifier is what connects the field in the form to the data you loaded — if it does not match, nothing will display.
Full steps: Show imported data into a review form
Settings reference
Setting | What it does | How to use it |
Import Field Group | Organises related import fields under a named group | Create one per theme (e.g. 'Moderation meeting', 'Partner data') |
Field name and type | Defines each single-value data point and its format | Name it as it should read to admins; set the type to match the value |
Sample template | A spreadsheet of your configured fields, keyed by Employee ID | Download it in the importer, populate, then upload |
Identifier | Links a review field to a specific attribute | In the review builder, set it to match the attribute exactly |
What the reviewee sees
Imported data appears as a standard field within the review form, alongside the other questions. Because the data is tied to each individual, people see only their own values — there is nothing for them to set up or switch on. If a value looks wrong or is missing, it is corrected by an admin in the Data Manager, not by the reviewee.
Prerequisites and common pitfalls
Permissions: loading and editing imported data is an admin task (super admin, or a restricted admin with the relevant access).
Create fields first: import values have nowhere to land until the matching fields exist.
Match the identifier: the review-builder identifier must match the attribute exactly, or the field stays blank.
Data is per user: if no value is loaded for someone, their field will simply be empty.
Tips and testing
After loading data, return to the Data Manager and use View existing data to confirm it uploaded.
Load a test value against one user before a full import, to confirm your mapping and identifier are correct.
Proxy in as a user (or preview the review) to check the value displays in the right place.
Check the review report and PDF as well as the on-screen form, so the value appears where you expect.
Where to next
Create an import attribute or group to hold external data
Bulk add imported data against multiple users
Upload or edit imported data against a single user
Show imported data into a review form
Financial tables vs imported data to show external data
Questions, or want this reviewed against our guide standard? Contact the CX team.