Write your awesome label here.

The Quantification Readiness Standard

Can your risk register be quantified at all?

The Quantification Readiness Standard

Make your risk register quantification ready.

Paste in the register you already have. It comes back audited against the IQRM Quantification Readiness Standard: what is a risk, what is an uncertainty, what is an issue, every line that cannot feed a model and the specific reason why, each of those lines rewritten, and a readiness score out of 100. No model, no software, no prior QSRA experience.

GET THE STANDARD – £5
Instant download. Nothing you paste is stored. 7 day refund, no questions.
Approved Saudi Aramco vendor ADNOC approved consultant CPD certified 200+ professionals trained

Why this exists

A register full of good risks can still be worth nothing.

A subcontractor on one of my programmes went quiet on cash. They had demobilised half their people. Every month the report came back the same. Three weeks late.

Nobody challenged it, because three weeks sounded survivable and the register said the risk was being managed.

I asked one question. What is our certainty of hitting three weeks?

The honest answer was negative one hundred percent.

I went back through that register afterwards. Sixty three entries. Every one a properly written risk with an owner, a score and a mitigation. Not one of them capable of producing a number anyone could defend.

That is when I stopped believing the problem was the software.

The diagnosis

Risk may or may not happen. Uncertainty is already happening.

A risk is an event with a probability attached. That is what your register records, and most registers record it well.

Uncertainty carries no probability, because it is occurring with certainty. Only the amount is in question. Your permits take between nine and twenty three days. Your reviews come back with comments about half the time. Your crews land somewhere between seventy and a hundred and ten percent of planned productivity depending on the week.

None of that is in your register. All of it is what actually decides your finish date.

Risk

May or may not occur. Carries a probability. Your register is full of these.

Uncertainty

Occurring right now. Carries no probability, only a range. Almost always missing.

Issue

Already happened. Belongs in the baseline, not the model. Usually sitting in the register anyway.

Most registers arrive between ninety and a hundred percent risk. A register with no uncertainty in it cannot produce a credible range, no matter how well the risks are written, and no amount of Monte Carlo will fix an input that was never captured.

What it does

Five passes over your register, in the same order every time.

1

It classifies every lineRisk, uncertainty or issue, and reports your split as a percentage. This one number usually ends the argument you have been having with your team for months.

2

It flags what cannot be modelledAgainst eleven named failures. Not "this is weak". The specific fault: no measurable range, consequence not quantified, cause written as the risk, effect written as the risk, two risks in one line, not mappable to an activity or a cost line, probability missing or ordinal, double counted, mitigation embedded, post mitigation only, uncertainty logged as a risk.

3

It rewrites every flagged lineBefore and after, side by side, in the IQRM standard form. Where your register does not contain the information a rewrite needs, it writes RANGE REQUIRED in the gap rather than inventing a number. It will not make one up. Not once, not as an illustration.

4

It scores the register out of 100Structure out of forty, quantifiability out of forty, uncertainty coverage out of twenty. Then it tells you which band you are in, the three highest value fixes in priority order, and what the score would need to reach to be called Quantification Ready. Above eighty six it says so plainly, and that is rare.

5

It names what is missingThe uncertainty categories a programme of your type would normally carry and yours does not. Permitting and approvals, design review cycles, procurement lead times, construction productivity, weather and access, interface dependencies.

Why it is called a standard

Because the same register should score the same on Tuesday as it did on Monday.

Most register reviews are somebody's opinion delivered in a workshop. Two reviewers, two answers, and no way to tell which one was right or whether anything improved after the rework.

This is fixed. Eleven named failures, one rewrite form, three scoring components with fixed weights, four bands. Run it on the same register twice and you get the same result. Run it before and after a clean up and the difference in the score is real rather than a feeling.

The standard form

Because of a cause that is a present fact, an event may occur, which would change a named activity or cost line by a measurable range.

Anything that cannot be written that way cannot be modelled, and the audit tells you which of the eleven reasons applies.

It carries downstream

The Quantitative Risk Register workbook is built to the same standard, so a register that passes the audit drops straight into the model without being re-written again.

Same definitions, same rewrite form, same split between risk and uncertainty.

The line it stops at

Your register is now quantifiable. It is not yet quantified.

That sentence is printed at the end of every audit it runs, and it is there deliberately.

This fixes the inputs. It does not produce a forecast. It will not select distributions, handle correlation between variables, account for merge bias across paths, or interpret a result. It will not tell you which parameters belong on your programme, what ranges they carry, or where that evidence already sits in your reporting, because that comes from project data rather than from rules.

Every one of those limits is written into the file itself. Ask it to cross one and it will decline and carry on with the audit.

Why a boundary is worth paying for

Anything that will happily invent a range for you is worse than useless on a capital programme, because the output looks exactly like real work. You will find out it was not at a sanction gate, in front of people whose job is to ask where the number came from.

This tool would rather hand you a gap marked RANGE REQUIRED than a plausible fiction.

Confidentiality

Your register never leaves your own account.

This is a file you download and run yourself. It is not a service, there is no server at this end, and nothing you paste is transmitted to IQRM, stored by IQRM or seen by anybody here.

The audit also opens by telling you to strip the project name, the activity names and the values if the register is commercially sensitive, because it works on structure rather than on what your project is called. If you are on an NDA covered programme, run it anonymised. The score comes out the same.

How it works

One file. Installed once. Used on every register you own.

What you get

A single .skill file. You add it to Claude once, in the skills area of your account, and it stays there.

After that you paste a register into a normal conversation and the audit runs. Pasted text, a table or a spreadsheet all work.

What you need

A Claude account. The free tier is enough to run it, though a long register will go further on a paid one.

Nothing else. No Excel add-in, no licence, no IT request, no install on a corporate machine.

If you have never installed a skill before, the file comes with a two paragraph instruction that takes about a minute to follow.

Who this is for

People who already run a register and suspect it is not good enough.

  • Risk managersWho have been told to produce a quantitative output and know the register underneath it will not carry one.
  • Planners and cost engineersWho are being handed a register to model and want to say something specific about why it cannot be modelled.
  • Project controls leadsWho need a defensible reason to send a register back rather than a personal opinion.
  • Anyone walking into a gate reviewWho would rather find the holes now than have somebody else find them at the table.

This is not an introduction to risk management. It assumes you already keep a register and know what one is for.

The Quantification Readiness Standard

£5

One payment. Yours to keep. Run it on every register you have, as many times as you like, for as long as you keep the file.

Why five poundsBecause this argument is far easier to prove than to explain. Run it on your own register once and you will not need me to convince you of anything. That is worth more to IQRM than the five pounds is.
RefundSeven days, no questions, no form. Reply to the receipt.
GET THE STANDARD – £5
Instant download. Nothing stored. Licensed to you for internal use.

Who wrote it

Rami Salem, QRMCert.

For years I did what everyone does. Get the team in a room, collect optimistic, most likely and pessimistic, put the three numbers in, press go. The output looked professional. It was built on opinion and everybody in the room knew it.

Then the results would come back saying eighteen months, somebody would say that cannot be right, and the inputs would get adjusted until the answer looked acceptable. That is the part that finished it for me. Not the bad models. The believable ones.

I have trained more than two hundred professionals since. The first thing almost every one of them needs is not a tool. It is to find out that their register was never going to work.

Better to find that out here than at a sanction gate.

Approved Saudi Aramco vendor ADNOC approved consultant CPD certified 200+ professionals trained

Questions

Before you buy.

Do I need Claude for this to work?
Yes. It is a skill file, and skills run inside Claude. A free account is enough to run it. If you do not have one, setting it up takes about two minutes and costs nothing.
Is my register safe to paste in?
It runs entirely inside your own account. Nothing is sent to IQRM and nobody here sees it. The audit itself opens by telling you to strip the project name, the activity names and the values if the register is sensitive, because it reads structure rather than content. On an NDA covered programme, run it anonymised.
Will it give me a P80?
No, and it will refuse if you ask. Confidence levels need a model, a set of distributions and a view on correlation. This audits and rewrites the inputs. That boundary is written into the file and it holds.
Will it tell me what ranges to use?
No. It names the uncertainty categories your register is missing, and stops there. Ranges come from your own project data, and a tool that invents them for you is producing fiction that looks like analysis.
How long does an audit take?
A few minutes for a register of sixty to eighty lines. Longer registers are best run in blocks.
What if my register is already good?
Then you will score in the eighties and it will say so. That is rare, and it is worth knowing with a number rather than assuming it.
Is there support?
No. At five pounds this is a file, not a service. If it does not do what this page says it does, ask for the refund and I will send it.
GET THE STANDARD – £5
Created with