When Frappe HR appraisals replace spreadsheet reviews
Move performance reviews into Frappe HR when the current process cannot show how a rating connects to a goal. In most organizations, reviews live in spreadsheets, email threads and manager notes, so nobody can trace a final score back to the objectives it was meant to measure. A Frappe HR Appraisal Cycle fixes the structure: it sets the review period for a company, attaches appraisal templates per designation, and can automate KRA evaluation from goal progress. That gives HR one record per employee per cycle, with the template, the goals and the scores kept together.
Before you configure anything, decide which parts of the process the software should carry. The feature stores and calculates; it does not decide your rating policy. Your organization still has to settle the rating scale and what each level means, how goal weights are set for each designation, whether progress-based scores are accepted as final or only as a starting point, and what a manager may change after self-appraisal and feedback are in. Calibration rules are the same kind of decision: who compares ratings across teams, when, and how disagreements are recorded. Write these rules down and have HR, finance and the relevant business leaders sign off before the first cycle opens.
Confirm three things with your own HR team before building. First, check the current Frappe HR documentation for the exact fields, options and automation behavior in your release, because the appraisal workflow is not described in detail in the sources available here. Second, list which designations need different templates and which goals feed into them, since a template that is wrong for one role will produce scores nobody trusts. Third, decide how appraisal outcomes will be used, for example in salary revisions or promotions, and make sure those downstream steps can read the final scores. Errors found after a cycle closes are harder to correct than errors found in a test cycle with a small group.
Scoring options and when each fits
This table compares goal-based KRA scoring, which is calculated from goal progress, with manual scoring by the reviewer, and one shared appraisal template against templates set per designation. Read each row as a decision: the trade-off shows what you must have in place before choosing an option. The main takeaway is that automation depends on clean goal data, manual scoring depends on reviewer calibration, and designation templates require ongoing upkeep as roles change.
| Decision | What it requires | Main trade-off | Choose it when |
|---|---|---|---|
| Goal-based KRA scoring | Goals created against the appraisal cycle, with progress recorded consistently by employees or managers | Scores are only as accurate as goal progress data; stale or loosely worded goals produce misleading results | Goals are measurable, owners update progress on a regular basis, and you want less manual scoring |
| Manual KRA scoring by reviewer | Reviewers score each KRA directly, with agreed rating criteria written down | Scores reflect reviewer judgment, so consistency across teams depends on calibration sessions | Work is hard to quantify, goals are qualitative, or managers need to explain ratings in detail |
| Hybrid scoring | Measurable KRAs use goal progress and qualitative KRAs use reviewer scores, with a clear rule for each | Two scoring paths add setup effort and must be explained to employees so the final score is understood | Roles mix quantifiable targets with behavioral or project-based expectations |
| One shared appraisal template | A single set of KRAs and rating scale applied to every employee in the cycle | Fewer templates to maintain, but KRAs may not fit specialized roles well | Designations are similar, or the organization is small and wants minimal setup |
| Appraisal templates per designation | A template for each designation with KRAs that match the role's duties and rating criteria | Fits role-specific work, but each template needs review whenever job descriptions or designations change | Roles differ materially, and HR can keep templates current each cycle |
| Self-appraisal and feedback | Employees complete their own assessment before the reviewer scores, with feedback steps defined in the cycle | Adds time to the cycle and can widen gaps between self and manager ratings, which must be discussed | You want employees to contribute evidence and the review process needs a documented second view |
| Calibration across reviewers | Agreed rating definitions and a review meeting where managers compare scores before finalization | Takes reviewer time, but reduces inconsistency in manual scoring | Multiple managers score similar roles and fairness across teams is a concern |
| Template upkeep | Named owner for each designation template, reviewed at the start of each cycle | Without an owner, templates drift from actual roles and KRAs stop matching work | You have frequent role changes or many designations in the company |
Setting up an appraisal cycle in Frappe HR
This sequence moves an appraisal cycle from a defined company and review period to a tested process that employees and managers can use. Each step ends with a check so problems surface in a small test group before the full population is affected.
Confirm the company and review period
Start by confirming which company the cycle covers, the review period start and end dates, and which employee groups are in scope. Your HR lead and the finance or payroll owner should agree these in writing, because the cycle is tied to company records and changing them later means reworking every appraisal record. Check that the employees in scope are active, have current designations and reporting managers, and that no one is missing from the employee master. The step is done when the company, period and scope are recorded in the cycle plan and signed off.
Define KRAs and designation templates
Agree the key result areas and goals for each job family with the managers who will score them, then build an appraisal template for each designation that needs one. Templates hold the criteria, their weightage and the rating scale used in the review. Keep KRA wording specific enough that two managers would score the same work similarly. The check is a list of every designation in scope with its template attached, so no employee falls through because a designation has none.
Decide the evaluation method
Choose how KRA scores are produced: scored manually by the manager against the template, or calculated from goal progress where the cycle is set to automate it. Confirm this choice with HR and the managers before goals are loaded, since the method determines whether goal records must carry progress values and who updates them. Document the rule for any mixed case, such as a template that is manual for some criteria. The check is a one-page evaluation note that each template owner has read and approved.
Load goals and appraisal records
Create the goals for each employee and link them to the relevant KRAs, then generate the appraisal records for the cycle. Confirm with the Frappe HR documentation how your version creates appraisal records from the cycle, and whether goals are attached before or after generation. Check a sample of records to confirm each employee has one appraisal, the correct template, the right reviewer and the goals that apply to their role. Any employee without a record or with the wrong template should be corrected before the test run.
Run a test cycle with a small group
Select a small group of employees across at least two designations and a few managers, then run the full path: self-appraisal, manager scoring, feedback and final submission. Use a test copy or a limited cycle if your environment provides one, and do not send production notifications to employees outside the group. Record every point where a field is missing, a score does not calculate as the evaluation note describes, or a user lacks permission. The check is a short defect list that is cleared or accepted before the full rollout.
Open self-appraisal and manager feedback
Once the test group completes without open defects, open the cycle to the full population in the order your process needs: self-appraisal first, then manager review and any feedback collection. Confirm that each user can see only their own appraisals and that managers see their direct reports, using the role and permission setup of your site. Monitor submissions against the cycle plan and follow up with employees and managers who have not started. The step is complete when every appraisal in scope has moved to the agreed stage and the feedback record is captured for the next review.
Verify results before closing the cycle
Before closing, review the scores, the calculated KRA results and the feedback against the evaluation note, and confirm that any manual overrides have a recorded reason. Export the appraisal records for HR and keep them with the cycle plan so the outcome can be explained later. Ask your Frappe HR support partner or internal admin to confirm how your version handles the close state and whether records can still be edited afterwards. The check is a signed-off summary showing counts by stage and designation, with exceptions listed.
Where appraisal rollouts go wrong
Most appraisal problems in Frappe HR trace back to setup decisions made before the first review opens. The cards below cover the risks we see most often and the control to put in place for each, so the cycle runs on the data it was designed to use.
Goals not linked to KRAs
If employees set goals that do not map to the KRAs on their appraisal template, the progress data never reaches the score. The KRA evaluation method can be automated from goal progress, but only when the goals and KRAs share the same definitions. Before launch, have each department lead confirm that every template KRA has at least one goal that feeds it, and test one cycle with two or three sample employees.
Designation changes after templates are built
Appraisal templates are assigned per designation. When a job title is renamed, split or promoted mid-year, employees can end up on a template that no longer matches their role, or on none at all. Assign a named owner to the designation list and agree a rule for when templates are cloned rather than edited. Check the employee list against the templates before each cycle opens, especially after reorganizations.
Scores entered after the cycle closes
Late manager ratings and self-appraisals create gaps between the cycle record and the decisions made from it, such as increments or bonus inputs. Confirm the review period, submission deadlines and who may still edit an appraisal once the cycle is closed. Write these rules into the cycle setup, then run a dry check two weeks before the deadline to list reviews that are still open.
Feedback mixed with ratings
When free-text feedback sits in the same fields as scored KRAs, managers write comments that change how a score is read, and reviewers cannot separate performance evidence from opinion. Decide which items carry a numeric score and which are narrative, and keep them in separate fields on the template. Ask HR to review a sample of finished appraisals to confirm that comments support, rather than replace, the scores.
Unclear access to peer reviews
Managers should see the appraisals of their own reports, not those of peers in other teams. Role and permission settings in ERPNext decide what each user can open, so an unreviewed setup can expose salary-linked review data across the company. Map each role to the appraisals it can read and edit, then test with a manager account from two different departments before any employee is invited to the cycle.
Who can see appraisals and how access is controlled
Appraisal records are personal data. They hold performance ratings, goal scores, self-assessments and manager comments about named employees, so access should be decided before the first cycle opens, not after the first complaint. In ERPNext, visibility is governed by role permissions on the Appraisal and Appraisal Cycle DocTypes, refined by user permissions that limit which employees a user can open. Confirm which roles can read, write and submit appraisals, and whether managers see only their direct reports or the whole department. Also decide who may view the KRA templates and any formulas used for scoring, since those reveal how ratings are calculated.
Identity is the other control point. ERPNext can sign users in through LDAP against Active Directory or OpenLDAP, with LDAP groups mapped to ERPNext roles at each login, and through Social Login Keys with providers or custom OAuth or OpenID Connect endpoints. A group mapping that is too broad can grant appraisal roles to people who should not see other employees' reviews, so review the mapping and the role assignments it produces. Scoring logic that goes beyond standard fields is usually written as a Server Script. From version 15, Server Scripts are disabled by default and must be enabled with server_script_enabled, and Frappe Cloud public shared benches do not allow them. If your scoring depends on custom code, confirm the hosting option supports it before you design the process around it.
Test every rule on a staging site with dummy employees in each role before the cycle opens. Log in as a manager, an HR user, a reviewer and a standard employee, then check that each can see exactly what they should and nothing more, including list views, reports, print formats and the self-appraisal link. Confirm that exports and the Data Import tool respect the same restrictions. Record the results as evidence, because auditors and works councils will ask how access to performance data was verified. Re-run the test whenever roles, LDAP mappings or permissions change.
Limits to confirm in your environment
Frappe HR appraisals depend on the version you run, the goal types you track and how your cycles treat people who join or leave mid-period. The cards below cover the checks that decide whether the built-in appraisal flow fits your process or needs custom work.
Frappe HR version and support status
Appraisal behavior changes between releases, so start by confirming which ERPNext and Frappe HR versions you run and whether they are still supported. Frappe's supported versions page lists the current support windows. Ask your team to record the exact version in writing, since later upgrades may change appraisal templates, cycle logic and KRA fields. A version that is out of support affects which fixes you can get.
Automated KRA coverage by goal type
The appraisal cycle can automate KRA evaluation from goal progress, but not every goal type will score the same way. List the goals your teams actually use, such as numeric targets, milestones, behavioral ratings and project outcomes, and test each one in a staging site. Confirm whether manual scoring must remain for any category, and who overrides an automated score when the goal data is incomplete.
Mid-period joiners and leavers
Cycles set a review period for a company, so people who join or leave during that period create edge cases. Check how the cycle assigns appraisals to new hires, whether their goals are prorated, and what happens when an employee exits before the review closes. Decide who signs off a partial appraisal, and make sure exits flow into your full and final process so unfinished reviews do not stay open on inactive records.
Export options for audit
Auditors and HR leaders often ask for evidence of how ratings were reached. Confirm which appraisal records, goal progress entries, self-appraisal responses and feedback can be exported, in what format, and with what user permissions applied. Test a full export before the first live cycle. Record who can run exports, because appraisal ratings feed pay and promotion decisions and carry access restrictions.
Custom scoring and where it lives
If your scoring formula goes beyond the built-in method, decide whether it can sit in configuration or needs a Server Script or a custom app. Server Scripts are disabled by default from version 15 and must be enabled with the server_script_enabled setting, and public shared benches do not allow them. Ask whether a custom app will need to be maintained through each upgrade, and who owns that code after go-live.
Questions buyers ask before setting up appraisals
What does it cost to set up appraisals in Frappe HR?
The cost is the time someone spends turning your review policy into configured templates, cycles and scoring rules, plus any testing and training. No price list applies, and the quote follows from a written scope. The main drivers are the number of designations that need their own template, how many scoring methods you use (manual ratings, goal-based KRA scoring or a mix), how many goals must be imported or migrated from a spreadsheet, and whether approval routing follows an existing org chart. Software licensing is not the main line item: ERPNext and Frappe HR are free and open source, and the Frappe Cloud prices listed on the ERPNext pricing page apply only if you choose that hosting. Ask for the quote to split one-time configuration from any recurring support or hosting costs.
How long does a first appraisal cycle take to prepare?
Preparation time depends mostly on how settled your review policy is before anyone opens the system. Teams that already agree on competencies, rating scales, weights and review dates usually spend the time on configuration and testing. Teams still debating what a KRA means or who approves a rating will spend longer on decisions than on setup. Plan for a pilot cycle with one department before rolling out company-wide, and confirm the timeline with your implementation partner or internal owner against the written scope rather than against an assumed duration.
What must HR supply before configuration starts?
HR must supply the decisions the software cannot make for you. Typical inputs are the list of designations that share a template, the competencies or KRAs for each, the weight of each KRA in the final score, the rating scale and its definitions, the review period and dates for each cycle, and who completes self-appraisals, manager reviews and any feedback. If goal-based scoring is used, you also need the goal source (for example, goals entered in the system or imported from a spreadsheet) and a rule for how goal progress maps to a KRA score. A short sign-off document covering these items prevents most rework.
Can our HR team configure appraisals without a partner?
Often yes, for a straightforward policy. Frappe HR's Appraisal Cycle sets a review period for a company, links appraisal templates per designation and can automate the KRA evaluation method from goal progress, so an HR administrator with access to the setup can build a basic cycle. A partner adds value when the policy has many designations, custom scoring logic, integration with payroll or a separate approval chain, or when the migration of past reviews is needed. Test the configuration with a few sample employees before a live cycle, and confirm with Frappe documentation which settings your version exposes.
What recurs after go-live?
After go-live, recurring work is operational rather than installation. Each cycle needs someone to open it on schedule, check that templates still match current designations, and confirm that managers and employees receive their tasks. Templates and KRAs change when roles change, so review them before each cycle. If you self-host, the platform itself needs patching, backups and monitoring, and the ERPNext releases page shows frequent minor releases on supported major versions. Any support retainer, hosting cost or continuous testing should be listed separately in the quote so you can see what repeats each year.
How do we handle a version upgrade without breaking appraisal data?
Treat the upgrade as a change to the whole HR stack, not only to appraisals. Check that your ERPNext and Frappe Framework version is on the supported versions list, since the supported versions page lists end-of-life dates, and note that Frappe warranty coverage requires a listed version and a matching Frappe Cloud support plan. Back up the site, run the upgrade in a staging copy, and confirm that open appraisal cycles, templates and any custom scripts still behave as expected. Custom scripts need extra attention: starting from version 15, Server Scripts are disabled by default and must be enabled with server_script_enabled, so confirm that setting after an upgrade.
Should goal-based KRA scoring or manual scoring be used?
Choose goal-based scoring when goals are entered and tracked consistently in the system and managers trust the progress data. Choose manual scoring when goals are qualitative, change often or are not yet tracked. The trade-off is consistency against judgment: automated scores are repeatable but only as good as the goal data behind them, while manual scores allow context but depend on each manager's calibration. Many organizations start with manual scoring for one cycle, collect goal data, and then introduce automation. Decide this before building templates, because the scoring method shapes which fields HR must maintain.
How DeployOpen scopes and delivers appraisal setups
DeployOpen plans, configures, tests, documents and supports Frappe HR appraisal setups inside the infrastructure you control. Engagements start from a written scope that defines which appraisal templates, cycles and KRA methods are in play, so your HR and finance teams agree on the design before any configuration begins.
How we scope
- Map which designations need their own appraisal template and which share one.
- Agree whether KRA scores are calculated from goal progress or entered manually by reviewers.
- Confirm the review period, cycle owners, approvers and who can see each appraisal record.
How we build
- Configure appraisal templates, KRA entries and cycle settings in a non-production ERPNext site first.
- Test a full cycle with sample employees, covering self-appraisal, manager scoring and final review.
- Record any custom scripts or fields in exportable form so changes can be reviewed and reproduced.
How we hand over
- Provide written documentation of templates, cycle steps, roles and the scoring method your team chose.
- Walk HR administrators through opening a cycle, tracking progress and closing it.
- Hand over a list of open decisions, such as rating scales or feedback rules, that your leadership must confirm.
How we support
- Offer ongoing support and upgrades as a retainer, sized to the written scope.
- Review appraisal configuration again before each new cycle or a change in ERPNext version.
- Confirm with your own HR policy owners any change to how goals or ratings feed compensation decisions.
