Delivery standards
What you can hold us to.
These are working commitments, not marketing. Each one describes something you can check in the material we hand over.
Checkable in every run note.
Every row accounted for
Rows in equals rows out plus rows held. The run note shows the arithmetic. If it does not balance, the run is not released.
Rules are explicit
Every transformation is listed in the specification. If we find ourselves wanting to make a judgement during a run, that is a sign the specification needs a new rule, and we raise it with you.
Held, not hidden
Rows that fail a check are returned in a separate sheet with the reason. They are not dropped, and they are not forced through.
Drift is noticed
Each recurring run is compared to the last. Sharp changes in volume, new columns or empty fields trigger a question before release.
Copies are minimised
Working copies are temporary. Archive retention is agreed per job. Deletion at the end of a retention period is recorded.
Changes are dated
Specification changes carry a version, a date and a reason, so any past output can be traced to the rules that produced it.
Replies within working hours
Monday to Friday, 09:00 to 18:00 UK time. Support replies describe what was checked and what was found.
Readable handover
If the arrangement ends, you receive the specification, mapping tables and remaining outputs in ordinary formats.
What a good outcome looks like
The honest measure of a processing job is how little anyone has to think about it. The file arrives, the output appears, the note says nothing unusual, and on the rare occasion something is odd, it is caught and explained before it reaches a report.
A secondary outcome is clarity. Writing a specification often surfaces decisions nobody had made explicitly. Even if the job later moves elsewhere, that document stays useful.