A consultancy that subcontracts delivery capacity carries a timing risk most engineering leads never model explicitly: the notice period on the subcontractor agreement and the renewal or termination window on the client's own contract rarely line up. When they don't, the consultancy can end up either paying for engineers it no longer needs, or short of engineers exactly when a renewal depends on delivery continuity.
The fix is not a longer notice clause. It is deliberately staggering the subcontractor notice window so it precedes the client renewal date, giving the consultancy a buffer to scale down, scale up, or walk away clean depending on what the client decides.
TL;DR
Subcontract notice periods for IT services in Vietnam, the US, and the EU are not set by statute; they are negotiated, and 30 to 90 days is the typical range for termination without cause.
SaaS and enterprise client contracts commonly run on annual cycles with automatic renewal unless notice is given in advance, which means the renewal decision date is usually known well before it happens.
The core mistake is setting the subcontractor notice period to expire at or after the client renewal date, rather than 30-60 days before it.
ISO 9001 and ISO 27001 require documented supplier relationship controls but do not prescribe a specific notice period, leaving the timing decision entirely to contract drafting.
Scaling a replacement or reduced subcontractor team typically takes 1 to 4 weeks with a pre-vetted engineering bench, which should directly inform how much buffer a consultancy builds into its exit timeline.
About the author: 724SOFTWARE has operated as a subcontract delivery partner for software consultancies and Microsoft, Odoo, and ERP implementation partners since its founding, structuring dedicated teams and ODC engagements around the client-facing renewal cycles of over 200 engagements across 10+ countries.
Why Does the Overlap Even Happen?
The overlap happens because two independent contracts, each negotiated on its own schedule, are being asked to move in sync without anyone owning that synchronization. A consultancy signs a subcontractor agreement with a delivery partner (say, a Vietnam-based team providing three backend engineers) on one signing date, with its own notice-period clock. Separately, the consultancy's contract with its end client runs on a different clock, often annual, with a renewal or non-renewal decision that has to be communicated to the client 30, 60, or 90 days out. Nobody writes these two dates onto the same calendar by default. The result is a scheduling gap that only becomes visible when someone has to make a termination decision under pressure.
This matters because the two clocks fail in opposite directions. If the subcontractor notice period is too short relative to the client renewal date, the consultancy loses staffing before it knows if the client is renewing. If it's too long, the consultancy is locked into paying for capacity after it already knows the client is walking away.
How Long Is a Typical Subcontractor Notice Period?
A subcontractor notice period is the number of days a consultancy or its delivery partner must give before terminating (or materially changing) the engagement without cause. There is no statutory minimum for IT services subcontracts in Vietnam, the US, or the EU; these figures are set entirely by the negotiated contract terms. In practice, negotiated notice periods for termination without cause in these markets range from 30 to 90 days.
Some sources on subcontractor terminations recommend giving more notice than the contract technically requires when timing allows, on the logic that a contractor who has room to plan an orderly exit is less likely to create disputes during the transition. That advice applies just as directly to the reverse case, a consultancy giving notice to its own subcontracted delivery team, because an abrupt exit creates handover risk on both sides.
The practical range worth planning around:
Notice period | When it's typical
|
|---|---|
30 days | Smaller subcontract engagements, single-role staff augmentation |
60 days | Mid-sized dedicated teams, multi-role delivery pods |
90 days | Larger ODC arrangements, engagements with knowledge-transfer requirements |
Firing an independent contractor without a fixed notice clause in the contract still typically settles into a two-week to 90-day range depending on the situation and the complexity of the handover.
When Do Client Contracts Actually Renew, and Why Does That Date Matter More Than the Signing Date?
The date that matters for planning is not when the client contract was signed. It's the date by which the consultancy must notify the client of non-renewal, which is usually well before the contract's actual expiration.
SaaS and enterprise contracts for offshore or outsourced development capacity typically run on annual renewal cycles, and they commonly auto-renew for successive one-year terms unless one party gives written notice ahead of the renewal date. That written-notice deadline, not the anniversary date itself, is the real trigger point. If the deadline to notify the client of non-renewal is 60 days before the anniversary, the consultancy's own internal staffing decision needs to be finalized before that 60-day mark, not after.
Building on that: a consultancy that hasn't mapped its subcontractor's notice clock against this client-facing deadline is, in effect, making a staffing commitment (or a termination commitment) blind to whether the revenue behind it still exists.
What's the Actual Sequencing That Avoids the Trap?
The sequencing that works puts the subcontractor decision point before the client renewal deadline, with enough runway left over to act on either outcome. In practical terms:
Identify the client renewal notice deadline first. This is the date, not the contract's expiration date, that determines when the consultancy must commit to renewing, renegotiating, or exiting the client relationship.
Set the subcontractor decision point 30-45 days before that deadline. This gives the consultancy time to either scale the subcontracted team up (if renewal looks likely), scale it down, or begin an orderly wind-down (if it doesn't).
Confirm the subcontractor's own notice period fits inside that window. If the subcontractor requires 90 days' notice and the consultancy only has 45 days of runway before its own client deadline, the math doesn't work, and the consultancy is exposed either way.
Build scale flexibility into the subcontractor agreement itself, rather than relying purely on termination clauses. Industry-standard timelines for scaling offshore teams up or down run 1 to 4 weeks, and providers that maintain a pre-vetted bench can move within days rather than negotiating a fresh hiring cycle each time.
This is the operational reason 724SOFTWARE structures dedicated team and ODC agreements around a 2-4 week scaling window rather than a rigid headcount commitment. A consultancy that can flex its subcontracted team size inside a month has far more room to react to a client renewal decision than one locked into a fixed team for a fixed term.
What Role Do Compliance Standards Play in This Timing Problem?
ISO 9001 and ISO 27001 require an organization to document and control its supplier relationships, including how subcontracted resources are managed and how continuity risk is handled. Neither standard mandates a specific notice period for changes in subcontractor resource availability; that detail is left to the individual contract or SLA.
What the standards do force is documentation: a consultancy aligned with ISO 27001:2022, for example, has to be able to show how it manages the risk of a subcontractor exiting mid-engagement, which in practice means the renewal-timing exercise described above has to be written down somewhere, not just understood informally between two account managers.
For consultancies selling into regulated buyers in Fintech or Healthcare, this documentation requirement is not paperwork for its own sake. It's the artifact a client's own procurement or security team will ask to see before agreeing to a renewal.
What Should a Consultancy Actually Do With This?
Map both clocks on one calendar before the next renewal cycle starts, not during it. Pull the client contract's non-renewal notice deadline and the subcontractor agreement's termination notice period into the same document, and check whether there's at least a 30-day buffer between the subcontractor decision point and the client deadline. If there isn't, that's a contract renegotiation to raise with the delivery partner now, while there's no live crisis forcing the conversation.
Frequently Asked Questions
Is there a legal minimum notice period for IT subcontractor agreements?
No. In Vietnam, the US, and the EU, notice periods for IT services subcontracts are set by negotiated contract terms, not statute. Typical ranges run 30 to 90 days for termination without cause.
Do SaaS client contracts always auto-renew?
Many do, on annual cycles, unless one party gives written notice by a specified deadline before the renewal date. This varies by contract, so the specific deadline needs to be checked in each agreement rather than assumed.
How fast can a subcontracted team actually be scaled up or down?
Industry timelines typically run 1 to 4 weeks, though providers with a pre-vetted engineering bench can move faster, sometimes within days for smaller adjustments.
Does ISO 27001 require a minimum subcontractor notice period?
No. It requires documented control over supplier relationships and continuity risk, but the specific notice period is left to the contract.
What happens if the subcontractor notice period is longer than the consultancy's own client-facing runway?
The consultancy risks being locked into paying for capacity after learning the client isn't renewing, which is exactly the scenario the staggered-timing approach is meant to prevent.
Should the subcontractor agreement and client contract use the same renewal date?
Not necessarily the same date, but the subcontractor's decision point should sit before the client's non-renewal notice deadline, with enough buffer to act on the outcome.
Why does this matter more for smaller consultancies?
A 2-20 person consultancy typically has one funded project behind its first subcontracted seat. A timing mismatch on that single engagement has a proportionally larger impact on cash flow than it would for a larger firm running multiple parallel contracts.
About 724SOFTWARE
724SOFTWARE is a Vietnam-based technology company working with software consultancies and implementation partners as a subcontract delivery partner, structuring dedicated teams and offshore development centers (ODCs) around 200+ engineers, 58% of whom are senior-level. T
eams scale from 1 to 50+ pre-vetted engineers within 2-4 weeks, which is the operational mechanism that lets consultancies match subcontractor capacity to their own client renewal cycles rather than being locked into fixed-term staffing. As a Vietnam IT company aligned with ISO 9001 and ISO 27001:2022 standards, 724SOFTWARE documents supplier-relationship controls in the way regulated end clients expect to see during procurement review, and maintains a follow-the-sun support model with sub-10-minute incident response for consultancies managing delivery across time zones.
If your consultancy is weighing how to structure or renegotiate a subcontractor agreement around an upcoming client renewal, get in touch with 724SOFTWARE at https://724software.com.vn.
