research

Measuring how many laptops run past their support end date

A method for counting staff laptops whose operating system or model no longer receives vendor security updates and for separating documented exceptions.

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 laptopStudy protocol
Verification sample10 percentStudy protocol
Review cadenceQuarterlyStudy protocol

Key takeaways

A laptop can remain in daily use long after the vendor stops shipping security updates. The asset register may show the purchase date, but the support end date depends on the model, the operating system, and the configuration. This study counts the laptops that are past their supported life and checks whether each one has a replacement plan. The result is a fleet risk measure, not a purchase order.

Question and scope

The study asks how many staff laptops are running an operating system or hardware model that no longer receives security updates from the vendor. The unit is one laptop. The population is every portable device assigned to an employee on the audit date. Record the date and the source used for each support end date. Record the result in the study file with the date and the reviewer.

Include devices bought through a stipend and devices managed by a contractor when the company owns the data. Exclude servers, shared lab machines, and devices that are waiting for disposal. Note how many devices could not be reached or identified. A count that silently drops the unreachable machines will understate the risk. Keep the evidence beside the case reference so another reviewer can check it.

Define support end

Define support end as the last date the vendor provides security updates for the operating system or the model. Use the vendor lifecycle page as the authority and record the date it was checked. Do not use the warranty end date as a substitute, because warranty and support are different commitments. Write the definition before collecting so two reviewers classify the same device the same way.

Separate the operating system lifecycle from the hardware support lifecycle. A supported system on an unsupported model may still be a risk if drivers and firmware no longer receive fixes. Note the devices that are in an extended support period and the date that period ends. A device that becomes unsupported during the planning year belongs in a separate watch list.

Build the device frame

Export the device list from the management console and match it to the asset register. Include the assigned user, the department, the model, the operating system, and the last check-in date. Remove the devices that have not checked in for thirty days and investigate them separately. A stale record can make the fleet look healthier than it is. Apply the same rule to every item in the sample before summarising the result.

Add the devices that appear in the asset register but not in the console. Ask the user or the team lead whether the device is still in service. Record the answer and the date. List the devices that cannot be reached and the reason, so the frame shows both what was measured and what could not be measured. Note any exception and the name of the person who approved it.

Collect the lifecycle data

For each device, capture the model, the operating system build, and the last update date. Match the model to the vendor lifecycle page and record the support end date. Store the raw export before any summary. Keep the query and the collection date with the export so another reviewer can repeat it. Store the raw export with the query that produced it.

Check the data for duplicate records caused by renamed devices or reimaged machines; normalise the model names so a suffix does not create a second category. Record the devices that returned an error and rerun the query once. A missing result is a finding, not a zero. Compare the result with the previous period before drawing a conclusion. Record the result in the study file with the date and the reviewer.

Verify the dates

Select at least ten percent of the devices and check the lifecycle date directly on the vendor page. Compare the live page with the date in the export. Record any difference and the likely cause, such as a model variant or a regional release. A date copied from a blog post is not a verified lifecycle date. Write the decision into the method note for the next reviewer.

Ask the asset owner to confirm the purchase date and the model for the sample. A device that was bought refurbished may have a shorter support window than the original sale suggests. Record the invoice or the vendor confirmation beside the sample. The verification should test both the date and the identity of the device. Check the record against the source system before closing the item.

Separate the exceptions

List the devices that are past support but still have a documented business reason to remain in use. Examples include a lab instrument that requires an old operating system or a machine that controls a specific piece of equipment. Ask the technical owner to confirm the reason in writing. Record the compensating control and the review date. Keep the sample sheet with the report so the count can be reproduced.

Check whether the exception is truly isolated or whether it hides a larger group. A single legacy application can keep a whole department on an old build. Note the number of users who depend on the exception and the cost of removing it. An exception without an end date is a permanent risk with a temporary label. Name the owner of the next action in the review note.

Measure exposure

Count the laptops past support and report the share of the measured fleet; split the count by operating system, model, and department. Report the devices that are past support and also missing endpoint protection or encryption. These combinations carry more risk than age alone. Record the date of the check beside the evidence file. Keep the evidence beside the case reference so another reviewer can check it.

Add the number of devices that will leave support within the next twelve months. A fleet with a large watch list needs a plan before the dates arrive. Report the count of devices with no replacement plan as a separate line. The report should show where the risk concentrates, not only the total. Use the same definition for every item in the population.

Report and remediate

Write a short report with the method, the measured population, the share past support, and the documented exceptions; group the findings by department and by model. Avoid naming individual users in the summary and use asset identifiers instead. Attach the raw export and the verification sheet. Note the systems that could not be measured in the report. Apply the same rule to every item in the sample before summarising the result.

Assign an owner and a due date to each finding. Start with devices that are past support and have no documented reason, then the ones with a near-term end date. Record the replacement or upgrade route and the test that confirms the fix. A finding is closed only when the device shows a supported configuration. Ask the technical owner to confirm the finding before publication.

Interview device owners

Ask five users whether they have been told that their device is out of support. Record the answer without judging the person, because the answer shows whether the message reached the floor. Ask the team lead whether a replacement request is already open. Compare the answers with the asset record. Keep the previous result beside the new one for comparison.

Include the person who supports the devices and the person who approves purchases. Ask whether the refresh plan includes the model and the date. A plan that exists only in the budget spreadsheet may not reach the user. Record the name of the person who owns the next action. File the export with the method note at the end of the study.

Repeat after fleet changes

Rerun the study after a large purchase, a merger, or an operating system upgrade. A new batch of devices can change the share even when the process has not changed. Compare the new result with the previous one and investigate any increase. Note the event that triggered the rerun beside the new export. Record the result in the study file with the date and the reviewer.

Keep the lifecycle page references and the query with the fleet documentation. Set a quarterly review and a monthly check of new devices. Record the date and the person who ran it. A stable share with documented exceptions is a better result than a one-time clean number. Keep the evidence beside the case reference so another reviewer can check it.

Limits of the study

The study sees the devices that the management console can reach. It cannot see a machine that is powered off, offline, or outside the console. It also cannot prove that a supported device is patched to the current level. State these limits so the report is read as a lifecycle review, not a security guarantee. Apply the same rule to every item in the sample before summarising the result.

The lifecycle dates may change after the collection, especially for extended support; repeat the study before a budget decision that depends on the dates. The method measures support status, not the business criticality of each device. Use the interviews and the exception list to interpret the number. Note any exception and the name of the person who approved it. Store the raw export with the query that produced it.

Keep evidence usable

Store the export, the query, the sample sheet, and the report in one folder with the audit date. Name the files by date and scope rather than by the person who ran the study. Give read access to the technical owner and the next reviewer. A folder that only one person can open will not survive a staff change. Store the raw export with the query that produced it.

Write a one-page method note that explains how to repeat the query and where to find the lifecycle references. Add the limitations and the systems that were out of scope. Include the date of the last run and the next planned date. The note should let a new reviewer reproduce the result without asking the original author. Compare the result with the previous period before drawing a conclusion.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the laptop support, password manager, vendor response, ticket triage, and access removal measures discussed here. The NIST SP 800-63B digital identity guidance supports the credential checks, NIST SP 800-53 Rev. 5 supports the access and audit records, 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 laptop support end date measure and the access removal completeness 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 measuring how many laptops run past their support end date 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 measuring how many laptops run past their support end date, 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 laptopStudy protocol
Verification sample10 percentStudy protocol
Review cadenceQuarterlyStudy protocol

Sources

  1. NIST Cybersecurity Framework 2.0Identify and protect outcomes used to frame the fleet lifecycle review.
  2. CISA Cross-Sector Cybersecurity Performance GoalsAsset inventory and vulnerability management baseline for small organisations.
  3. NIST SP 800-53 Rev. 5, Security and Privacy ControlsConfiguration and maintenance control language for unsupported systems.
  4. Microsoft Windows lifecycle FAQVendor lifecycle reference used to define support end.

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