A contract template should be selected because it fits the work, not because it is the document the organisation knows best.
The Week 7 presentation identifies several agreement types: specific scope of service, minor works, professional services, training or technical support, scheduled maintenance, contract orders and general supply of goods and services. The legal-precedent guidance then adds an important control: the transaction should be assessed before a preferred template is selected, and unusual or higher-risk arrangements should be escalated for commercial or legal review.
This produces a simple but powerful governance principle:
Contract type should follow delivery reality.
The Strategic Context
Organisations standardise contracts because repeated legal drafting is slow, expensive and inconsistent.
That standardisation is valuable.
The problem begins when a standard form becomes the default answer to different commercial problems.
A professional-services engagement depends heavily on expertise, intellectual output and advice. Minor works may involve site access, materials, safety and interaction with the customer's employees. Scheduled maintenance requires recurring service obligations and operational records. Training may need outcome measures and participant responsibilities.
Using the same generic agreement for all of them can either leave material risks unmanaged or burden simple transactions with unnecessary clauses.
What Leaders Commonly Misread
The first mistake is choosing a contract based only on value.
Contract value matters, but consequence of failure, complexity and dependency may matter more.
The second is assuming a short form is automatically proportionate.
A short agreement that omits critical obligations can create more dispute risk than a longer form that reflects the transaction clearly.
The third is using legal precedent without checking whether the underlying business model has changed.
The fourth is asking legal teams to “make the template fit” after procurement has already committed to a sourcing structure.
Reframing the Issue
Contract selection should be treated as a risk-and-delivery architecture decision.
The question is:
What does the supplier have to do, and what must the contract control for that work to succeed?
For a defined service, the core issue may be scope and acceptance.
For minor works, site coordination and materials may matter.
For professional services, capability, reliance, IP and deliverables may dominate.
For scheduled maintenance, response, records, availability and recurring obligations become central.
Strategic Analysis
Consider a hypothetical engineering organisation with three external needs.
First, it needs a specialist consultant to review a pressure-vessel design.
Second, it needs a contractor to relocate a small production machine.
Third, it needs a provider to service lifting equipment every quarter for three years.
A generic “supply of goods and services” agreement might technically cover all three.
But the delivery system differs.
The consultant provides professional judgement. The relocation contractor works physically on site and interfaces with production. The maintenance provider has recurring obligations and creates an operating record over time.
The contract should reflect those differences.
The Week 7 source correctly treats templates as a starting point, not a substitute for commercial judgement.
Executive Trade-offs
There is an unavoidable trade-off between standardisation and fit. Too many contract forms create confusion, training cost and inconsistent governance. Too few forms force materially different transactions into the same architecture.
A practical contract library should therefore cover the recurring patterns of work, not every conceivable category. The organisation might maintain a small number of well-governed forms with modular schedules for specialist issues such as data, site safety, intellectual property or service levels.
This approach preserves repeatability while allowing the contract to follow the real delivery system. It also makes legal resources more productive: specialists can focus on unusual risk rather than repeatedly rebuilding routine agreements.
The strongest measure of a contract library is not how many forms exist. It is whether users can select the right form quickly, understand its boundaries and recognise when the transaction no longer fits.
Decision Framework
Select the contract model against six criteria.
Scope stability
Is the work clearly defined or likely to evolve?
Delivery environment
Does performance occur on the customer's site or inside its operating system?
Professional reliance
Is the organisation relying on specialist judgement or advice?
Recurrence
Is the work one-off, call-off or ongoing?
Asset and material exposure
Who controls equipment, consumables or customer-furnished materials?
Consequence
What happens if the supplier performs badly?
These factors should influence contract selection before legal drafting begins.
From Strategy to Execution
Immediate action: create a simple contract-selection matrix linked to procurement strategy.
Medium-term capability building: define when procurement teams may use standard forms independently and when commercial or legal review is mandatory.
Long-term strategic positioning: use contract-performance data to improve the template library. Repeated disputes around the same clause or transaction type should trigger redesign rather than repeated negotiation.
Templates should evolve with operating reality.
Governance Implication
The contract-selection decision should be recorded with enough reasoning that another project can understand why the form was chosen. This is especially useful where a transaction sits near the boundary between categories, such as maintenance that includes significant modification work or professional services that create operational software. A short rationale prevents the template library becoming a menu selected by habit.
Signals to Monitor
Watch for one template being used across almost every category, heavy legal redlining after supplier selection, repeated clauses marked “not applicable”, project teams unable to explain why a particular form was chosen and simple contracts taking longer to negotiate than complex ones because the starting form is poorly matched.
Questions for the Leadership Team
- What delivery risk is this contract type designed to control?
- Are we selecting the form because it fits the work or because it is familiar?
- Which obligations are unique to this transaction?
- Does the supplier operate inside our site, systems or decision processes?
- What level of legal or commercial review is proportionate?
- Which recurring disputes indicate that our standard forms need redesign?
Closing Perspective
A contract form is not merely paperwork surrounding procurement.
It is the operating structure through which responsibilities, interfaces and risk become enforceable.
The right template reduces friction because it starts from the right commercial assumptions.
Related article: Legal Precedent Is a Control System, Not a Copy-and-Paste Shortcut
Related article: Match Contract Complexity to System Complexity: From Short-Form Services to Whole-of-Life Project Agreements
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.