IT Service Desk and Incident Handling Competence Assessment for Support TeamsThe ticket was closed in four minutes. It came back three times.

Methodology: Forty original exercises across five formats: twelve single-choice calls on a queue (what a ticket is, what it needs first, what closing it now would cost), eight select-every-that-applies exercises about what to capture or what belongs in a record, eight true-or-false claims about how support work behaves, six match-the-following exercises pairing a symptom with the first check that separates two causes, and six ordering exercises for a diagnosis, an escalation or a message. One response instruction is declared for the whole instrument and it is a KNOWLEDGE instruction: what is the right call here, never what the respondent would do on a bad day. Construct statement: this measures competence in handling requests and incidents on an IT service desk, across five parts: understanding what a request actually is, diagnosis and first checks, escalation and handover, keeping people informed, and preventing the repeat. It is a competence assessment and not a certification; it does not measure anybody's technical depth in any particular technology, operating system or tool, and it says nothing about how a person performs under a real queue on a real day. The five parts are organised on the openly published structure of the European e-Competence Framework, whose competence areas (plan, build, run, enable, manage) and proficiency-level scale are public standards; the parts here sit in its run, enable and manage areas at the level of an individual handling work under supervision or independently. The framework is named for attribution only. This instrument is not affiliated with, endorsed by, or derived from it, from its publishers, or from any service-management framework, certification or vendor, and every item is an original work written for this instrument. Scoring: every keyed exercise carries a declared answer prior, the share of ordinary respondents expected to choose each option, each match or each position, authored per exercise. Each part is scored as the mean quality over answered exercises, corrected against the mean of those priors, so zero means no better than a respondent answering the way people typically answer; select-every exercises are scored as balanced accuracy (keyed options selected, unkeyed options left) rather than F1, so that selecting everything and selecting nothing score the same. An unanswered exercise leaves the numerator, the denominator and the chance term together; it never scores zero. A sitting with fewer than twenty-four answered exercises is refused a report rather than given one on too little. The scoring design is the Reliable Change Index published on a first sitting: for each part and for the composite, the report prints the number of points a re-sitting would have to move, either side of today, for the movement to exceed measurement error at ninety-five per cent, computed as 1.96 times the declared standard deviation times the square root of twice one minus the assumed reliability. The reliability is McDonald's omega assumed from an inter-item correlation of .26, printed unrounded; a part with fewer than eight answered exercises or omega under .70 carries a three-way placement and no number, no thresholds and no percentile, and the refusal is printed. The standard deviation of each part and of the composite is taken from a modelled reference sitting of mixed ability built from the declared priors and run through this instrument's own scorer; it is an assumption stated in the open, and observed data will replace it. No percentile appears anywhere, because there is no norm group. The change threshold is a measurement threshold and is distinguished on the report from a minimally important difference, which is a value threshold set by whoever uses the score and is usually smaller. Sources drawn on: the practitioner literature on service management and incident, problem and change handling, described generically (the distinction between an incident, a request, a problem and a change; priority as impact and urgency together; the known-error record; the single point of contact); Rasmussen, Skills, rules and knowledge: signals, signs and symbols (1983) and Klein, Sources of Power (1998) on diagnosis and troubleshooting as hypothesis-driven work; Morris and Rouse, The effects of type of knowledge upon human problem solving in a process control task (1985) on the value of one change at a time; Haig, Sutton and Whittington, SBAR: a shared mental model for improving communication between clinicians (2006) and Starmer et al., Changes in medical errors after implementation of a handoff program (2014) on the content and order of a handover; Arora et al., Communication failures in patient sign-out and suggested strategies to improve (2005); Tax and Brown, Recovering and learning from service failure (1998) and Smith, Bolton and Wagner, A model of customer satisfaction with service encounters involving failure and recovery (1999) on what an update and an apology have to carry; Dekker, The Field Guide to Understanding Human Error (2006) and Reason, Managing the Risks of Organizational Accidents (1997) on blameless review and the cause behind the symptom; the European e-Competence Framework and Boyatzis, The Competent Manager (1982) on competence areas and proficiency scales; Jacobson and Truax, Clinical significance: a statistical approach to defining meaningful change in psychotherapy research (1991) and Christensen and Mendoza, A method of assessing change in a single subject (1986) for the reliable change index; McDonald, Test Theory: A Unified Treatment (1999) and Revelle and Zinbarg, Coefficients alpha, beta, omega and the glb (2009) for omega; and Haladyna, Downing and Rodriguez, A review of multiple-choice item-writing guidelines (2002) for the item-writing rules. No real vendor, product, ticketing tool, operating system or company is named in any candidate-facing string.