Who this is for
Data lead whose checks were set up once and now either fire too often or miss new kinds of bad load.
People have stopped reading the alerts, and a new table was never given any checks.
The result
Every month you receive a review of the alerts your checks raised, with noisy checks retuned and missing checks proposed as a pull request. Each change is shown to fire on a planted failure and stay quiet on recent good history. You review and merge.
What is included
- One data project with up to 40 checks already in place
- A monthly review of fired alerts: true, false and ignored
- Retuning of noisy checks and up to three new checks a month
- A pull request with each change shown on a planted failure and recent history
- A short summary of what changed and why
You receive
- The monthly review
- The pull request of changes
- The planted-failure and history evidence for each change
- A short summary
What is not included
- Running or hosting the checks
- Fixing the data or the loading jobs
- Seeing row values: only the schema and the counts, null shares and number or date ranges you send are used
- Out-of-hours cover or any guaranteed response time
- Merging anything
What we need from you first
- Which tool the checks run in and how many there are
- Roughly how many alerts fire a month
- No real records, personal data or credentials in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- Each month's review accounts for every fired alert as true, false or ignored.
- Every changed or new check fires on its planted failure and stays within the false-alert cap on recent history. We plant the failures, so this is a smoke test that a check can fire, not a measure of how many of your real bad loads it would catch.
- The input log shows only the schema, counts, null shares and number or date ranges; no text value and no list of most common values went to a model.
You read each report and tell us whether the marks and rules still suit you. A month counts as delivered when you have received the report.
When we would stop or decline
- No alert history exists
- Nobody labels the alerts
- You want row-level data sent to a model
- More than 40 checks, unless you ask for a quoted larger scope
Questions
Do you run the checks?
No. You run them in your own tool and send the month's alert history.
Can you turn a check off?
Only with your approval, and each change is shown first.
Do I need the one-off job first?
Not if checks already exist. We start from the alert history.
Price and terms
£99/month · untested offer price. Billing is monthly under the written terms we agree with you. Nothing is charged until you have agreed them.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.