research

Auditing the age of open vendor support cases

A method for listing open vendor cases, measuring age by severity and waiting party, and finding the cases that need an escalation before the next review.

Short answer

Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.

Research playbook

MeasureVolume and handling time
OwnerTechnical manager validates
Risk ruleName sensitive access
RefreshQuarterly benchmark review
On this pageJump to section

Key stats

UnitOne vendor caseStudy protocol
Age bands0-7, 8-30, 31+ daysStudy protocol
Review cadenceMonthlyStudy protocol

Key takeaways

A vendor support case can sit open for weeks without anyone noticing because the vendor portal is not the company's ticket queue. The case may be waiting on the vendor, on the company, or on a part that nobody ordered. The age alone does not show which. This audit measures the age of open vendor cases, separates the waiting party, and finds the cases that need an escalation.

Question and scope

The audit asks how old the open vendor support cases are, who is waiting on whom, and which cases have passed the response time in the contract. The unit is one vendor case. The population is every case open in the supported vendor portals on the audit date. The result describes the current backlog, not the vendor's overall performance. Record the audit date because the backlog changes as soon as a case closes.

Include cases raised by email or chat that never reached the portal, and note the channel. Exclude closed cases and renewals that are not support requests. Record the vendors in scope and the products they support. A case that is missing from the list will distort the age profile, so reconcile the portal with the company's ticket system. Note the cases that were opened by a customer rather than by the company.

Define an open case

Treat a case as open when the vendor has not confirmed a resolution or when the company has not accepted the fix. Record the status label used by each portal because vendors name their states differently. Note the date of the last update and the next promised date. A case that is marked pending customer for a month is still open and still aging.

Decide how to treat duplicate cases for the same fault. Keep the oldest case as the parent and link the duplicates to it. Count the parent once in the age analysis and note the duplicates separately. A duplicate that hides the original case makes the backlog look smaller than it is. Record the duplicate count in the report so the reader understands the case volume.

Build the case list

Export the case list from each vendor portal with the case number, subject, severity, created date, last update, and owner. Add the company contact and the affected system. Normalise the dates into one time zone before calculating age. Keep the raw exports with the audit file. Add the product and the vendor tier to each row so the analysis can be grouped.

Match each case to the company ticket that raised it. Mark the cases that have no internal ticket because those are the ones most likely to be forgotten. Ask the technical owner to confirm the list for each vendor. Record any case the owner knows about that the portal does not show. Give the list to the technical owner and ask them to confirm the missing cases.

Measure age and severity

Calculate the age in days from the created date to the audit date and the time since the last update. Report the median, the range, and the count older than thirty days. Split the results by severity and by vendor. A single average hides the small number of cases that consume most of the attention. Report the count older than the agreed escalation threshold as well as the median.

Add the waiting party for each case, such as vendor engineering, company confirmation, a third-party supplier, or a replacement part. Count the cases waiting on the company separately because those are the ones the team can move today. The waiting party is more useful than the status label when planning the next action. Record the date the case started waiting on the company so the delay is visible.

Match cases to contracts

For each vendor, find the contract and the service levels that apply to the product. Note the response and restoration targets for each severity. Compare the case age with the target and mark the cases that have breached it. Record the contract clause beside the case so the comparison can be checked. Note the severity definitions in the contract because vendors use different scales.

Check whether the vendor records the response time in the portal. If it does not, use the first human reply rather than the automated acknowledgement. Note the difference and apply it consistently. A breach that cannot be evidenced is difficult to escalate, so keep the timestamps. Keep the first human reply with the case note so the breach can be shown later.

Interview the owners

Ask the person who owns each vendor relationship how the case is progressing and what they are waiting for. Record the answer and the date. Ask whether the vendor has asked for information the company has not supplied. The interview often finds a case that is stalled because nobody answered a question. Ask the owner what they need from the company to move the case this week.

Ask what would make the case move faster and who can approve it. Note the escalation route and whether it has been used. Record the name of the vendor contact who last responded. A case with no named contact is a case without an owner on the vendor side. Record the date of the last vendor response and the channel used.

Report the tail

Report the count of open cases, the median age, and the oldest cases with their waiting party. Add the breaches by severity and the cases that are waiting on the company. Keep individual customer names out of the summary and use case references. Attach the raw export and the contract comparison. Add the number of cases with no contract reference as a separate gap.

Highlight the small number of cases that account for most of the total age. Those are the escalation candidates. Send the report to the vendor owners and the technical manager. Ask for a decision on each case older than the agreed threshold, not a general promise to follow up. Ask the technical manager to accept or reject the escalation list in writing.

Set an escalation rule

Write a rule that names the age and severity at which a case is escalated, the person who escalates it, and the evidence they send. Include the vendor contact and the contract clause. Set a shorter trigger for cases that affect a customer commitment or a security control. State the evidence required, such as the case number, the impact, and the missed date.

Add the rule to the vendor register and the support runbook. Give the vendor owner a monthly reminder to review the open cases before the report is due. Record each escalation and the response. A rule that is not tied to a date will be applied only when someone remembers. Review the escalation list at the monthly vendor meeting and close the items that moved.

Repeat each month

Run the audit monthly with the same fields and the same age bands. Compare the count and the median with the previous month. A stable count with older cases means the backlog is not moving. A falling count with a rising median means the easy cases are closing and the hard ones remain. Record the count of cases that closed during the month as well as the open backlog.

Review the result with the vendor owners and update the contract notes when a pattern appears. Keep the exports with the vendor register. Set the next audit date before the meeting ends. The monthly rhythm prevents a single forgotten case from becoming a quarterly surprise. Give the next audit date to the vendor owners before the meeting ends. Put the date in the vendor calendar rather than in a personal reminder.

Limits of the audit

The audit sees the cases that appear in the portals and the company ticket system. It cannot see a request that was made in a meeting or a chat that nobody logged. It also cannot prove that the vendor's status is accurate. State these limits so the report is read as a backlog review. Note the vendors that did not provide an export and treat them as a coverage gap.

The age measure describes the period and the vendors in scope. It does not compare vendors fairly when their products and severities differ. Use the waiting party and the contract target to interpret the number. Repeat the audit with the same definitions before drawing a trend. Record the scope and the date in the report so the next run can be compared.

Check the vendor's own reporting

Ask each vendor for its monthly case report and compare it with the portal export. Check the case count, the severity, and the response times. Note the cases that appear in one source and not the other. A report that counts only the cases the vendor wants to show will understate the backlog. Ask the vendor to explain any case that is missing from its report.

Record the report date and the period it covers, because vendors may close the month on a different day. Ask how the vendor calculates response time and whether it excludes waiting on the customer. Write the definition beside the number so the comparison is fair. The vendor's own measure is useful only when its rules are known. Keep the vendor definition beside the company definition in the audit file.

Plan the next quarter

Use the oldest open cases to set the agenda for the next quarterly vendor review. Name the cases that will be escalated, the evidence that will be sent, and the person who will send it. Ask the vendor for a written plan for the cases that cannot be resolved quickly. The agenda should be based on the data, not on the last conversation.

Review the contract terms that produced the most breaches and decide whether they still fit the business. A response target that the vendor cannot meet may need a different service level or a different supplier. Record the decision and the date. The next quarter should start with a smaller, better understood backlog. Record the contract change and the next review date in the vendor register.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the local administrator, password reset, vendor case, file restore, and browser credential measures discussed here. The NIST SP 800-63B digital identity guidance supports the verification and credential checks, NIST SP 800-34 contingency planning guidance supports the restore measure, and the GAO data reliability guidance supports the sampling approach. Apply your own policies, contracts, and system documentation when adapting the method.

Compare this study with the local administrator audit and the file restore timing study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.

Benchmark brief

What this research page must produce

Working number

A practical estimate for volume, review time, escalation rate, and assistant capacity.

Operating boundary

A clear split between routine support, preparation work, and technical ownership.

What the auditing the age of open vendor support cases data shows

Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.

The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.

Workflow

Recommended operating workflow

1

Collect a baseline

Pull the last 30 to 90 days of examples related to auditing the age of open vendor support cases, including completed work and unresolved exceptions.

2

Classify the work

Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.

3

Set the operating number

Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.

4

Refresh the benchmark

Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.

Decision rules

MetricUse it to decideManager action
Weekly volumeWhether the workflow is worth assigning as recurring assistant work.Approve a weekly capacity target and backlog threshold.
Access sensitivityWhether the assistant can work directly or only prepare review notes.Set least-privilege permissions and removal dates.
Escalation rateWhether the workflow is stable enough to delegate.Rewrite the SOP when exceptions exceed the agreed threshold.

Consolidated statistics

StatisticFigureSource
UnitOne vendor caseStudy protocol
Age bands0-7, 8-30, 31+ daysStudy protocol
Review cadenceMonthlyStudy protocol

Sources

  1. NIST SP 800-53 Rev. 5, Security and Privacy ControlsMonitoring and supplier management control language used to frame the review.
  2. NIST Cybersecurity Framework 2.0Supply chain and continuous monitoring outcomes for vendor oversight.
  3. SBA: Strengthen Your CybersecuritySmall business guidance on vendor and service provider risk.
  4. GAO Assessing Data ReliabilityApproach for documenting sources, sampling, and verification.

Measurement checklist

FieldWhat to captureOwner
VolumeWeekly request count, backlog age, and repeat issue patternsAssistant prepares, manager reviews
RiskAccess level, customer impact, security sensitivity, and approval needsTechnical owner
CadenceDaily, weekly, monthly, or quarterly review rhythmManager
EvidenceSample tickets, logs, screenshots, and before-after examplesAssistant collects, owner validates
EscalationTriggers, approval path, response time, and stop-work rulesTechnical owner

How to read the result

A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.

Source and refresh note

This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.

How should teams use this benchmark?

Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.

Get free benchmark review