# Paid L2/L3 Support Pilot Scorecard

> Use the TechSupport Team pilot scorecard to judge one paid support pilot on evidence from a live queue. Start with one application, a defined class of incidents and a buyer-side release owner. Record the baseline and the evidence required before the engineer starts.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/resources/l2-l3-support-pilot-scorecard/
- Updated: 2026-11-20

[Download CSV](https://techsupport-team.com/downloads/l2-l3-support-pilot-scorecard-v1.csv)

Suggested citation · TechSupport Team, “Paid L2/L3 Support Pilot Scorecard.” Version 1.0. [Reuse under CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).

## Score the trial

Table: Score the trial

| Measure | Weight | Acceptance evidence |
| --- | --- | --- |
| Investigation quality | 30% | Each sampled case records impact, evidence, reproduction status and next action. |
| Engineering handoff | 25% | A proposed fix or next-owner handoff is accepted, with test and rollback details where relevant. |
| Coverage and communication | 20% | Agreed response and update targets are tracked against in-scope incidents. |
| Product-team load | 15% | Compare incident-class volume and first useful evidence times with the baseline. |
| Runbook and continuity | 10% | The client can run a repeat drill and knows who owns each next action. |

Give each line a score of 0 for missing evidence, 1 for partial evidence or 2 for agreed evidence delivered. Multiply each weight by the score divided by 2. A review threshold of 75/100 is an example. Agree your threshold and evidence set in advance.

Worked score. A pilot scores 2, 2, 1, 1 and 2 in the order above. Its weighted score is 30 + 25 + 10 + 7.5 + 10 = 82.5. The coverage and load evidence need follow-up before expanding. Access and production approval rules are required regardless of the numeric score.

## Run a 30 day review

Use the first week to confirm access and run a drill. Track evidence on real in-scope incidents during the pilot. At the end, compare the agreed baseline, case sample and release handoffs. If live incident volume was too low for the test, add a repeat drill and decide whether to extend the trial. Record the outcome as expand, extend or stop and name the owner of the next step.

Use the [sample escalation dataset](https://techsupport-team.com/resources/saas-integration-escalation-sample-dataset/) to rehearse median evidence time, reopen rate and engineering load before you introduce the pilot.

## Get help with your support queue

### Discuss your workflow

Bring one recent escalation and the result your team needs.

- [Scope one production support queue](https://techsupport-team.com/services/saas-support/)
- [See a one-engineer SaaS pilot](https://techsupport-team.com/case-studies/pilot-to-expansion/)

## Source and reuse

Credit TechSupport Team and link to this page when sharing or adapting version 1.0 under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
