Technical Proposals
Risk Management in a Technical Proposal: A Guide
21 November 2026 · 7 min read · By NextBid Bid Experts
How to build the risk section of a technical proposal: project-specific risks, probability and impact, mitigation and an owner, presented so evaluators see control, not alarm.
A risk management section in a technical proposal shows the evaluation committee that you have identified what could disrupt delivery of this specific contract, rated each risk, and committed to a mitigation and an owner. It is built around a risk register: a table of project-specific risks, each with a probability, an impact, a mitigation and a named owner. Whether the tender booklet (كراسة الشروط والمواصفات) scores risk management as a separate criterion, and in what form, is set by the booklet, so read its evaluation criteria before you design the section.
Why does a risk section matter to the evaluators?
The committee scores your technical offer against the criteria and weights stated in the booklet; there is no national pass mark, and the entity sets its own minimum technical score. A risk section earns its place when it proves that your methodology is realistic. It should read as the other side of your work plan and schedule and your quality plan: the work plan says what you will do and when, and the risk section says what could move it and what you will do about it.
Which risks belong in the register?
Choose risks you can trace to the scope, the location and the conditions of this tender. A risk that applies to every project in every sector adds length without showing that you understood the contract. These six groups cover the ground for a technical offer:
- Schedule: activities on the critical path, long approval steps and handover dates that other parties control.
- Supply chain: imported or long-lead items, single-source materials and delivery to the place of work.
- Staffing and Saudization: availability of the key personnel you name in the offer, recruitment and training needed to meet Saudization requirements, and cover for absence.
- Site access: permits to enter, working-hours restrictions, shared sites and access for vehicles and equipment.
- Approvals: submittals, inspections and permits from the entity or from other authorities that sit between you and the next stage.
- Dependencies on the entity: data, drawings, decisions, utilities or premises that the entity has to provide for your work to proceed.
How do you rate probability and impact?
Use a simple scale and define it once in the section. A three-level scale (low, medium, high) is easy for a committee to read. Probability is how likely the event is before you act. Impact is what it would do to the schedule, the cost, the quality of the deliverable or the continuity of the service. Rate each risk twice if space allows: before mitigation, and after it (the residual rating). The second rating is what shows the mitigation has a purpose.
Keep the rating honest. A register in which every risk is rated low suggests the team has not looked closely, and one in which nearly every risk is rated high suggests the work is not under control. The ratings should match the pattern of the project that your work plan describes.
What does an illustrative risk register look like?
The table below shows a format only. It is not a template the booklet requires and it does not describe any real tender; replace every line with risks drawn from your own scope.
| Risk | Probability | Impact | Mitigation in the offer | Owner |
|---|---|---|---|---|
| Site team mobilisation is later than planned | Medium | High | Key personnel confirmed in the offer; start-up checklist agreed at kick-off; a named alternate for each key role | Project manager |
| Staffing plan is affected by Saudization requirements | Medium | Medium | Roles listed by nationality category; recruitment and training dates built into the work plan | HR lead |
| Imported equipment is delivered late | Medium | High | Orders placed at award; two approved sources; critical items flagged in the schedule | Procurement manager |
| Site access is delayed or restricted | Low | High | Access request submitted by the date in the work plan; fallback activities that do not need the site | Site manager |
| A permit or approval takes longer than planned | Medium | Medium | Submission list prepared during mobilisation; approvals shown as milestones in the schedule | Project manager |
| Entity inputs (data, drawings, decisions) arrive after the needed-by date | Medium | Medium | Inputs list with needed-by dates stated as assumptions; escalation route set in the governance plan | Contract manager |
How do you present risk without alarming the evaluators?
A risk section should show your control of the project, not warn the evaluators about it. Write each risk as a statement of what could affect delivery, followed at once by what you will do. Avoid dramatic wording; "could be delayed" informs, "is at serious danger" alarms.
- Lead with the mitigation and the owner, and keep the rating in the table.
- Limit the high-rated risks to those that genuinely deserve attention, each paired with a measure and a trigger for acting.
- Do not claim that the project carries no risk. A section with no risks is not credible.
- State dependencies on the entity as assumptions: what you need, by when, and what you will do if it arrives later than planned. Do not describe the entity as the cause of a problem.
- Do not use the section to add conditions or reservations to your offer. If a requirement looks unworkable, raise it through the inquiry process the booklet describes.
Keep prices and contingency amounts out of the technical offer unless the booklet asks for them. Which documents belong in which envelope is set by the booklet; the difference between the technical and financial proposals explains how the two relate.
Who should own each risk?
An owner is a role in your project team, not the company in general. Choose roles that also appear in your organisation chart and in the key personnel CVs, so the committee can see the same person or post in each part of the offer. The owner tracks the risk, applies the mitigation and escalates when the trigger is reached. For a risk that depends on the entity, the owner is the person on your side who follows it up.
A good risk section shows the committee where this project could go wrong and who will act: specific risks, honest ratings, and one mitigation and one named role for each.
Frequently asked questions
How many risks should a technical proposal list?
The booklet sets any requirement on length or format. If it sets none, list the risks that are specific to the scope and conditions of the tender and give each a mitigation and an owner. A short, specific register reads better than a long generic one.
Do I need a risk register if the booklet does not ask for one?
Check the booklet first, and follow its structure if it asks for a risk section. If it does not, a register is still a clear way to support your methodology and work plan, as long as it fits within any limits the booklet sets.
Should the risk section include costs?
No, unless the booklet asks for them. Describe the measure in the technical offer and deal with any cost in the financial offer, as the booklet directs.
Can I list the entity's late inputs as a risk?
Yes, as a dependency written neutrally. State the input you need, the date you need it by and what you will do if it comes later. Avoid wording that blames the entity.
What is a residual risk rating?
It is the probability and impact that remain after your mitigation is applied. Showing it next to the starting rating makes the effect of each measure visible to the committee.
Our bid management team writes technical proposals natively in Arabic and English, including the risk section, working from the booklet's criteria and the project details you provide so that the register matches the work plan, the staffing and the rest of the offer.
