{"id":89138,"date":"2026-09-12T21:12:36","date_gmt":"2026-09-12T14:12:36","guid":{"rendered":"https:\/\/itsystems.vn\/license-reclaim-process-when-an-employee-leaves\/"},"modified":"2026-09-12T21:12:36","modified_gmt":"2026-09-12T14:12:36","slug":"license-reclaim-process-when-an-employee-leaves","status":"publish","type":"post","link":"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/","title":{"rendered":"License Reclaim Process When an Employee Leaves"},"content":{"rendered":"<p><strong>Quick answer:<\/strong> License reclaim during employee offboarding is the process of identifying, disabling, transferring or removing software usage rights assigned to a person leaving the company. It applies not only to Microsoft 365, Adobe, AutoCAD, PDF tools or antivirus, but also to SaaS platforms such as CRM, accounting, project management, digital signing, VPN, cloud storage and internal tools. If the company only disables email but forgets software licenses, recurring cost may continue and access may remain open. License reclaim should therefore be part of offboarding together with accounts, devices, data and permissions.<\/p>\n<section class='its-cta'>\n<div style='background:#fff5f6;border:1px solid #ffd6dc;border-radius:8px;padding:22px;margin:28px 0'>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_87_1 counter-hierarchy ez-toc-counter ez-toc-light-blue ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">The content of the article<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#Need_to_standardize_license_reclaim_during_offboarding\" >Need to standardize license reclaim during offboarding?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#Why_do_businesses_lose_licenses_after_offboarding\" >Why do businesses lose licenses after offboarding?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#Step_1_receive_leaver_information_early\" >Step 1: receive leaver information early<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#Step_2_list_related_accounts_and_licenses\" >Step 2: list related accounts and licenses<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#License_reclaim_checklist_table\" >License reclaim checklist table<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#What_should_be_reclaimed_in_Microsoft_365\" >What should be reclaimed in Microsoft 365?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#How_to_handle_Adobe_AutoCAD_and_specialist_software\" >How to handle Adobe, AutoCAD and specialist software<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#Devices_local_data_and_installed_software\" >Devices, local data and installed software<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#Risk-based_priority_table\" >Risk-based priority table<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#Who_owns_the_license_reclaim_process\" >Who owns the license reclaim process?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#What_should_the_offboarding_report_include\" >What should the offboarding report include?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#How_ITS_Manager_supports_license_reclaim\" >How ITS Manager supports license reclaim<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#License_reclaim_FAQ\" >License reclaim FAQ<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#How_to_keep_the_workflow_from_being_forgotten\" >How to keep the workflow from being forgotten<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#Practical_monthly_control_for_license_reclaim\" >Practical monthly control for license reclaim<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/itsystems.vn\/en\/license-reclaim-process-when-an-employee-leaves\/#Need_to_standardize_license_reclaim_during_offboarding-2\" >Need to standardize license reclaim during offboarding?<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h3 style='margin-top:0'><span class=\"ez-toc-section\" id=\"Need_to_standardize_license_reclaim_during_offboarding\"><\/span>Need to standardize license reclaim during offboarding?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>IT Systems helps inventory users, devices and installed software, then implement <a href='https:\/\/itsystems.vn\/en\/it-asset-management-software\/software-license-management\/'>ITS Manager license management<\/a> to reduce unused seats, leftover access and future purchasing confusion.<\/p>\n<p><a href='https:\/\/itsystems.vn\/en\/contact-it-systems-vietnam\/' style='display:inline-block;background:#ef233c;color:#fff;text-decoration:none;padding:12px 18px;border-radius:6px;font-weight:700'>Contact IT Systems<\/a><\/p>\n<\/div>\n<\/section>\n<figure><img decoding=\"async\" src=\"https:\/\/itsystems.vn\/wp-content\/uploads\/2026\/09\/license-reclaim-flow-en-6.webp\" alt=\"License reclaim workflow during employee offboarding\" title=\"\"><figcaption>License reclaim workflow during employee offboarding<\/figcaption><\/figure>\n<h2><span class=\"ez-toc-section\" id=\"Why_do_businesses_lose_licenses_after_offboarding\"><\/span>Why do businesses lose licenses after offboarding?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>License leakage happens because HR, IT and procurement data often live in different places. HR knows who is leaving, finance knows software invoices, IT knows technical accounts and department managers know which tools the employee actually used. If those sources are not connected, licenses can remain assigned for months. With user-based products such as Microsoft 365, Adobe Creative Cloud and many SaaS tools, every unreclaimed user becomes recurring cost. With specialist software, the issue can also involve project files, customer data or intellectual property.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Step_1_receive_leaver_information_early\"><\/span>Step 1: receive leaver information early<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The process should start as soon as HR confirms resignation, termination or role transfer. IT needs the employee name, business email, department, last working day, handover owner, assigned devices, software used and data sensitivity. If information arrives too late, IT may only have time to block the main account and miss secondary licenses. Employees in finance, management, design, engineering or system administration should be marked as higher priority because they usually hold more access and higher-value software.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Step_2_list_related_accounts_and_licenses\"><\/span>Step 2: list related accounts and licenses<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>After receiving leaver data, IT should list all accounts and licenses linked to that person. This includes Microsoft 365, Google Workspace, Adobe, AutoCAD\/Autodesk, PDF tools, antivirus, backup, remote support, CRM, ERP, accounting, project management, data repositories, VPN, cloud, digital signing and internal systems. The list should not depend only on memory or user confirmation. <a href='https:\/\/itsystems.vn\/en\/it-asset-management-software\/software-license-management\/'>ITS Manager software license management<\/a> helps connect users, devices, licenses, evidence and reclaim status in one workflow.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"License_reclaim_checklist_table\"><\/span>License reclaim checklist table<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The table below is an operational checklist for SMEs. Each line should have a status, owner, deadline and evidence. The goal is not only to mark an account as disabled. The company should know that the license was reclaimed, data was handed over, the device was checked and local software was removed or transferred correctly. If the company already uses a <a href='https:\/\/itsystems.vn\/en\/software-license-inventory-checklist-for-businesses\/'>software license inventory checklist<\/a>, offboarding should become a dedicated branch of that recurring review.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<table>\n<thead>\n<tr>\n<th>Area<\/th>\n<th>Action<\/th>\n<th>Evidence<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>HR<\/td>\n<td>Confirm leaving date and handover owner<\/td>\n<td>Notice\/offboarding ticket<\/td>\n<\/tr>\n<tr>\n<td>Accounts<\/td>\n<td>Block login, revoke sessions, review MFA<\/td>\n<td>Log\/admin screenshot<\/td>\n<\/tr>\n<tr>\n<td>Licenses<\/td>\n<td>Reclaim or transfer seats<\/td>\n<td>Portal\/license record<\/td>\n<\/tr>\n<tr>\n<td>Devices<\/td>\n<td>Receive device, review software, clean data<\/td>\n<td>Device return record<\/td>\n<\/tr>\n<tr>\n<td>Report<\/td>\n<td>Summarize completion and open risks<\/td>\n<td>Offboarding report<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><span class=\"ez-toc-section\" id=\"What_should_be_reclaimed_in_Microsoft_365\"><\/span>What should be reclaimed in Microsoft 365?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>For Microsoft 365, the company needs to handle several layers: login, MFA, mailbox, OneDrive, Teams, SharePoint, groups, devices, admin roles and licenses. The account should not always be deleted immediately. A safer flow is to block sign-in, revoke sessions where appropriate, delegate or forward mailbox according to policy, hand over OneDrive or SharePoint data, and then reclaim the license. Reclaiming too early can disrupt file handover; leaving it too long wastes cost and leaves access exposure.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"How_to_handle_Adobe_AutoCAD_and_specialist_software\"><\/span>How to handle Adobe, AutoCAD and specialist software<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>For Adobe, AutoCAD and specialist software, check which portal assigned the license, whether the seat can be reassigned, whether project data is local or cloud-based and whether software should be removed from the returned device. Designers, CAD engineers and project staff often hold files that must be handed over before license reclaim. For <a href='https:\/\/itsystems.vn\/en\/licensed-software-for-businesses\/'>licensed software for businesses<\/a>, the goal is not only seat saving but project-asset protection. When installed software is unclear, <a href='https:\/\/itsystems.vn\/en\/it-asset-management-software\/automated-computer-inventory-agent\/'>automated computer inventory by Agent<\/a> helps review devices before reassignment.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Devices_local_data_and_installed_software\"><\/span>Devices, local data and installed software<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>License reclaim must be connected with device review. A returned laptop or PC should be checked for installed software, local data, login accounts, saved browser passwords, VPN, remote tools, synced cloud folders and device-based licenses. If the device is reassigned without cleanup, the company may leave old data or incorrect software on the machine. For remote employees, the process should include device return or at least access blocking, session revocation and cloud-data verification.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Risk-based_priority_table\"><\/span>Risk-based priority table<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Not every offboarding case has the same risk. An intern using basic email is different from a finance manager, designer with customer files, CAD engineer with drawings or administrator with system rights. A priority table helps IT handle business impact: which data is sensitive, which license is expensive, which account has high privileges and which system must be blocked immediately. This is more practical than applying one flat checklist to every employee.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<table>\n<thead>\n<tr>\n<th>Employee Group<\/th>\n<th>Main Risk<\/th>\n<th>Priority<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Finance<\/td>\n<td>Invoices, banking, accounting records<\/td>\n<td>Very high<\/td>\n<\/tr>\n<tr>\n<td>Design\/CAD<\/td>\n<td>Customer files, drawings, high-value licenses<\/td>\n<td>High<\/td>\n<\/tr>\n<tr>\n<td>Management<\/td>\n<td>Email, project files, approvals<\/td>\n<td>High<\/td>\n<\/tr>\n<tr>\n<td>Office staff<\/td>\n<td>Email, SaaS, devices<\/td>\n<td>Medium<\/td>\n<\/tr>\n<tr>\n<td>Intern\/temporary<\/td>\n<td>Short-term accounts<\/td>\n<td>Scope-based<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<figure><img decoding=\"async\" src=\"https:\/\/itsystems.vn\/wp-content\/uploads\/2026\/09\/license-reclaim-risk-en-5.webp\" alt=\"Risk priority matrix for license reclaim\" title=\"\"><figcaption>Risk priority matrix for license reclaim<\/figcaption><\/figure>\n<h2><span class=\"ez-toc-section\" id=\"Who_owns_the_license_reclaim_process\"><\/span>Who owns the license reclaim process?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A strong process needs clear ownership. HR announces the leaver event and effective date. The department manager confirms software, data and handover owner. IT disables accounts, reclaims licenses, checks devices and stores evidence. Finance or procurement checks subscriptions and ongoing costs. Leadership approves exceptions such as keeping a mailbox, transferring sensitive data or purchasing a replacement license. If everything is left to IT without business confirmation, both missed items and incorrect removal become more likely.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_should_the_offboarding_report_include\"><\/span>What should the offboarding report include?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>After completion, IT should prepare a short report: leaver name, disabled accounts, reclaimed licenses, transferred licenses, handed-over data, returned devices, remaining risks and recheck date. This helps leadership see that offboarding was completed with evidence, not only verbal confirmation. It also prepares data for the next <a href='https:\/\/itsystems.vn\/en\/software-license-quote-for-businesses-what-information-to-prepare\/'>software license quote<\/a>, because the company can see which licenses truly need purchase and which can be reused.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"How_ITS_Manager_supports_license_reclaim\"><\/span>How ITS Manager supports license reclaim<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a href='https:\/\/itsystems.vn\/en\/it-asset-management-software\/software-license-management\/'>ITS Manager<\/a> can manage licenses by user, device, department, renewal date, assignment status and reclaim status. When an employee leaves, the system can become a central checklist: what licenses the person has, which devices are related, what software is installed, where purchase evidence is stored and which actions remain open. This is stronger than <a href='https:\/\/itsystems.vn\/en\/software-license-management-vs-excel\/'>license management in Excel<\/a> when user count grows, because data is not scattered across files and email.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"License_reclaim_FAQ\"><\/span>License reclaim FAQ<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Should the account be deleted immediately? Not always; sign-in is usually blocked first and data is handed over before deletion. Can reclaiming a license delete data? It depends on the platform, so mailbox, OneDrive, cloud storage or project files should be checked first. Who confirms whether software is still needed? The department manager confirms business need and IT confirms technical status. How often should reclaimed licenses be reviewed? Review on the leaving date and again in the monthly license report to ensure no seat remains active unintentionally.<\/p>\n<p>This process should be documented as an evidence-based checklist because even one forgotten license can create recurring cost or unnecessary access. When the business repeats the workflow consistently, license data becomes cleaner and future purchases become more accurate. The important point is not only technical execution; it is coordination between HR, IT, finance and the department manager. Each team owns a different part of the truth, so the workflow must connect notice, business handover, technical access, procurement evidence and final reporting.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"How_to_keep_the_workflow_from_being_forgotten\"><\/span>How to keep the workflow from being forgotten<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The safest approach is to make license reclaim a required part of HR offboarding and monthly IT reporting. Every leaver should create an offboarding ticket where licenses are a separate checklist group, not a small note hidden under account closure. At month end, IT should compare the leaver list against still-active licenses to catch missed seats. With ITS Manager, the company can use connected user, device, software and license records to show which seats were reclaimed, which were transferred, which still need department confirmation and which should be reduced at renewal.<\/p>\n<p>This is especially useful for SMEs because the same person may handle several roles. Without a system, license reclaim depends on memory and personal follow-up. With a repeatable workflow, the company can maintain control even when HR, IT staff or department managers change. The result is cleaner renewal data, fewer wasted seats and stronger evidence when management asks why a software budget increased or decreased.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Practical_monthly_control_for_license_reclaim\"><\/span>Practical monthly control for license reclaim<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A practical monthly control is to compare three lists: employees who left or changed roles, active software licenses, and devices that still show paid software installed. Any mismatch should become an action item with an owner. For example, a Microsoft 365 license may be reclaimed, an Adobe seat may be transferred to a replacement designer, and a CAD workstation may need software cleanup before reassignment. This rhythm keeps the offboarding process alive after the first cleanup project and turns license reclaim into normal IT governance.<\/p>\n<p>It also gives finance a cleaner basis for renewal decisions, because unused seats and transferred licenses are visible before the next invoice arrives.<\/p>\n<p>That makes software spending easier to explain and easier to optimize.<\/p>\n<p>It also improves audit readiness.<\/p>\n<section class='its-cta'>\n<div style='background:#fff5f6;border:1px solid #ffd6dc;border-radius:8px;padding:22px;margin:28px 0'>\n<h3 style='margin-top:0'><span class=\"ez-toc-section\" id=\"Need_to_standardize_license_reclaim_during_offboarding-2\"><\/span>Need to standardize license reclaim during offboarding?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>IT Systems helps inventory users, devices and installed software, then implement <a href='https:\/\/itsystems.vn\/en\/it-asset-management-software\/software-license-management\/'>ITS Manager license management<\/a> to reduce unused seats, leftover access and future purchasing confusion.<\/p>\n<p><a href='https:\/\/itsystems.vn\/en\/contact-it-systems-vietnam\/' style='display:inline-block;background:#ef233c;color:#fff;text-decoration:none;padding:12px 18px;border-radius:6px;font-weight:700'>Contact IT Systems<\/a><\/p>\n<\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>License reclaim process for leavers: Microsoft 365, Adobe, AutoCAD, SaaS, devices, data, offboarding workflow and ITS Manager.<\/p>\n","protected":false},"author":34,"featured_media":89134,"comment_status":"","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_focus_keyword":"License Reclaim Process When an Employee Leaves","rank_math_title":"License Reclaim Process When an Employee Leaves","rank_math_description":"License reclaim process for leavers: Microsoft 365, Adobe, AutoCAD, SaaS, devices, data, offboarding workflow and ITS Manager.","rank_math_robots":"","rank_math_canonical_url":"","rank_math_schema":"","footnotes":""},"categories":[2039],"tags":[],"class_list":["post-89138","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dich-vu-it"],"wpml_current_locale":"en_US","wpml_translations":{"vi_VN":{"locale":"vi_VN","id":89137,"slug":"quy-trinh-thu-hoi-license-khi-nhan-vien-nghi-viec","post_title":"Quy tr\u00ecnh thu h\u1ed3i license khi nh\u00e2n vi\u00ean ngh\u1ec9 vi\u1ec7c","href":"https:\/\/itsystems.vn\/quy-trinh-thu-hoi-license-khi-nhan-vien-nghi-viec\/"}},"_links":{"self":[{"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/posts\/89138","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/users\/34"}],"replies":[{"embeddable":true,"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/comments?post=89138"}],"version-history":[{"count":0,"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/posts\/89138\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/media\/89134"}],"wp:attachment":[{"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/media?parent=89138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/categories?post=89138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itsystems.vn\/en\/wp-json\/wp\/v2\/tags?post=89138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}