Format Guidelines for Importing External Performance Data

15Five's external performance data import allows you to import review cycle data from sources outside of 15Five. This new capability enables you to:

  • Keep track of all performance data in one, easy-accessible location,
  • View trending review data across all performance review cycles, and
  • Easily populate the Performance tile of the HR Outcomes Dashboard using historical dataβ€” so you can immediately access insights and recommendations to improve performance across your organization.

For the import, you'll want to make sure your file is structured in a way that allows for easy processing. That way your data can be made available faster, and you can begin leveraging it for your Outcomes.

In this article, you will find...

Access and availability

⛔️ Required access to Feature Settings.
πŸ‘₯ This article is relevant to Account admins.
πŸ“¦ This feature is available in the Perform and Total Platform pricing packages.


File Guidelines

  • The file must be in CSV or XLSX format.
  • The file must contain some form of employee identifier - either Employee ID or Email Address.
  • Only one Performance Review cycle can be included per file. Each Performance Review cycle will need to be imported individually.
  • Files must be a single sheet / single tab.

Data Formatting

The following fields are able to be mapped for the file that you provide. Please note that:

  • There are very few required fields, but the more information you can provide, the more useful it will be. Both in being able to view the Performance Review cycle, and in helping you to leverage your Outcomes data.
  • You don't need to name the columns exactly as below, but it should be evident which column is applied to which field.
  • Questions should either be contained in the same column, or each have their own column (with the rows being the responses)
  • Some fields are "redundant" if you've used another field (e.g. if the full name column was used, you don't need to use the individual first and last name fields)
  • For clarity, the importer uses the following references for people:
    • Employee = The person the review is about
    • Responder = The author of the review

Field

Description

Question

The question that was asked in the review

Question info

The question description (if any)

Response

The response to the question

Score

The performance value to map to our rating scale.Β 
Currently our rating scale utilizes three performance indicator values - Bottom, Middle, and Top.

Employee name

The full name for the employee the review is written about (if the first and last name are in one column)

Employee first name

The first name of the employee the review is written about (if the first and last name are in separate columns)

Employee last name

The last name of the employee the review is written about if the first and last name are in separate columns

Employee id*

The employee ID of the employee who received the review

*Required if Employee Email is not used

Employee email*

The email of the employee who received the review

*Required if Employee ID is not used

Responder name

The full name of who wrote the review (if the first and last name are in one column)

Responses are grouped by responder if provided

Responder first name

The first name of who wrote the review (if the first and last name are in separate columns)

Responses are grouped by responder if provided

Responder last name

The last name of who wrote the review (if the first and last name are in separate columns)

Responses are grouped by responder if provided

Responder email

The email address of the person who wrote the review

Responder employee id

The employee ID of the person who wrote the review

Responder type

The type of review

Examples are manager, self, employee, peer, etc.


Sample Template

Depending on how your data export from your prior performance management system is formatted, it may be easier in some cases to use our template directly.

Download the file here!


Β 

Was this article helpful?

We're sorry to hear that.

Please tell us why →