Ask a civil contractor how they priced risk on their last tender and the honest answer is usually a number added at the end — five per cent, or ten if the job looked awkward, or whatever brought the total to where it needed to be. Ask which specific risks that number covered and the conversation stops.
That is not a criticism of estimators. It is what happens when there is no structure between reading the contract and writing the price. A risk register is that structure — a list of the things that could cost you money, what you decided to do about each one, and what it is worth. It is the least glamorous document in a bid and one of the few that changes the outcome. It earns that at the tender settlement meeting, where every item becomes a priced allowance, a qualification or an accepted exposure.
What a risk register actually is
Worth distinguishing from two things it gets confused with.
| Document | What it lists | Who uses it |
|---|---|---|
| Hazard register / SWMS | Things that could hurt people, and the controls | Site, safety regulator — see WHS management plans and SWMS |
| Risk register (this guide) | Things that could cost money or time, and the commercial response | The estimator, then the project manager |
| Issues register | Things that have already happened | Contract administration — see contract administration for civil SMEs |
The overlap is real — a safety event has a cost, and a cost risk can have a safety cause — but the documents have different audiences and different purposes, and merging them produces one document that serves neither. A commercial risk register asks a single question of every entry: if this happens, who pays?
The four things you can do with a risk
There are only four, and naming them forces a decision that otherwise gets avoided.
| Response | What it means at tender stage | Cost |
|---|---|---|
| Avoid | Do not bid, or qualify the risk out of your offer so it is not yours | Free, but may cost you the job |
| Reduce | Change the method, sequence or resourcing so the risk is smaller | Usually a real cost, and usually less than the risk |
| Transfer | Subcontract it, insure it, or push it back under the contract | The subcontract premium, the insurance premium, or a negotiation |
| Accept | Carry it, and price it | The priced allowance — or, if unpriced, your margin |
The fifth option, which is not on the list, is the one most commonly used: accept it without pricing it. That is not a risk response; it is a bet, made without deciding to make it. The entire value of a register is that it converts the fifth option into the fourth by forcing each item to be looked at once.
Two notes on transfer, because it is the response most often overestimated. Subcontracting a risk only transfers it to the extent the subcontractor can actually bear it — a subcontractor who fails leaves the risk back with you, plus the disruption. And insurance transfers the financial consequence of insured events only, subject to limits, excesses and exclusions; the programme consequence stays yours, as our guide to making an insurance claim on a civil job makes clear.
Where the risks come from
Seven sources. Working through them in order is what makes a register comprehensive rather than a list of whatever worried someone.
| Source | What to look for |
|---|---|
| The contract | Which party bears each named risk, what relief exists, time bars, liability caps, liquidated damages, termination and suspension rights |
| The specification | Tolerances you may not achieve, nominated products, prescribed methods, testing regimes, hold points |
| The site | Ground, water, services, access, contamination, neighbours, heritage, weather exposure |
| The programme | Dependencies you do not control — approvals, outages, possessions, client-supplied items, other contractors |
| The client | Decision-making speed, payment behaviour, how they have administered past contracts, whether the funding is secure |
| The market | Material availability and price movement, subcontractor and labour availability, plant availability |
| Yourselves | Capacity, key people committed elsewhere, unfamiliar work type, distance from base, cash position |
The last row is the one contractors skip, and it is often the largest. A job that is well within your capability at your normal workload is a different risk at capacity, in an unfamiliar region, with your best supervisor already committed. Those are register entries, and they are the same considerations that drive the framework in our guide to the go/no-go decision — which is really the register’s first output, not a separate exercise.
Reading the contract for risk transfer
The single richest source, and the one where an hour is worth the most.
How the standard Australian forms allocate risk, and how amendments change that allocation, is covered in our guides to AS 4000 and AS 2124 and contract forms beyond construct-only. This guide does not repeat that. What it adds is the method: read the contract once specifically hunting for risk, with a highlighter and a list, rather than reading it for comprehension and hoping the risks announce themselves.
The clauses that most often move risk onto a civil contractor, and what each turns into as a register entry:
- Site conditions and site information. Whether latent conditions relief exists, and whether the information provided is warranted or disclaimed — see latent conditions. An amended or deleted latent conditions clause is one of the largest single risk transfers available and it is usually one paragraph.
- Time bars. How long you have to notify a claim, and whether failure to notify extinguishes the entitlement — see extension of time and delay claims. A short bar is a risk with an administrative control, not a pricing one.
- Weather and inclement conditions. Whether relief is available, and on what basis.
- Approvals. Which are the principal’s and which are yours — see environmental approvals and permits.
- Quantities. Lump sum against remeasured, and how provisional quantities behave above the allowance — see schedule of rates vs lump sum and bills of quantities and provisional quantities.
- Liquidated damages and any cap. The maximum exposure, and how it compares to the margin.
- Liability, indemnity and consequential loss. Whether liability is capped, and whether any carve-outs are uncapped.
- Payment and security. Terms, retention, bank guarantee requirements, set-off rights — and the position under the payment legislation in our guide to security of payment in Australia.
- Suspension and termination for convenience. What you recover if the client simply stops.
- Escalation. Whether rise and fall applies over the contract period.
The discipline that makes this useful: for each one, write down what it would cost you if it happened, not just that it exists. A time bar is not a cost. A time bar plus a realistic assessment of how likely your site team is to miss it, multiplied by the value of the claims that would be lost, is a cost — and it usually justifies spending money on contract administration rather than on contingency.
Building the register during the bid
A workable structure for a civil SME. Seven columns, and no more.
| Column | Content |
|---|---|
| Risk | What could happen, in one sentence, specific to this job. Not “ground conditions” but “rock in the northern cut above the depth indicated” |
| Trigger | What would tell you it is happening, and when you would know |
| Consequence | Cost, time, or both — estimated, not categorised |
| Likelihood | A rough judgement. High, medium, low is enough |
| Response | Avoid, reduce, transfer or accept — the choice from §02 |
| Action | What you are actually doing: the qualification, the RFI, the allowance, the method change, the subcontract term |
| Owner | A person. At bid stage usually the estimator; at award it transfers |
Two things deliberately absent. There is no risk score, because a number produced by multiplying two guesses adds precision without adding information and encourages people to argue about the score rather than the response. And there is no colour rating, for the same reason. The value is in the response column, not the assessment columns, and any effort spent making the assessment look rigorous is effort taken from deciding what to do.
The register should be built while the estimate is built, not after it, because the two inform each other — a risk that turns out to be expensive to accept may change the method, which changes the estimate. The build-up method is in our guide to preparing civil works cost estimates.
Pricing risk without a made-up percentage
The practical question this whole document exists to answer.
A single percentage contingency has three problems. It is invisible to the client and therefore looks like margin they can negotiate away. It is not attached to anything, so nobody can say when it has been consumed or when it can be released. And it is applied uniformly to a job whose risks are concentrated in two or three activities.
A better approach, and it is not complicated:
- Price the ones you can price directly. Many register entries are not really uncertain in cost, only in occurrence — a service relocation, an extra approval, a monitoring regime. Estimate the cost, judge the likelihood, and carry a proportion.
- Put the big uncertain ones in the rate for that activity, not in a global contingency. If the drainage is the risky part, the drainage rate should carry it. That way the exposure and the money sit together, and if the drainage is remeasured you are still covered.
- Keep a small genuine unknown-unknowns allowance for what the register did not anticipate, and treat it as separate from the priced items.
- Do not carry the same risk twice. A risk allowed for in a rate and again in contingency is a bid you will lose for no reason. Cross-check.
- Write down what each allowance is for. This is the step that makes release possible later, and its absence is why contingency is never released.
The commercial framing matters too. Risk that is priced explicitly can be discussed with a client; risk buried in a percentage cannot. Where a client’s own contract creates the risk, saying so — “our price includes an allowance for X because clause Y allocates it to us; we would price Z lower if that were shared” — is a legitimate conversation and occasionally a productive one. It is the same argument our guide to pricing strategies for government tenders makes about competing on value rather than on price alone.
Qualify, clarify or price — choosing the response
For each accepted risk there are three possible tender-stage actions, and choosing the wrong one is how contractors either lose bids unnecessarily or win bids they should not have.
| Action | Use it when | Risk of using it |
|---|---|---|
| Raise a clarification | The tender documents are ambiguous, contradictory or silent, and an answer would remove the risk | Almost none, and the answer usually goes to all tenderers. Do this first — see tender clarifications and the RFI window |
| Qualify the offer | The risk is real, unpriceable and the documents are clear that it is yours | A qualification can render a bid non-conforming if handled badly — see non-conforming and alternative tenders |
| Price it and say nothing | The risk is quantifiable and you are willing to carry it | You may be the only tenderer who priced it, and lose on price to someone who did not |
That last row is the honest difficulty of this whole subject, and it deserves stating plainly. A contractor who prices risk properly competes against contractors who have not priced it at all, and in a lowest-price evaluation the disciplined bidder loses. Three things help: raise clarifications so the risk is removed for everyone rather than absorbed by you alone; put the reasoning where an evaluator can see it, because a bid that explains why it is higher sometimes survives a value-for-money assessment; and use the go/no-go discipline to decline work where the market is pricing a risk you are not prepared to ignore.
The risks that recur on civil jobs
A starting list. It is not exhaustive and it is not a substitute for reading this job’s documents, but it is the set that appears often enough to be worth a standing prompt.
| Risk | Where it is usually addressed |
|---|---|
| Ground conditions differ from the information provided | Latent conditions, and the site information clause |
| Earthworks does not balance; unsuitable material exceeds allowance | Earthworks balance, mass haul and spoil |
| Services not where shown, or not shown at all | Service location and proving |
| Excavation support required where battering was assumed | Temporary works and excavation support |
| Approvals late, or conditions more onerous than assumed | Environmental approvals and permits |
| Restricted hours or stoppages from complaints | Noise, vibration and dust management |
| Weather beyond the allowance, on moisture-sensitive material | Programme allowance and the inclement weather provisions |
| Material price movement or unavailability | Rise and fall and materials supply agreements |
| Subcontractor failure or non-performance | Subcontract terms, and a fallback |
| Client-caused delay and slow decisions | Time bars, notice discipline, extension of time and delay claims |
| Late or disputed payment straining cash | Cash flow and security of payment |
| Key personnel unavailable | Resourcing, and the commitments in your key personnel schedule |
| Design or model errors carried into construction | Machine control and model status |
| Quantities differ materially from the schedule | Measurement basis, provisional quantities |
| Access constrained or handed over late | Site access provisions and the programme |
Keeping this list as a standing prompt, and adding to it after every project debrief, is how a register stops being an act of imagination each time. It belongs with the reusable material described in our guide to building a tender content library.
Carrying it into delivery
The step that almost nobody takes, and the one that converts a pricing exercise into a management tool.
At award, the register should be handed over with the job — the same handover that transfers the estimate, the assumptions and the programme, described in our guide to contract award and mobilisation. What changes at handover:
- Ownership transfers from the estimator to named people on the project.
- Triggers become monitoring points. The person who owns the ground conditions risk should know what would tell them it is materialising, and be looking.
- Allowances become budget lines, visible in the cost report described in our guide to job costing and cost control, so consumption is tracked rather than absorbed.
- New risks get added. The register at award is not the register at month four.
- It gets reviewed on a rhythm — the same monthly meeting that reviews cost is the natural place, and it takes ten minutes.
There is a second benefit that is easy to miss. A live register is an early-warning system for claims. A risk that materialises is frequently a variation, a delay event or a latent condition, and the register entry — with its trigger, its date and its anticipated consequence — is contemporaneous evidence that you identified it and when. That is exactly the record the notice requirements in our guide to variations in civil construction contracts depend on.
Closing risks and releasing contingency
The discipline that pays for the whole exercise, and it is almost never done.
Risks expire. Once the bulk earthworks are complete, the rock risk is gone. Once the approval issues, the approval risk is gone. Once the last service is proved and the trench is backfilled, the strike risk on that section is gone. If an allowance was carried for each of those, the money should be released to the forecast result at the point the risk closes — not quietly consumed by other overruns, and not discovered as a windfall at the end.
Doing this produces three things a contractor otherwise never has:
- An honest forecast. A job carrying unreleased contingency for risks that have passed is forecasting worse than it is, which distorts every decision made on that forecast.
- A calibration record. Over several jobs, comparing what you allowed against what actually occurred tells you whether you price risk too high, too low, or in the wrong places. That is the feedback loop that improves estimating, and almost nobody has it.
- A defensible position on margin. A job that finishes above forecast because risks did not materialise is a different story from one that finished above forecast by accident, and the difference matters when explaining performance to a bank, a bonding provider or a prequalification assessor — see demonstrating financial capacity.
When the client asks for a risk register
Increasingly a returnable in its own right, and it requires a judgement.
The register you submit is not the register you priced from, and that is legitimate rather than dishonest — they have different purposes. Your internal register contains commercial assessments, allowances and judgements about the client that have no place in a submission. The submitted register should demonstrate that you have understood this job’s risks and have credible responses.
- Be specific to the site. Generic entries — “adverse weather”, “site conditions” — signal a template. Named entries signal that someone visited and read the documents.
- Show the response, not just the risk. The response column is what is being assessed.
- Include risks you will manage rather than only ones you are flagging, or it reads as a list of excuses under construction.
- Do not disclose your allowances. No client returnable requires the dollar value you carried, and volunteering it invites negotiation.
- Do not include entries that are really qualifications. If you are not accepting a risk, that belongs in your qualifications where it has contractual effect, not in a register where it has none.
- Do not list risks that are plainly the principal’s as though you were managing them. It reads as either confusion or an attempt to create an entitlement.
The general drafting approach is in our guide to addressing selection criteria. On this returnable specifically, evaluators are looking for one thing: evidence that you know what will go wrong on this job, which is a proxy for whether you have done one like it.
Registers that are theatre
Worth naming the failure modes, because a bad register is worse than none — it produces confidence without protection.
- The copied register. Last job’s list with the project name changed. Recognisable because the entries do not match the site.
- The scored register. Elaborate likelihood and consequence matrices producing colour-coded numbers, with an empty response column.
- The register with no owner. Every entry assigned to “project team”.
- The register nobody reopens. Written for the bid, filed at award, never reviewed.
- The register of things you cannot influence. Interest rates and global supply chains, listed because they sound serious, while the drainage sequence that will actually cost you money is absent.
- The register that only lists risks. No responses, no allowances — a list of worries rather than a set of decisions.
The test for whether yours is real: can you point to something in the price, the method, the programme, the qualifications or the subcontracts that exists because of an entry in the register? If not, the register did not do anything, whatever it looks like.
Checklist
- Is the register built during the estimate rather than after it?
- Have you worked through all seven risk sources, including your own capacity?
- Have you read the contract once specifically hunting for risk transfer?
- Have you checked whether the latent conditions clause has been amended or deleted?
- Do you know the time bars, and have you treated them as an administrative control rather than a priced risk?
- Is every entry specific to this job rather than generic?
- Has every risk been assigned one of the four responses?
- Is anything being accepted without being priced?
- Are the big uncertain risks priced into the relevant activity rate rather than a global percentage?
- Have you cross-checked that no risk is carried twice?
- Is it written down what each allowance is for?
- Have you raised clarifications for anything a client answer would resolve?
- Are qualifications used where a risk is genuinely unpriceable, and drafted so the bid stays conforming?
- Does the register transfer to the project at award, with named owners?
- Are allowances visible as budget lines in the cost report?
- Is the register reviewed monthly alongside cost?
- Are risks closed out and their allowances released to the forecast when they expire?
- Are you comparing allowed against actual across jobs to calibrate?
- If a client returnable is required, is it site-specific, response-focused, and free of your allowances?
- Can you point to something in the price, method or programme that exists because of a register entry?
The short version
- A risk register is the structure between reading the contract and writing the price. Without it, risks are accepted silently by default.
- There are four responses — avoid, reduce, transfer, accept. The fifth, accepting without pricing, is a bet nobody decided to make.
- Work through all seven sources. Your own capacity is the one most often skipped and often the largest.
- Read the contract once specifically hunting for risk transfer. An amended latent conditions clause is one paragraph and one of the biggest transfers there is.
- Skip the scoring matrix. The value is in the response column, not in making the assessment look rigorous.
- Price big uncertain risks into the relevant activity rate, not a global percentage — the exposure and the money should sit together.
- Write down what each allowance is for, or you will never be able to release it.
- Raise a clarification before you qualify, and qualify before you silently absorb.
- Pricing risk properly means competing against people who did not. Clarifications help, because they remove the risk for everyone.
- Hand the register over at award with named owners. A live register is also an early-warning system for claims and contemporaneous evidence.
- Close risks out and release the allowance when they expire. That is what produces an honest forecast and a calibration record.
- The test of a real register: can you point to something in the price, method, programme or subcontracts that exists because of it?
Sources and further reading
This guide is general information for Australian civil construction businesses and is not legal, contractual, insurance or financial advice. Risk allocation between principal and contractor is determined by the executed contract, including any amendments to standard forms, and differs between projects; nothing here describes the allocation under your contract. Whether a particular qualification renders a tender non-conforming, whether a notice satisfies a time bar, and whether a materialised risk gives rise to an entitlement are all matters for advice on the specific documents and facts. Insurance transfers only the financial consequences of insured events, subject to the policy terms, limits and exclusions. Always read the tender documents and the executed contract in full and take advice from a construction lawyer on risk allocation before committing to a price.
- Australian standard-form construction contracts and their risk allocation provisions — site conditions, notice and time bar requirements, weather relief, liability caps, liquidated damages, suspension and termination — referenced in §04 as the primary source of transferable risk. The published allocations and the effect of common amendments are sourced in full in our guides to AS 4000 and AS 2124 and contract forms beyond construct-only.
- Established risk management practice as applied in construction — the identify, assess, respond, monitor cycle and the avoid, reduce, transfer, accept response set described in §02. These are general management conventions rather than a regulated framework; the recommendation in §05 to omit scoring matrices is the guide’s own position, not a standard.
- Related TenderBuilt guides carrying the primary-source detail referenced above: the go/no-go decision, latent conditions, tender clarifications and the RFI window, non-conforming and alternative tenders, preparing civil works cost estimates, pricing strategies for government tenders, job costing and cost control, contract award and mobilisation, variations, extension of time and delay claims and security of payment in Australia.