I'm Brendan Hyland. I help regulated facilities transform their software, spreadsheets, workflows and documents from time-consuming, deviation-invoking, regulatory burdens, to the competitive advantage they were meant to be. Join me every week as we take a few minutes to explore, design, test and improve the critical systems we use in our facilities.
What are some of the hazards of using a data processing spreadsheet?
Let’s say you want to develop a spreadsheet that’s used over and over again to process batches of data.
What are the some of the hazards to data integrity associated with using such a spreadsheet?
- It might have bugs in it at the time of release.
- Its functionality might change unintentionally during use.
- Someone could use it incorrectly.
- Someone could enter incorrect data.
- Someone could accidentally change data that’s already been entered.
- The software or computer could crash during data entry or processing.
- The spreadsheet full of data could get lost or corrupted.
- The spreadsheet could give different results on different computers with different versions of Excel.
- You could end up with multiple versions of the spreadsheet without knowing which is the ‘correct’ one.
… and so on.
That’s a lot of hazards, and we haven’t yet gone into any specifics about the functionality of the spreadsheet, or even the kind of data it will be processing! Which of these should we be concerned about?
Until next time, thanks for reading!
– Brendan
p.s. Enjoy this message? Read more at the Hyland Quality Systems website.
The Daily HaiQu
I'm Brendan Hyland. I help regulated facilities transform their software, spreadsheets, workflows and documents from time-consuming, deviation-invoking, regulatory burdens, to the competitive advantage they were meant to be. Join me every week as we take a few minutes to explore, design, test and improve the critical systems we use in our facilities.
Last time we left off with a cliff-hanger of a question: How do you prove you're you when signing a document? There are several ways I've seen that the 3rd party providers prove that it's you who's signed the document: You clicked a link from an email. You paid for the service with a credit card. You provided some government issued photo ID. Someone, such as a notorized public or your HR department, has verified it's you in person. Obviously these are very different levels of assurance. Then...
There are several levels of 'signatures' that you can apply to an electronic document. The first and most basic is just an image of your written signature. One common option for this is to print the document, sign and scan it back in again. A more convenient version is to have an image of your signature saved that you can paste into documents. This is what many free versions of pdf software and word processors offer as a basic document signing option - a 'stamp' of your saved signature image....
Ever since COVID, document and signing workflows have been incorporated into everything. Dropbox has it. Microsoft Teams has it. Google Workspaces has it. If you need e-signatures, you probably have access to Docusign, Adobe, Hellosign, and so on. But what exactly are we talking about when we say "document and signing workflow"? Let's step back. Most document workflows are about moving some work through review, commentary, revision and approval. The old way to do this was to send a document...