Contract Law Basics
Legal Aspects of Technology Management - NIT Northern Institute of Technology Management, Hamburg · part of my Technology Management MBA · study notes for revision.
The section on contract law does not open with a definition. It opens with a situation, and the situation is deliberately chosen so that two problems arrive at the same time. A German company wants a new manufacturing execution system. The best provider on the market happens to sit in Israel. The two of them want to build something new together. What contract does that need, and what has to be inside it?
Both halves of that question are the syllabus. The second half is answered on the spot, with a twenty-point checklist for a research and development cooperation agreement that runs across five slides and is by far the densest thing in the session. The first half - which country’s law even applies to a German company and an Israeli company building something together - is not answered here at all. It is the reason the very next section of the deck is called Introduction to International Law.
So this chapter does two jobs. It sets out what a contract is according to the classification the earlier slides had already built, so that the checklist stops looking like an arbitrary shopping list and starts looking like the structure it actually is. Then it walks the checklist point by point, in the order the deck gives it.
1 · A contract is law that the parties write for themselves
Section titled “1 · A contract is law that the parties write for themselves”The slides just before this section had already sorted law into three kinds by asking who makes it. That list is the doorway into contract law, because contracts are the third entry on it.
The same slides also gave the raw material that norms are made of. In civil law the types of norms are rights, in the sense of claim bases, definitions, and legal consequences such as liability. And a claim base has a fixed logical shape:
This is the most useful thing in the section for reading a contract quickly, because it tells you what to look for. A clause that names conditions and attaches a consequence to them is a claim base: satisfy the conditions and you may demand the consequence. A clause that only describes something is a definition, and definitions on their own give nobody the right to demand anything. That is also the honest way to tell a binding commitment from a warm sentence about intentions. If a paragraph creates no claim base, there is nothing in it to enforce, however cooperative it sounds.
2 · Why the type of contract decides how much you have to write
Section titled “2 · Why the type of contract decides how much you have to write”One slide earlier the deck had asked what a set of quoted rules from purchase law actually mean. The first of them describes a sale in a single sentence: the purchase contract obliges the seller to hand over the object to the buyer and to procure ownership of it, and it obliges the buyer to pay the agreed purchase price and to accept the purchased item. Two parties, two duties each, and a complete contract.
The detail worth noticing is where that sentence comes from. It is a statutory provision, not a clause somebody negotiated. For an ordinary sale the law has already written the core of the deal, so a short order form is enough and the statute silently fills in the rest. Hold that against the case in the next section and the contrast explains the whole checklist.
- The main obligations already exist in the law: hand over the object, procure ownership, pay the price, accept the item
- The object is defined and finished before anybody signs
- What is owed can be checked by looking at the thing
- A thin document is workable, because the gaps are filled by statute
- No off-the-shelf statutory template describes what two companies innovating together owe one another
- The object does not exist yet, so it has to be specified in writing before it can be owed
- What counts as good enough has to be defined in advance or it cannot be judged later
- Everything unwritten is genuinely missing, which is why the deck answers with twenty points
3 · The case the section opens with
Section titled “3 · The case the section opens with”The scenario is short and every element in it is doing work.
The two questions put to the class are what kind of contract is needed and what elements does such a contract contain. The answer to the first is given by the title of the next five slides: a cooperation agreement for research and development. The answer to the second is the checklist itself.
4 · The twenty points at a glance
Section titled “4 · The twenty points at a glance”The checklist runs from 1 to 20, with sub-points under 4, 5, 6 and 7. It is easier to hold in your head if you group it, so here it is sorted into families before the walkthrough. The numbers are the deck’s own.
5 · Points 1 to 3: the foundations
Section titled “5 · Points 1 to 3: the foundations”1. Basis of the contract. The opening section names the parties, describes the project, and states in keywords the objectives to be achieved by the project. It is worth noticing that objectives go into the contract, not just into a slide deck. Once an objective is written into the basis of the contract it stops being an aspiration and becomes something the document can be read against.
2. Subject matter and elements of the contract. What the agreement is actually about, and what it is made of.
3. Contract components and ranking. A cooperation agreement of this kind is never one document. There are attachments, service certificates and similar papers, and the checklist asks not only that they be listed but that they be ranked. Ranking means deciding in advance which document wins when two of them say different things. This is one of those clauses nobody reads until the day it decides an argument, and then it decides it completely.
6 · Point 4: the joint development and what each side owes
Section titled “6 · Point 4: the joint development and what each side owes”Point 4 asks the plain question what should be worked on, and then breaks into ten sub-points. This is the operational heart of the agreement.
| Sub-point | What it covers | Why it earns its place |
|---|---|---|
| 4.1 General information | The framing of the joint development work | Sets the scope everything else is measured against |
| 4.2 Preparation and updating of the requirements specification | Writing the specification, and keeping it current as the project moves | In a development project the specification is the thing that is actually owed, so it needs a process, not a one-off document |
| 4.3 Obligations of the parties | What each side commits to do | The clause that turns a cooperation into a set of claim bases |
| 4.4 Training and workshops | Knowledge transfer between the partners | A joint build only works if both sides can operate what is built |
| 4.5 Official authorisations and notifications to public authorities | Permits and filings that the work requires | Someone has to own this or it is discovered late |
| 4.6 Compliance with internal guidelines | Marked in the checklist as optional | Company policies that the partner may or may not be asked to follow |
| 4.7 Safety and quality standards | The standards the work must meet | Feeds directly into what counts as a deficiency under point 7 |
| 4.8 Places of performance | Where the work is performed | Matters practically and, in a cross-border deal, legally |
| 4.9 Exclusivity | Whether either side may do the same thing with somebody else | In an innovative development this is often the commercially decisive line |
| 4.10 Use of the services by affiliated companies or service providers | Whether group companies and subcontractors may be brought in or may benefit | Decides how far the deal reaches beyond the two signatures |
Sub-point 4.3 is the one to underline. The purchase-law quotation in section 2 showed a statute handing both parties their obligations ready-made. Here the parties have to write their own, and that clause is what the whole rest of the checklist hangs off: you cannot be in delay, in breach, or liable for anything you were never obliged to do.
7 · Points 5 and 6: the schedule and the project machinery
Section titled “7 · Points 5 and 6: the schedule and the project machinery”5. Schedules for the project phase. Seven sub-points, and they are arranged as an escalation.
6. Project management and project controlling. Four sub-points: 6.1 project preparation, 6.2 risk and quality control, 6.3 project organization and 6.4 project controlling. This is the part of the contract that reads like a project management textbook, and that is the point. In a joint development the governance is part of what is owed. Who sits in which body, how risk and quality are monitored, and how progress is measured are contractual questions, not merely operational ones.
8 · Point 7: performance deficiencies and the remedy ladder
Section titled “8 · Point 7: performance deficiencies and the remedy ladder”This is the section to know cold, because it is the deck’s answer to what happens when a party does not deliver what it promised. Six sub-points, and they run in a deliberate order.
Three observations that are worth carrying into an exam answer.
First, 7.1 comes first for a reason. The contractually owed quality, the service level, has to be defined in the contract. Without it there is no benchmark, so there is no such thing as a deficiency, so none of the five sub-points beneath it can ever be triggered. Everything downstream depends on that one definition.
Second, the ladder escalates in a recognisable pattern: fix it, then pay for it, then leave. Correction and catching up keep the contract alive and try to get the promised result. Reduction of remuneration and the contractual penalty accept that the result will not be perfect and adjust the price instead. Withdrawal gives up on the contract. A well-drafted clause makes you climb the ladder rather than jump to the top of it.
Third, the contractual penalty and withdrawal appear twice in the checklist, once at 5.7 for being late and once at 7.4 and 7.5 for delivering badly. Time and quality are two independent ways of failing, and each gets its own route to the same two sanctions.
8. Functional tests, user tests and approval. The counterpart of point 7. Tests and formal approval are the moment at which the parties establish whether the service level in 7.1 has actually been met, so this is where the deficiency machinery is switched on or, ideally, never needed.
9 · Points 9 to 13: running the relationship
Section titled “9 · Points 9 to 13: running the relationship”| Point | What it is | The point of having it |
|---|---|---|
| 9 Mutual cooperation | The duties each side owes the other simply to make the joint work possible | In a development project one side can stall the other just by being unavailable, and this clause makes that a contractual issue |
| 10 Change requests | A procedure for changing what is being built | Innovative development changes by definition, so the contract needs a legitimate route for that instead of an argument |
| 11 Dispute settlement procedure | How disagreements are handled | Agreed in advance, while both sides are still friendly |
| 12 Remuneration and terms of payment | What is paid, and when | The main obligation on the paying side |
| 13 Documentations | What has to be documented and handed over | In a technology project the documentation is often what makes the deliverable usable at all |
Points 10 and 5.4 are worth reading together. Point 5.4 governs changes to the timetable and point 10 governs changes to the content, and in real projects a change request usually produces both, which is why the two clauses need to fit each other.
10 · Points 14 to 18: rights, secrets and things nobody controls
Section titled “10 · Points 14 to 18: rights, secrets and things nobody controls”14. Intellectual property rights and infringements. In a joint innovative development this is the point of the exercise. The clause has to say who owns what is created and what happens if the work infringes somebody else’s rights.
15. Secrecy. Two companies developing together necessarily see each other’s confidential material.
16. Liability. Who bears which loss, and up to what limit.
17. Insurance cover. The commercial backstop behind the liability clause, so that a liability that is agreed on paper is also one the other party could actually pay.
18. Force majeure. The events outside anybody’s control, and what they do to the obligations. This is the clause that answers whether a party that cannot perform because of such an event is nevertheless in breach.
- Ownership and rights of use in what the joint development produces
- What happens if the work infringes a third party’s rights
- Protection of the confidential material each side sees while working together
- Allocation of liability between the parties
- Insurance cover standing behind that allocation
- What happens to the obligations when performance is prevented by something outside either party’s control
11 · Points 19 and 20: ending it, and whose law decides
Section titled “11 · Points 19 and 20: ending it, and whose law decides”19. Term, termination. How long the agreement lasts and how it can be brought to an end. The checklist pairs the two words, which is the right way to think about it: the term says when the contract ends by itself, and termination says how a party can end it earlier.
20. Applicable law, that is choice of law, and place of jurisdiction. The last point on the list, and the bridge to the rest of the session. Two questions hide inside it and they are genuinely separate. Choice of law asks which country’s rules are used to decide what the contract means. Place of jurisdiction asks which country’s courts hear the case. A German company and an Israeli company have to settle both, and the fact that this is the closing item of the drafting checklist is exactly why the deck moves straight from here into international law.
Worked example
Section titled “Worked example”Take the deck’s own scenario and make it concrete. The German manufacturer needs a manufacturing execution system for its plant. The Israeli provider is the strongest in that field. They agree to build a new one together under a cooperation agreement for research and development.
The formation sequence below is ordinary commercial practice rather than a rule from these slides, which do not cover formation. What the checklist does tell you is what has to be inside the document once the parties reach step 4.
What each side owes. The provider owes the joint development work described in point 4: a requirements specification kept up to date under 4.2, the obligations it accepted under 4.3, training and workshops under 4.4, work meeting the safety and quality standards under 4.7, and delivery against the milestone concept under 5.2. The German company owes remuneration on the payment terms of point 12, the cooperation duties of point 9, and the participation in tests and approval under point 8.
Something goes wrong. Milestone three, the interface between the new system and the existing plant equipment, is delivered six weeks late and, when it is finally tested, it processes machine data more slowly than the agreed service level. Two separate failures, one of time and one of quality, which is exactly the split the checklist anticipates.
| The failure | Which clause governs it | The route the checklist gives |
|---|---|---|
| Milestone three is six weeks late | 5.6 delay with individual project steps and milestones | Establish it is a delay, not a legitimate timetable change under 5.4, then 5.7 contractual penalty and, if serious enough, withdrawal |
| The interface is slower than promised | 7.1 contractually owed quality, the service level | Measure against the service level defined in the contract, then work up point 7 |
| First response to the slow interface | 7.2 correction of the deficiency in performance | The provider is asked to put it right |
| The correction itself drags | 7.3 catching up and self-execution | Either the provider makes the work good, or the customer has the work done instead of waiting |
| Correction fails or is not worth waiting for | 7.4 reduction of remuneration or contractual penalty | Pay less for what was actually delivered, or apply the agreed penalty |
| The deliverable is unusable | 7.5 withdrawal and other rights | Exit the contract |
| Anything above, raised too late | 7.6 statute of limitations | The rights have expired and none of the rows above are available any more |
How it ends. If the parties work through the ladder and settle, the agreement runs to the end of its term under point 19 and any dispute along the way goes through the procedure in point 11. If they do not settle, point 20 decides whose law is applied to all of the above and which courts hear it, and the answer to that has nothing to do with who was right.
Apply it to your project
Section titled “Apply it to your project”-
Ask first whether the deal has a statutory template. If you are simply buying a finished thing, the law already supplies the main obligations, as the purchase-law quotation shows. If you are building something jointly, nothing is supplied and every obligation has to be written by you.
-
Find the claim bases. Read the document and mark every clause that names conditions and attaches a consequence to them. That is the a plus b plus c equals d shape. Clauses that only describe things are definitions, and they give you nothing to demand.
-
Check point 1 and point 2. Are the parties correctly named, is the project described, and are the objectives written into the contract rather than only into a presentation?
-
Rank your documents. List every attachment, annex and certificate and state which one prevails over which. Do this while nobody is arguing.
-
Find the obligations clause, 4.3. If you cannot point at the sentence that says what each side must do, you do not yet have obligations, and nothing downstream in the checklist can be triggered.
-
Look for the service level, 7.1. If the contractually owed quality is nowhere defined, you have no way to call anything defective, and the entire remedy ladder is unusable.
-
Trace your remedy ladder. Confirm the document actually contains correction, catching up and self-execution, reduction or penalty, and withdrawal, and check the limitation period so you know how long these rights survive.
-
Trace the time ladder separately. Milestones under 5.2, what counts as a deviation under 5.3, how the timetable may legitimately be changed under 5.4, and the penalty and withdrawal at 5.7.
-
Confirm the four clauses people forget. Intellectual property and infringement under 14, secrecy under 15, liability and its insurance backstop under 16 and 17, and force majeure under 18.
-
Read the last two points before you sign. Term and termination under 19, and choice of law together with place of jurisdiction under 20. In a cross-border deal these two decide the value of everything above them.
Key terms
Section titled “Key terms”| Term | What it means in plain words |
|---|---|
| Contract | Law made by natural or legal entities for themselves, sitting alongside statutory law and case law but binding only the parties to it |
| Statutory law | Law made by parliament as the legislative authority |
| Case law | Law that grows out of judgements, as the judicial authority develops the law further |
| Claim base | A norm shaped as requirement plus requirement plus requirement equals legal consequence, which is what lets one side demand something from the other |
| Legal consequence | What follows once the requirements of a claim base are met, for example liability |
| Cooperation agreement | The contract type the deck names for two companies developing something innovative together, here in a research and development setting |
| Contract components and ranking | The list of attachments, service certificates and other papers that form part of the contract, plus the order of precedence deciding which one wins in a conflict |
| Requirements specification | The written statement of what is to be built, which the checklist wants prepared and then kept updated |
| Obligations of the parties | The clause where each side’s duties are actually written down, since a joint development has no statutory template to supply them |
| Exclusivity | Whether a party may do the same work with somebody else |
| Milestone concept | The breaking of the project plan into named checkpoints, against which delay is then measured |
| Service level | The contractually owed quality, defined in advance, without which nothing can be called deficient |
| Self-execution | The remedy where the deficient work is carried out instead of waiting further for the party that owed it |
| Reduction of remuneration | Paying less because what was delivered fell short of what was owed |
| Contractual penalty | A sanction agreed in advance, triggered in the checklist both by delay and by deficient performance |
| Withdrawal | Getting out of the contract, the top of the remedy ladder and also the endpoint of the delay ladder |
| Statute of limitations | The period after which the rights arising from a deficiency can no longer be used |
| Force majeure | Events outside either party’s control, and the clause saying what they do to the obligations |
| Choice of law | The agreement on which country’s law is applied to the contract |
| Place of jurisdiction | The agreement on which country’s courts decide a dispute, a separate question from choice of law |
Test yourself
Section titled “Test yourself”- Name the three kinds of law the deck lists, say who makes each, and explain what is unusual about the third one appearing on the same list as the other two.
- Give the logical structure of a claim base, and explain how it helps you tell an enforceable clause from a merely descriptive one.
- Describe the scenario that opens the contract law section, state the two questions put to the class, and say which of them the section actually answers.
- Using the purchase-law quotation, state the obligations of the seller and of the buyer, and explain why a joint development needs a far longer contract than a sale does.
- List the six sub-points of the performance deficiencies section in order, and explain why the first one has to come first.
- The checklist mentions contractual penalty and withdrawal twice. Where, and why twice?
Revision summary
Section titled “Revision summary”Next: Cross-Border Trade → - whose law applies when the parties sit in different countries.