Security protects the principal against failure, but the cost of that protection eventually enters the commercial system.
Performance bonds, bank guarantees, retention and parent-company guarantees are often treated as standard contract requirements. The Week 11 material presents them as mechanisms intended to secure contractor performance, and the supplied AS 4000—1997 historically provides for several forms of security, including cash, retention moneys and approved unconditional undertakings.
The 2003 performance-bond paper adds an important distinction between conditional and unconditional bonds. It also highlights that security affects both parties: the owner gains protection, while the contractor may face fees, collateral requirements and restrictions on working capital.
The strategic question is therefore not, “How much security can we demand?”
It is:
What protection does the project actually need, and what is the most efficient way to create it?
The Strategic Context
Security exists because contracts do not eliminate counterparty risk.
A contractor can default, become insolvent, fail to complete, refuse to rectify defects or leave the principal facing additional completion cost. Security gives the principal access to value that may be available when performance fails.
But different security mechanisms behave differently.
Retention withholds part of earned payments.
A bank guarantee or unconditional undertaking uses third-party financial support.
A parent-company guarantee relies on the strength of the wider corporate group.
A conditional bond may require proof of breach or loss before payment.
An unconditional or on-demand bond is designed to be much more readily accessible, subject to its terms and applicable law.
Each mechanism changes cost, liquidity, enforceability and leverage.
What Leaders Commonly Misread
The first mistake is assuming more security always means less risk.
Security can reduce loss severity, but it does not improve contractor capability, planning, quality or supervision.
The second is ignoring the contractor's cost of providing security.
Banks and insurers charge fees. Unconditional guarantees may consume credit lines or require collateral. Retention reduces contractor cash flow. These costs can ultimately influence tender price, supplier appetite or financial resilience.
The third is treating all bonds as equivalent.
The supplied 2003 paper distinguishes conditional, unconditional and hybrid structures and notes that wording determines how easily a beneficiary can call the security. That legal position is historical and jurisdiction-sensitive. Current Australian law must be verified before publication. [FACT CHECK REQUIRED]
The fourth mistake is viewing security only as a default remedy. Its design also affects bargaining power during disputes.
Reframing the Issue
Security should be designed as part of a continuity and loss-control architecture.
Leaders should first identify the exposure they are trying to protect:
- completion cost following contractor failure;
- defects not rectified;
- advance payments;
- off-site materials;
- performance during the defects period;
- subcontractor or supply-chain risk.
Only then should they decide the instrument, amount, reduction profile and release trigger.
This reverses the common approach of inserting a standard percentage and asking questions later.
Strategic Analysis
The supplied AS 4000—1997 uses annexure items to define security form, amount and release arrangements. It also historically provides for security reduction at practical completion and later release around final certification, subject to the contract particulars.
This illustrates a sound design principle: security should follow the changing risk profile of the project.
Risk is not constant.
Before work begins, the principal may be exposed to mobilisation or advance-payment risk.
During construction, completion exposure may be high.
At practical completion, the asset is substantially available, so the risk changes.
During the defects period, the remaining concern may be rectification rather than total completion.
Holding the same security throughout may therefore be commercially inefficient unless the risk justifies it.
The teaching material suggests common percentages for bonds and retention, but those figures are historical examples rather than universal current practice. [FACT CHECK REQUIRED]
Supplier Economics
Security design can affect market quality.
A highly capable contractor with a strong balance sheet may absorb the requirement easily. A smaller specialist may face disproportionate pressure on banking capacity.
If the principal demands high unconditional security from every supplier regardless of scope, the policy can reduce competition or push capable smaller firms out of the market.
That does not mean security should be weak.
It means security should be proportionate to:
- contract value;
- financial exposure;
- contractor strength;
- replacement difficulty;
- project criticality;
- duration;
- availability of alternative remedies.
Strategic Analysis: Security Can Strengthen or Weaken Resilience
The principal and contractor can both become less resilient when security is designed poorly.
For the principal, inadequate security may leave a large completion exposure if the contractor fails. For the contractor, excessive security can absorb banking capacity that would otherwise support working capital, equipment purchases or other projects. The same mechanism intended to protect delivery can therefore contribute to financial pressure if it is disproportionate.
A hypothetical specialist-equipment contract shows the trade-off. A smaller supplier may have excellent technical capability but limited bank-guarantee capacity. Requiring a large unconditional guarantee, high retention and extended payment terms simultaneously could make the contract commercially unattractive or force the supplier to price the financing burden. A larger supplier may absorb those requirements more easily but charge a higher base price.
The principal should therefore evaluate security as part of total commercial structure, alongside payment timing, advance payments, retention, parent support, insurance and supplier financial strength.
Security also has behavioural effects. If the contractor believes security can be called too easily, the relationship may become defensive. If the principal cannot access security when failure occurs, the protection may be illusory. The mechanism must therefore be credible to both parties.
This is a portfolio issue as well. Standard security settings should be reviewed against actual loss experience. If guarantees are almost never called but regularly reduce supplier capacity, the organisation should test whether its policy remains proportionate. If repeated contractor failures have produced losses above available security, the opposite question should be asked.
Decision Framework
Use five questions when setting security.
Exposure
What realistic loss or continuity problem is the security intended to cover?
Instrument
Would retention, bank guarantee, parent guarantee or another mechanism address that exposure most effectively?
Accessibility
Under what conditions can the principal actually use the security?
Economic burden
What does the mechanism cost the supplier in fees, cash flow and borrowing capacity?
Release profile
When does the underlying risk reduce sufficiently for security to be reduced or released?
Current law concerning calls on unconditional undertakings, injunctions, unconscionability and retention-money trusts should be verified for the relevant jurisdiction. [FACT CHECK REQUIRED]
From Strategy to Execution
Immediate action: document the purpose of each security requirement in the procurement strategy and contract.
Medium-term capability building: track actual losses, bond calls and retention outcomes across projects to test whether standard security settings match real exposure.
Long-term strategic positioning: segment security requirements by project risk and supplier type rather than applying one percentage mechanically.
This improves both protection and market efficiency.
Signals to Monitor
Watch for security values disconnected from plausible exposure, suppliers pricing unusually high risk premiums, bank guarantees consuming critical contractor working capital, security remaining unreduced long after risk falls, unclear call conditions, or project teams treating a bond as a substitute for active performance management.
Another warning sign is a contractor with strong operational performance but deteriorating liquidity partly because commercial terms concentrate cash and security pressure.
Questions for the Leadership Team
- What loss are we actually trying to protect?
- Why is this security form better than the alternatives?
- What does it cost the supplier to provide?
- Could the requirement reduce competition or contractor resilience?
- Under what conditions can we call it?
- When should it reduce?
- Are we relying on security instead of managing performance?
Closing Perspective
Security is valuable because failure is possible.
But security is not free, and it is not performance management.
The strongest commercial design uses the minimum mechanism necessary to protect material exposure while preserving supplier capacity, market competition and project continuity.
Related article: Contractor Failure Is a Continuity Problem Before It Is a Legal Problem
Related article: Insurance Is Risk Architecture: Match Cover to Responsibility, Not Habit
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.