The OpLogica methodology.
The Decision Accountability Methodology is a defined, repeatable system for making important decisions reviewable, evidence-bound, human-approved, and reconstructable. It is a method, not a service offering.
Why traditional workflows struggle.
Traditional workflows optimize for getting the work done, not for keeping each decision reviewable. As automation and AI increase volume and speed, these weaknesses compound.
- Evidence
- Scattered across systems and inboxes, not bound to the decision.
- Approvals
- Informal, assumed, or made without a recorded approver.
- Exceptions
- Handled off the record, so edge cases leave no trail.
- Records
- Thin, so the full story is missing when a decision is questioned.
The gap the methodology addresses.
The reviewability gap is the space between knowing what happened and being able to explain how and why, in a way that can be reviewed. The methodology is built specifically to address it.
- Who approved it?
- On what evidence?
- With what reasoning?
- Can it be reconstructed today?
A defined, repeatable method.
The same method applies every time: a set of pillars, a step-by-step process, four phases, and three layers that run beneath them. That is what makes it a framework rather than a service.
-
Pillars
Six pillars define what an accountable decision requires.
-
Process
A repeatable step-by-step sequence applies the pillars.
-
Four phases
Audit, control pack, implementation, handover and operation.
-
Three layers
Evidence integrity, decision accountability, decision reconstruction.
Six pillars of the methodology.
These are the same six pillars used across the site, presented here as the methodological foundation.
- Reviewability Can the decision be reviewed after the fact?
- Evidence Integrity Is evidence present, retained, and bound to the decision?
- Approval Traceability Do approvals carry identity and rationale?
- Exception Visibility Are missing or invalid inputs routed and recorded?
- Decision Reconstruction Can the decision be reconstructed from retained records?
- Operational Accountability Is ownership clear across the workflow?
How the method works, step by step.
The method is a repeatable process, applied through the four phases that follow.
- Identify decision points Find the decisions that must be reviewable.
- Require and bind evidence Capture evidence and connect it to the decision.
- Record approvals Capture the approver, identity, and rationale.
- Route exceptions Send missing or invalid inputs to a person, recorded.
- Write tamper-evident records Support detection of later changes.
- Check reconstruction readiness Check whether the decision can be reconstructed from retained records.
Phase one: measure the gap.
The methodology applies first as measurement. The Workflow Audit scores one workflow across six categories with explicit 0, 1, and 2 anchors, maps decision accountability, and estimates operational exposure.
- Six scored categories, each with explicit 0, 1, and 2 anchors
- A decision accountability map
- An operational exposure estimate
- A premium reviewability report
- A recommended control pack
The exposure estimate is an operational planning estimate, not a loss prediction. The score summarizes reviewability posture, not compliance.
Phase two: define the controls.
The methodology then defines the control architecture that addresses the findings, configured for the workflow. For insurance, this is the Insurance Control Pack.
- Approval patterns
- Evidence requirements
- Exception handling
- Reviewability and reconstruction checkpoints
- Accountability mapping
Phase three: apply the controls.
The methodology then applies the agreed controls inside the workflow through Control Pack Implementation. The output is a workflow that produces reviewable, reconstructable records.
- Scope confirmation
- Control mapping
- Configuration
- Validation
- Handover
Phase four: operate with accountability.
The final phase is the workflow running with the controls in place. The client owns and operates the workflow, with no required subscription or platform lock-in.
- Decisions are recorded
- Evidence is bound
- Approvals are traceable
- Exceptions are routed
- Records support reconstruction readiness
Verify supports record integrity.
OpLogica Verify supports tamper-evident and reconstructable decision records across all phases. It is supporting infrastructure, not the product and not the methodology itself. A free Community Edition is public and inspectable.
Three layers run beneath the method.
- Evidence integrity Evidence is present, retained, and bound to the decision, with changes detectable. Evidence captured at the moment is stronger than evidence reconstructed later.
- Decision accountability Each decision ties to a recorded approver, a rationale, and clear ownership, so accountability is explicit at the level of the decision, not just the system.
- Decision reconstruction A decision can be reconstructed from retained records, after time has passed and people have changed, checked at a reconstruction checkpoint.
The evidence integrity layer.
- Present and required
- Retained and bound to the decision
- Changes detectable
The decision accountability layer.
- Recorded approver
- Recorded rationale
- Clear ownership
The decision reconstruction layer.
- Complete and bound records
- Tamper-evident records
- Reconstruction readiness check
The first application: insurance.
The methodology is general. Insurance is the first application because the problem is sharpest there: certificate, claims, and underwriting decisions carry real exposure and are made at volume.
- A general method.
- Sharpest first in insurance.
- Honest about scope: one bounded workflow elsewhere when the fit is strong, with no coverage promised that has not been built.
The principles behind the method.
- Measure before you change anything.
- Use explicit anchors, not subjective judgment.
- Capture evidence at the moment of the decision.
- Bind evidence to the decision it supports.
- Record the approver, the identity, and the reasoning.
- Make exceptions visible and routed, never silent.
- Write records that later changes cannot hide.
- Check that a decision can be reconstructed from retained records.
- Keep the method the same every time, so results are comparable.
- State the limits of the method honestly.
Questions about the methodology.
How does OpLogica work?
OpLogica applies one defined method, the Decision Accountability Methodology, across four phases: audit, control pack, implementation, and handover and operation, with three layers beneath them: evidence integrity, decision accountability, and decision reconstruction.
Is this a methodology or a service?
It is a methodology. The same defined, repeatable method runs every engagement, which is what makes OpLogica infrastructure rather than consulting.
What are the pillars?
Reviewability, evidence integrity, approval traceability, exception visibility, decision reconstruction, and operational accountability.
What are the four phases?
Audit measures the gap, the control pack defines the controls, implementation applies them, and handover and operation runs the workflow with accountability.
What are the three layers?
Evidence integrity, decision accountability, and decision reconstruction, which run beneath all four phases.
How does the audit phase work?
It scores one workflow across six categories with explicit 0, 1, and 2 anchors, maps decision accountability, and estimates operational exposure.
What is an explicit anchor?
A clear definition of what a 0, a 1, and a 2 mean for each scored item, so scoring is transparent and not subjective.
How does the control pack phase work?
It defines a control architecture, such as approval patterns, evidence requirements, exception handling, and checkpoints, configured for the workflow.
How does the implementation phase work?
It applies the controls inside the live workflow through scope confirmation, control mapping, configuration, validation, and handover.
What is handover and operation?
The workflow running with the controls in place, producing reviewable, reconstructable records, owned and operated by the client.
Is this compliance methodology?
No. It supports audit readiness and decision accountability. It does not certify compliance or provide regulatory approval.
Is this internal audit methodology?
No. It complements internal audit. It is not a replacement for internal audit or counsel.
Is this project management methodology?
No. It is a decision accountability method, not a project management framework.
How is the evidence integrity layer different from logging?
Logging records that something happened. The evidence integrity layer requires evidence to be present, retained, and bound to the decision, with changes detectable.
What makes a decision reconstructable?
Complete and bound records, tamper-evident records, and a reconstruction checkpoint that checks whether the decision can be reconstructed from retained records.
How does Verify relate to the methodology?
Verify is the integrity layer that supports tamper-evident and reconstructable decision records. It is supporting infrastructure, not the product or the methodology itself.
Can I verify any of this myself?
Yes. You can read the methodology and scoring model, explore a complete sample report on fictional data, and inspect the public Verify Community Edition.
Does the methodology guarantee outcomes?
No. It is designed to support reviewability, evidence readiness, and reconstruction. It does not guarantee outcomes.
Is the methodology specific to insurance?
The method is general. Insurance is the first application because the problem is sharpest there. The method can apply to one bounded workflow elsewhere when the fit is strong.
Is the scoring subjective?
The scoring uses explicit anchors to reduce subjectivity, and the method is applied the same way every time so results are comparable.
How long does the method take to apply?
The audit is typically a few business days after intake, and implementation is typically a few weeks for one workflow, each confirmed at scoping.
Where do I start?
Most engagements start with a Workflow Audit, which is the entry point to the control pack and implementation.
A method, not a collection of services.
The same defined method runs from measurement to handover and operation. That is what makes OpLogica infrastructure rather than consulting.