Choose a framework agreement (also called a long-term agreement, LTA, long-term arrangement or retainer) when the same kind of requirement will come back but you cannot say in advance how much, where or when: relief items through a season, vehicles for a monitoring programme, repeated workshops. Choose a one-off procurement when the requirement is one defined need with a known quantity, place and date. A framework saves the time of a new tender for each requirement; a one-off procurement prices exactly the need in front of you. Either works only when the documents say what is fixed, what each order confirms and what is not promised.
What the terms mean
The UN's Procurement Practitioner's Handbook (opens in a new tab) describes a long-term agreement as a written agreement with a supplier covering the commercial terms for orders that may be issued against it: pricing, discounts, payment, delivery and packaging, and the general conditions. It notes that such agreements go by many names, are usually the result of a competitive tender, and are typically non-exclusive, for a specified period and up to a ceiling of aggregate demand. Some commit the buyer to a level of orders; many only establish the framework.
| Arrangement | What it is | What triggers work |
|---|---|---|
| Framework agreement, LTA, retainer | What it isTerms agreed once, after competition, for a period and usually up to a ceiling | What triggers workA written task order or call-off |
| One-off request for quotation | What it isPrices for one defined requirement, for simpler or lower-value purchases under your rules | What triggers workThe purchase order or contract it awards |
| One-off tender (ITB or RFP) | What it isA formal solicitation for one larger or more complex requirement | What triggers workThe contract it awards |
Your organisation's own procurement rules decide which method a given value and risk requires; this guide is about the choice where the rules leave one.
When each is useful
| Situation | Usually suits |
|---|---|
| The same items or services recur, but quantities and places vary | Usually suitsA framework with task orders |
| Needs arrive at short notice, such as a response that must start quickly | Usually suitsA framework set up before the need |
| One requirement with a fixed quantity, place and date | Usually suitsA one-off procurement |
| A new or unusual item the market has not supplied to you before | Usually suitsA one-off procurement, after market research |
| A seasonal need you can forecast well, such as winter items for known sites | Usually suitsEither: a one-off with phased deliveries, or a framework if it recurs each year |
| Several partners or agencies buying the same thing | Usually suitsA framework other parties can call off from, if its terms allow |
The Logistics Working Group's August 2026 minutes (opens in a new tab) record that agencies' long-term agreements are under review for shared contracting under the UN80 joint supply chain initiative. A framework written with clear service lines and unit rates is easier to extend or share; one written as a vague promise is not.
What the framework fixes, and what each task order confirms
The most useful page of a framework agreement is the one that separates the two. A task order should not have to renegotiate what the framework already settled, and the framework should not pretend to settle what only an order can.
| The framework fixes | Each task order confirms |
|---|---|
| The services and item categories it covers | Each task order confirmsThe exact items and their specifications |
| How specifications are approved: a standard list, samples, or per order | Each task order confirmsSpecification sign-off or the sample approved for this order |
| The price basis and the rate schedule, and how and when rates may change | Each task order confirmsThe price of this order, calculated from the schedule |
| The zones or corridors it serves | Each task order confirmsThe delivery locations and handover points, to district level |
| How an order is issued, acknowledged and accepted, and by whom | Each task order confirmsThe order's reference, its issue date and the acceptance |
| The inspection standard and who inspects | Each task order confirmsThe inspection points for this order |
| The records, reporting templates and closeout standard | Each task order confirmsThe records due for this order, and when |
| Payment terms and the documents an invoice carries | Each task order confirmsThe invoice for this order, with its records |
| Liability for goods in the supplier's custody | Each task order confirmsThe goods and the custody period of this order |
| The term, any ceiling, and how the agreement ends | Each task order confirmsThe order's dates and milestones |
Each task order should be issued in writing, acknowledged in writing, and carry one reference that appears on every document it produces, from the quotation comparison to the delivery notes and the invoice. Then each order can be inspected, accepted, invoiced and closed on its own, and an auditor can follow any order from instruction to closeout without unpicking the whole framework.
Capacity and access are assumptions, not promises
A framework cannot promise that the supplier will always have stock, vehicles and staff free on the day an order arrives, or that every road will be open. Write the assumptions down instead: the volume the rates were priced for, how many orders may run at once, the notice an order needs, and what happens when an order is beyond them. Then write how a change is handled: who notifies whom, how quickly, how a revised date or price is proposed, and that nothing changes without written approval.
Seasonal access matters most. A framework that serves high-altitude districts should say how winter orders are planned, since roads there may close for months; the winter pre-positioning guide shows how to work back from the last safe delivery date.
What a framework usually does not promise
Read the agreement for what it leaves out. Many frameworks are non-exclusive: the buyer may buy the same things elsewhere, and the supplier may sell to others. Many do not guarantee any volume: a ceiling is a maximum, not a commitment to order. Neither side should plan on more than the agreement actually says. A supplier pricing a framework knows that, which is one reason framework rates can carry a premium over a one-off price for a single large order; the UN handbook notes the same trade-off.
If you need something a typical framework does not give, such as a minimum volume, an exclusive arrangement or reserved stock, it has to be written in, and it will be priced.
Pre-financing
Some frameworks ask the supplier to buy before it is paid. If yours does, the agreement should state what the supplier pre-finances, any maximum outstanding at one time, what triggers payment, and the documents that support each payment. Decide these with your finance team before the tender, not when the first order is waiting.
When a one-off procurement is better
A one-off procurement is usually the better choice when the requirement is clear and will not recur, when the item is new to you and the market needs testing, when a large single order would earn a better price than a framework's rates, or when the work is specialised enough that a different supplier may suit each time. It also keeps commitments simple: one requirement, one award, one closeout.
Template: task-order and framework checklist
Framework agreement and task-order checklist
For the requesting organisation: the first part when the framework is written or tendered, the second for every task order.
Part 1: the framework
- Services and item categories covered, and anything excluded
- How specifications are approved: list, samples or per order
- Price basis and rate schedule, and how rates may change
- Zones, corridors or provinces served
How an order is issued, acknowledged and accepted, and by whom
- Notice an order needs, and how many may run at once
- Volume the rates assume; no volume guaranteed unless stated
- Exclusive or non-exclusive, stated in the agreement
- Inspection standard and who inspects
- Records, reporting templates and closeout standard
- Payment terms and the documents an invoice carries
Pre-financing, if any: what, the maximum outstanding, what triggers payment
- Liability for goods in the supplier's custody
How access, capacity or price changes are notified and approved
- Term, ceiling, extension and how the agreement ends
Part 2: each task order
Task order referenceCarried on every document the order produces
Issued by and date
Acknowledged by the supplier, and date
| Line | Item and specification | Unit | Quantity | Rate from the schedule | Total |
|---|---|---|---|---|---|
| Province | District | Handover point | Who may sign | Quantity | Required by |
|---|---|---|---|---|---|
- Specification or sample approved for this order
- Inspection points and inspector named
- Records due and the date they are due
- Any change from the framework approved in writing
Closing the task order
Quantities dispatched, delivered and accepted reconciled by line
- Exceptions explained, with the approval for each
- Invoice matches the order and the records
- Records filed under the task order reference
Closed by and date
Template: quotation checklist for repeated assignments
When you tender the framework, ask every supplier the same questions, so the rates compare as well as the totals.
Quotation checklist for a framework or repeated assignments
Sent with the tender; each supplier answers every line.
What the supplier states
| Question | Supplier's answer |
|---|---|
| Rate for each service line, and its unit | |
| The volume each rate assumes | |
| How rates change, and on what notice | |
| Zones or provinces served, and who works in each | |
| Notice needed for an order, and how many orders at once | |
| How an order is acknowledged, and by whom | |
| Inspection offered, and the records it produces | |
| Records and reports for each order, in our templates | |
| Payment terms requested, and any advance | |
| Pre-financing offered, if requested, and its limits | |
| Liability for goods in custody, and the insurance position | |
| How access or capacity problems are reported, and how fast | |
| References for frameworks or repeated work of this kind |
An example from the record
Zhikal's current framework of this kind is a non-food-item procurement and distribution retainer for UN Women, active through December 2026. Its scope is nationwide, organised into six delivery corridors so that any task order routes to a standing team, and covers 28 listed non-food-item categories, with market research, competitive sourcing, pre-financed procurement, quality assurance, warehousing, transport and accountability records under one framework. That describes what the framework covers, not the items or quantities supplied under it. The case study sets out what the record states.
Zhikal quotes its procurement and distribution services for a single requirement or under a framework, and can quote vehicle rental and event management either way. The logistics RFQ checklist covers a one-off request in detail. To discuss which model suits a recurring requirement, send the categories, the expected pattern of orders and the provinces to the team in Kabul.
Sources
- UN Procurement Practitioner's Handbook (2006) (opens in a new tab)
Inter-Agency Procurement Working Group, published by the Logistics Cluster. Long-term agreements, supplier eligibility and post-qualification, clarifications during solicitation and evaluation, and due diligence.
- Afghanistan Coordination Meeting Minutes, Kabul, 12 August 2026 (opens in a new tab)
Logistics Working Group (Logistics Cluster). Border and corridor status, and the working group's daily road-status mapping.
External sources are cited for the facts they report and were checked when this guide was last updated. Citing them implies no relationship with, or endorsement by, their publishers.