Cycle health
Surfaces where a round is stalling — unstarted participants, incomplete sections, deadlines about to pass — while there is still time to fix it.
Zepth Node · Workforce
Performance Management
Goals and reviews on the same record as the work — so a review has context instead of a blank form.
Last updated
Zepth Node module
Performance
AI agent built into the module
Goals & OKRsCheck-insReview cyclesOn one record
Overview
Performance management usually lives in a tool nobody opens between cycles. The goals are set in January, the form arrives in December, and the manager reconstructs a year from memory in the twenty minutes before the meeting. The result is a rating, not a judgment.
Node keeps goals, check-ins and review cycles next to the people record they belong to. The reviewer opens a form that already knows tenure, role, attendance and what was agreed at the last check-in.
A review is only as good as its record
Ask a manager to assess twelve months from memory and you get recency — the last six weeks, weighted as though they were the year. It is not dishonesty; it is what memory does. The fix is not a better form. It is a record written while the work was happening.
Check-ins against a goal produce that record as a by-product of ordinary work. By the time the cycle closes, the evidence already exists and the review becomes a reading of it rather than a reconstruction.
Why it belongs on the people record
Performance tooling is usually bought separately and integrated badly, so the reviewer sees a form with a name on it and nothing else. Tenure, role history, whether the person changed teams in March, whether they were on extended leave — all of it sits in a system the reviewer is not looking at.
Keeping performance on the same record as the rest of the employment history means that context is present by default. It does not make the judgment for the manager. It stops the manager making one without it.
Tenure and role, already there. A first review after three months and a fifth review after five years are different conversations, and the form should know which one it is.
Absence in context. Extended leave during a cycle is context a fair review needs, and it is already on the record.
History across cycles. What was agreed last time is visible this time, so commitments carry forward instead of resetting.
The value
Why it matters
Reviews that actually happen, because the cycle is scheduled and tracked rather than remembered.
Goals visible between cycles, so progress is a running record instead of a year-end reconstruction.
Context on the same record — tenure, role and history are already there when the review opens.
Consistency across managers, because everyone runs the same cycle on the same structure.
Capabilities
What you can do
01
Goals & OKRs
Set objectives with measurable key results, track progress through check-ins, and keep the team aligned on what matters this cycle.
02
Check-ins
Lightweight progress updates against a goal, so the record of a year is written across it rather than at the end of it.
03
Review cycles
Run structured review rounds on a schedule — participants, forms and deadlines defined once and applied consistently.
04
On one record
Performance sits beside attendance, tenure and role, so a review opens with the context it needs rather than an empty page.
The workflow
How it actually runs
- 1
Set goals for the cycle
Objectives and measurable key results agreed between employee and manager at the start.
- 2
Check in against them
Short progress updates written while the work is fresh, building the record the review will read.
- 3
Open the review round
The scheduled cycle opens for the defined participants, with forms and deadlines already set.
- 4
Review with context
The reviewer sees goals, check-ins, tenure and role history alongside the form rather than in another system.
- 5
Close and carry forward
Outcomes are recorded, and what was agreed becomes visible context for the next cycle.
AI that does the work
How AI changes Performance management.
Neglected goals
Flags objectives with no check-in since they were set, which is the earliest reliable sign a cycle is drifting.
It never rates anybody
The agent drafts reminders and summaries of what exists. Assessment, rating and every judgment about a person stay with the humans accountable for them.
The engineer’s judgment stays in charge; the AI removes the latency and the blind spots.
Best practices
- Schedule the cycle before the quarter starts. A review round announced mid-quarter competes with the work it is meant to assess.
- Keep goals few and measurable. A list of fifteen objectives is a list of none, and it makes the review longer without making it better.
- Require check-ins between cycles. The entire value of the goal record is that it is written while the work is fresh.
- Separate the development conversation from the compensation decision, or the first one stops being honest.
Dashboards & reporting
Dashboards cover cycle completion by team and manager, goal progress distribution, check-in frequency, and review turnaround. Aggregates are available without exposing individual review content to people who should not see it.
Live dashboards
Drill-down & filters
Export to Excel / PDF
FAQ
Common questions
Does the AI score employees?
No. It watches the process, not the person — stalled cycles, goals without check-ins, rounds about to close incomplete. Every assessment and rating is written by a human.
Can we run more than one review cycle a year?
Yes. Cycles are defined with their own participants, forms and deadlines, so quarterly, half-yearly and annual rounds can run on whatever schedule you use.
What context does a reviewer see?
Goals and check-ins for the cycle, plus tenure, role history and what was agreed previously — because performance sits on the same record as the rest of the employment history.
Who can see review content?
Access follows the same role-based permissions as the rest of the people record, and aggregate reporting is available without exposing individual review content.
Do goals have to be OKRs?
No. Objectives with measurable key results are supported, but a goal can be as simple as a stated objective with check-ins against it.
Related modules
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
See it on your project.
A short, tailored walkthrough on your real workflow — no generic demo.