Integrated risk console

Contract Risk Score

Combine signals from Tender Risk Lab and calculators into one board-level index before pricing, project start or a claim strategy meeting.

Risk inputs

This is a screening score: Particular Conditions, applicable law and project facts still need separate review.

What this tool does

The tool collects answers on the contract’s key parameters — form, risk allocation, securities, claims mechanism, dispute route — and reduces them to a comparable score. The point is not the number but seeing which parameters drag the project down, so they can be discussed specifically rather than as a general sense that the contract is harsh.

Where the inputs come from

  • Answer from the actual Particular Conditions text, not from the general conditions of the chosen book.
  • The Contract Data is the main source on periods, caps and securities; treat a blank entry as the worst case.
  • If a clause is deleted or rewritten, that is its own answer, not "as per the standard".

How to read the result

A high risk score does not mean walking away. It means the risk must either be closed with a clarification question, priced in, or accepted deliberately with a management plan. The practical value is in the breakdown: two contracts with the same overall score can demand entirely different action if one has a problem with securities and the other with the claims mechanism.

What this tool does not account for

  • It does not read your contract: the score is only as accurate as the answers.
  • It does not account for the governing law, which can change how a liability cap or a time bar operates.
  • It does not assess the counterparty: the Employer’s payment record is outside the model and often decisive in practice.
  • It does not replace legal review of the actual text — this is screening, not an opinion.

Questions

What score should be treated as acceptable?

There is no universal threshold: acceptability depends on margin, the team’s experience with that model, and whether you have levers over the specific risks. It is more useful to compare against your own past projects than an abstract norm: if a contract is materially harsher than one you already ended up disputing, that is a signal to build in contingency.

What to do with the risks found before submitting a bid?

Sort them into three buckets: closable with a clarification question, needs a contingency in the price, accepted deliberately. The first bucket is the most valuable and the most underused: a clarification question costs incomparably less than a claim during execution, and the window for it closes within days.