Skip to content
Lorendix

Solutions · Data and reporting

Catch bad data before your board does

A library of checks that data is up to date, complete, correctly structured, free of duplicates and valid, improved across several organisations. We build them into your pipelines, so a failed load is stopped before it reaches a meeting.

Use cases

Is this you?

Everyone agrees that data should be checked, but few organisations have the checks, because writing them from scratch never becomes a priority.

A wrong figure reached leadership

A report went out with a figure that was clearly wrong, and nobody noticed until a senior reader questioned it.

Loads that fail silently

A source delivered only half its usual data, and every report that depended on it quietly changed.

The right person is told last

When something breaks, the person who can fix it is the last to hear about it.

Standards that are not enforced

Data standards exist on paper, but nothing in the pipelines actually applies them.

What it delivers

Checks grouped by the problem they catch

This makes it easy to put the right checks in the right places.

  • Timeliness: the data arrived when expected
  • Volume: the number of rows is within the normal range
  • Structure: unchanged, or changed deliberately
  • Uniqueness: no duplicates
  • Validity: values are within allowed ranges and formats
  • Failures sent to named owners

Check library

  • Freshness

    Arrived on time, or an alert is raised

  • Volume

    Within the expected range for the day

  • Structure

    No unannounced structural changes

  • Uniqueness

    No duplicate identifiers

  • Validity

    Ranges, formats and allowed values

  • Routing

    Failures sent to the owner, with examples

What we do around it

Placed carefully, and set up to take action

Checks are easy to add and easy to ignore. Our service is placing them well and making sure they take action.

Placement
We put checks where an error would otherwise spread furthest, rather than scattering them everywhere.
Thresholds
We tune the checks against your normal patterns, so alerts are rare enough to be taken seriously.
Enforcement
Critical checks stop dependent reports from refreshing, rather than only issuing a warning.
Ownership
Each check has a named owner, who is told when it fails.
Review
We review patterns of failures with you, and fix the underlying causes at the source.

Pricing and demonstrations

Tell us which report most needs to be right

We will show you the checks we would put in front of it first.

Priced according to your size, number of users and the support you need. There are no tiers.

All solutions