How do you calculate a documentation burden risk score?

It blends the severity, occurrence, and detection scores into one figure on the same scale. With severity 6, occurrence 4, and detection 3, the blended documentation burden risk score comes out to about 4.55.

What is a good documentation risk score?

Lower is better. Because inputs share a scale, a score near the top of the range flags a task that is high-impact, likely to slip, and hard to catch, which is exactly what should get extra controls first.

How is this different from a standard FMEA RPN?

It uses the same severity, occurrence, and detection thinking as an FMEA, but returns a blended score on the input scale rather than a raw product, which keeps results comparable and avoids the exaggerated spread a straight multiplication produces.

Why does detection difficulty matter for paperwork?

A gap you catch in a weekly QA review is far less dangerous than one that only surfaces during a regulator's audit or a client claim. Higher detection scores mean the miss hides longer, so it drives the risk up.

Which documentation tasks usually score highest?

Safety-case and ground-monitoring records tend to score high because a gap is severe, easy to miss under production pressure, and often only detected in audit. Routine daily logs usually score lower on severity.

How should I act on the score?

Rank all your documentation tasks by score and put your strongest controls on the top few: sign-offs, automated capture, or independent review. Do not spread scarce QA attention evenly across low and high scores alike.

Tunnel Boring & Heavy Civil Equipment calculator

Documentation Burden Calculator

Documentation burden risk scores how much a recordkeeping or compliance obligation on a tunnel boring or heavy civil project threatens the job if it is missed. Heavy civil work carries heavy paperwork: as-built records, inspection logs, ground-monitoring data, and safety-case entries that regulators and clients audit closely. QA managers and site engineers use this FMEA-style score to rank which documentation tasks deserve extra controls before an audit or a claim exposes a gap. By combining how bad a miss would be, how likely it is, and how hard it is to catch, the score turns a vague sense of paperwork pressure into a comparable number.

What this calculator does

Estimate documentation burden for tunnel boring and heavy civil equipment using production-ready inputs so teams can rank risks and decide which issue needs containment, controls, or escalation first.
Use it when documentation burden in tunnel boring and heavy civil equipment needs a defensible ranking against other tunnel boring and heavy civil equipment risks for the next review.
It blends a severity, an occurrence, and a detection score into a single documentation risk figure so compliance tasks can be ranked consistently.

Formula used

Documentation burden risk score = documentation burden severity score × documentation burden occurrence score × documentation burden detection score
Use the same scoring scale across comparable documentation burden risks.

Inputs explained

Compliance impact severity:
Documentation gap occurrence likelihood:
Audit detection difficulty:

How to use the result

Use it when prioritising which documentation controls to tighten ahead of a client audit, regulatory inspection, or contractual milestone.
Scores are subjective judgements on a shared scale, so the number only holds meaning when the same team applies the same rubric across every task it compares.

Current U.S. benchmarks

Steel mill PPI stands at 348.53 (BLS, May 2026), up 6.7% from a year earlier. New factory orders are up 2.3% year over year (Census).

Common questions

How do you calculate a documentation burden risk score? It blends the severity, occurrence, and detection scores into one figure on the same scale. With severity 6, occurrence 4, and detection 3, the blended documentation burden risk score comes out to about 4.55.
What is a good documentation risk score? Lower is better. Because inputs share a scale, a score near the top of the range flags a task that is high-impact, likely to slip, and hard to catch, which is exactly what should get extra controls first.
How is this different from a standard FMEA RPN? It uses the same severity, occurrence, and detection thinking as an FMEA, but returns a blended score on the input scale rather than a raw product, which keeps results comparable and avoids the exaggerated spread a straight multiplication produces.
Why does detection difficulty matter for paperwork? A gap you catch in a weekly QA review is far less dangerous than one that only surfaces during a regulator's audit or a client claim. Higher detection scores mean the miss hides longer, so it drives the risk up.
Which documentation tasks usually score highest? Safety-case and ground-monitoring records tend to score high because a gap is severe, easy to miss under production pressure, and often only detected in audit. Routine daily logs usually score lower on severity.

Last reviewed 2026-05-12.