"Executed" means signed to your ops team and fully performed to a bankruptcy lawyer, and the gap between those two readings decides who can walk away from your agreement. Here is what the term actually covers, and what changes the moment a contract crosses that line.
It's 4:40 on a Friday and your CFO wants a straight answer. The master services agreement with the new infrastructure vendor has 11 exhibits, a 36-month term, three pricing schedules that step up on the anniversary of a date nobody has pinned down, and a signature page that two of the four required signatories have returned. Procurement says the deal is "executed." Legal says it is "signed but not effective." Finance has already cut a purchase order. Three people are using the same word to describe three different states of the world, and the answer determines whether your company owes roughly $340,000 next quarter.
This happens constantly. The word "executed" is one of the most overloaded terms in commercial practice, and the ambiguity isn't academic trivia. It decides who can walk away, what a trustee can reject in bankruptcy, whether a diligence checklist item is actually closed, and whether the obligations buried in Section 9.4 are live or dormant. Most teams get through most deals without ever confronting the ambiguity. The problem is the deals where they do.
What follows is a plain treatment of what an executed contract actually is, where the two competing definitions come from, how to tell which one someone means, and what changes the moment a contract crosses that line. If your team touches agreements at any point in their life, from drafting through renewal, this distinction will eventually cost you money or save you some.
In everyday commercial usage, an executed contract is an agreement that has been signed by every party required to sign it, with all conditions to signature satisfied, so that it is legally binding and enforceable. The signatures are on the page. The authority to sign was real. The document is no longer a draft.
That's the working definition most business teams use, and for most purposes it's the right one. When your counterparty's counsel emails "fully executed copy attached," they mean the signature blocks are complete. When your contract repository shows a status of "Executed," it usually means the same thing.
Execution is not just ink on a page. For a contract to be genuinely executed rather than merely signed, three things generally need to be true.
There is also a fourth item that trips teams up regularly: the effective date. Execution and effectiveness are separate concepts. A contract can be fully executed on 14 September and effective on 1 January. It can also be executed on 14 September and effective retroactively as of 1 July. The signature completes the document. The effective date starts the clock. Conflating them is the single most common source of the "is this live yet?" confusion.
Here is where it gets genuinely messy, and why your lawyer and your ops lead can both be right while disagreeing.
The word carries two established meanings in law, and they point in opposite directions.
This is the transactional sense. To "execute" a document means to complete the formalities that make it binding: sign it, seal it, deliver it. A fully executed agreement is one where every signature is in place. This is the meaning embedded in phrases like "execution version," "execution copy," and "counterparts may be executed by electronic signature." It is overwhelmingly the dominant usage in commercial practice, and it is what most people mean 95 percent of the time.
This is the older doctrinal sense, and it survives in case law, bankruptcy practice, and academic treatment. An executed contract is one where both parties have completely performed their obligations. Nothing remains to be done. The deal is finished, not started. Under this meaning, a cash purchase at a store counter is an executed contract the moment goods and money change hands. A 36-month SaaS subscription signed this morning is decidedly not executed, because years of performance remain.
This isn't a cosmetic difference. It's architectural. Under Meaning One, execution is the beginning of the relationship. Under Meaning Two, execution is the end of it. The same document can be "executed" under the first definition and "executory" under the second, simultaneously, and both statements are correct.
Context resolves it almost every time, if you know what to look for.
The practical takeaway: when the stakes are high, don't rely on the word alone. Ask the follow-up. "Signed by everyone, or performed and closed out?" Ten seconds of clarification beats a quarter of misallocated revenue recognition.
If executed (in the classical sense) means fully performed, then executory contract is its opposite: an agreement where material obligations remain outstanding on both sides. This pair is the one that shows up on exams, in bankruptcy filings, and in the middle of transactions where somebody suddenly needs to know what a trustee can do.
The question is not whether the document is signed. It's whether performance remains. The widely used formulation, associated with the Countryman definition and adopted in much US bankruptcy practice, asks whether the obligations of both parties are so far unperformed that the failure of either to complete performance would constitute a material breach excusing the other's performance. If yes, the contract is executory. If no, it is executed.
Two things matter in that test. First, obligations must remain on both sides. If your counterparty has fully delivered and all you owe is money, many courts will treat the agreement as no longer executory, which converts your position into a simple debt claim. Second, the remaining obligations must be material. Boilerplate survival clauses and minor administrative duties generally don't keep a contract executory on their own.
The uncomfortable truth is that the line is not always crisp, and courts reach different conclusions on similar facts. What you can control is knowing where your agreements sit and what obligations are genuinely outstanding. That's a documentation problem more than a legal one.
The path from draft to executed is more procedural than most teams treat it. Each step creates a state change worth tracking.
Most commercial agreements permit execution in counterparts, meaning each party signs a separate copy and the collection of copies constitutes one agreement. This is convenient and universal. It is also where fully executed sets go missing. In most organizations, the "final" file is whatever was last emailed around, and reassembling a complete counterpart set from a shared drive months later is a genuinely unpleasant exercise. If you have ever been asked in diligence to produce a signature page nobody can find, you know the cost.
Abstractions are cheap. Here is where the executed versus executory line actually bites.
Your logistics provider, 18 months into a five-year agreement with favorable rates you negotiated hard for, files Chapter 11. Because both sides still owe material performance, the agreement is executory. That means the debtor (or trustee) can assume the contract, assume and assign it to a third party, or reject it. Rejection is treated as a pre-petition breach, which typically leaves you with an unsecured claim, and unsecured claims commonly recover cents on the dollar. If the contract had been fully performed on both sides, this option would not exist.
Your company is being acquired. Diligence asks which of your 400 supplier agreements survive a change of control. The answer depends on whether obligations remain outstanding, what the anti-assignment clause says, and whether the deal is structured as a stock purchase or an asset purchase. Agreements with no remaining obligations are largely irrelevant to the buyer. Agreements with substantial remaining obligations and a consent requirement are on the critical path, and each one may require a counterparty signature before closing.
Finance needs to know the contract inception date for revenue recognition. Under modern standards, that generally means the date the agreement becomes enforceable, not the date the last person clicked sign. If the effective date is 1 January and the signature date is 14 February, booking to the wrong one distorts the period. Multiply by a few hundred agreements and you have an audit finding.
An agreement auto-renews for successive 12-month terms unless either party gives 90 days' written notice before the anniversary of the effective date. Your team tracked the signature date instead. The window closed 11 days before anyone looked. You are now committed for another year at a rate you wanted to renegotiate. This is not a legal failure. It's a tracking failure, and it is extremely common.
Three domains punish imprecision here more than any others.
Section 365 of the US Bankruptcy Code gives a debtor broad power over executory contracts and unexpired leases. That power is asymmetric by design: the debtor gets to keep the agreements that are valuable and shed the ones that are not, and the non-debtor party has limited ability to resist. Whether your agreement falls inside that power turns on the executory test. Practitioners commonly observe that counterparties discover their agreement was executory only after receiving a rejection notice, which is the worst possible time to learn it.
Assumption comes with a price for the debtor: outstanding defaults generally have to be cured and adequate assurance of future performance provided. That gives the non-debtor counterparty leverage, but only a counterparty who knows what it is owed and can document it.
Anti-assignment clauses matter only where something remains to be assigned. In a carve-out, divestiture, or restructuring, the diligence work is essentially an inventory of live obligations: which agreements are still running, which require consent, which have change-of-control triggers, and which have already run their course. Teams that maintain that inventory continuously move quickly. Teams that reconstruct it under deal pressure spend six figures on outside counsel doing document archaeology.
Every diligence request list asks for material contracts, and most ask specifically for fully executed copies with all amendments, schedules, and exhibits. The word "fully executed" here means signed and complete. What buyers actually find, in most organizations, is a mix of executed originals, unsigned drafts saved under names suggesting they are final, amendments detached from their base agreements, and schedules referenced but never located. A well-maintained contract repository is not a nice-to-have at that moment. It is the difference between a clean diligence process and a purchase price adjustment.
Here is the part most contract processes handle badly. Execution is treated as the finish line. Signature collected, file saved, deal closed, team moves on. But under the classical definition, execution in the signing sense is precisely the moment the obligations become real. The document stops being a negotiation artifact and starts being a set of live commitments with dates attached.
A typical commercial agreement of any substance contains dozens of obligations that outlive the signing: payment schedules, service levels, reporting deliverables, insurance maintenance, audit rights, notice requirements, renewal windows, confidentiality periods, data handling commitments, and indemnity triggers. Most of them sit in prose, scattered across sections and exhibits, expressed in relative terms ("within 30 days of the end of each calendar quarter") rather than as dates on a calendar.
Disciplined contract obligation tracking addresses this, but only if it starts at execution rather than at the point where something has already gone wrong. Extracting obligations from a 90-page PDF two years after signing is a different and much harder exercise than capturing them while the document is still structured.
The question isn't whether your team can identify an executed contract. It's whether, 14 months from now, anyone can answer what it still obliges you to do without opening a file and reading it end to end.
Be honest about what the current stack does and doesn't do. E-signature platforms (DocuSign, Adobe Sign, Dropbox Sign) are excellent at the signature event itself: routing, authentication, audit trail, tamper evidence. They are not built to tell you what the contract obligates you to do afterward. CLM platforms (Ironclad, Agiloft, Icertis and others) do handle post-signature obligation and renewal tracking, often well, though they typically require meaningful configuration and work best when a real administrative owner exists. Word plus a shared drive remains the most common setup by a wide margin, and it is genuinely fine for low volume, though it offers nothing structural: the document is a blob of formatted text, and every question requires a human to reread it.
The gap that persists across all three is structural. In most tooling, a contract is a document during drafting and an image of a document afterward. The sections, defined terms, cross-references, and obligations that give the agreement its logic exist in the drafter's head and in the visual formatting, not in the file itself. That is why obligations get lost: there was never a machine-readable representation of them to lose.
An executed contract, in the classical legal sense, is one where all parties have completely performed their obligations, leaving nothing material outstanding. An executory contract is one where material obligations remain unperformed on both sides. The confusion arises because in everyday commercial usage "executed" simply means signed, and a contract can be signed and executory at the same time. The distinction matters most in bankruptcy, where a debtor has special powers to assume, assign, or reject executory contracts that do not apply to contracts already fully performed. When precision matters, ask whether the speaker means signed or performed.
Both, depending on who is speaking. In transactional and commercial contexts, which covers the overwhelming majority of everyday use, "executed" means signed by all required parties with the necessary formalities completed. In bankruptcy, insolvency, and doctrinal contexts, "executed" means fully performed. The phrase "fully executed" almost always means signed rather than performed. If someone says a contract is executed and the consequence matters, confirm which sense they intend before acting on it.
A contract is fully executed when every party required to sign has signed, each signatory had authority to bind their entity, and any formalities the agreement or applicable law requires (notarization, witnessing, delivery, counterpart exchange) have been satisfied. Partial signature does not count. Note that fully executed does not necessarily mean effective: if the agreement contains conditions precedent or a later effective date, obligations may not begin running until those are met. Track the signature date and the effective date as separate facts, because they are frequently different and finance, legal, and operations may each need a different one.
Yes, but only through mechanisms the agreement or law provides. The standard routes are a written amendment signed by all parties, exercise of a termination right contained in the agreement (for cause, for convenience, or on notice), mutual rescission, or a legal doctrine that voids or discharges the agreement such as fraud, mistake, impossibility, or frustration of purpose. Most commercial agreements contain a clause requiring amendments to be in writing and signed, which means informal agreement by email may not be effective. Every amendment should be linked back to the base agreement and the specific provisions it alters, because detached amendments are one of the most reliable ways to end up relying on a superseded term.
In most jurisdictions and for most commercial agreements, yes. Frameworks such as the US ESIGN Act and UETA, and comparable regimes in the UK, EU, and elsewhere, generally give electronic signatures the same legal effect as handwritten ones. There are narrow exceptions, commonly including wills, certain family law instruments, and some statutory notices, and some jurisdictions impose additional requirements for particular document types such as real property transfers. Practical enforceability also depends on the audit trail: evidence of who signed, when, and that the document was not altered afterward. Reputable e-signature platforms provide this, which is a meaningful part of their value.
Four things, ideally within days rather than months. Store the complete executed set (base agreement, all counterpart signature pages, all schedules and exhibits) in one findable place. Record the key dates: signature date, effective date, term end, renewal notice deadline, and any pricing anniversary. Extract the material obligations with an owner, a trigger, a deadline, and a citation back to the source clause. Distribute the relevant obligations to the teams that actually have to perform them, which is usually finance, operations, and whichever function owns the commercial relationship. Teams that skip this step spend the rest of the contract's life reconstructing it under pressure.
HERO is a document editor built on the premise that a contract should not stop being structured the moment it is signed. Sections, defined terms, cross-references, and obligations stay addressable after execution, so the agreement remains something your team can query rather than something they have to reread. That means renewal windows, payment triggers, and reporting deadlines stay connected to the clauses that created them, through every amendment. If your executed contracts currently live as flat files nobody can interrogate, book a demo and see what a structured one looks like.