Scattered calculations,
into a verified in-house Method.
We analyze your existing Excel, VBA, manuals, and validation records and turn them into an executable Method Pack that carries units, standards, tests, and a signed approval trail.
Decades of calculation know-how live only as an Excel file on one engineer's PC.
Where a formula came from and which standard it applied — the file alone won't tell you.
When the owner changes, the same calculation is verified from scratch — or used unverified.
With no record of who checked what and when, audit and handover rely on human memory.
From workbook to Method Pack
The core step is Differential Verify — the original workbook and the Method Pack run on the same inputs, and the results are proven to match within an approved tolerance (the Tolerance Manifest). This structurally blocks results from drifting during handover.
A Method Pack isn't a template — it's a version-pinned unit of execution
Method definition, dependencies, version
Input/output schemas carrying units
Deterministic calculation kernel — not an LLM
Approved tolerance thresholds
Golden, boundary, and property tests
Applied standards and clause mapping
Report format
Signed approval record
Three state axes are different things, so we manage them separately
Reproduces the behavior of a specific legacy workbook — does not claim current-code compliance
Only when standard name, edition, independent reviewer, review date, and evidence are all present
Before review — not for official use
The Method's release state — superseded belongs here, and is not an assurance basis.
The review state of a single calculation run — a maker creates it, a checker verifies it, an approver signs it.
What it does, and what it does not claim
- ✓Reproduce the results of a specific legacy workbook
- ✓State inputs, outputs, units, and sources explicitly
- ✓Differential verification against an approved tolerance
- ✓Version-control Method Packs and trace execution history
- ✓Maker–checker–approver workflow
- ✕General-purpose execution of any Excel/VBA
- ✕Declare current-code compliance without review
- ✕Present LLM-generated values as the official calculation
- ✕Learn across customers from one customer's calculations
- ✕Safety-related approval without independent review
Adoption path
Start with one or two representative calculations
We review file formats, VBA, validation records, and deployment constraints, then walk you through conversion feasibility and the readiness steps.
Request a conversion assessment