ANTE User Manual

Rank and Release the Results

Once every Evaluation is agreed, the people of a cycle are ranked: the section head proposes a rank for each person, the heads above check the spread against the bell curve, HR sets the final rank and approves, and then each person is told in a conversation and the result is published. This tutorial follows the Creative Studio from Start Ranking to published results.

Before You Start

  • All seven Evaluations of the FY2026 Annual Evaluation are agreed (see Run an Evaluation Cycle). The Ranking is refused while any active person's Evaluation is not agreed: agree it, or withdraw someone who left.
  • The cast: Demo Account (HR) starts and approves the Ranking. Lena Vargas (section head) ranks her section and holds the talks with Marco. Marco Reyes (manager of the six designers) holds the talks with them.
  • The company bell curve is the default: S 10% · A 20% · B 40% · C 20% · D 10% · E 0%.
From Start Ranking to published results
6 steps
  1. 1. Start Ranking: the Evaluation sheet appears
  2. 2. The section head proposes a rank for each person
  3. 3. Check the bell curve before locking
  4. 4. Lock the tiers, set the final rank and approve
  5. 5. Release: managers talk to each person, then publish
  6. 6. What the employee sees
1Start Ranking: the Evaluation sheet appears

On the cycle page HR clicks Start Ranking. Ante builds the Evaluation sheet: one row per person with what it already knows, and empty columns for the managers. The Ranking has five tiers: Section managers → Department / Division → GMs → GM + BOD → Approved. The Section managers tier is open first.

Years in gradecomputed
Whole years in the current job grade at the end of the review period.
Base rankcomputed
The rank the form recommends from the years in grade (B from 2 years, C from 1).
Selectioncomputed
1st, 2nd or 3rd+ selection of the person's grade group; used by the Promotion view.
Raw Scorecomputed
The total of the agreed Evaluation, with its version (v4 means four agreed versions).
Rank historycomputed
One small box per earlier year with the person's released rank.
What the sheet already shows for each person
PersonGradeYears in gradeBase rankSelectionRaw score
Ana LimGS33B2nd80.00
Marco ReyesMM24B2nd78.33
Ben CruzGS33B2nd76.67
Carla DiazGS22B1st76.67
Dan OcampoGS22B1st73.33
Elisa TanGS11Cnone71.67
Felix GoGS11Cnone70.00
All of it is computed. Ana's raw score 80.00 is the total from the Evaluation stage.
The Ranking card: five tiers, Section managers is current
  1. 1Current tier: managers fill and finalise
  2. 2Lock this tier and open the next
  3. 3Years in grade, base rank and raw score are computed
2The section head proposes a rank for each person

Lena opens Performance → Evaluation Center (or My section's Evaluation Center). Her rows show the manager columns. She fills them for each person and presses Finalise on the section.

MG RankS · A · B · C · D · E
The rank the section head proposes. Pre-set to nothing; the base rank is shown beside it as a hint.
Significant comment of MGtext, required when the rank differs from the base rank
Ante refuses a rank that differs from the base rank without a comment. The row shows Differs from base.
Prioritization (if necessary only)1, 2, 3 …
Orders people within the section when the heads need a sequence.
Finalise (section)
Locks the head's proposals. It lists anyone not ranked yet, and lets you finalise anyway.
Warning
A rank that differs from the base rank, here Ana at A while her base rank is B, always needs a comment. That is the audit trail for a bell-curve exception.
Lena's proposals for the Creative Studio
PersonBase rankMG rankComment needed
Ana LimBAYes: delivered the brand system early and mentored two designers
Ben CruzBBNo
Carla DiazBBNo
Marco ReyesBBNo
Dan OcampoBBNo
Elisa TanCCNo
Felix GoCCNo
Lena's Evaluation Center: raw score, prioritization, MG rank and comment
  1. 1Raw Score
  2. 2MG Rank, base rank beside it
  3. 3Significant comment
  4. 4Differs from base: Ana A against base B
3Check the bell curve before locking

Bell Curve (button on the cycle page) counts how many people hold each rank, per job grade and for the whole company, against the guideline. Choose the Scope (company or one unit) and the Rank column (MG rank, SM/GM rank, final rank).

Scope
The whole company or one unit of the org tree.
Rank columnMG rank · SM/GM rank · Final rank
Which proposal is counted. The page counts what is saved.
Count / guideline (per rank)
How many people hold the rank against how many the guideline allows, with the share. A box over the guideline is marked with a warning.
Budget notefree text, 500 characters
The increase budget for the review period, shown beside the curve. Nothing is calculated from it.
Creative Studio against the company bell curve (7 people)
Guideline: S 10 · A 20 · B 40 · C 20 · D 10 · E 0 (%)Each share × 7, rounded upS 1 · A 2 · B 3 · C 2 · D 1 · E 0
Proposed by Lena→S 0 · A 1 · B 4 · C 2 · D 0 · E 0
Over the guideline→B by 1
B has one person more than the guideline, so the page marks it. It is a warning: the heads decide whether to move someone.
Bell Curve: counts per grade against the guideline
  1. 1Scope
  2. 2Rank column
  3. 3Total row: B 4 / 4
  4. 4Guideline for all 7 people, rounded up
  5. 5Budget note
4Lock the tiers, set the final rank and approve

HR presses Lock … to close one tier and open the next: Department / Division, then GMs. Each lock freezes a numbered version of every row, so the history shows who proposed what. At the last tier HR (with the board) sets the Final rank and presses Approve (Final).

Lock … and open the next tier
Freezes the proposals of the current tier. Refused while a person's Evaluation is not agreed.
SM/GM rank
The rank the department and division heads propose over the section heads'.
Final rankS · A · B · C · D · E
The decision. The Approve button needs every final rank set, or asks you to confirm.
Board approverspeople, optional
Named people who may set the final rank with HR. None named yet in the tutorial company.
Approve (Final)
Freezes the whole sheet as the result. After this only an amendment can change a rank.
ReopenHR, with a reason
Takes the sheet back one step. Anything already released goes "under review".
The result HR approves
PersonRaw scoreMG rankFinal rank
Ana Lim80.00AA
Marco Reyes78.33BB
Ben Cruz76.67BB
Carla Diaz76.67BB
Dan Ocampo73.33BB
Elisa Tan71.67CC
Felix Go70.00CC
The five tiers each keep a version: Section managers v1, Department / Division v2, GMs v3, GM + BOD v4, Approved v4.
Three tiers locked; the last tier waits for the final rank and approval
  1. 1Locked tiers with their version and date
  2. 2GM + BOD: board and HR set the final rank
  3. 3Approve (Final)
5Release: managers talk to each person, then publish

Once the Ranking is approved, HR clicks Open Release and may set a discussion deadline. Employees see their rank only after it is published. The manager and the employee both confirm the talk took place; then the manager (or HR) publishes.

Discussion deadlinedate, optional
After it, HR may publish a result with a reason from the Resolution Center. Tutorial: 15 December 2026.
Discussed (manager)button + note
The manager confirms the talk took place, with a note of what was said.
We Discussed My Result (employee)
The employee confirms from their own page. With "Both press Discussed" on (the default), both are needed.
Publish (row / section / all discussed)
Shares the rank with the employee: "FY2026 · Rank B · shared by Marco Reyes on …". Publishing twice is refused.
UnpublishHR, with a reason
Takes a published result back; the discussion stays.
Info

If a rank changes after the talk, with the default setting both people are asked to discuss again before it can be published.

Release to employees: 5 of 7 discussed, 5 of 7 published
  1. 1Release opened Nov 20, 2026
  2. 2Discussion deadline Dec 15, 2026
  3. 35 of 7 discussed · 5 of 7 published
6What the employee sees

After publishing, the employee's My Performance shows the result with who shared it and when. They never see the raw score (unless the form says so), the manager's comments, or anyone else's rank. Ana and Felix have not been discussed yet, so their results stay hidden and show on HR's list as waiting.

Release progress at the end of this tutorial
PersonFinal rankDiscussedPublished
Ben CruzBYesYes
Carla DiazBYesYes
Dan OcampoBYesYes
Elisa TanCYesYes
Marco ReyesBYesYes
Ana LimANoNo
Felix GoCNoNo
After 15 December HR can publish the two remaining results from the Resolution Center, each with a reason.
Ben's own page after Marco published his result

What the Job Produced

Result of the FY2026 ranking
People ranked7
Final ranks (S · A · B · C · D · E)→0 · 1 · 4 · 2 · 0 · 0
Results published to employees→5 of 7
Salary review and promotions can now start→Evaluation sheet approved
The approved Evaluation sheet is what the salary review, the promotion recommendations and the amendments read.
Where the approved result goesWhat it reads
Salary ReviewFinal rank per person, to suggest the increase
PromotionsFinal rank, selection and years in grade
AmendmentsThe approved sheet, to correct one person
Next year's Rank historyThe released rank, one box per year