Distributor Technical Capability Scorecard Template
Summary
A distributor technical capability scorecard needs 4 sections: scope and metric definitions, results by metric, recurring failures and bottlenecks, and improvement items. A manufacturer's channel or technical service manager uses it to compare how distributors handle technical inquiries, and the comparison holds only when every denominator and exclusion rule is fixed before data is pulled.
ISO 22400-2:2014 presents each key performance indicator by its formula and corresponding elements, its time behaviour, its unit or dimension and other characteristics (ISO 22400-2:2014).
The KCS v6 metrics matrix lists article creation as an activity measure and states "DO NOT PUT GOALS ON ACTIVITIES!" (Consortium for Service Innovation, KCS v6, 2016).
KCS v6 expects first technical contact resolution to decline as self-service becomes more effective, which it calls a good thing (Consortium for Service Innovation, KCS v6, 2016).
With 8 of 10 inquiries resolved, a 95% Wilson interval runs from about 49% to 94%; with 80 of 100 it runs from about 71% to 87% (illustrative counts; Wilson, 1927, method as given in the NIST/SEMATECH e-Handbook).
Who uses a distributor technical capability scorecard, and what does it decide?
A distributor technical capability scorecard is used by a manufacturer's channel manager, technical service manager or regional sales director to decide which distributors can handle technical inquiries on their own, which need training, and where the manufacturer's own support is getting stuck. It is not a sales scorecard. Volume, margin and stock turns belong elsewhere; this template looks only at technical work: inquiries from end customers about product choice, application, failures and test results.
The decisions it supports are concrete. A distributor with a high self-resolution rate and complete escalations can be given a wider product scope or fewer review calls. A distributor whose escalations arrive without process conditions or analysis needs training on what to collect before calling the manufacturer. A bottleneck that sits inside the manufacturer, such as slow sample analysis, becomes an improvement item for the manufacturer's own team.
Generic distribution assessments answer a different question. The SCM Dojo distribution operations assessment, for example, covers basic management capabilities, logistics capabilities and materials management in 58 diagnostic questions (SCM Dojo), with no technical support metrics. ISO/IEC 20000-1:2018 names a customer that requires a consistent approach by all its service providers, including those in a supply chain, as one of its users (ISO/IEC 20000-1:2018), and that is the role a manufacturer takes when it scores every distributor on the same definitions.
What goes in each column of the distributor technical capability scorecard?
The distributor technical capability scorecard has five data sheets, plus an Instructions sheet and an illustrative Example sheet. Four data sheets follow its four sections (metric definitions, the scorecard of results, recurring failures and bottlenecks, and improvement items), and an escalation review sheet feeds the escalation quality results. The table below previews every column a user fills in, so a manager can check before the first period that each metric has a fixed denominator, exclusion rule and unit. All example values are illustrative and come from no real distributor. Section numbers in the first column match the sheets: 1 is metric definitions, 2 the scorecard, 3 the escalation review, 4 bottlenecks and 5 improvement items.
Scorecard column | What goes in it | Unit | Example (illustrative) |
|---|---|---|---|
1. Metric ID, version and name | Short code, the version of its definition and a plain name | Text | SR-1 v2, self-resolution rate (illustrative) |
1. Definition | What the metric measures, in one sentence | Text | Share of eligible technical inquiries closed by the distributor without manufacturer help (illustrative) |
1. Numerator | What is counted on top | Count | Eligible inquiries closed with no escalation and not reopened within 30 calendar days (illustrative) |
1. Denominator | What is counted underneath | Count | Eligible technical inquiries closed in the period (illustrative) |
1. Exclusion rules | Each rule with an ID, applied before counting | Text | X1 commercial questions; X2 document resend only; X3 manufacturer-only by policy (illustrative) |
1. Unit and day basis | Unit of the result; calendar or business days | %, days | %, calendar days (illustrative) |
1. Target and direction | Target value and whether higher or lower is better | Metric unit | 70% or higher (illustrative) |
1. Data source and computable | Where the counts come from; yes, or no with the reason | Text | Inquiry log; yes (illustrative) |
1. Fixed on | Date this definition version was fixed, before the period's data pull | YYYY-MM-DD | 2026-06-30 (illustrative) |
2. Period | Month or quarter the row covers, by close date | YYYY-MM or YYYY-Qn | 2026-Q3 (illustrative) |
2. Distributor code | Code, not the company name, when the sheet is shared | Text | D-04 (illustrative) |
2. Metric ID and version | The definition version the row was scored on | Text | SR-1 v2 (illustrative) |
2. Numerator and denominator | The two counts behind the value | Count | 41 and 60 (illustrative) |
2. Excluded cases | Cases removed by exclusion rules | Count | 9 (illustrative) |
2. Value, unit, target, prior period | Result with its unit, against target and last period | Metric unit | 68%, 70%, 63% (illustrative) |
2. Case mix note and sample flag | Difficulty and product mix; flag when the denominator is under the minimum | Text | Mostly new-application work; n below minimum: no (illustrative) |
2. Comment | Anything a reader of the row needs, such as why it is not ranked | Text | Not ranked (illustrative) |
3. Escalation ID, distributor code, received date | One row per escalation received in the period | Text, YYYY-MM-DD | E-0311; D-04; 2026-08-12 (illustrative) |
3. Escalation content items | Request and urgency, product, process, phenomenon, analysis, actions, evidence | Yes or no each; count of 7 | 6 of 7 present (illustrative) |
3. Escalation grade and scope | Complete, partial or returned; within the distributor's agreed scope | Text | Partial; within scope (illustrative) |
3. Grader, second grader, note | Who graded; the second grade for sampled escalations; what was missing | Text | Grader A; Grader B: partial; coolant concentration not given (illustrative) |
4. Bottleneck, evidence, cause | Where cases stall, the records that show it, the main cause | Text | Sample analysis queue; 14 cases; one test instrument (illustrative) |
4. Where it sits and shared mechanism | Distributor code or manufacturer stage; the mechanism the grouped failures share | Text | Manufacturer laboratory; single test capacity (illustrative) |
4. Cases affected and total loss | Count and loss in one unit for all bottlenecks | Count; days | 14 cases; 96 customer-waiting days (illustrative) |
4. Position | Fix now, watch, or no action needed | Text | Fix now (illustrative) |
5. Item ID and bottleneck targeted | Code of the item and the bottleneck it addresses | Text | I-01; escalations missing process conditions (illustrative) |
5. Improvement item | Action, owner by role, deadline, resources | Text, date, hours | Escalation checklist training; channel manager; 2026-12-15; 6 hours (illustrative) |
5. Expected effect | The loss reduction the item should bring, with its unit | Text, unit | Fewer partial escalations (illustrative) |
5. Success metric and acceptance | The metric that confirms the effect; owner accepted yes or no | Text | Escalation quality SQ-1 above 80% in 2027-Q1; yes (illustrative) |
5. Result at next review | What the success metric showed at the next review | Text | Entered at the 2027-Q1 review (illustrative) |
The key rows are the denominator and the exclusion rules in section 1: if they change between periods or between distributors, no value in section 2 can be compared, so the template keeps them on their own sheet with a version number. The second key row is the case mix note: a value that reaches a distributor review without its counts and its case mix invites a ranking the data cannot support.
Which metrics belong on a distributor technical capability scorecard?
A distributor technical capability scorecard works best with three to six outcome metrics that each answer a decision: self-resolution rate, escalation quality, escalation scope, reopen rate, and time to first technical answer. Fewer leave a capability unexamined; more go unread.
Self-resolution rate shows whether the distributor closes eligible technical inquiries without the manufacturer. Escalation quality shows whether the cases it does pass on arrive ready to work. Escalation scope shows how many escalations fall inside the scope the distributor agreed to handle, which separates a training need from a reasonable hand-off. Reopen rate, counted when a closed inquiry comes back on the same problem within a fixed window, guards self-resolution against early closure. Time to first technical answer, in calendar or business days stated in the definition, shows responsiveness.
Activity counts do not belong on the scorecard as targets. The Consortium for Service Innovation writes in its KCS v6 guidance that "Goals on activities seldom, if ever, generate the desired outcome." (Consortium for Service Innovation, KCS v6, 2016), and its metrics matrix lists article creation as an activity rather than an outcome. Inquiry counts, visits and documents sent can appear as context, not as targets.
ISO 22400-2:2014, which ISO lists as under revision, offers a structure for each definition: it presents each indicator by formula, elements, time behaviour and unit (ISO 22400-2:2014). It was written for manufacturing operations management, so the template borrows its layout, not its indicators.
How do you fix the denominator and exclusion rules for a distributor self-resolution rate?
The denominator and exclusion rules for a distributor self-resolution rate are fixed by writing them on the metric definition sheet, with a version number, before any inquiry is pulled for the period, and by applying the same version to every distributor. The self-resolution rate is then the share of eligible technical inquiries a distributor closed without manufacturer help in the period.
Start with what enters the denominator. Count technical inquiries by close date in the period, so an inquiry open at period end waits for the period in which it closes. Merge duplicates of one problem into one inquiry.
Then write each exclusion as a numbered rule. Typical rules remove commercial questions about price, stock or delivery; requests to resend a document such as a safety data sheet or certificate of analysis with no technical question; and inquiries the manufacturer's policy reserves for itself, such as warranty claims or OEM approval letters, because the distributor cannot close those by design. Record the excluded count next to every value, so growth in exclusions shows.
Next, define what counts as resolved without help. An inquiry the distributor closed after a short call to the manufacturer counts as escalated if the answer came from the manufacturer. An inquiry reopened on the same problem within the reopen window counts as not resolved.
A change to any rule creates a new version that starts in the next period. Recompute earlier periods or show the break in the trend; never mix versions in one comparison.
How do you grade escalation quality on a distributor technical scorecard?
Escalation quality on a distributor technical scorecard is graded on what each escalation carried when it reached the manufacturer, not on how many escalations there were. A low escalation count can mean strong local capability or cases held back too long; the content of each escalation shows which.
The table below decides the grade by checking seven content items in every escalation received in the period.
Content item | Present when the escalation states | Grade effect (illustrative rule) |
|---|---|---|
Request and urgency | The question for the manufacturer and the date it matters by | Missing item lowers the grade |
Product | Product name, grade, lot or batch, pack and age | Missing item lowers the grade |
Process | Equipment and operating conditions with units, such as temperature in °C or concentration in % | Missing item lowers the grade |
Phenomenon | What was seen, where, when, how often and how it was measured | Missing item lowers the grade |
Analysis done | Tests run, method and results with units | Missing item lowers the grade |
Actions taken | What the distributor or customer tried and what happened | Missing item lowers the grade |
Evidence | Data files, photos or a sample reference | Missing item lowers the grade |
As an illustrative rule, grade an escalation complete when all seven items are present, partial when any item is missing but the manufacturer could start after asking, and returned when the manufacturer could not start work. Escalation quality is then the share of escalations graded complete in the period. Record separately whether the case lay inside the distributor's agreed scope: a complete escalation inside scope points to a training topic, while one outside scope is a proper hand-off.
Have two people grade a sample of escalations each period and compare. Where they disagree, tighten the wording of the item, not the score.
How do you fill in the distributor scorecard each period?
The distributor scorecard is filled in each period in seven steps, from the metric definitions to the improvement items, each relying on the one before.
Confirm the metric definition sheet. Check each metric's version, denominator, exclusions, unit, day basis and target. Mark any metric the records cannot compute, with the reason.
Pull the closed technical inquiries for the period by close date, for every distributor in scope. Classify each one as eligible or excluded, and note the exclusion rule ID.
Count the numerator, denominator and excluded cases for each distributor and metric, and compute the value only from these counts.
Grade each escalation on the escalation review sheet against the seven content items and record whether it fell inside the agreed scope.
Compare each value with its target and with the prior period. Flag any row whose denominator falls under the minimum your team set, and do not rank flagged rows.
Group repeated failures by the mechanism they share, not by matching labels, and enter each bottleneck with its evidence, main cause, cases affected and total loss in one unit.
Write an improvement item for every bottleneck marked fix now, with an owner by role, a deadline, the resources needed and the metric that will confirm its effect. Review the items from the previous period against their success metrics.
The editable Excel version of this distributor scorecard, with a CSV of the scorecard columns for import into other tools, is at the end of the page.
Illustrative distributor scorecard entries
Illustrative distributor scorecard entries for two distributors in one quarter show how the counts, the case mix note and the sample flag change what a result means. Every code, count and percentage in this example is illustrative and comes from no real distributor. Both distributors were scored on the same definition versions in the same quarter, which is what makes the rows comparable at all.
The table below shows illustrative results under self-resolution rate SR-1 v2 and escalation quality SQ-1 v1.
Distributor | Metric | Result (illustrative) | Note (illustrative) |
|---|---|---|---|
D-04 | Self-resolution rate SR-1 v2 | 41 of 60 eligible, 68%, target 70% | 9 excluded under X1 and X2; many new-application cases |
D-04 | Escalation quality SQ-1 v1 | 15 of 19 complete, 79% | 3 partial, missing process conditions; 1 returned |
D-07 | Self-resolution rate SR-1 v2 | 8 of 10 eligible, 80%, target 70% | Below minimum denominator of 20: not ranked |
D-07 | Escalation quality SQ-1 v1 | 0 of 2 complete | Both returned: no lot, no analysis |
The key row is D-07's self-resolution rate: 80% looks better than D-04's 68%, but it rests on 10 inquiries, so the row is flagged and not ranked (illustrative). D-04's partial escalations all lack process conditions, which makes "what to collect before escalating" the first training topic, while D-07's two returned escalations are a second signal that its capability is not yet visible in the numbers. The next review compares each distributor with its own 2026-Q3 values first (illustrative).
Where does a distributor technical capability scorecard mislead?
A distributor technical capability scorecard misleads when rates from small samples are ranked, when distributors with different case mixes are compared as equals, and when a falling number is read as decline although the cause is a better channel.
Small samples come first. With 8 of 10 inquiries resolved, a 95% Wilson interval for the rate runs from about 49% to 94%; with 80 of 100 resolved, from about 71% to 87% (illustrative counts; Wilson, 1927, method as given in the NIST/SEMATECH e-Handbook). The first distributor could be anywhere from weak to excellent, so set a minimum denominator and show the counts with every value.
Case mix is the second trap. A distributor serving new applications or strict OEM approvals gets harder inquiries than one selling repeat products to stable users. A comparison between distributors should state differences in case difficulty, case mix and sample size in the note beside each value, and compare a distributor first with its own prior periods.
Third, better self-service can lower the numbers. The KCS v6 metrics matrix states that as self-service becomes more effective, first contact resolution will decline and cost per incident will go up, and it calls this a good thing because total support cost should fall (Consortium for Service Innovation, KCS v6, 2016). The same happens when customers find easy answers in published guides.
Finally, the scorecard measures technical handling, not customer satisfaction. ISO 10004:2018 gives guidelines for monitoring and measuring customer satisfaction (ISO 10004:2018); run that measurement alongside rather than inferring it from these rates.
Distributor scorecard checklist
The distributor scorecard checklist below covers what has to be true before the scorecard is shared with distributors or used to change a distributor's scope.
[ ] Every metric on the definition sheet has a version, numerator, denominator, numbered exclusion rules, unit, calendar or business day basis, target and data source.
[ ] Metrics the records cannot compute are listed with the reason, not left out.
[ ] The definitions were fixed before the period's data was pulled, and every distributor was scored on the same version.
[ ] Each value shows its numerator, denominator and excluded cases.
[ ] Rows under the minimum denominator are flagged and not ranked.
[ ] Each comparison between distributors states case difficulty, case mix and sample size.
[ ] Escalations were graded on the seven content items, and a sample was graded twice.
[ ] Repeated failures are grouped by shared mechanism, and every bottleneck shows its loss in one unit.
[ ] Every fix-now bottleneck has an improvement item with owner, deadline, resources and success metric.
[ ] Items from the previous period were checked against their success metrics.
[ ] Activity counts appear only as context, with no targets.
[ ] A shared copy uses distributor codes and leaves out other distributors' results.
Lubinpla's technical support performance analysis diagnoses each distributor's capability by self-resolution rate and escalation quality, with denominators and exclusion rules fixed before any query.