Why we’re building Batchread.

Batchread is built in Belgium for process, MS&T and QA teams who still work from paper batch records.

The problem

TODO(human) Why this problem, in your own words: the founder’s relevant experience, stated specifically and truthfully.

Three principles

  1. What it is unsure of comes to you. A value the software is not sure of goes to a person with the reason, and has no number in the export until a person has checked it. Nothing on screen says “passed”.
  2. Your records stay on your computer. Batchread is installed software whose own code makes no network connection. We never receive your records.
  3. A person checks, and the reading is kept. When you confirm or type a value, who and when is recorded beside the software’s reading, which is never overwritten.

Why local

Batch records hold a site’s process, its suppliers and its people’s names. Sending them to a cloud service means a supplier assessment, a data processing agreement and a question for every auditor. Software that runs where the records already are needs none of that.

Who writes the guides

Every guide is checked by a person against its sources before it goes live. How we write.

Contact

hello@batchread.com. Publisher details are in the legal notice.