OpLogica
Start your audit
Menu
Start your audit
Exposure Estimator

Think through your decision exposure.

When decisions cannot be reviewed, evidenced, approved, or reconstructed, organizations may face reviewability questions. This estimator helps you think about that, illustratively, before deciding whether to request an audit. It computes nothing.

Read the thesis

Decision exposure estimator showing evidence, approval, reconstruction, integrity, exceptions, and exposure outcomes

Why think about exposure.

The estimator helps you reflect on the potential operational impact of weak reviewability, missing evidence, undocumented approvals, poor exception handling, and weak reconstruction, conceptually, as a starting point for thinking, not a measurement. It is illustrative and not an audit.

It is an illustrative, educational, exploratory experience that prompts reflection across eight domains. It is a thinking aid, consistent with the methodology, and nothing more.

How this estimator thinks.

Reviewability questions tend to grow when decisions cannot be reconstructed, reviewed, or explained. The estimator helps you think about where that exposure may sit, conceptually, without quantifying it.

The eight exposure domains.

The prompts in each are illustrative and reflective.

  • Operational exposure

    Disruption and rework when decisions cannot be explained.

  • Decision accountability exposure

    Unclear ownership and authority for decisions.

  • Evidence exposure

    Missing, unlinked, or unretained evidence.

  • Approval exposure

    Unrecorded or unverifiable approvals.

  • Exception exposure

    Edge cases handled invisibly or inconsistently.

  • Reconstruction exposure

    Decisions that cannot be reconstructed from retained records.

  • Record exposure

    Incomplete, editable, or conflicting records.

  • Governance exposure

    Unclear ownership, policy, and review.

Illustrative

Reflective prompts across the eight domains.

Reflect on each, considering where exposure may sit. These are illustrative prompts. Nothing is computed.

Operational exposure

  1. If a key decision were questioned, could your team respond quickly?
  2. How much effort would it take to gather the basis for a past decision?
  3. Could a disruption occur if a decision could not be explained?
  4. How dependent is the workflow on specific individuals?
  5. Could repeated rework arise from unclear past decisions?
  6. How much time is spent reconstructing decisions after the fact?
  7. Could operational delays follow from missing records?
  8. How exposed is the workflow if a system changes?
  9. Could inconsistent handling create operational friction?
  10. How resilient is the workflow to staff turnover?

Decision accountability exposure

  1. Could you show who was accountable for a given decision?
  2. Could you explain why a decision was made?
  3. Is it clear who had authority for each decision?
  4. Could you demonstrate that the right person decided?
  5. Is accountability traceable across teams?
  6. Could you explain a decision if challenged later?
  7. Is it clear how a final decision was reached?
  8. Could accountability be reconstructed after staff changes?
  9. Is there a clear line from decision to owner?
  10. Could an outside reviewer follow the accountability trail?

Evidence exposure

  1. Could the evidence behind a decision be located later?
  2. Is the evidence linked to the decision it supports?
  3. Could you confirm which version of evidence was used?
  4. Is evidence retained as long as it may be needed?
  5. Is evidence stored in shared systems, not personal accounts?
  6. Could evidence be missing if a person left?
  7. Is evidence captured at the time of the decision?
  8. Could evidence be unreadable over time?
  9. Is evidence captured consistently across the workflow?
  10. Could a decision be harder to explain if evidence were lost?

Approval exposure

  1. Could you show who approved a given decision?
  2. Is the reason for approval recorded?
  3. Is approval tied to the specific decision and version?
  4. Could approvals be missing if made verbally?
  5. Is approval explicit rather than assumed?
  6. Could exposure arise from skipped approvals under pressure?
  7. Is it clear who has authority to approve what?
  8. Could an approval apply to the wrong version?
  9. Is approval recorded in the system of record?
  10. Could a decision be exposed if approval cannot be shown?

Exception exposure

  1. Are exceptions recorded when they happen?
  2. Is the reason for each exception captured?
  3. Is the resolution of each exception recorded?
  4. Could recurring exceptions be handled inconsistently?
  5. Are exceptions routed to someone with authority?
  6. Could exceptions be handled outside the system of record?
  7. Is it clear when an exception is resolved?
  8. Could you tell later that an exception occurred?
  9. Is the cause of an exception recorded?
  10. Could exposure arise from invisible exceptions?

Reconstruction exposure

  1. Could a past decision be reconstructed from retained records?
  2. Could it be reconstructed after the people involved left?
  3. Could it be reconstructed after the workflow changed?
  4. Can evidence and record be matched later?
  5. Can the sequence of steps be reestablished?
  6. Is the reasoning captured somewhere durable?
  7. Could reconstruction depend on a retired tool?
  8. Could reconstruction produce conflicting stories?
  9. Could a new employee follow the decision trail?
  10. Could a simple later question go unanswered?

Record exposure

  1. Does each decision produce a record?
  2. Could records be missing required fields?
  3. Could records lack a creator or timestamp?
  4. Are records linked to their evidence and approval?
  5. Could records be edited without a trail?
  6. Could conflicting versions of a record exist?
  7. Are records stored where they can be found?
  8. Could records capture outcomes but not reasoning?
  9. Could a record be unverifiable as unaltered?
  10. Could exposure arise from incomplete records?

Governance exposure

  1. Is there a clear owner for the workflow?
  2. Is it clear who is accountable for its decisions?
  3. Are roles and authorities documented?
  4. Is there a consistent policy the workflow follows?
  5. Is policy adherence visible in the records?
  6. Is the workflow reviewed periodically?
  7. Are changes to the workflow recorded?
  8. Is knowledge held in records, not just people?
  9. Is there a way to raise and resolve concerns?
  10. Could governance be explained to an outside reviewer?

How the estimator works.

You reflect on the illustrative prompts across the eight domains, consider where exposure may sit, and form an illustrative, qualitative sense of your exposure, with an honest explanation of what it means and an optional next step. The estimator produces no number, score, or prediction.

Illustrative exposure scenarios.

Each is a clearly labeled illustrative scenario using no real organization, statistic, or event.

Illustrative
  1. Evidence cannot be located, suggesting exposure if a decision is questioned.
  2. Approvals are unrecorded, suggesting exposure to an unanswerable accountability question.
  3. Exceptions are invisible, suggesting exposure to repeated, unmanaged edge cases.
  4. Records are editable, suggesting exposure to disputes about what was decided.
  5. Reconstruction depends on one person, suggesting exposure to staff turnover.
  6. Governance is informal, suggesting exposure to unclear ownership.
  7. Evidence is unlinked, suggesting exposure when proof is needed quickly.
  8. Reasoning is uncaptured, suggesting exposure to second-guessing later.
  9. A workflow changed, suggesting exposure for older decisions.
  10. Evidence sits in personal accounts, suggesting exposure to access loss.
  11. Approvals are verbal, suggesting exposure to disputed sign-off.
  12. Exceptions are closed without explanation, suggesting exposure to recurrence.
  13. Records lack timestamps, suggesting exposure to sequence disputes.
  14. A decision was reversed without rationale, suggesting exposure to confusion.
  15. Two systems disagree, suggesting exposure to conflicting accounts.
  16. Knowledge is held in people, suggesting exposure to departure risk.
  17. A simple later question has no answer, suggesting broad reconstruction exposure.
  18. Authority is unclear, suggesting exposure to accountability gaps.
  19. Evidence cannot be version-confirmed, suggesting exposure to the wrong basis.
  20. A trail is fragmented across teams, suggesting exposure to incomplete review.

Illustrative exposure patterns.

Recurring patterns of how exposure tends to arise. Conceptual, not accusatory.

  • Evidence not captured at the moment of decision.
  • Evidence not bound to the decision.
  • Approval made but not recorded.
  • Approver identity or rationale missing.
  • Exceptions handled outside the system of record.
  • Exceptions closed without explanation.
  • Records incomplete or missing fields.
  • Records editable without a trail.
  • Decisions not tied to a specific record.
  • Knowledge held in people, not records.
  • Trails fragmented across systems or teams.
  • Reconstruction that fails once time passes.
  • Reasoning never captured.
  • Authority unclear or undocumented.
  • Policy adherence not visible in records.
  • Versions of evidence or records unconfirmed.
  • Dependence on tools no longer in use.
  • Inconsistent handling of similar cases.
  • No periodic review of the workflow.
  • No clear owner for the workflow.

Illustrative exposure indicators.

Signs of potential exposure you might notice, framed without blame.

  • You cannot quickly find the basis for a past decision.
  • You cannot show who approved a decision.
  • You cannot explain why an exception was made.
  • You cannot confirm a record is unaltered.
  • You rely on one person to reconstruct decisions.
  • You cannot map old decisions after a change.
  • You store evidence in personal accounts.
  • You record outcomes but not reasoning.
  • You handle similar cases inconsistently.
  • You cannot tie a record to its evidence.
  • You cannot tie a record to its approval.
  • You discover exceptions only by accident.
  • You cannot confirm which version was used.
  • You lack a clear workflow owner.
  • You have undocumented roles and authorities.
  • You cannot show policy adherence in records.
  • You depend on a retired tool to reconstruct.
  • You find conflicting versions of records.
  • You cannot reestablish the sequence of steps.
  • You cannot answer a simple later question.

Illustrative mitigation concepts.

Concepts to consider, not promises or guaranteed fixes. A Workflow Audit and control pack address them in practice.

  • Capture evidence at the moment of the decision.
  • Bind evidence to the specific decision.
  • Record approvals explicitly.
  • Capture approver identity and rationale.
  • Record exceptions and their reasons.
  • Record how exceptions are resolved.
  • Require complete records with key fields.
  • Use controls or trails designed to make later record changes easier to detect.
  • Maintain a single authoritative record.
  • Capture reasoning, not just outcomes.
  • Design decision records to support later reconstruction.
  • Reduce dependence on specific individuals.
  • Assign a clear workflow owner.
  • Document roles and authorities.
  • Make policy adherence visible in records.
  • Confirm versions of evidence and records.
  • Avoid dependence on retired tools.
  • Handle similar cases consistently.
  • Review the workflow periodically.
  • Keep knowledge in records, not only in people.

Understanding your estimate.

The estimate is an illustrative, qualitative sense of where exposure may sit, not a number, score, prediction, or risk quantification. More areas of concern suggest more to examine; fewer suggest a more reconstructable workflow.

  • Qualitative, not quantitative.
  • Self-reported, not verified.
  • Only a Workflow Audit provides an assessed result.

Reflection bands.

Qualitative and illustrative, self-reported, not measured or predictive. There are no numbers or thresholds.

  • Limited areas to examine

    Few prompts raised concern. Your workflow may already have stronger reconstruction readiness.

  • Moderate areas to examine

    Several prompts raised concern across domains. There may be exposure worth examining.

  • Significant areas to examine

    Many prompts raised concern. An audit could examine where the exposure concentrates.

Why estimation is not an audit.

This estimator is a self-reported, illustrative reflection that computes nothing. A Workflow Audit is a formal, assessed engagement that examines the workflow, scores it against explicit anchors, and produces a premium report with an operational exposure planning estimate. The estimator is a starting point; the audit is the formal assessed engagement.

See the Workflow Audit

From estimation to audit.

If the estimator surfaced areas of concern you want examined, the next step is a Workflow Audit, which assesses one workflow formally and produces an assessed result, including an operational exposure estimate as a planning estimate. There is no obligation.

Start your audit See a sample report

What to consider next.

  • Which exposure areas matter most to you.
  • Whether your workflow is a fit for an audit.
  • Whether you want a formal assessment.

How this fits with the rest.

The estimator and the self assessment.

The Self Assessment Tool estimates reviewability maturity; the estimator helps you think about exposure. Both are illustrative, neither is an audit.

Try the self assessment

The estimator and the audit.

The estimator is a self-reported reflection that computes nothing. The audit is a formal, assessed engagement with a premium report.

See the Workflow Audit

The estimator and the gallery.

The Decision Failure Gallery illustrates how decisions become difficult to review; the estimator helps you think about the exposure those failures represent.

See the Decision Failure Gallery

Who this is for.

  • Operators and executives in decision-heavy workflows
  • Risk and compliance leaders
  • Reviewers in partially automated or AI-assisted workflows
  • Insurance teams, especially, reflecting on exposure before an audit

Who this is not for.

  • Those seeking a quantitative risk model
  • Those seeking compliance or legal validation
  • Those seeking an insurance calculation
  • Those expecting a guaranteed result

About these examples.

The scenarios, patterns, indicators, and mitigation concepts are illustrative. Organizations vary. The estimator is educational, exposure may arise in many different environments, the page does not imply wrongdoing, and an exposure concept is not evidence of misconduct. The estimator computes nothing and predicts nothing.

Estimator questions, answered.

What is this estimator?

An illustrative, educational, exploratory experience that helps you think about exposure concepts across eight domains. It is not a Workflow Audit.

Does it calculate anything?

No. It computes nothing and produces no number, score, or prediction.

Is this a risk calculator?

No. It is not a calculator, prediction engine, financial model, or risk quantification engine.

Is this a prediction?

No. It predicts nothing. It is a reflective, conceptual exercise.

Is this advice?

No. It is not legal, compliance, insurance, financial, or risk advice.

Is this a risk assessment?

No. It is not a risk assessment or a certification.

Does it guarantee anything?

No. It is illustrative and educational, and guarantees no result or outcome.

Is this a substitute for professional review?

No. It is not a substitute for professional review of any kind.

What does it help me think about?

Operational, decision accountability, evidence, approval, exception, reconstruction, record, and governance exposure, conceptually.

What are the eight domains?

Operational, Decision accountability, Evidence, Approval, Exception, Reconstruction, Record, and Governance exposure.

Why these domains?

Because they are the dimensions where weak reviewability can create exposure, consistent with our methodology.

Does it use my data to compute a score?

No. It computes nothing. Any data handling follows our Privacy Policy, and public materials use fictional data only.

Are the scenarios real?

No. Every scenario is clearly labeled illustrative, with no real organization, statistic, or event.

Are the patterns based on research?

No. They are illustrative patterns, with no fabricated research or data.

Are the indicators a checklist I am graded on?

No. They are illustrative indicators for reflection, not a graded checklist.

Are the mitigation concepts guaranteed fixes?

No. They are illustrative concepts to consider, not promises or guaranteed fixes.

What does my estimate mean?

It is an illustrative, qualitative sense of where exposure may sit, self-reported and not verified. Only a Workflow Audit provides an assessed result.

Are there numbers or thresholds?

No. The reflection bands are qualitative and illustrative, with no numbers, thresholds, or formula.

Does a significant band mean we are at risk?

It suggests areas to examine. It is not a verdict, a finding of fault, or a prediction.

Does this mean we did something wrong?

No. An exposure concept is not evidence of misconduct. Exposure can arise with good people and good intentions.

How is this different from the audit?

The estimator is a self-reported, illustrative reflection that computes nothing. The audit is a formal, assessed engagement with a premium report.

Does the audit give a number?

The audit produces an operational exposure estimate as a planning estimate, clearly framed as a planning estimate, not a prediction or a loss forecast.

Should I use this or the self assessment?

They are complementary. The self assessment estimates reviewability maturity, and the estimator helps you think about exposure. Both are illustrative.

Is this specific to insurance?

The domains apply broadly, and our first focus is insurance, where the audit is most developed.

Is there any obligation to request an audit?

No. The estimator is free and carries no obligation.

What should I do after the estimator?

If it surfaced areas you want examined, a Workflow Audit is the next step, with no obligation. You can also read the methodology, the thesis, or a sample report.

Can this replace an audit?

No. It is a starting point. Only a Workflow Audit provides an assessed result.

Why do you offer this for free?

To help visitors think clearly about exposure before deciding whether an audit is right for them.

Will my estimate be shared?

No. The estimator is for your own reflection.

Is this exhaustive?

No. The prompts, scenarios, patterns, indicators, and concepts are representative and illustrative, not a complete catalog.

Does this connect to your products?

It reflects the exposure dimensions the audit assesses and the scoring model explains, and it points to the audit without pressure.

Is this fear marketing?

No. The tone is calm and exploratory, with no fear, urgency, or scarcity.

Do you invent statistics or incidents?

No. We invent no statistics, research, incidents, regulations, benchmarks, or risk models.

Where can I learn the full method?

On the methodology and scoring model pages, with the deliverable shown on the sample report page.

How do I start a Workflow Audit?

Through the Request Audit page, which explains the process and carries no obligation at submission.

Is this estimator a prediction engine?

No. It is an illustrative reflection aid, not a prediction engine, and this specification implements no calculation or scoring logic.

Start your audit

A way to think, not a verdict.

The estimator is a way to think about exposure, not a verdict or a number. It computes and predicts nothing, and it points to the audit as the real assessment. If it surfaced areas you want examined, a Workflow Audit is the next step, with no obligation.

Start your audit Read the methodology