What Good Self-Evaluation Examples Actually Look Like for MSP Technicians

A self evaluation in an MSP is not a compliance form. It is structured pre-work a technician completes before a review conversation. Its job is to prime the technician to reflect on specific, measurable performance so the manager can run a two-way conversation instead of a one-sided debrief. 

The standard version fails because it uses competency language such as teamwork, communication, and initiative that has no anchor in how MSP technicians are actually measured. CSAT scores, SLA compliance, ticket volume, and first-call resolution rate are the real performance dimensions. Self evaluation questions must connect to those or technicians default to one-liners. 

According to SHRM’s 2023 Performance Management Survey, 58% of HR leaders report self-assessments are the lowest-quality input in their review process. In MSPs, this gap is structural. Generic questions produce generic answers regardless of technician capability. One service delivery manager who switched from a generic Google Form to metric-anchored questions saw a measurable change in response quality before quarterly conversations. The questions changed. The team did not.

L1 is measured on volume, speed, script adherence, and end-user communication. Self-evaluation responses must reflect those dimensions, not leadership or strategic thinking. Here are example phrases across four L1 performance areas. 

Ticket handling and volume: “My ticket volume this quarter was [X]. Of those, I resolved [Y%] without escalation. The types of tickets I escalated most were [category]. I am planning to address that by [specific action].” 

SLA compliance: “I met SLA on [X%] of tickets. The SLA breaches I was involved in were on [ticket category]. Here is what I think contributed to those.” 

CSAT scores: “My CSAT score averaged [X] this quarter. The tickets where I received lower scores were typically [type]. I think the issue was [reason] and I am working on [fix].” 

“My average handle time this quarter was [X minutes]. On [ticket type], it was higher than that. I have identified [root cause] as the main factor.” 

Process adherence: “I followed the [specific process/script] on [X%] of calls. The situations where I deviated were [describe]. I did that because [reason].” 

“I flagged [X] tickets for knowledge base documentation that did not have an existing solution. [Y] of those got added.” 

A useful L1 self-evaluation response contains three things: a specific number, a named ticket type or customer scenario, and a self-identified development area. One-liners fail all three tests. 

One example worth noting: an L1 technician self-rated 9 out of 10 on customer communication while his ConnectWise CSAT was 6.2 out of 10. A metric-anchored question, “Looking at your CSAT scores this quarter, what do you think drove the result?”, surfaced that gap before the review conversation instead of making the review confrontational. 

2025 note: MSPs running quarterly self-evaluations report higher L1 retention rates compared to annual-only cycles. Shorter reflection windows produce more actionable responses from junior technicians who have not yet built the habit of performance self-awareness.

L2 sits between execution and judgment. These technicians handle what L1 cannot, and they are expected to reduce what reaches L3. Generic templates that treat L2 the same as L1 produce identical one-liner responses and leave the coaching conversation with nowhere to go. 

Self-evaluation responses for L2 should focus on escalation judgment, complex resolution quality, and knowledge contribution to L1. 

Complex ticket resolution: “The most complex ticket category I worked this quarter was [type]. My average resolution time on those was [X]. Here is what I learned that I did not know at the start of the quarter.” 

Escalation judgment: “I handled [X] escalations from L1 this quarter. Of those, I resolved [Y%] without escalating further to L3. The ones I escalated to L3 were [type]. I escalated because [reason].” 

“When I escalated a ticket to L3, I typically [describe how you prep the handoff]. This quarter, [X] of my L3 escalations came back to me. Here is what I think that means.” 

Knowledge contribution: “I identified [X] recurring L1 escalations that I think could be resolved at the L1 level with better documentation or training. I [did/did not] flag those. Here is why.” 

“I contributed [X] knowledge base articles or resolution notes this quarter. The gaps I documented were [describe].” 

CSAT on escalated issues: “My CSAT on escalated tickets averaged [X] this quarter. On the tickets where CSAT came in low, the common factor was [describe].” 

L2 is the tier most likely to plateau when self-evaluations do not ask about knowledge contribution and escalation judgment. For EOS-driven MSPs, the L2 self-evaluation is also the place to assess Rock completion and core value alignment in quarterly conversations. The self-evaluation is the only structured input that surfaces whether a technician sees themselves on a path to L3 or is content at L2 long-term.

L3 is measured on documentation quality, escalation reduction rate, mentorship of L1/L2, and the degree to which their knowledge is transferable rather than siloed. Generic templates completely miss these dimensions for senior engineers. 

Knowledge transfer and documentation: “I contributed [X] knowledge base articles this quarter. Of the recurring L1/L2 escalations I handled, [Y] now have documented resolution paths that did not exist before.” 

“The area where I think my knowledge is still siloed, where if I left tomorrow the team would struggle, is [describe]. Here is what I am doing about it.” 

Escalation reduction: “The escalation volume reaching me from L2 this quarter was [X]. Compared to last quarter, that is [higher/lower]. Here is what I think drove the change.” 

Team development: “I spent approximately [X hours] this quarter working directly with L1/L2 on skill development through ticket shadowing, documentation review, or training. Here is what I think the impact was.” 

“The most complex issue I resolved this quarter was [describe]. Here is what made it hard and what I would do differently if it came in again.” 

L3 self-evaluations are the most underused coaching tool in MSPs. Senior engineers are assumed to be self-directed, so managers rarely push them to reflect on contribution versus execution. That assumption is how knowledge silos form quietly and how L3 engineers disengage without anyone noticing until they hand in their notice.

A useful response contains three elements: a specific number or operational metric, a named ticket type, client scenario, or performance area, and a self-identified gap or development focus. A response missing all three is a one-liner regardless of word count. 

The useless response is a symptom of a bad question, not a disengaged technician. 

Useless: “I worked hard this quarter and helped a lot of customers.” 

Useful: “My CSAT averaged 7.4 this quarter, down from 8.1 last quarter. The drop was mostly on tickets involving [specific issue type]. I think I was rushing those because of volume pressure. I want to slow down on that category next quarter even if it affects my handle time.” 

Same technician. Different question. Completely different conversation. 

Gallup 2024 found that only 29% of employees strongly agree their performance reviews are fair. Self evaluation quality directly drives perceived fairness. Technicians who had no structured input feel the review was one-sided. The self evaluation is the input that makes the 1:1 a two-way conversation rather than a manager monologue. Service delivery managers who see weak self evaluations should audit the form before they audit the technician.

Standard self evaluation templates break the EOS model because they produce passive responses. EOS requires the technician to show up with a point of view. That means questions must be forward-looking and tied to the quarter’s Rocks and core values. 

Six EOS-adapted self evaluation questions for MSP technicians: 

• “What was your biggest win this quarter, specifically something you can point to in ticket data, CSAT feedback, or a client outcome?” 

• “What is one thing that is not working in your current role, in the process, the tools, or your own performance, that you want to fix next quarter?” 

• “Did you complete the Rock or development goal we set at the start of this quarter? If not, what got in the way?” 

• “Where do you feel you are aligned with the company’s core values and where do you think there is a gap?” 

• “What one thing would make you more effective in your role next quarter and what would it take to make that happen?” 

• “Is there anything you are working on that you think your manager does not know about, a client relationship, a recurring issue, a skill you are building?” 

One EOS MSP with a 40% self evaluation completion rate found that conversations with completed evaluations ran 25 to 30 minutes with clear action items. Without them, 10 minutes with no commitments. The document is not the point. The preparation it creates is.

Myth 1: “Technicians cannot self-evaluate objectively, so it is not worth doing.” Objectivity is not the goal. Preparation is. A technician who reflects for 15 minutes before a review produces a better conversation than one who walks in cold. Accuracy is the manager’s job. Reflection is the technician’s job. 

Myth 2: “We track everything in the PSA. We do not need self evaluations.” PSA data tells you what happened. Self evaluation tells you why the technician thinks it happened and what they plan to do about it. Ticket volume is not a substitute for employee perspective. Gallup found 65% of employees feel they do not receive enough feedback to improve, even in data-rich environments. 

Myth 3: “Generic HR templates are fine. A question is a question.” Technicians disengage from questions that do not connect to their work. An L2 engineer will write two sentences about “demonstrating leadership” and two paragraphs about a specific escalation that changed the outcome for a client. Specificity drives quality. 

Myth 4: “Self evaluations are an HR thing, not a service delivery thing.” In MSPs, the service delivery manager runs the review. Reframing the self evaluation as “pre-work for your quarterly conversation” rather than “an HR form” increases completion rates and response quality consistently.

If your technicians are handing in one-liners, the form is the problem, not the team. Metric-anchored, tier-specific questions give technicians a frame of reference they can actually respond to. The conversation quality follows. 

Having the right examples is half the answer. The other half is a process that gets self evaluations completed before the review, stored where you can use them, and connected to the performance data you already have. 

Team GPS builds self evaluation collection into your technician review cycle, structured by role, sent on a schedule, and visible alongside productivity and KPI data when you are in the room. No spreadsheet. No chasing responses. No separate tab. See how the Productivity feature works.

Q: What is a good self evaluation example for an MSP helpdesk technician?

A. A good example references a specific metric like CSAT or SLA compliance, names a ticket type or scenario, and includes a self-identified gap. Generic phrases give the manager nothing to work with in the review conversation.

Q: Should L1, L2, and L3 technicians use different self evaluation questions?

A. Yes. L1 anchors to volume, first-call resolution, and CSAT. L2 focuses on escalation judgment and knowledge contribution. L3 addresses documentation quality and escalation reduction. One generic form across all three tiers produces identical one-liner responses regardless of role.

Q: How often should MSP technicians complete a self evaluation?

A. Quarterly matches the operational cadence most MSPs run and produces more actionable responses than annual cycles. A quarterly format should use 3 to 5 targeted prompts rather than a 10 to 15 question annual form.

Q: Why do technicians write one-line self evaluations?

A. Because the questions have no anchor in their actual work. Replace competency language with questions tied to PSA metrics and the response quality follows immediately.

Q: How does Team GPS support the technician self evaluation process?

A. Team GPS integrates self evaluation collection into the technician review cycle with structured, role-specific prompts stored alongside KPI and productivity data, giving managers a longitudinal view of technician development across quarters.