For analysts and reporting teams

Know what changed before the numbers go out.

Monthly and regulatory reports are only as right as the file behind them. Datainspec tells you what changed since the version you trusted, in plain words, with the rows.

Sound familiar?

The report looks off. Now what?

  • The numbers jumped, and the morning goes on finding out why.

  • A column vanished, a unit changed or a category appeared overnight, and nobody said so.

  • Nobody wants to be the one who sent out the wrong figure.

What you get

Answers, not alerts.

01

What changed, in plain words

Point it at the file you trust and the new one. Every column is checked, and each finding says what changed, how much, and in which rows.

  • “1,703 Lyon prices are 100× their September price”
  • The rows behind it, ready to export
Try it in the demo
The results screen for October's orders: critical, exit code 2, 7 findings, starting with the missing payment_method column.
02

Explain expected changes once

A new product line is not a problem. Mark it as expected and say why: your decision comes back, with your name, when the same finding returns next month.

See triage
The triage screen: the findings, and the choices Noise, Expected change, Real problem and Snoozed.
03

Your own rules, in a form

Quantity ≥ 1, a list of allowed values, a range: written in a form and checked against the approved data before you save.

See the rules screen
The rules tab: rules suggested from the approved data, a quantity minimum of 1, and no violations in the approved baseline.

How it fits your month

Before the numbers go anywhere.

  1. 1The file arrivesFrom a store, a supplier, another team.
  2. 2Open it in DatainspecWhat changed since last month, column by column.
  3. 3Decide what it meansExpected change or real problem, with a reason.
  4. 4Publish, or holdSend the report, or ask for a re-export, with the evidence.

The difference

From a jump in the dashboard to the cause in the file.

Without it
With Datainspec
Spotting the jump in the dashboard
Seeing the change in the delivery, before the dashboard
Comparing two exports by hand
Every column checked against the version you trusted
Explaining the same expected change every month
Mark it once; your reason comes back with it
Emailing extracts to ask what happened
A share-safe report: counts and statistics, no values

Also in the app

The small things that save the morning.

A tap on the shoulder

A tray icon shows each gate's state, and Windows notifies you when a gate blocks or a scan finishes.

Each column's history

See how a column moves month after month, across every approved version.

Share without sharing data

Send a report outside the team with counts and statistics only, no values from the data.

Questions

What analysts ask.

Do I need to write code?

No. It is a Windows app: pick the version you trust and the new delivery, and it works out every column itself.

Can it read Excel files?

Not directly yet. Save the sheet as CSV; it handles the separators, encodings, decimal commas and date orders Excel exports produce.

Will it tell me when something is wrong?

The app's tray icon shows each gate's state, and Windows notifies you when a gate blocks or a scan finishes.

What if the change is expected?

Mark it as an expected change and write why. The decision is recorded with your name and shown again when the same finding comes back.

Check next month's file before it goes out.

Bring one recurring report's data to a pilot; we review what it caught together.