Data ServicesProcessing & related hosting

Intake

How a job gets onto the bench.

The order matters. Words first, layout second, rules third, real data last.

No data is requested in the first conversation.

The description

A few paragraphs in your own words. What arrives, from where, how often. What you need back and who uses it. What currently goes wrong. We reply with questions rather than a quote, because the questions are where the job takes shape.

The layout

Column names and a handful of dummy rows that show the shape without real content. Our header inspector tool can help you check a header line before you send it. If the layout changes between sources, we ask for each version.

The specification

A document you can read in ten minutes. For each field: what it should contain, how it is checked, what transformation applies and what happens if a check fails. For the job: inputs, outputs, schedule, retention, who receives what. You approve it, or we change it until you can.

The arrangements

Transfer route, access, retention and the contractual terms that govern processing on your behalf. Only when these are in place do we ask for a real file.

The trial

One real run, compared line by line with your existing result where one exists. Every difference is classified: a bug in our rules, a bug in the old process, or a decision that needs making. Trials often surface long-standing quirks; that is a useful outcome in itself.

The routine

Runs to the agreed schedule with a note each time. A short review after the first few cycles checks whether thresholds and held-row rules are pitched correctly.

Ready for step A?

The job sheet builder on the tools page will help you write it.