Skip to main content
All CollectionsSurvey Admin HubEffectiveness SurveysCommunications
Individual Effectiveness 360 communications (Admin driven coachless workflow)
Individual Effectiveness 360 communications (Admin driven coachless workflow)

Guide to Individual Effectiveness (admin-driven coachless) survey notifications: message types, recipients, and timing in the 360 process.

Jared Ellis avatar
Written by Jared Ellis
Updated over a week ago

Individual Effectiveness communications are a mix of notifications and reminders. Participants will only receive a few of these messages, based on their role within the survey and how the survey is set up.

Messages will be grouped based on how they are sent:

  • Standard Communications - sent under most circumstances, as part of the standard workflow.

  • Standard Reminders - only sent to people who have not completed certain tasks within a configured timeframe.

  • Nomination Only - only sent if you are allowing employees to select reviewers.

  • Administration only - only sent under unusual circumstances, such as a change of coach.

And who they are sent to:

  • Employee - the person who is the subject of the 360.

  • Reviewer - each person who the Employee has asked for feedback.

Emails are consolidated into a single email for:

  • Invite Reviewer - lists each person who has asked for feedback from the reviewer

  • Reviewer Reminder - lists each person who has asked for feedback, and has not yet been done by the reviewer

The table below shows when the most common communications are sent during the life of a 360 process in the "Admin driven coachless" workflow.

Note: if Administrators "Share" feedback with employees, this bypasses the Employee Feedback Ready and Feedback Due Date Passed communications.

Admin_Driven_Coachless.png

The following table lists all of the possible communications for this workflow, the circumstances under which they are sent, and the default feedback due dates (found in the survey configuration page):

Admin_Driven_Coachless.png

When an employee has been asked to give feedback to several people at once, they will receive one email with a list of all the people who have requested feedback.

Specifically, the emails and reminders that are bundled are Invite Reviewer and Reviewer Reminder, for this workflow option.

Survey communication tip:

  • For bundled feedback communications (i.e. when a reviewer is invited to provide feedback for more than one person via a bulk launch action), the Employee name and Employee preferred name variables resolve as “your peers”.

  • For individual feedback communication (i.e. when a reviewer is invited to provide feedback for one person at a time, either by the person's 360 process being launched individually, or if they are added as a reviewer to an existing 360 process), the Employee name and Employee preferred name variables will work as expected (i.e returning the person being reviewed's name).

  • Reviewer reminder communication (Bundled only, regardless of the number of feedback requests): The Employee name variable will resolve as “your colleagues.” The Employee preferred name variable should not be used; when used it resolves as “your." For example: ”You’ve got just a few days left to give feedback to Employee preferred name to help them understand their strengths ” would resolve as ”You’ve got just a few days left to give feedback to “your" to help them understand their strengths”

  • Feedback request list and coached employees list communication variables use the 'Name' field; there's currently no way to configure these to use the 'Preferred name' field.

  • Reviewer invites and reminders contain two types of access to provide feedback:

    1. Direct link - only populates if the reviewer has been asked to provide feedback for multiple colleagues; there will be a list of reviewee's names. These are personal survey links (hyperlinked on the Reviewee's names).

    2. ‘Give feedback’ button - This button directs you to your Home page and your Tasks list; clicking on this button therefore requires you to login to the platform.

Did this answer your question?