An IT support function without a defined process is a series of reactive conversations. Someone emails a technician directly — bypassing the ticketing system. The most urgent ticket is not the one getting worked because priority is not visible. A recurring issue is resolved again and again by different technicians because no one wrote up the solution the first time. A user waits three days without acknowledgement because the SLA is aspirational rather than enforced. These are not capability problems — they are structure problems. A defined IT support process establishes the single point of contact, the triage and routing logic, the escalation paths, the SLAs, and the feedback loops that convert a reactive team into a reliable, measurable IT support function. This free IT support checklist gives IT managers, service desk team leads, and MSP operations teams a structured framework for the full IT support operational process.
Role: Single point of contact for all user requests. Handles common, well-defined issues — password resets, software installations, account unlocks, how-to queries, known errors with documented fixes.
Scope: Issues resolvable using knowledge base articles, documented runbooks, or standard procedures without specialist knowledge.
Target first-call resolution: 70–80% of all tickets.
Escalates to: Tier 2 when the issue is not in the knowledge base, requires specialist knowledge, or is not resolved within the Tier 1 SLA.
Role: Specialist technical investigation for issues that cannot be resolved at Tier 1. Covers system administration, network issues, application troubleshooting, and hardware faults.
Scope: Issues requiring specialist technical knowledge, system access, or investigation beyond standard procedures.
Target resolution: Issues escalated by Tier 1 and resolved without vendor involvement.
Escalates to: Tier 3 when resolution requires vendor support, significant infrastructure change, or vendor-held expertise.
Role: Highest technical expertise within the organisation (infrastructure engineers, architects) plus vendor and third-party support relationships.
Scope: Complex infrastructure issues, vendor bugs, configuration changes requiring expert knowledge, and escalations requiring vendor involvement.
Target resolution: Issues that require engineering-level intervention or vendor resolution.
Escalates to: Vendor or specialist third party for issues beyond internal capability.
This checklist covers the full IT support operational framework in six phases — from establishing the support function through to continuous improvement. Run it to set up a new IT support function or to assess and improve an existing one.
The foundation of an effective IT support function is a single, well-known point of contact. An IT team that accepts requests by email, Teams message, phone, hallway conversation, and ticketing system simultaneously cannot measure, prioritise, or improve its performance.
These six metrics, tracked consistently, show where the support function is performing and where it needs attention.
Definition: % of tickets resolved at Tier 1 without escalation.
Benchmark: 70–80% is good; below 60% suggests knowledge base gaps or Tier 1 skill gaps.
Definition: Average time from ticket creation to resolution, by priority level.
Why: Trend over time reveals whether process improvements are working; by priority shows where focus is needed.
Definition: % of tickets resolved within the committed SLA timeframe.
Benchmark: 95%+ for P1/P2; 90%+ overall is the minimum for a well-functioning service desk.
Definition: Average score from user satisfaction surveys following ticket closure.
Why: The quality metric that complements the efficiency metrics; fast resolution that satisfies the user is the goal.
Definition: Number of open tickets beyond their target resolution date.
Why: A growing backlog is the earliest visible indicator of capacity or process problems.
Definition: % of tickets that are for the same issue that was previously resolved.
Why: High repeat rates indicate workarounds rather than fixes; input to problem management.
CheckFlow’s IT support checklist runs the same triage, routing, and escalation sequence for every ticket — ensuring priority is visible, SLA clocks are set, and escalation paths are followed regardless of who is on shift. A consistent process produces consistent service quality.
The most common knowledge management failure in IT support is that Tier 2/3 resolutions are never written back to the Tier 1 knowledge base — so the same issue is escalated again next week. CheckFlow’s ticket closure phase includes a knowledge base update task, making continuous improvement a structural part of the process rather than an intention.
Every ticket processed through CheckFlow generates timestamped data on triage time, escalation time, and resolution time. The MTTR, SLA compliance, and escalation rate metrics that IT managers need are built from this data automatically — without separate tracking spreadsheets.
The IT support process covers the operational framework. For the individual ticket handling workflow in detail, CheckFlow’s Support Ticket Response Template covers the step-by-step process for each ticket from intake to closure. See the Support Ticket Response Template →
For MSPs managing IT support across multiple client environments simultaneously, CheckFlow’s MSP Process Management page covers the multi-client process visibility that MSP operations require. See CheckFlow for MSPs →
Support Ticket Response Checklist
IT Help Desk Daily Checklist
Incident Management Checklist
Problem Management Checklist
IT Service Request Fulfilment Checklist
Describe the process in a sentence and the AI checklist generator drafts the phases and tasks for you.
An IT support process covers six areas: support function setup and governance (single point of contact, ticketing system, team structure, operating hours, scope, SLA matrix), request intake and triage (acknowledgement, categorisation, priority assignment, and routing), Tier 1 resolution (known issue resolution using knowledge base, user communication, and escalation trigger), Tier 2 and 3 escalation (structured handover, vendor escalation, and knowledge base update), ticket closure and satisfaction (user confirmation and CSAT), and continuous improvement (knowledge base maintenance, metrics review, and recurring issue identification). The tiered model — Tier 1 for common issues, Tier 2 for specialist investigation, Tier 3 for engineering and vendor escalation — is the standard structure for effective IT support functions.
A first contact resolution (FCR) rate of 70–80% is generally considered strong for a well-resourced IT service desk. FCR measures the percentage of tickets resolved at Tier 1 without escalation to a specialist team. Rates below 60% typically indicate one of three problems: insufficient knowledge base coverage (solutions that Tier 1 should be able to apply are not documented), Tier 1 skill gaps (technicians who lack confidence or training to apply known solutions independently), or incorrect triage (tickets routed to Tier 1 that genuinely require Tier 2 involvement). Tracking FCR by category reveals which of these is the primary driver.
The terms are often used interchangeably but historically refer to different scope levels. A help desk is primarily reactive — it handles break-fix incidents and user requests, focusing on returning users to normal operation. A service desk is broader in scope, covering the full range of IT service interactions including incidents, service requests, access management, and change support. ITIL defines the service desk as the single point of contact between the IT department and users for all service interactions. Most modern IT support functions operate as service desks rather than help desks, handling both reactive incidents and proactive service requests.
A four-level priority matrix is the ITIL-aligned standard: P1 (Critical) for complete service outages or major security incidents affecting multiple users — immediate response, hours-level resolution. P2 (High) for significant degradation or issues affecting key business functions — response within one hour, resolution within four hours. P3 (Medium) for single-user issues with a workaround available — response within four hours, resolution within one business day. P4 (Low) for requests, minor issues, and questions — response within one business day, resolution within three to five business days. Priority should be assigned based on both impact (how many users affected and how critical) and urgency (how time-sensitive the resolution is).
14-day free trial, no card required. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.
14-day free trial, no credit cardFull refund in your first 30 daysUS hosting, EU on request
