Writing Reviews

Why It Matters

The review you write becomes two things at once: feedback the reviewee reads after finalization, and the audit evidence your company samples from for years. Kit’s review form is structured so both come out well — required ratings make the assessment explicit, narrative answers carry the substance, and the submitted timestamp proves the review happened inside the cycle, not the night before the audit.

Review content is sensitive employee data, and Kit treats it that way: answers and summaries are encrypted at rest, and only your assigned reviews ever appear in your queue.

Your Review Queue

Everything assigned to you lives in Performance > My reviews — reviews you owe in active cycles, each with the reviewee’s name, your role, the due date, and its state. The Performance dashboard shows the same queue under “Reviews you owe.” Press Start (or Continue on a draft you’ve begun) to open the form.

Reviewer Roles

Role	Who writes it	How it’s assigned
Manager	The reviewee’s manager	Automatic, from the Managers map, when the participant joins the cycle
Self-review	The reviewee, about themselves	Automatic when the cycle includes self-reviews
Peer	A named colleague	Added manually per participant on the cycle page

All three roles fill the same form, and each is labeled in the final evidence record. Peers are named, never anonymous — an accountability record with anonymous entries wouldn’t survive an audit. One review per reviewer per participant; a manager or peer can never be the reviewee themselves.

Filling the Form

The form shows the reviewee’s role expectations (what this review measures against), then the cycle’s frozen question set:

• Rating questions — answered on the template’s 1–N scale. All rating questions are required for submission.
• Text questions — narrative answers; optional.
• Overall rating — a single 1–N score for the review. On the finalized register, the manager’s overall rating is the one reported per employee.
• Summary — the closing narrative: themes, representative contributions, growth areas.

On a self-review there’s one extra field: Your own notes — work the tools can’t see: mentoring, incident response, unblocking others. It’s stored on your participant record and feeds AI drafts of the reviews others write about you, so it’s the highest-leverage box on the form.

Draft, Submit, Retract

Action	Button	What happens
Save a draft	Save draft	Content is stored (encrypted); nobody else sees it; return anytime
Submit	Submit review	Validates required ratings, stamps submitted_at, marks the review Submitted
Retract	Retract (on My reviews)	Reopens a submitted review for edits

Submission is refused while any rating question is unanswered — the form tells you how many are missing. Retracting is available for as long as the cycle is active: finalization hard-blocks on unsubmitted reviews, so nothing downstream can have consumed your review yet. Once the cycle is finalized, all reviews are read-only forever; the evidence snapshot must not drift from what was submitted.

Reminders

If the cycle has a due date, Kit chases so you don’t have to: a nudge email while your review is still open, and a last call as the due date arrives — each linking straight to the form. After finalization, reviewees are notified that their completed evaluation is available, including the full manager review.

Quick Checklist

• Open Performance > My reviews and start the oldest due review
• Read the role expectations before scoring
• Answer every rating question; use text answers for the “why”
• On your self-review, fill Your own notes with tool-invisible work
• Submit before the due date — retract later if you need to amend

Next Steps

• AI-Drafted Reviews — let the AI assemble the evidence, then edit and own it
• Goals and Check-ins — the evidence trail that makes reviews easier to write