Admin Configuration
Enable the feature, configure cadence, seed review cycles, and monitor operational health
Open Employee Performance
Go to Admin → Employee Performance (/admin/performance-management). This is the operations console for cadence adherence, sentiment signals, and review queues. Open Performance Review settings from the page to configure frequency, automation, templates, and company objectives.
Initial setup checklist
Confirm module access
Ensure Performance Management is enabled for your tenant before users see Profile → Performance or admin tools.
Publish a review template
In settings → Templates, create and publish at least one Performance Review template. Assign it to the learner population (via template assignments) so seeded reviews use the correct form.
Set frequency and anchor date
Under Frequency & due dates, choose default frequency (monthly / quarterly / annually), set the Frequency anchor date, and configure Days until due for pre-meeting deadlines.
Apply department overrides (optional)
In Department frequency, override the tenant default for departments that need a different review rhythm. Leave blank to inherit the default.
Seed the initial cycle
Click Create initial Performance Review cycle. The API uses your anchor date and creates scheduled reviews for eligible learners. Review created vs skipped counts in the response or KPI movement.
Configure automation (optional)
Enable automatic frequency enrollment, auto-seed for new starters, auto-seed when a manager is newly assigned, and Require initial tenant seed before automation if you want a deliberate first seed before background jobs run.
Add company objectives
Under Company objectives, maintain strategic objectives managers and learners align to during reviews. Retire outdated objectives rather than reusing ambiguous labels.
Cadence and due dates explained
| Setting | What it controls |
|---|---|
| Default frequency | How often scheduled-cycle reviews are created (monthly / quarterly / annually) |
| Frequency anchor date | Start anchor for the first scheduled cycle — required before seed |
| Days until due | Pre-meeting due date = this many days after review assignment |
| Department overrides | Per-department frequency replacing the tenant default |
| Auto-seed policies | Whether new starters or manager changes trigger new scheduled reviews automatically |
Warning
Reporting lines and no-line-manager handling
Seeding skips learners without a line manager on their user record. The No line manager KPI on the dashboard shows how many active learners are affected.
Settings → No line manager handling lets you include these learners in governance exports. Use Export no line manager CSV to share a remediation list with HR — assign managers in User Management, then re-run seed or wait for automation on the next eligibility check.
Tip
Review statuses (admin view)
Upcoming and Overdue tabs list reviews by status. Use this when triaging operations:
| Status | Admin interpretation |
|---|---|
| scheduled | Assigned but pre-meeting not started — nudge learner or manager |
| in_progress | Draft pre-meeting or partial manager work |
| submitted | Learner submitted — manager should schedule or complete the review meeting |
| locked | Complete — counts toward completion rate |
| reopened | Historical review unlocked — monitor for re-lock and audit reason |
Reports, analytics, and exports
Analytics tabs on Employee Performance support governance and leadership reviews:
| Tab / area | Use it for |
|---|---|
| KPI tiles | Total reviews, upcoming, overdue, completion rate, no-line-manager count, stale objectives |
| Snapshot | Compare learner and manager feedback averages by department or location |
| Trends | Workload, momentum, confidence, manager satisfaction, quality metrics over time |
| Individual | Per-person report panel with embedded review oversight links |
| Upcoming / Overdue | Operational queue management — filter by manager, department, location |
| Export CSV | Evidence packs for HR, leadership, or compliance stakeholders |
Recommended rhythm: check KPIs weekly, trends monthly, export a governance snapshot each reporting cycle.
What to verify after setup
- Expected learners received review assignments (compare headcount to seed result)
- No-line-manager KPI is low or has an owned remediation plan
- Upcoming and overdue queues look reasonable for your organisation size
- Completion rate moves as managers lock reviews
- Published templates match the fields you expect in manager/learner UIs
- Company objectives appear in review workflows
- Audit logs show assignment, pre-meeting, and completion events
Governance and audit coverage
| Event | What you should see in Audit Logs |
|---|---|
| Review assigned | Assignment with actor and target review context |
| Pre-meeting completed (learner) | Self completion with learner as actor |
| Pre-meeting completed on behalf | Manager or admin actor completing for learner |
| Review completed (locked) | Lock/completion event with timestamp |
| Review reopened | Reopen with reason where captured |
Audit filters
In Admin → Audit Logs, include performance-related action types when investigating a specific review lifecycle. Entries should be human-readable with actor and target user context.
Reopen from an admin perspective
Reopening is initiated from the review UI (manager workflow). Admins monitor reopened items in queues and individual reports. After corrections, the manager must lock the review again. Treat reopen as an exception with documented reason — not a substitute for getting the first lock right.
Manager-facing steps: Managers guide.
FAQ
Do I need an anchor date before seeding?
Yes. The UI blocks seed without a frequency anchor date — it anchors when scheduled-cycle assignments begin.
Why were users skipped during initial seed?
Common reasons: existing open review for that learner, missing line manager, or learner outside template assignment scope. Check no-line-manager export and user manager fields.
Can I change frequency mid-year?
Yes — update tenant or department overrides and save. Existing open reviews keep their schedule; future cycle automation uses the new settings. Communicate expectations to managers.
How do templates relate to seeding?
Template assignments determine which learners receive which form structure. Publish templates before seeding; archive old templates instead of deleting when historical reviews reference them.
Can managers submit pre-meeting on behalf of learners?
Yes — supported for live meetings. Audit trail distinguishes on-behalf vs self-service submission.
What if audit events are missing?
Confirm the review action completed successfully (e.g. lock did not error) and that audit filters include performance events. Check both admin and manager actors if investigating on-behalf flows.
Related guides
- Overview — lifecycle and roles
- Managers — day-to-day review completion
- Audit Logs — investigating events