Reviewer Workbook

overview the reviewer workbook is where you configure what the comp cycle actually looks like for managers — which columns are shown, which are editable, who can see what, and how the workbook is structured everything in this section is editable while the cycle is live (with a pause) adding & ordering columns click select columns to add any charthop field to the workbook once added, columns can be reordered by dragging regular fields vs changed fields for most fields, you'll notice two versions available — for example, title and title changed these are the same underlying field, but they behave differently title — displays the current value (read only context) title changed — the editable version, intended for entering a change to that field within the cycle for fields you don't expect managers to edit in the cycle (e g , department), you only need the regular version for fields where managers will be making changes (e g , title, base annualized), include the changed version changed fields are referenced in cql and formulas with a change after prefix — e g , change after title heads up if someone enters a value in a changed field that is identical to the employee's current value in primary, the value will appear to disappear after they type it in this is expected behavior — since the entered value isn't technically a change from the current value, charthop treats it as no change and clears the field column settings each column in the workbook has the following configurable properties, accessible by clicking the diagonal arrows on that column label (alias) override the default field label with a custom header name example rename "base annualized" to "current salary " editable three options editable — anyone who can see the column can edit it view only — no one can edit it edit only if — editable only when a condition is met (see below) edit only if define conditions that control when a field is editable there are two types of conditions and they can be combined data condition (about the employee being reviewed) the field is editable only if certain data is true about that employee example only editable if the employee's promotion field is yes role condition (about the cycle user) the field is only editable by certain roles example only final approvers, owners, and collaborators can edit this field commonly used for sensitive fields like comp band you can combine both e g , only final approvers/owners/collaborators can edit this field, and only if the employee is being promoted visible to control who sees the column default is everyone options data condition (about the reviewer/approver looking at the column) the column is only visible to users whose own data matches a condition example only show this column to reviewers whose department is engineering role condition only certain roles can see this column (e g , final approvers, owners, and collaborators only) "under jobs" count condition show the column only if the reviewer has at least one employee beneath them that meets a condition example only show a local currency column if the reviewer has at least one employee with a non usd base currency the cql pattern for this (underjobs count{ currency!="usd"} > 0) this is useful when visibility isn't cleanly tied to the reviewer's own attributes, but rather to the makeup of their pod conditions can be combined with or (||) or and (&&) example show this column if the reviewer has a non usd employee beneath them or their name is joe or kate collaborator visibility collaborators always see at least everything the manager sees — they will never see less if there are columns restricted to collaborators only, those will appear for the collaborator but not the manager think of collaborator visibility as an overlay manager view + any collaborator only columns budget & guidelines indicates whether a budget or guideline interacts with this field informational only — not something that typically needs to be configured manually color optionally color code the column header clients can configure this themselves — no need for csms to set it up workbook level settings frozen columns specify how many columns should stay fixed as managers scroll horizontally configured at the top of the workbook settings avoid freezing too many columns (5–6 is roughly the limit before the frozen area takes up the whole view) url & label add a hyperlink that appears in the top left corner of the workbook for all reviewers useful for linking to a reviewer guide, comp philosophy doc, or any reference resource allow reviewers & approvers to view the audit log the audit log tracks every edit made in the cycle — what field was changed, who changed it, and for which employee by default, the audit log is only visible to cycle owners toggling this setting on allows reviewers and approvers to see the audit log as well, scoped to only the employees and fields they can already see in the cycle most clients leave this off the main consideration managers would be able to see that they gave someone a 5% raise and that it was later changed to 2% by an approver customers should decide whether that level of transparency is appropriate for their culture before enabling it this setting can be toggled on and off even after the cycle is launched — no pause required post launch flexibility the reviewer workbook is the most flexible section of the cycle after launch almost everything can be changed while the cycle is live by pausing and making edits add or remove columns reorder columns add, edit, or remove editability and visibility conditions change aliases/labels adjust frozen columns one important caution do not remove an editable column that already has data entered in it removing it would delete whatever managers have already entered for that field in the cycle