Business context
Viet Nam's Decree No. 371/2026/ND-CP took effect on 15 November 2026. It governs the recruitment and management of Vietnamese workers employed by foreign organisations and individuals within its scope. Recruitment needs must be notified to the competent managing body and published on the National Employment Exchange, another lawful employment platform or the organisation's official website. The decree also establishes notification duties after an employment contract is signed or terminated, generally within ten working days.
For business leaders, this is more than an administrative posting requirement. A vacancy now sits inside a visible chain connecting workforce demand, public information, candidate selection, contractual commitment and management records. That chain can support transparency and labour-market access, but it also exposes weak role definitions, late approvals and inconsistent data between business units, human resources, external recruiters and authorised bodies.
Core management problem
The core problem is that many companies manage hiring as a collection of separate tasks. A manager requests headcount, finance confirms budget, HR publishes a role, an agency searches, a contract is signed and someone later updates a file. Each step may be completed, yet the organisation cannot prove that the position, public notice, selection criteria, contract and regulatory notification describe the same business need.
Three clocks make the gap larger. The operating clock wants people quickly. The candidate clock depends on market availability, notice periods and offer acceptance. The governance clock requires approved information and timely records. When the first clock overrides the others, companies can create rework, inconsistent job descriptions, premature offers, untracked contractors or late notifications. Hiring speed then produces operational and reputational friction instead of productive capacity.
Common mistakes
The first mistake is treating publication as the finish line. Posting a vacancy does not prove that the role is approved, accurately scoped or connected to a funded operating need. The second is copying a generic job description across platforms while the hiring manager, recruiter and contract use different titles, duties, location or reporting lines. The third is assuming every foreign-invested employer or every worker is covered in exactly the same way without confirming the decree's scope and competent managing body.
Another mistake is assigning the process entirely to HR. Workforce demand originates in commercial plans, production schedules, service commitments and control requirements. If those owners do not define the business outcome, workload, capability and start-date evidence, HR can only accelerate an unclear request. Companies also lose control when agency records, candidate consent, interview evidence, offer approval, signed contracts and notifications are stored in separate systems with no common identifier.
Practical framework: the workforce demand-to-record chain
Build one chain with five linked records. The demand record states the business purpose, approved headcount, budget, location, manager, capability, employment form and required date. The publication record preserves the approved vacancy text, channel, publication date and responsible party. The selection record links criteria, shortlist, interviews, decision evidence and candidate communication. The contract record confirms the final title, duties, workplace, start date and approval. The management record captures the required post-signing and post-termination notifications and their acknowledgements.
Use three release gates. A role-release gate confirms that business demand, budget, scope and publication text agree before the vacancy goes live. An offer-release gate confirms candidate evidence, compensation authority, conflicts, data handling and operating readiness before commitment. A record-close gate confirms that the signed terms match the approved role and that every required notification, system update and document has an owner and deadline.
Give every vacancy a stable case identifier from request to exit. It should connect the approved role, every published version, candidate decision, contract and subsequent notification without putting unnecessary personal data into management dashboards. The identifier makes exceptions visible: changed scope, direct recruitment, urgent hiring, agency substitution, delayed start, contract amendment or early termination. Management can then distinguish a legitimate exception from an invisible process break.
Management process
Run a weekly workforce-release review for open priority roles. The hiring manager owns demand and capability evidence; finance owns budget authority; HR owns publication and candidate process; the relevant compliance or legal owner confirms applicability and notification design; operations confirms workplace readiness. The meeting should decide release, hold, redesign or close. It should not become a status call listing every candidate.
Track a small set of operating measures: days from approved demand to compliant publication, percentage of vacancies with one approved description across channels, days from offer to complete record, notifications due within ten working days, reopened cases, agency exceptions and early attrition by role. Pair speed with quality. A shorter hiring cycle is valuable only if the role is executable, the evidence chain is complete and the new employee reaches productive work.
Connect workforce planning to business scenarios. Base demand should be supported by contracted workload or stable operating need. Option demand should have a trigger, such as a customer award, capacity threshold or regulatory approval. Observed demand should remain a talent-market signal, not released headcount. This prevents policy compliance from becoming a justification for premature hiring and allows recruitment readiness without forcing an irreversible cost commitment.
Patrick Lee Business Lens
Growth asks which customer promise, market-entry step or service level requires the role. Manufacturing asks whether the workplace, supervisor, process, equipment and training can turn the hire into reliable capacity. Risk asks whether scope, data, authority, timing and evidence remain consistent from vacancy to exit. Growth × Manufacturing × Risk should therefore be visible in the same workforce case, not divided into a commercial forecast, an HR requisition and a compliance file.
My business judgment is that Decree 371 should be used to improve decision quality, not merely add a posting step. Public recruitment information creates a forcing mechanism: leaders must explain what capability they need, why it is funded, who owns the outcome and how the final employment record connects to the original demand. Companies that build this chain can move faster because exceptions are explicit and evidence does not have to be reconstructed after the fact.
Management implication
The new framework can make recruitment more transparent, but transparency alone does not create talent or execution. Management should use the effective date to review open roles, covered entities, publication channels, competent bodies, contract-notification routines, agency instructions and record ownership. Where legal scope is uncertain, obtain qualified advice before changing the process rather than applying one interpretation to every entity.
The leadership test is practical: can the company trace an approved workforce need to the public vacancy, selection decision, signed contract, required notification and productive operating outcome? If any link depends on memory or disconnected files, the process is not controlled. A workforce demand-to-record chain turns a new requirement into better hiring discipline while preserving speed, accountability and business value. This article provides independent commercial-management commentary and does not provide legal, employment, tax or other regulated advice.
