Make the next trial reviewable.
Keep the rules. Recheck the relationships. Hand your client the evidence.
01 Project & rules
Company, contact and product master data only. No payroll, general ledger or live-system connection.
Saving downloads a versioned JSON configuration. Files and session data are not stored in the browser. Save before refreshing.
Relationships between files
Child fields follow the parent key order. Relationship checks inherit the parent's explicit key rules. Parent IDs never become numbers.
02 Source & trial files
Keep the source snapshot fixed. Replace the trial exports after a correction. Changing source content starts a new comparison baseline.
UTF-8 CSV only · comma, tab or semicolon · 10 MiB per file · 500,000 cells across all loaded source and trial files · 500 columns per file.
03 Keep a baseline
REPEATABLE CHECKSA rule, scope, revision or source hash change prevents a “resolved” claim. Checksums identify content; they are not digital signatures.
04 Client evidence
A clear record of what changed.
Run the checks to see blockers, coverage and the evidence your client can review.
A reviewable client handoff
Download a local ZIP containing a readable HTML report, issues.csv, manifest.json, project config and run snapshot. The report includes original finding values, file hashes, rules, time zone and unverified scope. Review before sharing.
No report is sent automatically. CSV formula prefixes are a mitigation, not a guarantee. The HTML report can be printed to PDF by your browser.
Scope, privacy and what “resolved” means
Your files stay in this session
Processing and hashing run in a cancellable browser worker. No uploads, storage, tracking, paid API or source-file edits. Clear session or refresh drops the app's data references. The host still receives normal page requests; private previews may require hosting sign-in. Extensions, devices and exported evidence are outside this app's control.
Rules are opt-in
Exact strings are the default. Text case/space handling, explicit calendar-date formats and non-financial measurement tolerances only apply when selected. IDs and keys cannot use numeric or date rules. Unsupported values become blockers.
Evidence is narrower than approval
Unmapped and excluded fields are unverified. Duplicate-key groups remain isolated; references to duplicate parents are ambiguous. A finding is resolved only when the same check can be re-run successfully. Missing identity or coverage is shown as not rechecked. “Unchanged” means the same finding remains open; its evidence can differ.
Different project rules, versions, scope or source hashes make runs incomparable. No report authorizes production cutover or replaces a client's business review. At most 20,000 findings are supported; exceeding this stops the run without a partial report.