A business laptop fleet is ready for Windows 11 when each device has a verified eligibility result, an approved application and peripheral test, and a named deployment owner. Meeting Windows 11 hardware requirements is the first gate. It does not prove the laptop suits its employee's workload or that the business can deploy it without unresolved exceptions.
Build the decision from individual assets rather than a statement that “all our laptops are recent”. Devices with similar names can differ in processor, firmware, memory and condition. A dated inventory gives IT and procurement a record they can act on.
Build one readiness record per laptop
Start with asset ID, manufacturer, exact model, exact processor, installed memory, storage capacity and available space. Add the current Windows edition and version, firmware details and management status. Assign the device to a user or role group so the technical result can be compared with actual work.
Record the evidence source and check date. A supplier description, old purchase invoice and current device assessment answer different questions. Where the device has not been checked, use “not assessed” rather than guessing from another laptop of the same series.
Include remote and spare devices. The inventory should show which assets are unavailable for assessment and who will arrange access. This prevents the fleet total from appearing complete while travelling users or emergency replacements remain unreviewed.
Check eligibility against current Microsoft requirements
Microsoft's Windows 11 requirements include a compatible 64-bit processor or system on a chip, at least 1 GHz and two cores, 4 GB RAM, 64 GB storage, UEFI firmware with Secure Boot capability, and TPM 2.0. Graphics and display requirements also apply. Additional features can have further requirements.
Record the processor's complete model and the eligibility assessment result. A clock speed or “Core i5” label alone does not prove processor support. Record TPM version, UEFI mode, Secure Boot capability and its current state as separate fields, so IT can distinguish an unsupported condition from a configuration requiring review.
Microsoft's organizational planning guidance identifies PC Health Check for Windows 10 Home, Pro and Pro for Workstations eligibility checks. Enterprise and Education users should follow their IT administrators' assessment process. Keep the resulting report or managed-device evidence with the asset record.
Send failed or unclear checks to the IT owner and, where needed, the device manufacturer. Firmware changes require the company's approved procedure and recovery preparation. Do not turn an unexplained failure into an instruction to bypass hardware checks.
Validate business suitability after the eligibility check
Use a representative device and approved business tasks to test the target Windows edition and version. Record application versions, add-ins, security tools, VPN, printing, scanners, docks and external displays. Name an application owner who can accept the result.
Test complete work, not just application launch. A finance user may need an add-in, file export and printer workflow; a remote employee may need the approved access method and meeting peripherals. Choose the tasks from the actual role rather than copying those examples as a mandatory test set.
Also assess memory, working storage, battery condition and the physical setup against the role. The business laptop specification guide explains how to capture those workload requirements. Operating-system minimums remain separate from the configuration IT accepts for productive work.
Use a retain, replace or review worksheet
Keep hardware eligibility and operational approval in separate columns. A device can pass the first and remain blocked by an application dependency. Give every exception an owner, next action and review date.
| Record area | Evidence to capture | Decision to record |
|---|---|---|
| Device identity | Asset ID, exact model, CPU, current edition and version | Assessment matched to the actual asset |
| Hardware eligibility | Dated tool or managed assessment; TPM and firmware findings | Eligible, ineligible or needs technical review |
| Role suitability | Application tasks, available storage, memory and device condition | Retain, replace or further workload test |
| Application and peripheral checks | Target build, versions, test result and application-owner sign-off | Approved or named exception |
| Deployment and support | IT owner, licence review, backup plan and support end date | Approved wave or time-limited exception plan |
A “retain” decision should name the accepted configuration and target build. A “replace” decision should explain which requirement failed. “Needs review” should remain visible until the responsible person resolves it; it is not an approval to deploy.
Illustrative example: eligibility and readiness differ
Illustrative planning example, not an audit result or configuration recommendation: A company assesses 24 laptops. Eighteen pass its hardware eligibility assessment, four require investigation of firmware or TPM findings, and two are confirmed ineligible through its assessment process.
Of the eighteen eligible devices, fifteen pass the agreed application tests. Three remain on hold because a business add-in has not been validated on the target build. The approved deployment group is therefore fifteen devices, not eighteen. The four unreviewed devices are not automatically replacement candidates, and the two ineligible devices need an approved next step.
Procurement can now request hardware against the confirmed replacement requirement while IT resolves the other exceptions. The numbers describe an assumed decision record; they do not predict how many devices in another fleet will qualify.
Record Windows 10 exceptions by edition and support route
Windows 10 reached its general end-of-support date on 14 October 2025. That date has already passed. Microsoft's commercial ESU guidance describes enrollment for continued critical and important security updates, with a maximum three-year period for eligible commercial and education devices. ESU does not restore general support or add new features.
Do not apply one retirement date to every Windows 10 asset. Microsoft's Windows 10 release information lists separate servicing timelines, including Long-Term Servicing Channel releases. Record the exact edition, version, applicable lifecycle and any confirmed ESU entitlement with its coverage dates.
Have the licence and security owners approve each remaining exception and its review date. A device still starting successfully does not establish its support status, and an assumed ESU entitlement is not an evidence record.
Approve the deployment plan and supplier scope
Before rollout, IT should approve the target edition and build, application results, user-data protection, recovery approach, change window and user support. Run a controlled pilot with representative roles and record issues before expanding the approved group.
If replacement laptops are needed, give suppliers the accepted role requirements, quantities, locations, dates and duration. Monthly rentals have a minimum term of one month. Record who owns licences, device management, application installation and migration. Agree any supplier tasks explicitly; a hardware enquiry does not establish a deployment service.
Frequently asked questions
Does TPM 2.0 alone make a laptop Windows 11 compatible?
No. TPM 2.0 is one requirement. The complete device must meet the processor, firmware, memory, storage, graphics and display conditions that apply. Keep a dated eligibility assessment for the exact asset, then test its applications and peripherals separately.
Does Secure Boot need to be recorded separately from TPM?
Yes. TPM version and UEFI Secure Boot capability are different checks. Record Secure Boot's current state too, so IT can investigate configuration and policy questions. Use the organization's approved assessment and manufacturer guidance rather than changing firmware settings without review.
Should every ineligible laptop be replaced immediately?
First confirm why it is ineligible and whether the result needs manufacturer or IT review. Then select an approved replacement or time-limited support route based on the role and risk assessment. Keep unresolved devices outside the approved deployment group.
Can a laptop meet the minimums but still be unsuitable?
Yes. Hardware eligibility does not establish acceptable application performance, peripheral compatibility or device condition. Test the actual role's work on the intended build and record application-owner approval before treating the laptop as ready for business use.