Proposal software risk scenarios need a scored register before quotes go out

What to take away

The decision is whether to trust an informal list of worries or a scored register with owners and dates.
Score each scenario on likelihood and cost, then set a threshold that forces a named person to act.
Re-test the register when pricing, headcount or regulation changes, not only at renewal.
Keep the approval trail, because a customer or regulator may ask how a figure was agreed.

Define the scenarios before you rate them

Write each scenario as one testable sentence

A risk scenario is a short statement of what could go wrong, plus the conditions that make it likely.

Unscorable vs Scorable Scenario

Unscorable

Statement: Tool is risky
Condition: None given
Testable: No
Scoreable: No

Scorable

Statement: Rep reuses old price list
Condition: After a 4% uplift
Testable: Yes
Scoreable: Yes

"Our quoting tool is risky" cannot be scored. "A rep reuses last quarter's price list after a 4% uplift" can.

A quote carries a price, a term and a product claim. If any of those is wrong, the customer usually spots it before your legal team does.

Typical entries include a discount above the approved band, an expired price list left in a template, a clause that conflicts with the master agreement, and a personal data field copied into a shared drive.

Documented controls help here. BSI's page on BS EN ISO 9001 explains the British adoption of the quality standard, including how an auditable approval process is described.

Stress each scenario against a trigger

Triggers are events that change the odds. A new price list, a new market, a round of redundancies or a new AI drafting feature all shift what can go wrong.

Work through each trigger and ask which scenarios become more likely.

Ask a second question at the same time: what does the trigger change about the deal itself? A price rise moves margin. A new market adds a tax or language question. Note the answer beside the scenario.

Some scenarios touch anti-bribery duties. Where a deal involves gifts, hospitality or a third-party intermediary, the Bribery Act 2010 guidance from GOV.UK sets out six principles for commercial organisations.

Demand generation carries its own version of the problem. If a campaign advertises a price the quoting tool cannot produce, the promise becomes the risk. The Google Ads guide for demand generation campaigns explains how those campaigns are set up and measured.

Score each scenario on two axes

Likelihood and cost are enough for most teams. A third axis, such as reputational damage, tends to produce arguments rather than decisions.

Risk Scoring Rubric

Score

1: Two unrelated failures
2: Happened to known team
3: Happened here in 12 months
4: Monthly unless intervened

Likelihood test

1: Under £2,000
2: £2,000 to £10,000
3: £10,000 to £50,000
4: Over £50,000

Illustrative cost

1: Log, review annually
2: Add manual check
3: Name owner and date
4: Fix before next quote

What happens next

1
2
3
4

Buyer expectations move faster than most registers are updated. The proposal software trends and outlook for England in 2027 sets out which changes are worth planning around.

Build a rubric your team can defend

Where you have a log of past errors, rate likelihood from it. If you have no log, ask the two people who handle escalations and take the higher answer.

The bands below are illustrative figures for a mid-sized sales team. Replace them with your own costs where you have them.

Score	Likelihood test	Illustrative cost	What happens next
1	Needs two unrelated failures at once	Under £2,000 of rework	Log it, review annually
2	Has happened to a team you know	£2,000 to £10,000 and one customer conversation	Add a manual check
3	Happened here in the last 12 months	£10,000 to £50,000, or a delayed signature	Name an owner and a date
4	Happens monthly unless someone intervenes	Over £50,000, or a legal referral	Fix it before the next quote goes out

Set thresholds that force action

A score with no threshold is a filing exercise. Decide in advance which score stops a quote until someone signs it off.

Write the threshold next to the rubric, so nobody has to interpret it during a live deal. Put the same rule in the template as a margin note.

Keep the register alive

Competitor and buyer shifts belong in the same review. The proposal software market outlook in England covers what has changed in the buyer base, which helps when you re-rate likelihood.

Give every scenario an owner and a date

An owner is a person, not a team. Set a review date for each entry and put it in the same calendar as your pricing reviews.

A register that sits in a file nobody opens is a document, not a control. Give it a standing slot in a meeting with a named chair.

Keep the evidence you would need later

Keep the approved price list, the approval message and the version of the template that was live. If a customer disputes a figure, that file answers the question faster than a search through email.

Common questions

How many scenarios should a register hold?

There is no standard number. Most teams cover the main failure routes in fewer than a dozen entries, and longer lists tend to go unread.

Who should own the risk register?

Usually the person who owns the quoting process. Finance or legal should review entries that touch contract terms or anti-bribery duties.

How often should the register be reviewed?

Whenever a trigger fires, such as a pricing change, a new market or a system release. An annual read-through catches entries that have quietly gone stale.