The 30-Day Notice Clause: What Your Dev Contract Should Demand

Last updated October 2026

In a software development contract, the terms that count most are the ones that decide how you get out: termination for convenience on 30 days’ notice, a written assignment of all code and IP, constant access to the repository, transition assistance that is spelled out, and a termination fee that is capped or zero. You can always renegotiate price and scope down the road. You can’t fix a bad exit clause after you’ve signed it.

Key takeaways

A 30-day termination for convenience clause is the best single protection you have against a vendor that stops delivering, since it turns your leverage from something you get once a year into something you hold every month.
Labeling software a “work made for hire” doesn’t do the job by itself. Insist on an express written assignment of every right in the code.
You should have live repository access from day one, in an account you own, rather than getting it “on final payment.”
Put transition assistance in the contract with hours, rates and deliverables. Otherwise it gets priced after you’ve already given notice.
AI-assisted delivery calls for one more clause: a warranty that human engineers reviewed and modified the delivered code, along with infringement indemnity.

Why is the notice period the most important term in a software development contract?

Most buyers haggle over the rate and only skim the termination section, which gets things the wrong way round. The rate tells you what a good month costs. The notice period tells you how many bad months you’re stuck paying for once you can see the engagement is going wrong.

Run the numbers. A team that bills $40,000 a month under a 90-day notice clause costs $120,000 to walk away from, and that’s before the delay to whatever comes next. Under a 30-day clause, the same exit costs $40,000. That gap isn’t a discount. It’s what the vendor’s confidence in its own work is worth.

The length of notice also shapes how people behave while the work is under way. A vendor you can replace within a month has to earn every next month. A vendor sitting on a guaranteed quarter of revenue can coast through one of them. If you haven’t settled on an engagement model yet, our pillar guide on delivery pods vs. staff augmentation vs. project outsourcing walks through how each one usually deals with notice and exit.

What should a termination for convenience clause really say?

Termination for convenience means you can end the contract without having to prove a breach. If you don’t have it, walking away from a vendor that’s just slow or mediocre means arguing they missed a standard nobody ever put in writing. In its Contract Corner analysis of termination for convenience provisions, the legal team at Morgan Lewis names three terms that determine whether the right actually works: how long it takes from notice to the effective date, the termination fee, and the termination assistance the customer is entitled to get. The same piece points out that fees often slide downward over the term, and that providers may try to tack on the cost of breaking third-party contracts and redeploying their staff.

In a dev services contract, that comes down to five sentences you’ll want to find:

Notice: either party can terminate for any reason with 30 days’ written notice.
Fee: there’s no termination fee, or there’s one that’s a fixed dollar amount, shrinks over the term, and hits zero within the first few months.
Payment: you pay for work done and accepted up to the effective date, and nothing for the rest of the term.
Prepaid amounts: any unused prepayment or deposit comes back to you within a set number of days.
Assistance: the vendor gives transition assistance during the notice period at the contract rate.

Strike lost profits on the unexpired term first. That’s just a lock-in fee under another name.

Which software development contract terms belong on your checklist?

Keep the table below next to you while you read a draft. For every row, find the clause that answers it. If there’s no such clause, or it’s weaker than what the right-hand column says, flag it for negotiation.

Term	Weak version to push back on	What to demand
Termination for convenience	Only for cause, or 90 days or longer	30 days’ written notice, either party
Termination fee	Lost profits on the remaining term	None, or a fixed amount that declines to zero
Minimum term	12 months committed up front	No minimum, or a short pilot period
IP ownership	“Work made for hire” label only	Express written assignment of all rights in code, docs, and infrastructure scripts
Code access	Delivered on final payment	Repository in your account from day one, with commit access visible to you
Credentials and infrastructure	Vendor-owned cloud and domain accounts	All accounts registered to you, vendor added as a user
Transition assistance	“Reasonable cooperation”	Defined hours, rate, and deliverables during the notice period
Key personnel	Vendor may reassign at will	Named engineers, replacement only with notice and your approval
Non-solicitation	Bars you from hiring vendor staff for 24 months	Short period, with a fixed conversion fee instead of a ban
AI-generated code	Silent	Disclosure of tools, human review warranty, infringement indemnity

A few of these rows affect price. Our guide to reading a software development proposal for hidden costs explains how vendors shift cost into change orders and exclusions, which is the commercial half of the same negotiation.

If the contract says “work made for hire,” do you own the code?

Not always, and most contract checklists miss this. Under US law, work done by an independent contractor counts as a work made for hire only when it fits one of nine statutory categories and both sides sign a written agreement saying so. The US Copyright Office’s Circular 30 on works made for hire names the nine: a contribution to a collective work, part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, and an atlas. Computer programs aren’t among them.

That means a clause that only calls the code a work made for hire could leave ownership with the agency or with its individual contractors. Fixing it costs little. The contract should also contain an express assignment of all right, title and interest in the deliverables, a promise to sign whatever further documents are needed to perfect that assignment, and a warranty that every engineer and subcontractor on the project has signed a matching assignment to the vendor. This is general information, not legal advice, so have your own counsel look over the final wording.

AI-assisted delivery makes the gap wider. On January 29, 2025, the Copyright Office published Part 2 of its Artificial Intelligence report, which concluded that outputs can be protected only where a human has determined sufficient expressive elements, and that just providing prompts doesn’t qualify. If a vendor’s engineers take big chunks of assistant output without changing them in any meaningful way, part of what you paid for may have no copyright at all. Get three things in writing: disclosure of which AI tools were used, a warranty that the vendor’s engineers reviewed and modified the delivered code, and indemnity for infringement claims no matter how the code was produced.

What should happen to the code and credentials once you give notice?

With the right contract, nothing dramatic. The code already sits in your repository, the cloud accounts already belong to you, and the vendor just loses access on the effective date. Notice periods get ugly when the buyer finds out, on the first day of notice, that the production database lives in the agency’s AWS account and the domain is registered to the agency’s founder.

Make the handover list a contract deliverable, not a favor:

The full repository history, branches and tags included, in an account you control.
Infrastructure as code, environment configuration, and a list of every secret along with where it’s kept.
Admin credentials for each third-party service, handed over and rotated.
Architecture notes, a runbook covering deploys and rollbacks, and the list of open defects.
A set number of knowledge-transfer hours with the engineers who wrote the code, booked within the notice period.

Source code escrow is the backup plan when a vendor licenses software to you rather than assigning it. The source code escrow agreement checklist by Kilpatrick Townsend & Stockton, published as LexisNexis Practical Guidance, lists release events such as breach of support obligations, insolvency and change of control, plus duties to report changes to the code and to cooperate with verification. When you’re paying outright for custom development, a live repository in your own account is both simpler and stronger than escrow.

Which contract red flags should stop you from signing?

A notice period of 60 days or longer on a team you haven’t watched deliver. You can’t judge a new team faster than you’re able to leave it.
Termination fees linked to the rest of the term. The vendor is building in the odds that you’ll want out.
Code withheld until final payment. Your own product turns into collateral in every billing dispute.
“Reasonable cooperation” as the only wording on transition. The party you just fired gets to decide what reasonable means.
An unlimited right to swap engineers. The senior people on the sales call may never write a single line of your code.
No mention of AI tooling at all. Either the vendor hasn’t considered ownership, or it would prefer you didn’t bring it up.

For rate benchmarks and risk controls that apply to contractor engagements, read our guide to IT staff augmentation rates, contracts, and risk controls.

Frequently asked questions

Is 30 days a fair notice period for a software development contract?

Yes, for time-based team engagements. Thirty days is enough for a clean handover and gives the vendor room to redeploy people. A longer period only makes sense when the vendor put real money in up front on your behalf, and even then a fixed termination fee that declines over time is fairer than a long notice period.

How is termination for cause different from termination for convenience?

Termination for cause needs a breach, usually with a cure period, so you have to show the vendor missed a written obligation. Termination for convenience lets you end the contract for any reason with notice. If the contract only allows termination for cause, you can end up stuck with a vendor that’s slow but not technically in breach.

Should a software development contract cover AI coding tools?

Yes. AI-generated output affects who owns the copyright, your exposure to open-source licenses, and how much review is needed. The contract should require tool disclosure, a warranty of human review and modification, and indemnity for infringement claims however the code was made.

How TopDevz writes its contracts

We built our own terms to pass this checklist. Delivery Pods start at $15K per month with 30-day notice, your repository holds the code from the very first commit, and with 96% team retention, the engineers you meet are the ones who stay. If you’re already tied to a vendor whose code you don’t trust, the $4,950 Rescue Audit shows what you really own and what moving would take, and the fee is credited toward remediation if we end up doing the work.

Start a Rescue Audit

Stuck in a contract you’d like to leave, or unsure you own your code? Get a ranked findings register ahead of your next renewal date. Start a Rescue Audit.