Every value traced to its page, every number computed by code, every decision signed by a named person.
Built for verification firms and energy auditors working under CCTS and ADEETIE. Never sold to the audited entity.
18,247 t
Read from page 1: “Quantity dispatched 18,247 MT”
One path, whatever the scheme. The methodology pack decides what each step requires.
Rate the risk factors, set the sampling policy and get the plan approved. Every save is a new version.
Verification plan, version 2
Approved by the lead verifier. It replaces version 1, which is kept.
PDFs, scans, spreadsheets, SCADA exports and evidence packs, plus site observations, photos and meter readings.
Evidence received
Each file is hashed on arrival, and its type is read from the bytes.
Values arrive with their source. Declared figures are compared with the evidence and a person decides.
Declared against evidence
The gap is shown and measured against a tolerance. It goes to a person, never to the calculation.
A versioned, hashed engine computes from accepted facts only, using the method the scheme prescribes.
Run 7, computed from accepted facts
Code does the arithmetic. A model proposes values, and never produces a number.
Findings become issues. The entity answers through a link, and the verifier checks the response.
Finding MB001
The entity answered through a single-use link, with no account and no view of anything else.
An independent technical review, two named sign-offs and a hashed submission package.
Sign-off
Two named people sign. Neither can be the one who observed or drafted.
Verification plan, version 2
Approved by the lead verifier. It replaces version 1, which is kept.
Synthetic data. One engagement, from the plan to the signed package.
Not a document viewer with a model bolted on. Each part exists because a verifier has to answer for it.
Rate scope, data and control risk. The approved plan sets the sampling rate, and a changed plan is a new version, never an edit.
| Risk factor | Rating | Why |
|---|---|---|
| Scope | Medium | Two kilns and a captive plant |
| Data | High | Coal stock in a manual register |
| Control | Low | Production confirmed in SAP |
Version 3 replaces version 2 after a change in data risk. Version 2 is kept.
Synthetic data.
Every result can be traced back to a source and a person. These are the rules the product will not bend.
The calculation engine is versioned and hashed. Language models never perform arithmetic.
A page, a cell, a time range or a site observation. Without one of those, the value is refused.
Material values always need a named reviewer. Nothing approves them automatically.
Reconciliation rules raise findings for a verifier to judge. Drafts cannot invent numbers.
The person who observed does not accept it, and a drafter does not review. Two people sign.
Every run records the engine version, pack version and a hash of its inputs, chained to the last.
Sector methodology lives in packs, as data, and the engine never branches on sector. A scheme without checked content stays marked as such.
Carbon Credit Trading Scheme
9 of 9 sector packs runnable
BEE scheme for energy efficiency in MSMEs
14 of 14 sector packs runnable
Embedded-emissions verification for installations. The flow and data model are drawn; the calculation rules, default values and verification requirements wait for a primary source and a practitioner.
Emission intensity per kilogram of hydrogen against a threshold. The boundary, renewable-matching rules and certificate format are still to be confirmed before anything is built on them.
Competing firms share this product, so isolation and an unalterable record are designed in, not added later. Controls we have not built yet are tracked, not hidden.
Row-level security on every tenant table. Signed-in users can read their firm's rows and write nothing directly.
Audit events, facts, runs and sign-offs cannot be edited or deleted, even by the server.
Files are hashed on arrival and stored privately under that hash. Their type is read from the bytes.
Four roles, one capability map, checked by the menu, the page and the route.
Verification firms and energy auditors working on India's BEE schemes. It is built for the verifier and is never sold to the audited entity.
Who is VerifyStack for?
Verification firms and energy auditors working on India's BEE schemes. It is built for the verifier and is never sold to the audited entity.
Tell us which scheme you work on. We will walk through one engagement from the plan to the signed package, with your questions in mind.
Prefer to start straight away? Create your firm's account