Templates per role
The structure of a review is defined once and reused, so cycles stop being a design project.
Reviews are the first thing a busy team drops
Everyone agrees reviews matter, and almost every small firm does them late, inconsistently, or not at all. Designing the process is work, running it is work, and the client deadline always wins.
Reviews makes the cycle a system instead of a project. Templates define the structure once. Cycles run on schedule. Calibration keeps different reviewers' scores comparable.
And because evaluations accumulate per role, the third review is better than the first: there is a history to talk about, not a vibe.
How it works
1
Set the template
Decide once what a review covers for each role. Every cycle after that reuses it.
2
Run the cycle
Evaluations go out and come back on schedule, without a people lead chasing each one by hand.
3
Calibrate
Scores are made comparable across reviewers, so the result reflects the work, not the grader.
4
Build the history
Each cycle lands in a per-role record, so growth and drift are both visible over time.
What it runs
Calibration
Reviewer scores are brought into line, which is what makes evaluations fair enough to act on.
History per role
Evaluations accumulate against roles over time. Promotion cases and problem patterns both come with evidence.
Cycles on schedule
Review season arrives on the calendar, not whenever someone finally has capacity to organise it.
Where it sits
Reviews is part of the People department of the Service Business OS, included on every plan. One credit allowance covers every module, so there is no per-agent pricing and no surprise line items.
Compare plansWorks with
Questions owners ask
What does calibration mean here?
Consistency across reviewers. Calibration keeps a strict reviewer and a generous one from producing incomparable scores for the same quality of work, so a review says something about the person, not the reviewer.
What is history per role?
Each person's evaluations accumulate against their role over time, so a review conversation starts from a record, not from whatever the last six weeks felt like.
Do I have to design the process from scratch?
No. Cycles run on templates, so the structure of a review is decided once and reused, instead of reinvented every cycle.
Make the review cycle a system
Reviews is live now. Start the trial and it is one of the modules unlocked from day one, reading the same clients and projects as the rest of the OS.
Start your 14-day trial
Every module unlocked for 14 days. Card details at checkout, nothing charged until day 14, cancel any time before then.
What starting actually involves
- Every module unlocked for 14 days — no feature is held back for a higher plan
- Card details at checkout, nothing charged until day 14
- Cancel before then and you pay nothing
- Setup runs on your own clients and projects, not a demo dataset