3 ms·
I used to be the IT Director for a document scanning business in the UK. Scanning paper HR records was the single most painful job we had to do. The entire fil
by marcus_holmes 11y ago
I used to be the IT Director for a document scanning business in the UK.
Scanning paper HR records was the single most painful job we had to do. The entire file became a complete legal nightmare purely because it stopped being paper and became covered by Data Protection.
Usually the HR department had to go through every single employee file and shred any documents that might be grounds for legal action before they got scanned.
The process before scanning was:
- employee is annoyed
- employee requests their HR file
- HR sanitise file and sends it to employee
after scanning, every single page was indexed. So they couldn't react to a request by destroying pages (because there'd be holes in the index). So they had to sanitise every single file before scanning.
I understand the point of Data Protection law, but in this case it was really counter-productive. Evidence was destroyed wholesale.
- pjc50 11y agoThat sounds like "working as intended" - after all, if instead of just requesting their file the employee had initiated legal action against you, it would have been illegal to destroy those documents. And it also raises the question of which part of your HR process is generating incriminating documents in the first place?
- marcus_holmes 11y agonot so much "incriminating" as "not required to be kept and could possibly be misconstrued". Not our HR process, our customer's. What was actually destroyed depended on their interpretation of the law. One common one was the Data Protection requirement to not keep inaccurate data meant that all but the latest employee change of address forms had to be destroyed. Easy to implement post-scanning, pain in the arse to do pre-scanning.