Performance Reviews for Agencies: A Practical Quarterly Process

The Quarterly Check-In Model: What It Covers

A quarterly check-in is not a mini annual review. It has a different scope, format, and purpose. What it covers: progress on goals from the previous quarter, observations about performance in the past 90 days (both what went well and what could improve), the team member's own assessment, and goals for the next 90 days. The conversation takes 30 minutes, not two hours. What it does not cover: compensation decisions (those happen annually or at role change), disciplinary matters (those have their own process), organizational strategy. The distinction matters because mixing these topics changes the emotional register. A 30-minute development conversation feels fundamentally different from a 90-minute review where compensation and discipline are also on the table. The quarterly model works because it is lower stakes and therefore more honest.

How to Prepare for a Quarterly Review

Preparation separates a useful quarterly check-in from a pleasant but vague conversation that produces nothing actionable. The manager's preparation takes 15-20 minutes if the right data is accessible.

• Review the goals from last quarter — were they achieved? Partially? Not achieved? Have a clear view before the conversation.
• Pull the objective data — hours logged, tasks completed, billable utilization rate, project delivery track record for the quarter.
• Review your own notes — from 1:1s, project retrospectives, or client feedback over the past 90 days.
• Identify your 2-3 main points — not a comprehensive list of everything that happened. Being focused is more useful than being comprehensive.
• Send a brief self-assessment request — three to five business days before the review: What went well this quarter? What was harder than expected? What did you learn? What do you want to focus on next quarter?

The Data You Should Pull Before the Meeting

Objective data transforms a performance conversation from an exchange of impressions into a discussion of evidence:

• Work Report — hours and projects for the quarter: total hours logged per week, hours per project, billable vs non-billable split. Was the person fully utilized? Were there periods of apparent underwork or overwork?
• Task completion rate — tasks assigned vs completed, with any pattern in types of tasks consistently late. More direct than hours alone.
• Billable utilization rate — quarterly average at, above, or below target. A significant divergence from target warrants a conversation about what consumed non-billable time.
• Sentiment data — if running weekly pulse check-ins, the quarterly trend is relevant context. Not as a performance metric, but as context for the person's subjective experience alongside objective performance data.

The Review Conversation Structure

The 30-minute quarterly check-in has three parts, each roughly equal time. Part 1 — Look back (10 minutes): start with the team member's self-assessment. 'How do you feel the quarter went overall?' Let them lead. Their assessment tells you a great deal about their self-awareness. After their assessment, share yours. Start with what went well — specific examples, not generic praise. Then address what could improve — specifically and with reference to observable behaviors or data. Part 2 — Current state (5 minutes): a brief check on how the person is experiencing their current situation. Workload, role clarity, any support they need. If you already know from sentiment tracking that the person found the quarter difficult, address it directly. Part 3 — Look forward (15 minutes): the goals conversation. Ideally the team member proposes their own goals (this creates ownership) and you refine, add, or redirect. Goals should be specific, connected to real project work, and attached to a metric that lets you evaluate progress. 'Improve client communication' is not a goal. 'Deliver all client status updates within 24 hours of the agreed deadline for all active projects in Q3' is a goal.

Common Performance Review Mistakes Agencies Make

Mistakes that reliably undermine quarterly reviews:

• No specifics — only impressions: 'You had a strong quarter' and 'you need to improve your communication' are the two most common statements and the two least useful. Both describe an impression without reference to specific events or outcomes.
• One-way conversation: a review where the manager talks and the team member listens is a monologue. The self-assessment component exists to prevent this.
• No action items: a quarterly review that ends without written goals for the next quarter has produced nothing that either party can reference in 90 days.
• Conflating performance and compensation: when compensation is on the table in the same conversation as development feedback, attention goes immediately to compensation and feedback becomes background noise.
• Recency bias without data: reviewing the last 6 weeks of a 13-week quarter. Pulling Work Reports and task data before the meeting corrects for this by making the full quarter visible.

Using Melororium Data in Performance Reviews

Melororium provides three types of data useful as performance review inputs: Work Reports: filter by team member and by the quarter being reviewed (Q3 = July 1 to September 30). Use this data as evidence in the conversation: 'Looking at the Work Report for Q3, your billable utilization averaged 62% — below our 65-80% target range. I want to understand what was consuming the remaining 38% of your time.' Productivity tab: the work session timeline for any selected period. Before the quarterly review, scan the pattern for the quarter — consistent periods of overtime that the task data or self-report did not surface? Weeks with notably sparse session data? The session timeline is context, not verdict. Sentiment scores: if running weekly pulse check-ins, pull the team member's sentiment trend for the quarter. A consistent 7-8 indicates a stable experience. A pattern of declining scores in the second half — even if they never fell below 6 — is worth asking about.

Goal-Setting for the Next Quarter

Goals set in a quarterly review should meet four criteria:

• Specific — connected to real work, not abstract improvement areas. 'Reduce average task cycle time on design deliverables from 4 days to 3 days for projects in Q4' is specific. 'Be more efficient' is not.
• Measurable — evaluable with data that will be available in 90 days. If you cannot look at a Work Report or task log at end of quarter and know whether this goal was achieved, it is not measurable enough.
• Owned by the team member — goals that the manager imposes get minimal ownership. Goals that the team member proposes and the manager refines get maximum ownership. Start with: 'What do you want to focus on next quarter?'
• Balanced — include something that develops strengths, not just addresses weaknesses. A review that only identifies improvement areas leaves team members feeling criticized rather than developed.

The 30-Day Follow-Up

Quarterly reviews have the highest development value when followed up at 30 days. A brief 15-minute check-in at the 30-day mark serves one purpose: confirming that the goals set in the review are actually being worked on and that there are no obstacles needing to be addressed. Most goal-setting conversations produce good intentions and no structural change in behavior, because the immediate pressures of client work reassert themselves within a week. The 30-day check-in is a lightweight accountability mechanism that moves goals from 'discussed in a meeting' to 'actively being worked on with management visibility.' The check-in does not need to be elaborate: 'How are you tracking on the three goals from the quarterly review? Any obstacles I can help with?' If one goal has stalled, there are still 60 days of the quarter to address it. If the check-in does not happen and the goal has stalled, you find out in 90 days when it is too late for the current quarter.