Explore the expanded editions. Read every sample free before choosing a book.

Portfolio practice / 3 MIN READ

Apply a risk-tolerance rule without turning unknowns into passes

Classify three fictional supplier recovery records against an explicit threshold and keep measured results separate from missing evidence.

Server racks and network cabling inside a data center
Illustrative photograph by imgix on Unsplash.
On this page

A threshold is useful only when its scope, measurement and boundary are clear. Missing evidence is not a measured value. This original fictional case practices applying a supplied decision rule without changing it to suit the result.

The numbers below are invented training conditions. They are not recommended recovery requirements, legal standards or acceptable limits for any real service.

Fix the rule before reading results

Fictional Rowan Services says: “For this exercise, a supplier meets the numeric recovery condition when the documented duration for the specified scenario is no more than four hours. A duration above four hours requires escalation to the named risk owner. Missing evidence requires a separate information request; it is not a pass. Meeting this condition alone does not authorize onboarding.”

Assume the first two records use the required scenario, scope and start/end definitions. The third has not supplied such a record. These assumptions make the arithmetic bounded; a real review would need to establish them.

SupplierSupplied evidenceClassification under the fictional rule
ADocumented duration: 240 minutesMeets the numeric condition exactly
BDocumented duration: 247 minutesExceeds the condition by 7 minutes; escalate
CMarketing statement: “rapid recovery”Evidence missing; request the specified record

Four hours equals 240 minutes. “No more than” includes the boundary itself. Rounding B to four hours before comparison changes the rule and conceals the exceedance. Assigning C a duration of zero invents a measurement.

Separate classification from permission

A suitable note says: “A meets this supplied numeric condition. B exceeds it and requires the specified escalation. C cannot be classified on duration from the supplied statement. None of these conclusions alone establishes onboarding approval or overall supplier suitability.”

NIST's risk-tolerance glossary provides context for an organization's accepted level of risk or uncertainty. It does not supply this four-hour threshold. The exercise uses an explicit fictional rule so that readers can inspect the reasoning rather than guess an unstated policy.

Ask for evidence that resolves the right uncertainty

For B, request the risk owner's disposition and any additional evidence required by the fictional process. Do not assume a minor numeric exceedance is immaterial or that you may approve it yourself. For C, request the scenario, scope, measurement definitions and documented result. A more confident marketing sentence would not resolve those missing fields.

Now suppose C supplies a result of 225 minutes from a different scenario. The evidence has improved, but it still does not meet the specified evidence condition. Revise the note to describe the mismatch rather than immediately assigning a pass.

Your finished artifact should preserve the rule, conversions, classifications, evidence requests and revised conclusion. For choosing focused versus connected practice, use risk-tolerance preparation. The risk-register worked example helps place a supported conclusion in a broader record without hiding uncertainty in a color or score.

PUT IT INTO PRACTICE

Risk & Evidence Portfolio Kit

Connect the individual document to a complete fictional case, with registers and a versioned decision memo.

Choose another free evidence, application or portfolio task