Call-Off Contracts Under a Framework, Explained (2026)

A call-off contract is the document you use to order specific goods or services under a framework agreement that is already in place. The framework sets the rules once; the call-off draws down actual work against those rules. If the framework is the umbrella, the call-off is the individual purchase that shelters under it. This guide explains what a call-off is, how it relates to the framework, when a binding contract actually forms, and how to set one up. ## What a call-off contract is Under a two-layer structure, the framework agreement contains the terms that stay the same across every order, and the call-off contract contains the terms that change each time: what is being ordered, how much, when, and at what price within the framework's pricing rules. A call-off may be called a call-off order, a purchase order, a work order or a statement of work, depending on the industry, but the idea is the same. It is the mechanism by which the buyer "calls off" supplies or services from the framework. Because the heavy terms already live in the framework, a call-off can be short. Often it is a one or two page order that references the framework and fills in the specifics. That is the whole point: speed and consistency. ## How the call-off relates to the framework The framework and the call-off work together. The framework provides the standing terms, such as liability, confidentiality, intellectual property, warranties and governing law. The call-off provides the transaction detail and incorporates the framework terms by reference. Two things must be clear for this to work cleanly: - Incorporation. The call-off should expressly bring in the framework terms, so there is no doubt they apply.

• Order of precedence. If a call-off and the framework conflict, which one wins? Frameworks usually state this. A common approach is that the framework governs, except on points the framework expressly allows the call-off to vary. Without clear incorporation and precedence, you can end up arguing about which terms actually apply to a given order, which defeats the purpose of having a framework at all. ## When a binding contract forms A common point of confusion is whether the framework itself is a binding contract. In many arrangements the framework sets terms but does not, on its own, commit the buyer to buy anything; the binding obligation to supply and pay arises when a call-off is placed and accepted. In others, the framework includes a minimum commitment. The drafting decides it, so the framework and call-off should make clear: - What act forms a binding call-off (for example, the buyer issuing an order and the supplier accepting it, or the supplier beginning performance).
• Whether the supplier can refuse a call-off, or must accept orders within agreed limits.
• When obligations and risk pass for the specific order. ## Key terms in a call-off - Reference to the framework. The framework agreement, its date, and a statement that its terms apply.
• Description of what is ordered. Specific goods or services, quantity and specification.
• Price. Within the framework's rate card or pricing method.
• Dates and milestones. Delivery or performance dates, and any phased milestones.
• Order-specific terms. Only those the framework permits the call-off to set, such as a particular service level or acceptance test for this order.
• Acceptance. How the order is accepted and when it becomes binding.
• Order of precedence reminder. A line confirming the framework prevails except where it allows variation. ## An illustrative structure 1. Call-off reference and date

2. Reference to the framework agreement and incorporation of its terms
3. Description of goods or services ordered
4. Quantity and specification
5. Price and payment within framework rules
6. Delivery or performance dates and milestones
7. Any permitted order-specific terms
8. Acceptance and formation of the binding call-off
9. Precedence confirmation and signature This is a skeleton to show the shape, not a form to drop into a live deal. Call-off arrangements interact with procurement rules and the exact wording of the parent framework, so specific drafting should be reviewed by a qualified lawyer for the jurisdiction. ## Common pitfalls - A call-off that does not clearly incorporate the framework, leaving the applicable terms uncertain.

• Order-specific terms that quietly rewrite core framework risk provisions they were never meant to touch.
• Confusion over whether the framework alone commits the buyer, when actually the call-off is what binds.
• No clear point of acceptance, so it is unclear when the contract formed.
• Pricing in the call-off that drifts outside the framework's agreed rates. ## Keeping framework and call-offs connected The practical difficulty with call-offs is volume and linkage. One framework can sit above dozens of orders, and it is easy to lose track of which call-off inherits which terms, which ones varied something, and what is still live. That is exactly where an AI contract workspace helps, by modelling each document as a structured clause tree and linking related documents so a framework and its call-offs stay connected and their terms stay visible. Adira is built this way and keeps drafting, review, versioning and activity history together. It is India-first today, with other jurisdictions on its roadmap, so confirm local depth before relying on it. More at Adira. The explanation above stands on its own. ## Bottom line A call-off contract is how you order specific goods or services under a framework that already exists: a short document that incorporates the framework terms and fills in the quantity, price and dates for one order. For it to work, the call-off must clearly bring in the framework terms, respect the order of precedence, and make plain when a binding order forms. Get those right, keep order-specific terms within what the framework allows, and get local legal advice on the detail.