Contract types
A contract type is the payment model of a procurement contract. It sets how the client pays the contractor and who bears the gap between planned and actual cost. The PMBOK Guide describes four fundamental models: fixed-price, cost-reimbursable, time and materials (T&M) and target cost. The project manager reads each one from the client's point of view and then from the contractor's. They select a type or a hybrid and set out the reasons in a justification note. In Switzerland, the Code of Obligations governs a price fixed in advance as an exact amount and a price set by the value of the work.
Goal
The project manager who chooses the contract type decides who will pay for an overrun and how the client pays the contractor. According to the PMBOK Guide, the type defines the terms and conditions under which a project acquires goods, services or results from external sources. It sets the framework for financial arrangements, risk distribution and the nature of the relationship between the parties.
Fixed-price puts the overrun on the contractor. Cost-reimbursable leaves it with the client. Time and materials fixes the hourly rate: the contractor bears the risk on its hourly cost and the client pays for every hour. The cost ceiling shifts whatever exceeds it to the contractor. Target cost shares the overrun by a ratio.
A project often holds both roles: it buys from suppliers and sells its own work to a client. The PMBOK Guide notes that the names of the types vary across industries and organisations. The project manager therefore judges a contract by its pricing mechanism rather than by its label.
The technique produces the contract type and its justification note. The US Federal Acquisition Regulation (FAR) requires this note in every contract file. The team that renews a contract learns from it why the organisation chose this type.
The organisation chooses the type after the make-or-buy analysis has concluded in favour of buying. This choice comes before the call for tenders, whose documentation contains the draft contract.
Usage
When to use
- Decision to buy taken: set the type before drafting the tender documentation and its draft contract.
- HERMES procurement analysis: answer the task's question about forms of contract.
- Scope partly uncertain: split the purchase into lots and give each lot the type that fits it.
- Contractor preparing an offer: price the risk premium of a fixed price or propose another type. In public procurement, the contractor offers the form of remuneration that the tender documentation sets. It proposes another type only if the documentation leaves it that choice.
- Contract negotiation: read each price clause from both points of view before conceding or demanding it. In public procurement, the contracting authority holds no bidding rounds to push the price down (art. 11 let. d PPA): the tender documentation sets the form of remuneration.
- Renewal or new phase: move to a firmer price once experience makes the work possible to estimate.
When not to use
- Decision to buy not yet taken: run the make-or-buy analysis first.
- Drafting or legal classification of a specific contract: leave the clauses and the classification to a lawyer.
- Claim or dispute on an ongoing contract: the type is already set; claims administration handles the claim through negotiation or under the procedure that the contract sets out.
Description
The client's point of view and the contractor's
The PMBOK Guide lists advantages and disadvantages for each type. It also concedes that a party can exploit the terms of a contract. It still sets a goal: a contract that benefits both parties.
| Type | Payment | Typical uses | Client side | Contractor side |
|---|---|---|---|---|
| Fixed-price | A price set in advance for a defined scope | Construction, product development, services whose work can be estimated accurately | Known budget. Price sometimes higher because of risk premiums | Profit possible if the work is well run. Bears the overrun |
| Cost-reimbursable | The contractor's actual costs plus a fee that usually covers its profit | Uncertain scope, high-risk project, research and development, complex construction | Flexibility. Risk of cost escalation | Reduced financial risk. Profit sometimes limited |
| Time and materials (T&M) | The time and materials used plus a margin | Small projects, maintenance, scope unclear at the start; IT services and consulting | Flexibility. Close cost monitoring | Costs covered. Time and resources closely scrutinised |
| Target cost | A target cost and a rule for sharing savings and overruns | Large infrastructure, complex manufacturing | Encourages cost control. Requires a clear target and sharing rule | Incentive to be efficient. Bears part of the overrun |
Fixed-price
The fixed-price contract sets a price in advance against a defined scope. It transfers the cost risk to the contractor and gives the client a predictable budget. The contractor prices that risk: its price contains a premium that covers what it cannot estimate.
The FAR describes the firm fixed price as a price that is not subject to any adjustment on the basis of the contractor's cost experience. It requires one when the risk is minimal or can be predicted with an acceptable degree of certainty.
Cost-reimbursable
The cost-reimbursable contract pays the contractor its actual costs plus a fee that usually covers its profit. The client keeps the cost risk and gains flexibility: the scope can change without the parties renegotiating a firm price.
The FAR limits reimbursement to the allowable costs that the contract prescribes.
Time and materials
Under a time-and-materials (T&M) contract, the contractor bills the client for the time spent and the materials used. The contract sets hourly rates in advance that include wages, overheads and margin. The PMBOK Guide treats it as a hybrid of fixed-price and cost-reimbursable. The hourly rate is fixed. The number of hours is not.
The FAR notes that time and materials gives the contractor no positive incentive to control its costs or to work efficiently. It therefore requires the client to monitor performance and the contract to set a cost ceiling that the contractor exceeds at its own risk.
Target cost
The target-cost contract sets a target cost and a rule by which the parties share the saving or the overrun. The PMBOK Guide asks that the contract define both clearly.
The FAR calls this mechanism a fixed-price incentive contract. It does not use "target cost" as the name of a type. At the outset the parties negotiate a target cost, a target profit, a price ceiling and a profit adjustment formula. When the final cost exceeds the target, the formula reduces the contractor's profit and can make it negative. Above the price ceiling the contractor absorbs the difference as a loss.
In the example, the contract sets a target cost of CHF 1'000'000, an equal split and a price ceiling of CHF 1'150'000. The calculation leaves out fees and margin. The actual cost reaches CHF 1'200'000. The formula splits the CHF 200'000 overrun: the client pays CHF 1'100'000 and the contractor absorbs CHF 100'000. The amount paid stays below the price ceiling. A real contract sets its own ratio.
Target cost = fixed price
Hybrids and recent forms
The PMBOK Guide allows hybrid contracts. They combine elements of fixed-price and cost-reimbursable or add other flexibility clauses. The PMBOK Guide also describes recent practices as adaptations of the fundamental types.
- Agile contract: agile principles applied to a fundamental type, for example a time-and-materials contract whose deliverables follow the iterations.
- Smart contract: a blockchain executes contract clauses automatically. These clauses usually settle milestone payments.
- Outcome-based contract: the price rests on measurable results rather than on the resources committed; the form applies to fixed-price and cost-reimbursable contracts.
- Sustainable contract: environmental, social and governance (ESG) criteria enter the contract.
- Collaborative contract: enhanced sharing of risk or reward within a fundamental type, for example a cost ceiling on a time-and-materials contract, a reduced rate or performance incentives.
In a 2008 post on the Scrum Inc. blog, Jeff Sutherland published the principles of the "Money for nothing" and "Change for free" clauses that a team on the Open Plans Agile Contract Project had agreed on. These clauses supplement the chosen type. Scrum calls each iteration a sprint. Under "Money for nothing", the client can end the contract at the end of any sprint. It then pays the contractor 20% of the remaining contract value. Sutherland reserves this clause for a client that takes part in the Scrum team. Under "Change for free", the client can replace scope items between two sprints with a new feature of the same size at no extra cost.
In Switzerland, Wolfgang Straub takes up both principles in an article in the journal Jusletter (2015). He also describes the agile fixed price ("agiler Festpreis"), which he takes from a book by Opelt, Gloger, Pfarl and Mittermayr. The parties describe the scope in broad terms. They break one representative epic down into user stories and estimate the whole project in story points. An epic groups user stories: each one describes a need from the user's point of view. A story point rates the effort and risk of a user story. During a trial phase of two to five sprints, the parties then estimate the team's velocity: the number of story points it completes per sprint. At the end of this phase, the parties set a binding framework of deadlines and costs. They agree on a key for sharing extra cost and savings. This key works like the sharing ratio of a target cost.
The Swiss framework
The Code of Obligations (CO) governs the price in the work contract and the remuneration in the mandate. Its terms differ from the PMBOK Guide's.
The work contract obliges the contractor to produce a piece of work and the customer to pay for that work (art. 363 CO). Where the parties fix the price in advance as an exact amount, the contractor may not charge more, even if the work entailed more labour or greater expense than predicted (art. 373 para. 1). The customer pays the full price even where the work entailed less labour (para. 3).
The CO limits this transfer of risk. Where unforeseeable extraordinary circumstances prevent the work or seriously hinder it, the court may authorise an increase in the price or the termination of the contract (art. 373 para. 2).
Where the parties fixed no price in advance or only an approximate amount, the price is determined according to the value of the work and the contractor's expenses (art. 374). Where the estimate is exceeded by a disproportionate amount through no fault of the customer, the customer may withdraw from the contract (art. 375 para. 1).
The mandate covers the conduct of business or the provision of services (art. 394). Remuneration is payable where agreed or customary. Either party may revoke or terminate the mandate at any time. A party that does so at an inopportune juncture compensates the other for the resulting damage (art. 404).
Art. 373 corresponds to the PMBOK Guide's fixed price. A service billed by the time spent often falls under the mandate or an innominate contract. No official text maps the PMBOK Guide's types to the articles of the CO. The classification depends on the facts and decides which rules apply, including the right to revoke a mandate at any time. The project manager leaves it to a lawyer.
For an agile project, Straub argues that the method does not decide the classification. The subject of the service and the intention of the parties decide it. In his view, an agile project can fall under the work contract. The work must be determinable without being described in detail: on acceptance, the customer checks that it conforms. The agile process specifies its content during the project. The work contract also allows a price set by the value of the work (art. 374). This classification dates from 2015.
The general terms and conditions (GTC) of the Confederation provide two forms of remuneration: fixed prices or a time and material basis with a cost ceiling (GTC for IT services, clause 15.1; GTC for service contracts, clause 7.1). For a federal office, the HERMES tender documentation contains these GTC: they set the possible forms of remuneration.
For cantons and communes, Digital Public Services Switzerland (DPSS) publishes the General terms and conditions for ICT goods/services. The 2025 edition applies to contracts concluded from 17 March 2025. It provides the same two forms of remuneration (clause 13.1). A contractor that bills on a time and material basis submits a signed report and remains bound by the cost ceiling (clause 13.2). Neither these GTC nor those of the Confederation contain a clause specific to agile projects.
A federal office procures under the Federal Act on Public Procurement (PPA). A cantonal buyer applies the 2019 Intercantonal Agreement on Public Procurement (IVöB) once its canton has joined it. Both texts lay down the same rules in art. 11 let. d, art. 24 paras. 1 to 5, art. 25 and art. 39.
The contracting authority holds no bidding rounds to push the price down (art. 11 let. d PPA). For complex contracts, intellectual services or innovative goods, work or services, it may conduct a dialogue with the tenderers in an open or selective procedure (art. 24 para. 1). In the dialogue, the contracting authority and the tenderers specify the subject of the procurement and define the solutions or procedures. The dialogue may not serve to negotiate prices (para. 2). The contracting authority announces the dialogue in the invitation to tender (para. 1). It also states the process, any compensation for taking part and the deadlines for the final tender (para. 3).
The contracting authority may adjust the tenders with the tenderers (art. 39 para. 1). Both texts allow the same two grounds. The first applies when adjustment is the only way to clarify the contract or the tenders or to make the tenders comparable (para. 2 let. a). The second is a change to the goods, work or services that is objectively necessary (let. b). A call for price adjustments is permitted only in these cases (para. 3).
The contracting authority therefore sets the form of remuneration in the tender documentation. After the tenders arrive, it cannot change it through negotiation. According to the Federal Council's dispatch on the PPA, a tenderer that only chooses another form of remuneration does not submit a variant (art. 33). Its tender does not comply with the invitation to tender. The exception is an invitation to tender that leaves the choice of the form of remuneration to the tenderer.
A framework agreement sets the terms of the goods, work or services for a given period, in particular their price and, where appropriate, the quantities envisaged (art. 25 para. 1). Individual contracts implement it. They take over the form of remuneration that the framework agreement sets.
Among the award criteria, the PPA lists the reliability of the price, the innovation content and the efficiency of the methodology (art. 29 para. 1). The IVöB does not list the reliability of the price. When the procurement concerns solutions, possible solutions or procedures, both texts allow the contracting authority to omit the weighting of the criteria (para. 3). An agile purchase can meet the condition of para. 3: the client and the contractor specify its content during the project.
Choosing a type
Steps 1 to 4 put what the PMBOK Guide describes and the FAR mechanism into a sequence. Steps 5 to 7 come from practice.
- Assess the scope. The project manager establishes what the documentation describes precisely and what remains uncertain. The PMBOK Guide links fixed-price to work that can be estimated accurately and cost-reimbursable to uncertain scope.
- Take both points of view. For each candidate type, the project manager writes down what the client risks and what the contractor risks. A contractor doing the same exercise prices the risk premium of its fixed-price offer.
- Select a type or a hybrid. The project manager can split the purchase into lots: a fixed price for the described part and time and materials with a cost ceiling for the uncertain part.
- Set the sharing rule. For a target cost, the project manager sets the target, the ratio and the price ceiling. For time and materials, they set the cost ceiling. They calculate each party's share on a saving and on an overrun.
- Have the contract classified. A lawyer checks the classification under the CO and the price clauses.
- Record the choice. The project manager records the type in the draft contract of the tender documentation and then in the agreement. They tie payments to contract milestones and write the justification note. In public procurement, the agreement takes over the type that the tender documentation sets. The tenderer can change it in its tender only if the documentation leaves it the choice of type.
- Monitor and review. Time and materials requires a record of hours and materials throughout the contract. At renewal, the project manager reviews the type. The FAR calls for avoiding protracted use of cost-reimbursement or time and materials once experience provides a basis for firmer pricing.
The US Department of Defense handbook MIL-HDBK-245D (1996) guides the drafting of the work order (statement of work, SOW). This guide shows how to describe the work that step 1 assesses. The SOW states which results the client expects and leaves the choice of method to the contractor. It expresses the requirements in specific, quantitative and performance-based terms. According to the handbook, precisely stated requirements let both parties negotiate a fair price. The SOW then becomes the standard against which the client measures the contractor's performance. In the statement of objectives (SOO) variant, the client replaces its SOW with a statement of its objectives in the tender documentation. Each tenderer writes its own SOW and attaches it to its tender.
In a HERMES project
In HERMES, the task "Prepare procurement analysis" produces the Procurement analysis outcome. Its content includes the "forms of contract". The tender documentation contains the draft contract and the general terms and conditions of the core organisation. In public procurement, it therefore sets the form of remuneration.
At the Contract award milestone, the project sponsor decides on the contract award. The contract work with the successful tenderer can then begin. The Agreement outcome governs the cooperation between the project sponsor and the developer. HERMES distinguishes two kinds: the project agreement and the contract. Its contents include effort and costs, quality assurance and acceptance, warranty and change management.
In HERMES, agile delivery is confined to the Execution phase. The HERMES Leitfaden Agilität (2026 edition) contains a decision aid for choosing between the traditional and the agile approach. Two of its criteria touch on the contract. The criterion "Lieferant / Integrator" (supplier or integrator) asks whether the supplier works with traditional or agile development methods. Under the criterion "Variabilität" (variability), the traditional approach focuses on scope: a change affects resources and time first. The agile approach focuses on time and resources: a change affects scope first.
Pitfalls
A fixed price on a vague scope
The contractor covers the unknown with a premium or with change requests. Either way, the client pays for the uncertainty and loses the predictability it was looking for. A fixed price holds when the documentation describes the scope well enough for a contractor to price it.
Time and materials without a cost ceiling or a record
Without a cost ceiling and without a record of hours, the client discovers the overrun on the invoice. The contract sets the cost ceiling, how often the record is produced and who approves it.
A target cost without a quantified formula
If the contract quantifies neither the target nor the ratio, the parties negotiate each party's share at the moment of the overrun. That is when their interests diverge most. The contract writes out the formula and adds a worked example.
A type kept too long
The team chooses time and materials because it cannot yet estimate the work. The contract stays in place after the team has learnt to estimate the work. At renewal, the project manager moves to a fixed price or a target cost.
A single point of view
A client who drafts the contract from its own point of view alone transfers all the risk and pays the premium. A contractor who does the same looks for the clause to exploit.
AI considerations
The PMBOK Guide reports that AI-powered contract analysis tools refine risk assessment. It adds that machine learning predicts cost overruns from historical project data.
A language model extracts the price clauses from a draft contract or an offer: rate, cost ceiling, target, price ceiling, sharing ratio, milestone payments. It writes the spreadsheet formulas that calculate each party's share for several final costs. It flags a clause that contradicts the type the contract or offer declares, for example a fixed price that bills overtime.
The project manager tests the formula before using it: on the case calculated by hand (CHF 1'100'000 for an actual cost of CHF 1'200'000) and on an actual cost of CHF 1'400'000. At that cost, the client pays the price ceiling of CHF 1'150'000. A formula that leaves out the price ceiling gets the first case right and gives CHF 1'200'000 for the second.
The classification under the CO stays with the lawyer. An offer contains a tenderer's prices and trade secrets. The buyer enters it only into an AI service that the buyer's organisation has authorised.
Examples
The justification note compares the candidate types from both points of view and reaches a conclusion. A cantonal office commissions a portal for study grant applications. The specifications describe the portal. The interface with the cantonal taxpayer register has yet to be specified.
| Candidate type | Client side (the office) | Contractor side | Verdict |
|---|---|---|---|
| Fixed price for the whole lot | Known budget. The offer contains a premium for the unknown interface. | Bears any overrun on the interface. | Rejected: the premium pays for an uncertainty that the office can remove. |
| Cost-reimbursable for the whole lot | Pays any overrun on the portal and on the interface alike. Checks every cost. | No cost risk. Limited profit. | Rejected: the portal is described and can be priced. |
| Target cost for the whole lot | Shares savings and overruns. Must set a target for an interface that nobody has costed. | Incentive to be efficient. Bears part of an overrun it cannot estimate. | Rejected: the target for the interface would be a guess. |
| Time and materials with a cost ceiling for the whole lot | Pays for the portal and the interface by the time spent up to the cost ceiling. | Covered up to the cost ceiling. Bears what exceeds it. | Rejected: the portal is described; time and materials would pay by the hour for work that a fixed price can cover. |
| Fixed price for the portal and time and materials with a cost ceiling for the interface | Known budget for the portal. Interface at CHF 160 an hour, cost ceiling of CHF 96'000 (600 hours), monthly record. | Covered on the interface up to the cost ceiling. Bears the overrun on the portal and whatever exceeds the cost ceiling. | Selected. After the interface, the office reviews the type for maintenance. |
The selected row is a hybrid: the office splits the lot where the uncertainty changes.
Visualisations
The cost ceiling moves time and materials towards the contractor. The sharing ratio positions a target cost.
Cost
| Phase | Level | Justification |
|---|---|---|
| Preparation | Medium | Describe the scope, isolate what remains uncertain, bring together the project manager, the buyer and the lawyer. |
| Execution | Medium | Read each candidate from both points of view, calculate each party's share for several final costs, have the legal classification checked. |
| Documentation | Low | A justification note of one to two pages and the price clauses of the draft contract. |
Tooling
A spreadsheet is enough for the justification note and for calculating the split: one row per candidate type, one column per final cost and each party's share in the cells.
The PMBOK Guide counts contract templates (fixed-price, cost-reimbursable and T&M) among the organisational process assets. An in-house template spares the buyer from rewriting the price clauses for every purchase.
During execution, contract management software or the project spreadsheet tracks the ceilings, the hours consumed and the payment dates.
Sources
- PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed., Appendix X4, §X4.8 Contract Type: the definition, the dual perspective of client and contractor and the goal of a contract that benefits both parties. §X4.8.1 Fundamental Contract Models: the four models, their uses, the two perspectives, the variation of names across industries, the hybrids. §X4.8.2 Emerging Trends in Contract Management: the recent forms and the observation on AI. §2.4.3 Tailoring Considerations: the choice of contract type in the procurement strategy. Section 2.2.3: contract templates among the organisational process assets.
- Swiss Confederation, Swiss Code of Obligations (SR 220): fedlex.admin.ch. Art. 363 (work contract), art. 373 (firm commitment), art. 374 (price by the value of the work), art. 375 (withdrawal because estimate exceeded), art. 394 (mandate) and art. 404 (revocation and termination of the mandate).
- Swiss Confederation, Federal Act on Public Procurement (PPA, SR 172.056.1): fedlex.admin.ch. Art. 11 let. d (no bidding rounds), art. 24 (dialogue), art. 25 (framework agreements), art. 29 (award criteria), art. 33 (variants) and art. 39 (adjustment of tenders).
- Schweizerische Bau-, Planungs- und Umweltdirektoren-Konferenz (BPUK), Interkantonale Vereinbarung über das öffentliche Beschaffungswesen (IVöB) of 15 November 2019 (German text). Art. 11 let. d, art. 24 paras. 1 to 5, art. 25 and art. 39 (same rules as the PPA). Art. 29 (award criteria without the reliability of the price).
- Swiss Federal Council, Dispatch of 15 February 2017 on the total revision of the Federal Act on Public Procurement, BBl 2017 1851 (German text). Commentary on art. 33: another price type does not make a variant; the contracting authority can leave the choice of price type to the tenderer. Federal Office for Buildings and Logistics (FOBL), Kompetenzzentrum Beschaffungswesen Bund (KBB) and Rechtsdienst BBL, Merkblatt Varianten, status as at 19 August 2020 (German text): same rule.
- Federal Procurement Conference (FPC), General terms and conditions for IT services, status as at January 2024, clause 15.1 (fixed prices or time and material basis with a cost ceiling). General terms and conditions of the Confederation for service contracts, status as at January 2024, clause 7.1 (time and material basis with a cost ceiling or fixed prices).
- Digital Public Services Switzerland (DPSS), General terms and conditions for ICT goods/services, March 2025 edition. It applies to contracts concluded from 17 March 2025. Clause 13.1 (fixed prices or time and material basis with a cost ceiling) and clause 13.2 (signed report, binding cost ceiling).
- US General Services Administration et al., Federal Acquisition Regulation, Part 16 Types of Contracts: acquisition.gov/far/part-16. §16.103 (choice of type, justification documentation, move to firmer pricing), §16.202-1 (firm fixed price), §16.301-1 (cost-reimbursement), §16.403-1 (fixed-price incentive: target, target profit, price ceiling, formula), §16.601 (time and materials: hourly rates, surveillance, ceiling). The FAR governs US federal public procurement. It documents the pricing mechanisms.
- US Department of Defense, Department of Defense Handbook for Preparation of Statement of Work (SOW), MIL-HDBK-245D, 3 April 1996. §1.1 (fair price), §1.2 (standard for judging performance), §3.1 (quantitative requirements), §3.3 and §3.6.4 (results rather than method), section 5 (statement of objectives).
- Swiss Confederation, Federal Chancellery, HERMES 2022: outcome Agreement (project agreement and contract, contents); outcome Tender documentation (draft contract, general terms and conditions); task Prepare procurement analysis; outcome Procurement analysis (forms of contract); outcome Contract award milestone (the sponsor's decision). HERMES Reference Manual – Project management, 2022 edition, 3rd printing (revised), 9 March 2026, section 4.4.1.9 Procurement analysis (p. 51): the content item "forms of contract".
- Swiss Confederation, Federal Chancellery, HERMES Leitfaden Agilität, 2026 edition (German text; no English edition). Section 2.2 "Entscheidungshilfe" (decision aid), criteria "Lieferant / Integrator" and "Variabilität".
- Jeff Sutherland, Agile Contracts: Money for Nothing and Your Change for Free, Scrum Inc. blog, 25 October 2008 (Internet Archive copy). The post publishes the principles of the "Money for nothing" and "Change for free" clauses that the Open Plans Agile Contract Project team had agreed on.
- Wolfgang Straub, Verträge für agil geführte Projekte, Jusletter, 21 December 2015 (German text). Margin nos. 47 to 57 (agile fixed price, "Money for nothing", "Change for free"), margin nos. 61 and 78 (classification of an agile contract under Swiss law). The article predates the 2019 PPA.

